{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-32694 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-32694 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-32694 is a medium-severity vulnerability in saleor, published on 25 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-32694 and fix it if it is affected.\n\nWhat it is: CVE-2023-32694 is a medium-severity vulnerability in saleor, published on 25 May 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 CVE-2023-32694 in the wild and no public exploit code.\n\nAffected product: saleor. No package-level version data is available, so check the vendor advisory linked from the reference page.\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/CVE-2023-32694/ (Markdown: https://insights.sbomify.com/CVE-2023-32694/index.md)","id":"CVE-2023-32694","markdown":"https://insights.sbomify.com/CVE-2023-32694/index.md","name":"CVE-2023-32694","record":{"aliases":["GHSA-3rqj-9v87-2x3f"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Saleor e-commerce platform","requires_auth":"none","summary":"Attackers can exploit timing side-channels in HMAC validation to forge payment events, requiring the Adyen plugin to be enabled.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"saleor","vendor":"saleor"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-208","name":"Observable Timing Discrepancy"},{"id":"CWE-203","name":"Observable Discrepancy"}],"description":"Saleor Core is a composable, headless commerce API. Saleor's `validate_hmac_signature` function is vulnerable to timing attacks. 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.7.68, 3.8.40, 3.9.49, 3.10.36, 3.11.35, 3.12.25, and 3.13.16.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Non-constant time HMAC comparison in Adyen plugin in Saleor","id":"CVE-2023-32694","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Insufficient validation when decoding a Socket.IO packet","id":"CVE-2023-32695"},"packages":[],"prev":{"headline":"Decidim Cross-site Scripting vulnerability in the external link redirections","id":"CVE-2023-32693"},"products":["saleor"],"published":"2023-05-25","related":[{"cvss_score":8.7,"headline":"Saleor has an Insecure Direct Object Reference (IDOR) in GraphQL API","id":"CVE-2026-24136","kev_date_added":null,"published":"2026-01-23"},{"cvss_score":8.5,"headline":"Saleor vulnerable to stored XSS via Unrestricted File Upload","id":"CVE-2026-23499","kev_date_added":null,"published":"2026-01-21"},{"cvss_score":7.5,"headline":"Saleor Affected by Denial of Service via Unbounded GraphQL Query Batching","id":"CVE-2026-33756","kev_date_added":null,"published":"2026-04-08"},{"cvss_score":7.5,"headline":"Saleor has a resource exhaustion vulnerability in GraphQL queries","id":"CVE-2026-35401","kev_date_added":null,"published":"2026-04-08"},{"cvss_score":7.2,"headline":"Saleor lacks proper HTML sanitization in rich text fields","id":"CVE-2026-22849","kev_date_added":null,"published":"2026-01-21"},{"cvss_score":6.5,"headline":"Saleor is vulnerable to staff-authenticated error message information disclosure vulnerability via Python exceptions","id":"CVE-2023-26051","kev_date_added":null,"published":"2023-03-02"},{"cvss_score":6.5,"headline":"Missing Authorization in saleor/saleor","id":"CVE-2022-0932","kev_date_added":null,"published":"2022-03-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-01-16","vendors":["saleor"]},"summary":"Attackers can exploit timing side-channels in HMAC validation to forge payment events, requiring the Adyen plugin to be enabled.","url":"https://insights.sbomify.com/CVE-2023-32694/"}