Saleor up to 3.19.18 cross-site request forgery

Summaryinfo

A vulnerability identified as problematic has been detected in Saleor up to 3.19.18. Affected by this vulnerability is an unknown functionality. This manipulation causes cross-site request forgery. This vulnerability is registered as CVE-2024-31205. Remote exploitation of the attack is possible. No exploit is available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Saleor up to 3.19.18. It has been declared as problematic. Affected by this vulnerability is some unknown functionality. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. The CWE definition for the vulnerability is CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. As an impact it is known to affect integrity. The summary by CVE is:

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

The advisory is shared at github.com. This vulnerability is known as CVE-2024-31205 since 03/29/2024. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.

Upgrading to version 3.14.64, 3.15.39, 3.16.39, 3.17.35, 3.18.31 or 3.19.19 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Saleor

Version

• 3.14.0
• 3.14.1
• 3.14.2
• 3.14.3
• 3.14.4
• 3.14.5
• 3.14.6
• 3.14.7
• 3.14.8
• 3.14.9
• 3.14.10
• 3.14.11
• 3.14.12
• 3.14.13
• 3.14.14
• 3.14.15
• 3.14.16
• 3.14.17
• 3.14.18
• 3.14.19
• 3.14.20
• 3.14.21
• 3.14.22
• 3.14.23
• 3.14.24
• 3.14.25
• 3.14.26
• 3.14.27
• 3.14.28
• 3.14.29
• 3.14.30
• 3.14.31
• 3.14.32
• 3.14.33
• 3.14.34
• 3.14.35
• 3.14.36
• 3.14.37
• 3.14.38
• 3.14.39
• 3.14.40
• 3.14.41
• 3.14.42
• 3.14.43
• 3.14.44
• 3.14.45
• 3.14.46
• 3.14.47
• 3.14.48
• 3.14.49
• 3.14.50
• 3.14.51
• 3.14.52
• 3.14.53
• 3.14.54
• 3.14.55
• 3.14.56
• 3.14.57
• 3.14.58
• 3.14.59
• 3.14.60
• 3.14.61
• 3.14.62
• 3.14.63
• 3.15.0
• 3.15.1
• 3.15.2
• 3.15.3
• 3.15.4
• 3.15.5
• 3.15.6
• 3.15.7
• 3.15.8
• 3.15.9
• 3.15.10
• 3.15.11
• 3.15.12
• 3.15.13
• 3.15.14
• 3.15.15
• 3.15.16
• 3.15.17
• 3.15.18
• 3.15.19
• 3.15.20
• 3.15.21
• 3.15.22
• 3.15.23
• 3.15.24
• 3.15.25
• 3.15.26
• 3.15.27
• 3.15.28
• 3.15.29
• 3.15.30
• 3.15.31
• 3.15.32
• 3.15.33
• 3.15.34
• 3.15.35
• 3.15.36
• 3.15.37
• 3.15.38
• 3.16.0
• 3.16.1
• 3.16.2
• 3.16.3
• 3.16.4
• 3.16.5
• 3.16.6
• 3.16.7
• 3.16.8
• 3.16.9
• 3.16.10
• 3.16.11
• 3.16.12
• 3.16.13
• 3.16.14
• 3.16.15
• 3.16.16
• 3.16.17
• 3.16.18
• 3.16.19
• 3.16.20
• 3.16.21
• 3.16.22
• 3.16.23
• 3.16.24
• 3.16.25
• 3.16.26
• 3.16.27
• 3.16.28
• 3.16.29
• 3.16.30
• 3.16.31
• 3.16.32
• 3.16.33
• 3.16.34
• 3.16.35
• 3.16.36
• 3.16.37
• 3.16.38
• 3.17.0
• 3.17.1
• 3.17.2
• 3.17.3
• 3.17.4
• 3.17.5
• 3.17.6
• 3.17.7
• 3.17.8
• 3.17.9
• 3.17.10
• 3.17.11
• 3.17.12
• 3.17.13
• 3.17.14
• 3.17.15
• 3.17.16
• 3.17.17
• 3.17.18
• 3.17.19
• 3.17.20
• 3.17.21
• 3.17.22
• 3.17.23
• 3.17.24
• 3.17.25
• 3.17.26
• 3.17.27
• 3.17.28
• 3.17.29
• 3.17.30
• 3.17.31
• 3.17.32
• 3.17.33
• 3.17.34
• 3.18.0
• 3.18.1
• 3.18.2
• 3.18.3
• 3.18.4
• 3.18.5
• 3.18.6
• 3.18.7
• 3.18.8
• 3.18.9
• 3.18.10
• 3.18.11
• 3.18.12
• 3.18.13
• 3.18.14
• 3.18.15
• 3.18.16
• 3.18.17
• 3.18.18
• 3.18.19
• 3.18.20
• 3.18.21
• 3.18.22
• 3.18.23
• 3.18.24
• 3.18.25
• 3.18.26
• 3.18.27
• 3.18.28
• 3.18.29
• 3.18.30
• 3.19.0
• 3.19.1
• 3.19.2
• 3.19.3
• 3.19.4
• 3.19.5
• 3.19.6
• 3.19.7
• 3.19.8
• 3.19.9
• 3.19.10
• 3.19.11
• 3.19.12
• 3.19.13
• 3.19.14
• 3.19.15
• 3.19.16
• 3.19.17
• 3.19.18

License

• open-source

Website

• Product: https://github.com/saleor/saleor/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion