First published: Tue Oct 08 2019(Updated: )
An XPath entity injection vulnerability exists in Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3 or 2.3.2-p1. An attacker can craft a GET request to page cache block rendering module that gets passed to XML data processing engine without validation. The crafted key/value GET request data allows an attacker to limited access to underlying XML data.
Credit: psirt@adobe.com
Affected Software | Affected Version | How to fix |
---|---|---|
composer/magento/product-community-edition | >=2.2<2.2.10>=2.3<2.3.2-p2 | |
composer/magento/community-edition | >=2.3.0<2.3.2-p2 | 2.3.2-p2 |
composer/magento/community-edition | >=2.2.0<2.2.10 | 2.2.10 |
CentOS Libgcc | >=2.2.0<2.2.10 | |
CentOS Libgcc | >=2.2.0<2.2.10 | |
CentOS Libgcc | >=2.3.0<2.3.2 | |
CentOS Libgcc | >=2.3.0<2.3.2 | |
CentOS Libgcc | =2.3.2 | |
CentOS Libgcc | =2.3.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-8158 is rated as a medium severity vulnerability due to the potential for XPath entity injection.
To fix CVE-2019-8158, upgrade Magento to version 2.2.10 or 2.3.3 and higher.
CVE-2019-8158 affects Magento versions 2.2.0 to 2.2.9 and 2.3.0 to 2.3.2.
You can check your Magento version against the affected ranges to determine if your site is vulnerable to CVE-2019-8158.
CVE-2019-8158 allows attackers to exploit unvalidated input leading to potential XPath entity injection attacks.