First published: Tue Oct 08 2019(Updated: )
A security bypass vulnerability exists in Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3 or 2.3.2-p1. A user with privileges to generate sitemaps can bypass configuration that restricts directory access. The bypass allows overwrite of a subset of configuration files which can lead to denial of service.
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<2.3.2-p2 | 2.3.2-p2 |
composer/magento/community-edition | >=2.2<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-8133 has a severity rating that indicates a security bypass vulnerability in Magento, which can lead to configuration file overwrites.
To fix CVE-2019-8133, upgrade to Magento version 2.2.10 or 2.3.3 or later.
CVE-2019-8133 affects Magento 2.2 versions prior to 2.2.10 and Magento 2.3 versions prior to 2.3.3 or 2.3.2-p1.
The impact of CVE-2019-8133 allows users to bypass restrictions on directory access, potentially leading to denial of service.
Using unsupported versions of Magento with CVE-2019-8133 is risky as it may expose your site to known vulnerabilities.