{"answers":{"affected":"2 open source packages ship an affected version, including pypqc.","exploited":"There is no known exploitation of GHSA-hvh4-5qr6-3v7r in the wild and no public exploit code.","fix":"No fix has been published for GHSA-hvh4-5qr6-3v7r yet. Limit exposure of the affected software until one is available.","what":"GHSA-hvh4-5qr6-3v7r is a vulnerability in pypqc, published on 5 Jun 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-hvh4-5qr6-3v7r and fix it if it is affected.\n\nWhat it is: GHSA-hvh4-5qr6-3v7r is a vulnerability in pypqc, published on 5 Jun 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-hvh4-5qr6-3v7r in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- pypqc (PyPI): affected from 0.0.4 up to 0.0.6.2; no fix listed\n- pypqc (PyPI): affected from 0.0.4 up to 0.0.6.2; no fix listed\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-hvh4-5qr6-3v7r/ (Markdown: https://insights.sbomify.com/GHSA-hvh4-5qr6-3v7r/index.md)","id":"GHSA-hvh4-5qr6-3v7r","markdown":"https://insights.sbomify.com/GHSA-hvh4-5qr6-3v7r/index.md","name":"GHSA-hvh4-5qr6-3v7r","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Python cryptography library","requires_auth":"none","summary":"An attacker can recover private keys from pypqc Kyber implementations on macOS or clang-compiled systems by analyzing timing discrepancies during decapsulation requests.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\n`kyber512`, `kyber768`, and `kyber1024` on Mac OS \\(or when compiled with clang\\) only: An attacker able to submit many decapsulation requests against a single private key, and to gain timing information about the decapsulation, could recover the private key. Proof-of-concept exploit exists for a local attacker.\n\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N/E:P/RL:U/RC:C  \n\n### Patches\nNo patch is currently available / pending upstream [PQClean#556](https://github.com/PQClean/PQClean/issues/556).\n\n### Workarounds\nNo workarounds have been reported. The 0.0.7 -\u003e 0.0.7.1 upgrade, when available, should be a drop-in replacement\u003c!--; it has no known breaking changes--\u003e.\n\n### References\n\nhttps://pqshield.com/pqshield-plugs-timing-leaks-in-kyber-ml-kem-to-improve-pqc-implementation-maturity/\n\nhttps://github.com/antoonpurnal/clangover\n\nhttps://www.github.com/PQClean/PQClean/issues/556\n\nhttps://www.github.com/pq-crystals/kyber/commit/9b8d30698a3e7449aeb34e62339d4176f11e3c6c","ecosystems":["PyPI"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"Observable Timing Discrepancy in pypqc","id":"GHSA-hvh4-5qr6-3v7r","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0.0.4"],"last_affected":["0.0.6.2"],"package":"pypqc","purl":null,"source":"GHSA-hvh4-5qr6-3v7r"},{"ecosystem":"PyPI","fixed":[],"introduced":["0.0.4"],"last_affected":["0.0.6.2"],"package":"pypqc","purl":"pkg:pypi/pypqc","source":"GHSA-hvh4-5qr6-3v7r"}],"products":null,"published":"2024-06-05","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":"An attacker can recover private keys from pypqc Kyber implementations on macOS or clang-compiled systems by analyzing timing discrepancies during decapsulation requests.","url":"https://insights.sbomify.com/GHSA-hvh4-5qr6-3v7r/"}