CVE-2019-12331 XXE in PHPSpreadsheet due to incomplete fix for previous encoding issue

High 8.8 Published Updated

An attacker can exploit an XXE vulnerability in PhpSpreadsheet to read sensitive files or execute code by bypassing entity checks via double-encoded payloads.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2019-12331?

CVE-2019-12331 is a high-severity vulnerability in n/a, published on 7 Nov 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

Official description

PHPOffice PhpSpreadsheet before 1.8.0 has an XXE issue. The XmlScanner decodes the sheet1.xml from an .xlsx to utf-8 if something else than UTF-8 is declared in the header. This was a security measurement to prevent CVE-2018-19277 but the fix is not sufficient. By double-encoding the the xml payload to utf-7 it is possible to bypass the check for the string ‚<!ENTITY‘ and thus allowing for an xml external entity processing (XXE) attack.

Weakness: CWE-611

Which versions are affected by CVE-2019-12331?

4 open source packages ship an affected version, including phpoffice/phpexcel and phpoffice/phpspreadsheet. It affects 1 product.

PackageAffectedFixed in
phpoffice/phpexcel PackagistAll versions to 1.8.2None
phpoffice/phpexcel PackagistAll versions to 1.8.2None
phpoffice/phpspreadsheet PackagistAll versions1.8.0
phpoffice/phpspreadsheet PackagistAll versions1.8.0

Products include Phpoffice Phpspreadsheet.

How do I fix CVE-2019-12331?

Upgrade to a fixed version.

Is CVE-2019-12331 being exploited?

There is no known exploitation of CVE-2019-12331 in the wild and no public exploit code.

Sources

Also known as GHSA-vvwv-h69m-wg6f.

Is CVE-2019-12331 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free