{"answers":{"affected":"3 open source packages ship an affected version, including github.com/supranational/blst.","exploited":"There is no known exploitation of GHSA-x279-68rr-jp4p in the wild and no public exploit code.","fix":"Upgrade github.com/supranational/blst to 0.3.3 or later.","what":"GHSA-x279-68rr-jp4p is a vulnerability in github.com/supranational/blst, published on 7 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-x279-68rr-jp4p and fix it if it is affected.\n\nWhat it is: GHSA-x279-68rr-jp4p is a vulnerability in github.com/supranational/blst, published on 7 Oct 2022. 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-x279-68rr-jp4p in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/supranational/blst (Go): affected from 0.3.0; fixed in 0.3.3\n- github.com/supranational/blst (Go): affected from 0.3.0; fixed in 0.3.3\n- github.com/supranational/blst (Go): affected from 0.3.0; fixed in 0.3.3\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-x279-68rr-jp4p/ (Markdown: https://insights.sbomify.com/GHSA-x279-68rr-jp4p/index.md)","id":"GHSA-x279-68rr-jp4p","markdown":"https://insights.sbomify.com/GHSA-x279-68rr-jp4p/index.md","name":"GHSA-x279-68rr-jp4p","record":{"aliases":["GO-2022-1053"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Go cryptographic library","requires_auth":"none","summary":"The blst library may produce incorrect results in modular inversion, potentially leading to invalid signatures, though no production impact has been observed.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\nBlst versions v0.3.0 to v0.3.2 can produce the incorrect outputs for some inputs to the blst_fp_eucl_inverse function. This could theoretically result in the creation of an invalid signature from correct inputs. However, fuzzing of higher level functions such as sign and verify were unable to produce incorrect results and there has been no reported occurrences of this issue being encountered in production use.\n\n### Description\nDuring the course of differential fuzzing of the blst library by @guidovranken it was discovered that blst would produce the incorrect result for some input values in the inverse function. This was the result of the introduction of a new inversion formula in version v0.3.0. This source of these incorrect outputs was due to two issues:\n\n1. The amount of inner loop iterations was not sufficient for the algorithm to converge.\n2. It was erroneously assumed that the absolute value of the intermediate result would be capped at 767-bits. As a result, some output values were truncated by one bit or the most significant bit was misinterpreted as the sign.\n\n### Patches\nThis issue has been resolved in the v0.3.3 release and users are recommended to upgrade immediately.\n\n### References\nThe software used to uncover this issue can be found [here](https://github.com/guidovranken/cryptofuzz).\n\n### Credits\nA special thanks to Guido Vranken (@guidovranken) for his discovery and disclosure of this vulnerability.\n\n### For more information\nIf you have any questions or comments about this advisory please email us at [hello@supranational.net](mailto:hello@supranational.net)","ecosystems":["Go"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Blst vulnerable to incorrect results for some inputs in blst_fp_eucl_inverse function","id":"GHSA-x279-68rr-jp4p","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Go","product":null,"products":[],"type":"other","year":"2022"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"Go","fixed":["0.3.3"],"introduced":["0.3.0"],"last_affected":[],"package":"github.com/supranational/blst","purl":null,"source":"GHSA-x279-68rr-jp4p"},{"ecosystem":"Go","fixed":["0.3.3"],"introduced":["0.3.0"],"last_affected":[],"package":"github.com/supranational/blst","purl":"pkg:golang/github.com/supranational/blst","source":"GHSA-x279-68rr-jp4p"},{"ecosystem":"Go","fixed":["0.3.3"],"introduced":["0.3.0"],"last_affected":[],"package":"github.com/supranational/blst","purl":"pkg:golang/github.com/supranational/blst","source":"GO-2022-1053"}],"products":null,"published":"2022-10-07","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"The blst library may produce incorrect results in modular inversion, potentially leading to invalid signatures, though no production impact has been observed.","url":"https://insights.sbomify.com/GHSA-x279-68rr-jp4p/"}