CVE-2019-12331: XXE in PHPSpreadsheet due to incomplete fix for previous encoding issue
(updated )
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.
References
- github.com/FriendsOfPHP/security-advisories/blob/master/phpoffice/phpspreadsheet/CVE-2019-12331.yaml
- github.com/PHPOffice/PhpSpreadsheet
- github.com/PHPOffice/PhpSpreadsheet/blob/master/CHANGELOG.md
- github.com/PHPOffice/PhpSpreadsheet/commit/0e6238c69e863b58aeece61e48ea032696c6dccd
- github.com/PHPOffice/PhpSpreadsheet/pull/1041
- github.com/PHPOffice/PhpSpreadsheet/releases/tag/1.8.0
- github.com/advisories/GHSA-vvwv-h69m-wg6f
- herolab.usd.de/security-advisories/usd-2019-0046
- nvd.nist.gov/vuln/detail/CVE-2019-12331
Code Behaviors & Features
Detect and mitigate CVE-2019-12331 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →