{"answers":{"affected":"2 open source packages ship an affected version, including ncurses. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-15548 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-15548 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-15548 is a critical memory corruption vulnerability in n/a, published on 26 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-15548 and fix it if it is affected.\n\nWhat it is: CVE-2019-15548 is a critical memory corruption vulnerability in n/a, published on 26 Aug 2019. 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-2019-15548 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ncurses (crates.io): affected all versions up to 5.101.0; no fix listed\n- ncurses (crates.io): affected all versions up to 5.101.0; no fix listed\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-2019-15548/ (Markdown: https://insights.sbomify.com/CVE-2019-15548/index.md)","id":"CVE-2019-15548","markdown":"https://insights.sbomify.com/CVE-2019-15548/index.md","name":"CVE-2019-15548","record":{"aliases":["GHSA-g7r5-x7cr-vm3v","UBUNTU-CVE-2019-15548"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust ncurses crate","requires_auth":"none","summary":"Buffer overflows in the Rust ncurses crate allow attackers to execute arbitrary code or cause denial of service via mishandled C function interactions.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ncurses","vendor":"ncurses_project"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"An issue was discovered in the ncurses crate through 5.99.0 for Rust. There are instr and mvwinstr buffer overflows because interaction with C functions is mishandled.","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":false,"headline":"Buffer overflow and format vulnerabilities in ncurses","id":"CVE-2019-15548","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2019"},"n_packages":2,"n_references":1,"next":{"headline":"Memory exhaustion in asn1_der","id":"CVE-2019-15549"},"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["5.101.0"],"package":"ncurses","purl":null,"source":"GHSA-g7r5-x7cr-vm3v"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["5.101.0"],"package":"ncurses","purl":"pkg:cargo/ncurses","source":"GHSA-g7r5-x7cr-vm3v"}],"prev":{"headline":"Mishandling of format strings in ncurses","id":"CVE-2019-15547"},"products":["n/a"],"published":"2019-08-26","related":[{"cvss_score":7.5,"headline":"Mishandling of format strings in ncurses","id":"CVE-2019-15547","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":"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":"Buffer overflows in the Rust ncurses crate allow attackers to execute arbitrary code or cause denial of service via mishandled C function interactions.","url":"https://insights.sbomify.com/CVE-2019-15548/"}