CVE-2019-8136: Magento 2 Community Edition Insecure Component

Published Oct 8, 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.

Other sources

Magento 2 Community Edition Insecure Component

— Packagist

PRODSECBUG-2416: Using vulnerable component that provides abstraction of HTTP specification

Affected Software

13 affected componentsFixes available
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
Magento Magento>=2.2.0<2.2.10
Magento Magento>=2.2.0<2.2.10
Magento Magento>=2.3.0<2.3.2
Magento Magento>=2.3.0<2.3.2
Magento Magento=2.3.2
Magento Magento=2.3.2
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
composer/magento/product-community-edition>=2.2, <2.2.10
2.2.10
composer/magento/product-community-edition>=2.3, <2.3.2-p2
2.3.2-p2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/magento/community-edition to a version that resolves this vulnerability.

    Fixed in 2.3.2-p1
  2. Upgrade

    Upgrade composer/magento/community-edition to a version that resolves this vulnerability.

    Fixed in 2.2.10
  3. Upgrade

    Upgrade composer/magento/product-community-edition to a version that resolves this vulnerability.

    Fixed in 2.2.10
  4. Upgrade

    Upgrade composer/magento/product-community-edition to a version that resolves this vulnerability.

    Fixed in 2.3.2-p2
  5. Upgrade

    Upgrade Magento 2 Community Edition to a version that resolves this vulnerability.

    Fixed in 2.2.10
  6. Upgrade

    Upgrade Magento 2 Community Edition to a version that resolves this vulnerability.

    Fixed in 2.3.3
  7. Upgrade

    Upgrade Magento 2 Community Edition to a version that resolves this vulnerability.

    Fixed in 2.3.2-p1

Event History

Oct 8, 2019
Advisory Published
12:00 AM
Data Sourced
via Packagist·12:00 AM
DescriptionSeverityAffected Software
Nov 5, 2019
CVE Published
via MITRE·11:18 PM
Data Sourced
via MITRE·11:18 PM
DescriptionWeakness
Nov 6, 2019
Data Sourced
via NVD·12:15 AM
RemedyDescriptionSeverityAffected Software
May 24, 2022
Advisory Published
via GitHub·05:00 PM
Data Sourced
via GitHub·05:00 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2019-8136?

CVE-2019-8136 is considered a medium severity vulnerability that affects specific versions of Magento.

2

How do I fix CVE-2019-8136?

To remediate CVE-2019-8136, upgrade Magento to version 2.2.10 or 2.3.3 or later versions.

3

Which versions of Magento are affected by CVE-2019-8136?

CVE-2019-8136 affects Magento 2.2 versions prior to 2.2.10 and Magento 2.3 versions prior to 2.3.3.

4

What type of vulnerability is CVE-2019-8136?

CVE-2019-8136 is classified as an insecure component vulnerability within the Magento platform.

5

Is there a patch available for CVE-2019-8136?

Yes, patches are available in the updated versions of Magento, specifically 2.2.10 and 2.3.3.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203