{"answers":{"affected":"3 open source packages ship an affected version, including github.com/binance-chain/tss-lib. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-12118 in the wild and no public exploit code.","fix":"Upgrade github.com/binance-chain/tss-lib to 1.2.0 or later.","what":"CVE-2020-12118 is a high-severity vulnerability in n/a, published on 23 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-12118 and fix it if it is affected.\n\nWhat it is: CVE-2020-12118 is a high-severity vulnerability in n/a, published on 23 Apr 2020. 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-2020-12118 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/binance-chain/tss-lib (Go): affected all versions; fixed in 1.2.0\n- github.com/binance-chain/tss-lib (Go): affected all versions; fixed in 1.2.0\n- github.com/binance-chain/tss-lib (Go): affected all versions; fixed in 1.2.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/CVE-2020-12118/ (Markdown: https://insights.sbomify.com/CVE-2020-12118/index.md)","id":"CVE-2020-12118","markdown":"https://insights.sbomify.com/CVE-2020-12118/index.md","name":"CVE-2020-12118","record":{"aliases":["GHSA-399h-cmvp-qgx5","GO-2022-0769"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Go cryptographic library","requires_auth":"none","summary":"Attackers can compromise signing rounds or obtain sensitive information by crafting parameters in the keygen protocol of the Binance tss-lib library.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"tss-lib","vendor":"binance"}],"cvss":{"score":8.2,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-276","name":"Incorrect Default Permissions"}],"description":"The keygen protocol implementation in Binance tss-lib before 1.2.0 allows attackers to generate crafted h1 and h2 parameters in order to compromise a signing round or obtain sensitive information from other parties.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Incorrect Default Permissions in Binance tss-lib","id":"CVE-2020-12118","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"business_logic","year":"2020"},"n_packages":3,"n_references":2,"next":{"headline":"Business logic in n/a","id":"CVE-2020-12119"},"packages":[{"ecosystem":"Go","fixed":["1.2.0"],"introduced":["0"],"last_affected":[],"package":"github.com/binance-chain/tss-lib","purl":null,"source":"GHSA-399h-cmvp-qgx5"},{"ecosystem":"Go","fixed":["1.2.0"],"introduced":["0"],"last_affected":[],"package":"github.com/binance-chain/tss-lib","purl":"pkg:golang/github.com/binance-chain/tss-lib","source":"GHSA-399h-cmvp-qgx5"},{"ecosystem":"Go","fixed":["1.2.0"],"introduced":["0"],"last_affected":[],"package":"github.com/binance-chain/tss-lib","purl":"pkg:golang/github.com/binance-chain/tss-lib","source":"GO-2022-0769"}],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2020-12117"},"products":["n/a"],"published":"2020-04-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can compromise signing rounds or obtain sensitive information by crafting parameters in the keygen protocol of the Binance tss-lib library.","url":"https://insights.sbomify.com/CVE-2020-12118/"}