{"answers":{"affected":"5 open source packages ship an affected version, including smallvec. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-25023 in the wild and no public exploit code.","fix":"Upgrade smallvec to 0.6.13 or later.","what":"CVE-2018-25023 is a high-severity memory corruption vulnerability in n/a, published on 26 Dec 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-2018-25023 and fix it if it is affected.\n\nWhat it is: CVE-2018-25023 is a high-severity memory corruption vulnerability in n/a, published on 26 Dec 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-2018-25023 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- smallvec (crates.io): affected all versions; fixed in 0.6.13\n- smallvec (crates.io): affected all versions; fixed in 0.6.13\n- smallvec (crates.io): affected all versions; fixed in 0.6.13\n- smallvec (crates.io): affected all versions; fixed in 0.6.13\n- smallvec (crates.io): affected from 0.0.0-0; fixed in 0.6.13\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-2018-25023/ (Markdown: https://insights.sbomify.com/CVE-2018-25023/index.md)","id":"CVE-2018-25023","markdown":"https://insights.sbomify.com/CVE-2018-25023/index.md","name":"CVE-2018-25023","record":{"aliases":["DEBIAN-CVE-2018-25023","GHSA-55m5-whcv-c49c","GHSA-66p5-j55p-32r9","RUSTSEC-2018-0018","UBUNTU-CVE-2018-25023"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust smallvec crate","requires_auth":"none","summary":"The smallvec Rust library allows creating uninitialized values, potentially leading to memory corruption, crashes, or arbitrary code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"smallvec","vendor":"servo"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-908","name":"Use of Uninitialized Resource"}],"description":"An issue was discovered in the smallvec crate before 0.6.13 for Rust. It can create an uninitialized value of any type, including a reference type.","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 smallvec","id":"CVE-2018-25023","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2018"},"n_packages":5,"n_references":3,"next":{"headline":"Out-of-bounds Write in actix-web","id":"CVE-2018-25024"},"packages":[{"ecosystem":"crates.io","fixed":["0.6.13"],"introduced":["0"],"last_affected":[],"package":"smallvec","purl":null,"source":"GHSA-55m5-whcv-c49c"},{"ecosystem":"crates.io","fixed":["0.6.13"],"introduced":["0"],"last_affected":[],"package":"smallvec","purl":"pkg:cargo/smallvec","source":"GHSA-55m5-whcv-c49c"},{"ecosystem":"crates.io","fixed":["0.6.13"],"introduced":["0"],"last_affected":[],"package":"smallvec","purl":null,"source":"GHSA-66p5-j55p-32r9"},{"ecosystem":"crates.io","fixed":["0.6.13"],"introduced":["0"],"last_affected":[],"package":"smallvec","purl":"pkg:cargo/smallvec","source":"GHSA-66p5-j55p-32r9"},{"ecosystem":"crates.io","fixed":["0.6.13"],"introduced":["0.0.0-0"],"last_affected":[],"package":"smallvec","purl":"pkg:cargo/smallvec","source":"RUSTSEC-2018-0018"}],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2018-25022"},"products":["n/a"],"published":"2021-12-26","related":[{"cvss_score":9.8,"headline":"Buffer overflow in SmallVec::insert_many","id":"CVE-2021-25900","kev_date_added":null,"published":"2021-01-22"},{"cvss_score":9.8,"headline":"Double free in smallvec","id":"CVE-2018-20991","kev_date_added":null,"published":"2019-08-26"},{"cvss_score":9.8,"headline":"Double free in smallvec","id":"CVE-2019-15551","kev_date_added":null,"published":"2019-08-26"},{"cvss_score":9.8,"headline":"Memory corruption in smallvec","id":"CVE-2019-15554","kev_date_added":null,"published":"2019-08-26"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-11-18","vendors":["n/a"]},"summary":"The smallvec Rust library allows creating uninitialized values, potentially leading to memory corruption, crashes, or arbitrary code execution.","url":"https://insights.sbomify.com/CVE-2018-25023/"}