CSRF in Saleor

CVE-2024-31205

Saleor is an e-commerce platform. Starting in version 3.10.0 and prior to versions 3.14.64, 3.15.39, 3.16.39, 3.17.35, 3.18.31, and 3.19.19, an attacker may bypass cross-set request forgery (CSRF) validation when calling refresh token mutation with empty string. When a user provides an empty string in `refreshToken` mutation, while the token persists in `JWT_REFRESH_TOKEN_COOKIE_NAME` cookie, application omits validation against CSRF token and returns valid access token. Versions 3.14.64, 3.15.39, 3.16.39, 3.17.35, 3.18.31, and 3.19.19 contain a patch for the issue. As a workaround, one may replace `saleor.graphql.account.mutations.authentication.refresh_token.py.get_refresh_token`. This will fix the issue, but be aware, that it returns `JWT_MISSING_TOKEN` instead of `JWT_INVALID_TOKEN`.

Vulnerability class: CSRF (Cross-Site Request Forgery)

EPSS: 0.002 (9.3th percentile) — read the EPSS interpretation.

CVSS v3 metric

CVSS v3 base score 4.2 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N.

Affected products

  • Saleor — versions >= 3.10.0, < 3.14.64, >= 3.15.0, < 3.15.39, >= 3.16.0, < 3.16.39

Weakness classification (CWE)

Public proof-of-concept exploits

References

Frequently asked questions

What is CVE-2024-31205?
CVE-2024-31205 is a medium-severity vulnerability in Saleor, classified under Cross-Site Request Forgery (CSRF). CVSS score: 4.2/10. Published 2024-04-08.
How severe is CVE-2024-31205?
Medium severity. CVSS v3 base score is 4.2 out of 10.
Is CVE-2024-31205 known to be exploited?
1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.