Saleor is vulnerable to unauthenticated information disclosure via Python exceptions
- 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 3.1.48, 3.11.12, 3.10.14, 3.9.27, 3.8.30, and 1 more
- 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
Saleor is a headless, GraphQL commerce platform delivering personalized shopping experiences. Some internal Python exceptions are not handled properly and thus are returned in API as error messages. Some messages might contain sensitive information like infrastructure details in unauthenticated requests. This issue has been patched in versions 3.1.48, 3.7.59, 3.8.0, 3.9.27, 3.10.14 and 3.11.12.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- saleor saleor
From 2.0.0 · fixed in 3.1.48; From 3.11.0 · fixed in 3.11.12; From 3.10.0 · fixed in 3.10.14; From 3.9.0 · fixed in 3.9.27; From 3.8.0 · fixed in 3.8.30; From 3.7.0 · fixed in 3.7.59
- saleorPyPI
From 2.0.0 · fixed in 3.1.48
- saleorPyPI
From 3.11.0 · fixed in 3.11.12
- saleorPyPI
From 3.10.0 · fixed in 3.10.14
- saleorPyPI
From 3.9.0 · fixed in 3.9.27
- saleorPyPI
From 3.8.0 · fixed in 3.8.30
- saleorPyPI
From 3.7.0 · fixed in 3.7.59
- saleorPyPI
From 2.0.0 · fixed in 3.1.48; From 3.7.0 · fixed in 3.7.59; From 3.8.0 · fixed in 3.8.30; From 3.9.0 · fixed in 3.9.27; From 3.10.0 · fixed in 3.10.14; From 3.11.0 · fixed in 3.11.12