First published: Tue Oct 08 2019(Updated: )
An insecure component vulnerability exists in Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3 or 2.3.2-p1. Magento 2 codebase leveraged outdated versions of HTTP specification abstraction implemented in symphony component.
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-p1 | 2.3.2-p1 |
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-8136 is considered a medium severity vulnerability that affects specific versions of Magento.
To remediate CVE-2019-8136, upgrade Magento to version 2.2.10 or 2.3.3 or later versions.
CVE-2019-8136 affects Magento 2.2 versions prior to 2.2.10 and Magento 2.3 versions prior to 2.3.3.
CVE-2019-8136 is classified as an insecure component vulnerability within the Magento platform.
Yes, patches are available in the updated versions of Magento, specifically 2.2.10 and 2.3.3.