{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-4076 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2021-4076 is a high-severity vulnerability in tang, published on 2 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-4076 and fix it if it is affected.\n\nWhat it is: CVE-2021-4076 is a high-severity vulnerability in tang, published on 2 Mar 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 CVE-2021-4076 in the wild and no public exploit code.\n\nAffected product: tang. 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-2021-4076/ (Markdown: https://insights.sbomify.com/CVE-2021-4076/index.md)","id":"CVE-2021-4076","markdown":"https://insights.sbomify.com/CVE-2021-4076/index.md","name":"CVE-2021-4076","record":{"aliases":["DEBIAN-CVE-2021-4076","DSA-5025-1","GHSA-83f4-c2vq-g2p3"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"cryptographic binding server","requires_auth":"none","summary":"A flaw in the tang server allows attackers to leak private keys, compromising cryptographic security.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"tang","vendor":"tang_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"A flaw exists in tang, a network-based cryptographic binding server, which could result in leak of private keys.","ecosystems":[],"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":"Information disclosure in tang","id":"CVE-2021-4076","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in Chrome","id":"CVE-2021-4078"},"packages":[],"prev":{"headline":"Server-Side Request Forgery (SSRF) in snipe/snipe-it","id":"CVE-2021-4075"},"products":["tang"],"published":"2022-03-02","related":[],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"A flaw in the tang server allows attackers to leak private keys, compromising cryptographic security.","url":"https://insights.sbomify.com/CVE-2021-4076/"}