{"answers":{"affected":"5 open source packages ship an affected version, including libpulse-binding. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-25001 in the wild and no public exploit code.","fix":"Upgrade libpulse-binding to 2.5.0 or later.","what":"CVE-2018-25001 is a medium-severity use after free vulnerability in n/a, published on 31 Dec 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-25001 and fix it if it is affected.\n\nWhat it is: CVE-2018-25001 is a medium-severity use after free vulnerability in n/a, published on 31 Dec 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-25001 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- libpulse-binding (crates.io): affected from 1.0.5; fixed in 2.5.0\n- libpulse-binding (crates.io): affected from 1.0.5; fixed in 2.5.0\n- libpulse-binding (crates.io): affected from 1.0.5; fixed in 2.5.0\n- libpulse-binding (crates.io): affected from 1.0.5; fixed in 2.5.0\n- libpulse-binding (crates.io): affected from 1.0.5; fixed in 2.5.0\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-25001/ (Markdown: https://insights.sbomify.com/CVE-2018-25001/index.md)","id":"CVE-2018-25001","markdown":"https://insights.sbomify.com/CVE-2018-25001/index.md","name":"CVE-2018-25001","record":{"aliases":["GHSA-6gvc-4jvj-pwq4","GHSA-f56g-chqp-22m9","RUSTSEC-2018-0020"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust libpulse-binding crate","requires_auth":"low_privilege","summary":"A use-after-free vulnerability in the libpulse-binding Rust crate allows attackers to potentially execute arbitrary code or cause a denial of service.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"libpulse-binding","vendor":"libpulse-binding_project"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-416","name":"Use After Free"}],"description":"An issue was discovered in the libpulse-binding crate before 2.5.0 for Rust. proplist::Iterator can cause a use-after-free.","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":"Duplicate Advisory: Use after free in libpulse-binding","id":"CVE-2018-25001","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"use_after_free","year":"2018"},"n_packages":5,"n_references":1,"next":{"headline":"File upload in n/a","id":"CVE-2018-25002"},"packages":[{"ecosystem":"crates.io","fixed":["2.5.0"],"introduced":["1.0.5"],"last_affected":[],"package":"libpulse-binding","purl":null,"source":"GHSA-6gvc-4jvj-pwq4"},{"ecosystem":"crates.io","fixed":["2.5.0"],"introduced":["1.0.5"],"last_affected":[],"package":"libpulse-binding","purl":"pkg:cargo/libpulse-binding","source":"GHSA-6gvc-4jvj-pwq4"},{"ecosystem":"crates.io","fixed":["2.5.0"],"introduced":["1.0.5"],"last_affected":[],"package":"libpulse-binding","purl":null,"source":"GHSA-f56g-chqp-22m9"},{"ecosystem":"crates.io","fixed":["2.5.0"],"introduced":["1.0.5"],"last_affected":[],"package":"libpulse-binding","purl":"pkg:cargo/libpulse-binding","source":"GHSA-f56g-chqp-22m9"},{"ecosystem":"crates.io","fixed":["2.5.0"],"introduced":["1.0.5"],"last_affected":[],"package":"libpulse-binding","purl":"pkg:cargo/libpulse-binding","source":"RUSTSEC-2018-0020"}],"prev":{"headline":"Out-of-bounds Read in stringstream","id":"CVE-2018-21270"},"products":["n/a"],"published":"2020-12-31","related":[{"cvss_score":7.5,"headline":"Use after free in n/a","id":"CVE-2018-25027","kev_date_added":null,"published":"2021-12-26"},{"cvss_score":7.5,"headline":"Use after free in n/a","id":"CVE-2018-25028","kev_date_added":null,"published":"2021-12-26"},{"cvss_score":7.5,"headline":"Duplicate Advisory: Uncaught Exception in libpulse-binding","id":"CVE-2019-25055","kev_date_added":null,"published":"2021-12-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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"A use-after-free vulnerability in the libpulse-binding Rust crate allows attackers to potentially execute arbitrary code or cause a denial of service.","url":"https://insights.sbomify.com/CVE-2018-25001/"}