Vulnerability · Published Apr 8, 2024 · Assigned by GitHub_M

CVE-2024-31205Saleor CSRF bypass in refreshToken mutation

Medium 4.2

In plain English

A medium-severity cross-site request forgery in saleor from saleor. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 9% of all known vulnerabilities).

Severity (CVSS 3.1)4.2Medium

Exploit odds (30 days)0.2%top 91.0% of all CVEs

Exploited in the wildNo reportsCISA SSVC: none

Attack toolingNoneno public tooling known

Official description

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`.

Affected products (as reported)

Vendor	Product	Versions
saleor	saleor	>= 3.10.0, < 3.14.64>= 3.15.0, < 3.15.39>= 3.16.0, < 3.16.39>= 3.17.0, < 3.17.35>= 3.18.0, < 3.18.31>= 3.19.0, < 3.19.19

Weakness: CWE-352 · Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N

References

https://github.com/saleor/saleor/security/advisories/GHSA-ff69-fwjf-3c9w x_refsource_CONFIRM
https://github.com/saleor/saleor/commit/36699c6f5c99590d24f46e3d5c5b1a3c2fd072e7 x_refsource_MISC