{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-20452 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2018-20452 is a high-severity use after free vulnerability in n/a, published on 25 Dec 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-20452 and fix it if it is affected.\n\nWhat it is: CVE-2018-20452 is a high-severity use after free vulnerability in n/a, published on 25 Dec 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-20452 in the wild and no public exploit code.\n\nAffected product: n/a. 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-20452/ (Markdown: https://insights.sbomify.com/CVE-2018-20452/index.md)","id":"CVE-2018-20452","markdown":"https://insights.sbomify.com/CVE-2018-20452/index.md","name":"CVE-2018-20452","record":{"aliases":["DEBIAN-CVE-2018-20452","GHSA-3hq6-4m9g-pfg4","UBUNTU-CVE-2018-20452"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"libxls library","requires_auth":"none","summary":"Attackers can cause a crash or potentially execute code via a crafted file due to invalid memory management in libxls.","user_interaction":"required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"libxls","vendor":"libxls_project"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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":"The read_MSAT_body function in ole.c in libxls 1.4.0 has an invalid free that allows attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a crafted file, because of inconsistent memory management (new versus free) in ole2_read_header in ole.c.","ecosystems":[],"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 after free in n/a","id":"CVE-2018-20452","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2018-20453"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2018-20451"},"products":["n/a"],"published":"2018-12-25","related":[{"cvss_score":8.8,"headline":"Memory corruption in libxls","id":"CVE-2017-2910","kev_date_added":null,"published":"2020-12-02"},{"cvss_score":8.8,"headline":"Integer overflow in libxls","id":"CVE-2017-12108","kev_date_added":null,"published":"2018-04-24"},{"cvss_score":8.8,"headline":"Integer overflow in libxls","id":"CVE-2017-12109","kev_date_added":null,"published":"2018-04-24"},{"cvss_score":8.8,"headline":"Integer overflow in libxls","id":"CVE-2017-12110","kev_date_added":null,"published":"2017-11-20"},{"cvss_score":8.8,"headline":"Memory corruption in libxls","id":"CVE-2017-12111","kev_date_added":null,"published":"2017-11-20"},{"cvss_score":8.8,"headline":"Memory corruption in libxls","id":"CVE-2017-2897","kev_date_added":null,"published":"2017-11-20"}],"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":"Attackers can cause a crash or potentially execute code via a crafted file due to invalid memory management in libxls.","url":"https://insights.sbomify.com/CVE-2018-20452/"}