{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-15870 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-15870 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-15870 is a medium-severity vulnerability in Libming Libming, published on 25 Aug 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-15870 and fix it if it is affected.\n\nWhat it is: CVE-2018-15870 is a medium-severity vulnerability in Libming Libming, published on 25 Aug 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-15870 in the wild and no public exploit code.\n\nAffected product: Libming Libming. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-15870/ (Markdown: https://insights.sbomify.com/CVE-2018-15870/index.md)","id":"CVE-2018-15870","markdown":"https://insights.sbomify.com/CVE-2018-15870/index.md","name":"CVE-2018-15870","record":{"aliases":["GHSA-8ffr-89xh-hq29","UBUNTU-CVE-2018-15870"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"libming library","requires_auth":"none","summary":"An invalid memory address dereference in libming allows attackers to cause a segmentation fault and application crash, resulting in denial of service.","user_interaction":"required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"libming","vendor":"libming"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"An invalid memory address dereference was discovered in decompileGETVARIABLE in libming 0.4.8 before 2018-03-12. The vulnerability causes a segmentation fault and application crash, which leads to denial of service.","ecosystems":[],"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":"Null dereference in n/a","id":"CVE-2018-15870","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"libming:libming","products":["libming:libming"],"type":"null_dereference","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Null dereference in n/a","id":"CVE-2018-15871"},"packages":[],"prev":{"headline":"Supply chain in n/a","id":"CVE-2018-15869"},"products":["n/a"],"published":"2018-08-25","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2023-50628","kev_date_added":null,"published":"2023-12-20"},{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2020-11894","kev_date_added":null,"published":"2020-04-19"},{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2020-11895","kev_date_added":null,"published":"2020-04-19"},{"cvss_score":9.1,"headline":"Information disclosure in n/a","id":"CVE-2019-16705","kev_date_added":null,"published":"2019-09-23"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2023-36239","kev_date_added":null,"published":"2023-06-22"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2023-31976","kev_date_added":null,"published":"2023-05-09"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2020-6628","kev_date_added":null,"published":"2020-01-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"An invalid memory address dereference in libming allows attackers to cause a segmentation fault and application crash, resulting in denial of service.","url":"https://insights.sbomify.com/CVE-2018-15870/"}