{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-9145 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-9145 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-9145 is a medium-severity denial of service vulnerability in Exiv2 Exiv2, published on 30 Mar 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-9145 and fix it if it is affected.\n\nWhat it is: CVE-2018-9145 is a medium-severity denial of service vulnerability in Exiv2 Exiv2, published on 30 Mar 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-9145 in the wild and no public exploit code.\n\nAffected product: Exiv2 Exiv2. 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-9145/ (Markdown: https://insights.sbomify.com/CVE-2018-9145/index.md)","id":"CVE-2018-9145","markdown":"https://insights.sbomify.com/CVE-2018-9145/index.md","name":"CVE-2018-9145","record":{"aliases":["GHSA-v97h-jqp9-pcjg"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Exiv2 image metadata library","requires_auth":"none","summary":"A large buffer size in the DataBuf constructor can cause a SIGABRT, leading to a denial of service in applications using Exiv2.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"exiv2","vendor":"exiv2"}],"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-20","name":"Improper Input Validation"}],"description":"In the DataBuf class in include/exiv2/types.hpp in Exiv2 0.26, an issue exists in the constructor with an initial buffer size. A large size value may lead to a SIGABRT during an attempt at memory allocation. NOTE: some third parties have been unable to reproduce the SIGABRT when using the 4-DataBuf-abort-1 PoC file.","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":"Denial of service in n/a","id":"CVE-2018-9145","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"exiv2:exiv2","products":["exiv2:exiv2"],"type":"denial_of_service","year":"2018"},"n_packages":0,"n_references":4,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-9147"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2018-9144"},"products":["n/a"],"published":"2018-03-30","related":[{"cvss_score":8.8,"headline":"Out-of-bounds write in exiv2","id":"CVE-2023-44398","kev_date_added":null,"published":"2023-11-06"},{"cvss_score":8.8,"headline":"Denial of service in n/a","id":"CVE-2019-9143","kev_date_added":null,"published":"2019-02-25"},{"cvss_score":8.8,"headline":"Denial of service in n/a","id":"CVE-2019-9144","kev_date_added":null,"published":"2019-02-25"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2018-14046","kev_date_added":null,"published":"2018-07-13"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2017-12955","kev_date_added":null,"published":"2017-08-18"},{"cvss_score":8.1,"headline":"Memory corruption in n/a","id":"CVE-2018-14338","kev_date_added":null,"published":"2018-07-17"},{"cvss_score":8.1,"headline":"Information disclosure in n/a","id":"CVE-2018-9305","kev_date_added":null,"published":"2018-04-04"}],"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":"A large buffer size in the DataBuf constructor can cause a SIGABRT, leading to a denial of service in applications using Exiv2.","url":"https://insights.sbomify.com/CVE-2018-9145/"}