{"answers":{"affected":"2 open source packages ship an affected version, including Adyen and adyen.","exploited":"There is no known exploitation of GHSA-f3q4-ggfp-jv34 in the wild and no public exploit code.","fix":"Upgrade Adyen to 7.1.0 or later.","what":"GHSA-f3q4-ggfp-jv34 is a vulnerability in Adyen, published on 30 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-f3q4-ggfp-jv34 and fix it if it is affected.\n\nWhat it is: GHSA-f3q4-ggfp-jv34 is a vulnerability in Adyen, published on 30 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-f3q4-ggfp-jv34 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- Adyen (PyPI): affected from 2.2.0; fixed in 7.1.0\n- adyen (PyPI): affected from 2.2.0; fixed in 7.1.0\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-f3q4-ggfp-jv34/ (Markdown: https://insights.sbomify.com/GHSA-f3q4-ggfp-jv34/index.md)","id":"GHSA-f3q4-ggfp-jv34","markdown":"https://insights.sbomify.com/GHSA-f3q4-ggfp-jv34/index.md","name":"GHSA-f3q4-ggfp-jv34","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Adyen Python library","requires_auth":"none","summary":"Attackers can bypass HMAC signature validation in Adyen Python library via timing attacks, allowing unauthorized notification processing.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Adyen APIs Library for Python timing attack vulnerability","id":"GHSA-f3q4-ggfp-jv34","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"security_feature_bypass","year":"2024"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"PyPI","fixed":["7.1.0"],"introduced":["2.2.0"],"last_affected":[],"package":"Adyen","purl":null,"source":"GHSA-f3q4-ggfp-jv34"},{"ecosystem":"PyPI","fixed":["7.1.0"],"introduced":["2.2.0"],"last_affected":[],"package":"adyen","purl":"pkg:pypi/adyen","source":"GHSA-f3q4-ggfp-jv34"}],"products":null,"published":"2024-08-30","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can bypass HMAC signature validation in Adyen Python library via timing attacks, allowing unauthorized notification processing.","url":"https://insights.sbomify.com/GHSA-f3q4-ggfp-jv34/"}