Spreadsheet::ParseXLSX up to 0.29 on Perl XML::Twig no_xxe xml external entity reference

Summaryinfo

A vulnerability has been found in Spreadsheet::ParseXLSX up to 0.29 on Perl and classified as problematic. This affects the function XML::Twig. The manipulation of the argument no_xxe leads to xml external entity reference. This vulnerability is traded as CVE-2024-23525. It is possible to initiate the attack remotely. There is no exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Spreadsheet::ParseXLSX up to 0.29 on Perl and classified as critical. This issue affects the function XML::Twig. The manipulation of the argument no_xxe with an unknown input leads to a xml external entity reference vulnerability. Using CWE to declare the problem leads to CWE-611. The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

The Spreadsheet::ParseXLSX package before 0.30 for Perl allows XXE attacks because it neglects to use the no_xxe option of XML::Twig.

The weakness was shared 01/18/2024 as 10. The advisory is shared at github.com. The identification of this vulnerability is CVE-2024-23525 since 01/17/2024. Technical details are known, but no exploit is available.

Upgrading to version 0.30 eliminates this vulnerability. The upgrade is hosted for download at metacpan.org.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Spreadsheet::ParseXLSX

Version

• 0.1
• 0.2
• 0.3
• 0.4
• 0.5
• 0.6
• 0.7
• 0.8
• 0.9
• 0.10
• 0.11
• 0.12
• 0.13
• 0.14
• 0.15
• 0.16
• 0.17
• 0.18
• 0.19
• 0.20
• 0.21
• 0.22
• 0.23
• 0.24
• 0.25
• 0.26
• 0.27
• 0.28
• 0.29

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion