{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-34121 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2021-34121 is a high-severity vulnerability in n/a, published on 18 Jul 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-34121 and fix it if it is affected.\n\nWhat it is: CVE-2021-34121 is a high-severity vulnerability in n/a, published on 18 Jul 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-34121 exists.\n\nAffected product: n/a. 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-34121/ (Markdown: https://insights.sbomify.com/CVE-2021-34121/index.md)","id":"CVE-2021-34121","markdown":"https://insights.sbomify.com/CVE-2021-34121/index.md","name":"CVE-2021-34121","record":{"aliases":["DEBIAN-CVE-2021-34121","GHSA-vvmp-35v7-f6q6","UBUNTU-CVE-2021-34121"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"htmodoc library","requires_auth":"none","summary":"An out-of-bounds read in htmodoc allows attackers to leak memory layout information, potentially aiding further exploitation.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"htmldoc","vendor":"htmldoc_project"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"An Out of Bounds flaw was discovered in htmodoc 1.9.12 in function parse_tree() in toc.cxx, this possibly leads to memory layout information leaking in the data. This might be used in a chain of vulnerability in order to reach code execution.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Information disclosure in n/a","id":"CVE-2021-34121","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Null dereference in n/a","id":"CVE-2021-34122"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2021-34119"},"products":["n/a"],"published":"2023-07-18","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-46478","kev_date_added":null,"published":"2024-10-24"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-45508","kev_date_added":null,"published":"2024-09-01"},{"cvss_score":9.8,"headline":"Memory corruption in htmldoc","id":"CVE-2021-23158","kev_date_added":null,"published":"2022-03-16"},{"cvss_score":9.8,"headline":"Memory corruption in htmldoc","id":"CVE-2021-23165","kev_date_added":null,"published":"2022-03-16"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2021-34119","kev_date_added":null,"published":"2023-07-18"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2022-28085","kev_date_added":null,"published":"2022-04-27"}],"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-10-28","vendors":["n/a"]},"summary":"An out-of-bounds read in htmodoc allows attackers to leak memory layout information, potentially aiding further exploitation.","url":"https://insights.sbomify.com/CVE-2021-34121/"}