First published: Tue Jun 25 2019(Updated: )
An information leakage 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. A SOAP web service endpoint does not properly enforce parameters related to access control. This could be abused to leak customer information via crafted SOAP requests.
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-7951 affects Magento 2.1 prior to 2.1.18, 2.2 prior to 2.2.9, and 2.3 prior to 2.3.2.
The severity of CVE-2019-7951 is high due to the potential for customer information leakage.
You can fix CVE-2019-7951 by updating to Magento 2.1.18, 2.2.9, or 2.3.2.
CVE-2019-7951 is an information leakage vulnerability related to improper access control in SOAP web services.
Yes, CVE-2019-7951 can be exploited by remote attackers through crafted SOAP requests.