Shopware 6 allows attackers to check for registered accounts through the store-api
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.5.8.17, 6.6.10.3, 6.7.0.0-rc2, 6.5.8.18
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Shopware 6 is an open commerce platform based on Symfony Framework and Vue. Through the store-api it is possible as a attacker to check if a specific e-mail address has an account in the shop. Using the store-api endpoint /store-api/account/recovery-password you get the response, which indicates clearly that there is no account for this customer. In contrast you get a success response if the account was found. This vulnerability is fixed in Shopware 6.6.10.3 or 6.5.8.17. For older versions of 6.4, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- shopware shopware
fixed in 6.5.8.17; From 6.6.0.0 · fixed in 6.6.10.3; From 6.7.0.0-rc1 · fixed in 6.7.0.0-rc2
- shopware/corePackagist
From 6.6.0.0 · fixed in 6.6.10.3
- shopware/platformPackagist
From 6.6.0.0 · fixed in 6.6.10.3
- shopware/corePackagist
From 6.7.0.0-rc1 · fixed in 6.7.0.0-rc2
- shopware/platformPackagist
From 6.7.0.0-rc1 · fixed in 6.7.0.0-rc2
- shopware/corePackagist
fixed in 6.5.8.18
- shopware/platformPackagist
fixed in 6.5.8.18