Skip to content

Non-constant time HMAC comparison in Adyen plugin

Moderate
NyanKiyoshi published GHSA-3rqj-9v87-2x3f May 24, 2023

Package

saleor (GHCR)

Affected versions

>= 2.11.0, < 3.7.68
>= 3.8.0, < 3.8.40
>= 3.9.0, < 3.9.49
>= 3.10.0, < 3.10.36
>= 3.11.0, < 3.11.35
>= 3.12.0, < 3.12.25
>= 3.13.0, < 3.13.16

Patched versions

3.7.68
3.8.40
3.9.49
3.10.36
3.11.35
3.12.25
3.13.16

Description

Saleor's validate_hmac_signature function is vulnerable to timing attacks.

Impact

Malicious users could abuse this vulnerability on Saleor deployments having the Adyen plugin enabled in order to determine the secret key and forge fake events, this could affect the database integrity such as marking an order as paid when it is not.

This issue has been patched in versions 3.13.16, 3.12.25, 3.11.35, 3.10.36, 3.9.49, 3.8.40, and 3.7.68.

Workarounds

We strongly recommend upgrading to the latest versions, in case of inability to upgrade straight away, possible workarounds are:

  • Add rate-limit to the /plugins/channel/<channel>/mirumee.payments.adyen/webhooks endpoint
  • Disable the Saleor Adyen plugin

References

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

CVE ID

CVE-2023-32694