Magento 2 Community Edition Access Control Bypass
Impact
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.
Source excerpt · OSVAffected packages
Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.
| Affected range | Recorded fix |
|---|---|
| From 2.1.0 before 2.1.18Ecosystem versions | 2.1.18 |
| From 2.2.0 before 2.2.9Ecosystem versions | 2.2.9 |
| From 2.3.0 before 2.3.2Ecosystem versions | 2.3.2 |
Version evidence: OSV · GHSA-2fhr-f6q6-c4p2
View original version evidence (29 explicit versions)
Original source description
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.
References
- Security advisory nvd.nist.gov/vuln/detail/CVE-2019-7950
- Security advisory github.com/FriendsOfPHP/security-advisories/blob/master/magento/product-community-edition/CVE-2019-7950.yaml
- Source reference github.com/magento/magento2
- Security advisory magento.com/security/patches/magento-2.3.2-2.2.9-and-2.1.18-security-update-13
- Security advisory web.archive.org/web/20211206084839/https://magento.com/security/patches/magento-2.3.2-2.2.9-and-2.1.18-security-update-13