PYSEC-2023-1 Adyen has utility methods for validating notification HMAC signatures.
Not scored
Published
Check this codebase for PYSEC-2023-1 and fix it if it is affected.
What it is: PYSEC-2023-1 is a vulnerability in adyen, published on 24 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of PYSEC-2023-1 in the wild and no public exploit code.
Affected packages and fixed versions:
- adyen (PyPI): affected from 2.2.0; fixed in 7.1.0
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/PYSEC-2023-1/ (Markdown: https://insights.sbomify.com/PYSEC-2023-1/index.md)
Attackers can bypass HMAC signature validation in Adyen notification methods via timing attacks, potentially allowing unauthorized access to payment data.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is PYSEC-2023-1?
PYSEC-2023-1 is a vulnerability in adyen, published on 24 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Adyen has utility methods for validating notification HMAC signatures. The is_valid_hmac and is_valid_hmac_notification methods are vulnerable to a timing attack, you should compare the hash of the HMACs instead.
Which versions are affected by PYSEC-2023-1?
1 open source package ship an affected version, including adyen.
| Package | Affected | Fixed in |
|---|---|---|
adyen PyPI | From 2.2.0 | 7.1.0 |
How do I fix PYSEC-2023-1?
Upgrade adyen to 7.1.0 or later.
Is PYSEC-2023-1 being exploited?
There is no known exploitation of PYSEC-2023-1 in the wild and no public exploit code.