{"answers":{"affected":"3 open source packages ship an affected version, including rgb. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-25016 in the wild and no public exploit code.","fix":"Upgrade rgb to 0.8.20 or later.","what":"CVE-2020-25016 is a critical memory corruption vulnerability in n/a, published on 29 Aug 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-25016 and fix it if it is affected.\n\nWhat it is: CVE-2020-25016 is a critical memory corruption vulnerability in n/a, published on 29 Aug 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-25016 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- rgb (crates.io): affected from 0.5.4; fixed in 0.8.20\n- rgb (crates.io): affected from 0.5.4; fixed in 0.8.20\n- rgb (crates.io): affected from 0.5.4; fixed in 0.8.20\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-25016/ (Markdown: https://insights.sbomify.com/CVE-2020-25016/index.md)","id":"CVE-2020-25016","markdown":"https://insights.sbomify.com/CVE-2020-25016/index.md","name":"CVE-2020-25016","record":{"aliases":["DEBIAN-CVE-2020-25016","GHSA-g4rw-8m5q-6453","RUSTSEC-2020-0029","UBUNTU-CVE-2020-25016"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust rgb crate","requires_auth":"none","summary":"Attackers can exploit unsafe memory handling in the Rust rgb crate to read uninitialized memory or execute arbitrary code via pointer dereferencing.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"rgb-rust","vendor":"rgb-rust_project"}],"cvss":{"score":9.1,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-843","name":"Access of Resource Using Incompatible Type"},{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"A safety violation was discovered in the rgb crate before 0.8.20 for Rust, leading to (for example) dereferencing of arbitrary pointers or disclosure of uninitialized memory. This occurs because structs can be treated as bytes for read and write operations.","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":"Out of bounds access in rgb","id":"CVE-2020-25016","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2020"},"n_packages":3,"n_references":2,"next":{"headline":"Other in n/a","id":"CVE-2020-25017"},"packages":[{"ecosystem":"crates.io","fixed":["0.8.20"],"introduced":["0.5.4"],"last_affected":[],"package":"rgb","purl":null,"source":"GHSA-g4rw-8m5q-6453"},{"ecosystem":"crates.io","fixed":["0.8.20"],"introduced":["0.5.4"],"last_affected":[],"package":"rgb","purl":"pkg:cargo/rgb","source":"GHSA-g4rw-8m5q-6453"},{"ecosystem":"crates.io","fixed":["0.8.20"],"introduced":["0.5.4"],"last_affected":[],"package":"rgb","purl":"pkg:cargo/rgb","source":"RUSTSEC-2020-0029"}],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2020-25015"},"products":["n/a"],"published":"2020-08-29","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-04","vendors":["n/a"]},"summary":"Attackers can exploit unsafe memory handling in the Rust rgb crate to read uninitialized memory or execute arbitrary code via pointer dereferencing.","url":"https://insights.sbomify.com/CVE-2020-25016/"}