CVE-2022-39275: Improper object type validation in saleor
Saleor is a headless, GraphQL commerce platform. In affected versions some GraphQL mutations were not properly checking the ID type input which allowed to access database objects that the authenticated user may not be allowed to access. This vulnerability can be used to expose the following information: Estimating database row counts from tables with a sequential primary key or Exposing staff user and customer email addresses and full name through the assignNavigation() mutation. This issue has been patched in main and backported to multiple releases (3.7.17, 3.6.18, 3.5.23, 3.4.24, 3.3.26, 3.2.14, 3.1.24). Users are advised to upgrade. There are no known workarounds for this issue.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2022-39275?
CVE-2022-39275 is classified as a high severity vulnerability.
How do I fix CVE-2022-39275?
To fix CVE-2022-39275, upgrade to versions 3.1.25, 3.2.15, 3.3.27, 3.4.25, 3.5.24, 3.6.19, or 3.7.18 or later of Saleor.
What components are affected by CVE-2022-39275?
CVE-2022-39275 affects Saleor versions from 2.0.0 to 3.7.17.
What impact does CVE-2022-39275 have on users?
CVE-2022-39275 allows authenticated users to access database objects they should not be permitted to access.
When was CVE-2022-39275 disclosed?
CVE-2022-39275 was disclosed in 2022.