First published: Tue Jun 25 2019(Updated: )
A denial-of-service vulnerability exists in Magento 2.1 prior to 2.1.18, Magento 2.2 prior to 2.2.9, Magento 2.3 prior to 2.3.2. Under certain conditions, an unauthenticated attacker could force the Magento store's full page cache to serve a 404 page to customers.
Credit: psirt@adobe.com
Affected Software | Affected Version | How to fix |
---|---|---|
composer/magento/product-community-edition | >=2.1<2.1.18>=2.2<2.2.9>=2.3<2.3.2 | |
composer/magento/community-edition | >=2.3.0<2.3.2 | 2.3.2 |
composer/magento/community-edition | >=2.2.0<2.2.9 | 2.2.9 |
composer/magento/community-edition | >=2.1.0<2.1.18 | 2.1.18 |
CentOS Libgcc | >=2.1.0<2.1.18 | |
CentOS Libgcc | >=2.2.0<2.2.9 | |
CentOS Libgcc | >=2.3.0<2.3.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-7915 has a severity rating that may classify it as a denial-of-service vulnerability affecting affected Magento versions.
To resolve CVE-2019-7915, upgrade Magento to version 2.1.18, 2.2.9, or 2.3.2 or later.
Magento versions 2.1 prior to 2.1.18, 2.2 prior to 2.2.9, and 2.3 prior to 2.3.2 are vulnerable to CVE-2019-7915.
CVE-2019-7915 can be exploited by unauthenticated attackers, allowing them to affect the Magento store's cache.
An indication of CVE-2019-7915 exploitation is the Magento store returning a 404 error page to customers.