{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2021-20192 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-20192 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-20192 is a vulnerability, published on 25 Aug 2022."},"fix_prompt":"Check this codebase for CVE-2021-20192 and fix it if it is affected.\n\nWhat it is: CVE-2021-20192 is a vulnerability, published on 25 Aug 2022. \nExploitation: There is no known exploitation of CVE-2021-20192 in the wild and no public exploit code.\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-20192/ (Markdown: https://insights.sbomify.com/CVE-2021-20192/index.md)","id":"CVE-2021-20192","markdown":"https://insights.sbomify.com/CVE-2021-20192/index.md","name":"CVE-2021-20192","record":{"aliases":[],"analysis":null,"analysis_generated_by":null,"assigner":"redhat","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2021-20192","indexable":false,"kev":null,"kind":"cve_rejected","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2021"},"n_packages":0,"n_references":0,"next":{"headline":"Out-of-bounds Read and Missing Release of Memory after Effective Lifetime in tar","id":"CVE-2021-20193"},"packages":[],"prev":{"headline":"Insertion of Sensitive Information into Log File in ansible","id":"CVE-2021-20191"},"products":[],"published":"2022-08-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"REJECTED","updated":"2022-08-25","vendors":[]},"summary":null,"url":"https://insights.sbomify.com/CVE-2021-20192/"}