GHSA-f3q4-ggfp-jv34 json
Adyen APIs Library for Python timing attack vulnerability
published 2y ago modified last yr.
- cvss
- 5.3
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi adyen 7.1.0
Is GHSA-f3q4-ggfp-jv34 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | adyen | >=2.2.0, <7.1.0 |
7.1.0 |
Classification
- Weakness
-
- CWE-347 Improper Verification of Cryptographic Signature
References
-
github.com
/Adyen/adyen-python-api-library/pull/170
web
-
github.com
/Adyen/adyen-python-api-library/commit/3292133dbc00ffc4cccfb92de672a76eaa587ca5
web
-
github.com
/Adyen/adyen-python-api-library/issues/168
web
-
github.com
/Adyen/adyen-python-api-library
package
-
github.com
/pypa/advisory-database/tree/main/vulns/adyen/PYSEC-2023-1.yaml
web
Sources
- GitHub Advisory GHSA-f3q4-ggfp-jv34
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.