{"answers":{"affected":"3 open source packages ship an affected version, including truetype. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-28030 in the wild and no public exploit code.","fix":"Upgrade truetype to 0.30.1 or later.","what":"CVE-2021-28030 is a high-severity vulnerability in n/a, published on 5 Mar 2021. 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-28030 and fix it if it is affected.\n\nWhat it is: CVE-2021-28030 is a high-severity vulnerability in n/a, published on 5 Mar 2021. 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-28030 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- truetype (crates.io): affected all versions; fixed in 0.30.1\n- truetype (crates.io): affected all versions; fixed in 0.30.1\n- truetype (crates.io): affected from 0.0.0-0; fixed in 0.30.1\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-28030/ (Markdown: https://insights.sbomify.com/CVE-2021-28030/index.md)","id":"CVE-2021-28030","markdown":"https://insights.sbomify.com/CVE-2021-28030/index.md","name":"CVE-2021-28030","record":{"aliases":["GHSA-v7q4-97x4-4qw2","RUSTSEC-2021-0029"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust truetype crate","requires_auth":"none","summary":"Attackers can read uninitialized memory contents via a crafted Read operation in the truetype crate, potentially exposing sensitive data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"truetype","vendor":"truetype_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-908","name":"Use of Uninitialized Resource"}],"description":"An issue was discovered in the truetype crate before 0.30.1 for Rust. Attackers can read the contents of uninitialized memory locations via a user-provided Read operation within Tape::take_bytes.","ecosystems":["crates.io"],"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":"Use of Uninitialized Resource in truetype","id":"CVE-2021-28030","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":3,"n_references":1,"next":{"headline":"move_elements can double-free objects on panic","id":"CVE-2021-28031"},"packages":[{"ecosystem":"crates.io","fixed":["0.30.1"],"introduced":["0"],"last_affected":[],"package":"truetype","purl":null,"source":"GHSA-v7q4-97x4-4qw2"},{"ecosystem":"crates.io","fixed":["0.30.1"],"introduced":["0"],"last_affected":[],"package":"truetype","purl":"pkg:cargo/truetype","source":"GHSA-v7q4-97x4-4qw2"},{"ecosystem":"crates.io","fixed":["0.30.1"],"introduced":["0.0.0-0"],"last_affected":[],"package":"truetype","purl":"pkg:cargo/truetype","source":"RUSTSEC-2021-0029"}],"prev":{"headline":"Uninitialized memory access in toodee","id":"CVE-2021-28029"},"products":["n/a"],"published":"2021-03-05","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":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"},{"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":"Attackers can read uninitialized memory contents via a crafted Read operation in the truetype crate, potentially exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2021-28030/"}