{"answers":{"affected":"1 open source package ship an affected version, including adyen.","exploited":"There is no known exploitation of PYSEC-2023-1 in the wild and no public exploit code.","fix":"Upgrade adyen to 7.1.0 or later.","what":"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."},"fix_prompt":"Check this codebase for PYSEC-2023-1 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of PYSEC-2023-1 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\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/PYSEC-2023-1/ (Markdown: https://insights.sbomify.com/PYSEC-2023-1/index.md)","id":"PYSEC-2023-1","markdown":"https://insights.sbomify.com/PYSEC-2023-1/index.md","name":"PYSEC-2023-1","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 notification methods via timing attacks, potentially allowing unauthorized access to payment data.","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 has utility methods for validating notification HMAC signatures.","id":"PYSEC-2023-1","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"security_feature_bypass","year":"2023"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"PyPI","fixed":["7.1.0"],"introduced":["2.2.0"],"last_affected":[],"package":"adyen","purl":"pkg:pypi/adyen","source":"PYSEC-2023-1"}],"products":null,"published":"2023-01-24","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can bypass HMAC signature validation in Adyen notification methods via timing attacks, potentially allowing unauthorized access to payment data.","url":"https://insights.sbomify.com/PYSEC-2023-1/"}