{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-20652 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-20652 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-20652 is a medium-severity denial of service vulnerability in n/a, published on 1 Jan 2019. 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-20652 and fix it if it is affected.\n\nWhat it is: CVE-2018-20652 is a medium-severity denial of service vulnerability in n/a, published on 1 Jan 2019. 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-20652 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-20652/ (Markdown: https://insights.sbomify.com/CVE-2018-20652/index.md)","id":"CVE-2018-20652","markdown":"https://insights.sbomify.com/CVE-2018-20652/index.md","name":"CVE-2018-20652","record":{"aliases":["GHSA-j56v-9w7f-7jg3"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"tinyexr library","requires_auth":"none","summary":"Remote attackers can cause a denial-of-service via crafted input leading to excessive memory allocation in the tinyexr library.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"tinyexr","vendor":"tinyexr_project"}],"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-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"An attempted excessive memory allocation was discovered in the function tinyexr::AllocateImage in tinyexr.h in tinyexr v0.9.5. Remote attackers could leverage this vulnerability to cause a denial-of-service via crafted input, which leads to an out-of-memory exception.","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-20652","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in WhatsApp Business for iOS","id":"CVE-2018-20655"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2018-20651"},"products":["n/a"],"published":"2019-01-01","related":[{"cvss_score":9.8,"headline":"Null dereference in n/a","id":"CVE-2018-12688","kev_date_added":null,"published":"2018-06-22"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2018-12503","kev_date_added":null,"published":"2018-06-16"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2018-12092","kev_date_added":null,"published":"2018-06-11"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2018-12064","kev_date_added":null,"published":"2018-06-08"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2022-34300","kev_date_added":null,"published":"2022-06-22"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2022-38529","kev_date_added":null,"published":"2022-09-06"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2020-18428","kev_date_added":null,"published":"2021-07-26"}],"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":"Remote attackers can cause a denial-of-service via crafted input leading to excessive memory allocation in the tinyexr library.","url":"https://insights.sbomify.com/CVE-2018-20652/"}