First published: Tue Jun 25 2019(Updated: )
An access control bypass 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. An unauthenticated user can bypass access controls via REST API calls to assign themselves to an arbitrary company, thereby gaining read access to potentially confidental information.
Credit: psirt@adobe.com 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 |
Magento | >=2.1.0<2.1.18 | |
Magento | >=2.2.0<2.2.9 | |
Magento | >=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-7950 is classified as a critical vulnerability due to its potential to allow unauthorized access to sensitive information.
To fix CVE-2019-7950, upgrade to Magento version 2.1.18, 2.2.9, or 2.3.2 or later.
CVE-2019-7950 affects Magento versions prior to 2.1.18, 2.2.9, and 2.3.2.
An attacker can bypass access controls and assign themselves to an arbitrary company, gaining unauthorized read access.
Yes, a security update patch is available for CVE-2019-7950 in the form of upgraded versions of Magento.