{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-45666 exists.","fix":"Apply the vendor's patch.","what":"CVE-2023-45666 is a high-severity use after free vulnerability in nothings stb, published on 20 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-45666 and fix it if it is affected.\n\nWhat it is: CVE-2023-45666 is a high-severity use after free vulnerability in nothings stb, published on 20 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-45666 exists.\n\nAffected product: nothings stb. 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-2023-45666/ (Markdown: https://insights.sbomify.com/CVE-2023-45666/index.md)","id":"CVE-2023-45666","markdown":"https://insights.sbomify.com/CVE-2023-45666/index.md","name":"CVE-2023-45666","record":{"aliases":["DEBIAN-CVE-2023-45666","UBUNTU-CVE-2023-45666"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"stb image library","requires_auth":"none","summary":"A double-free or memory leak in stb_image's GIF loader can cause crashes or potential code execution when processing malformed images.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"stb_image.h","vendor":"nothings"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-415","name":"Double Free"}],"description":"stb_image is a single file MIT licensed library for processing images.  It may look like `stbi__load_gif_main` doesn’t give guarantees about the content of output value `*delays` upon failure. Although it sets `*delays` to zero at the beginning, it doesn’t do it in case the image is not recognized as GIF and a call to `stbi__load_gif_main_outofmem` only frees possibly allocated memory in `*delays` without resetting it to zero. Thus it would be fair to say the caller of `stbi__load_gif_main` is responsible to free the allocated memory in `*delays` only if `stbi__load_gif_main` returns a non null value. However at the same time the function may return null value, but fail to free the memory in `*delays` if internally `stbi__convert_format` is called and fails. Thus the issue may lead to a memory leak if the caller chooses to free `delays` only when `stbi__load_gif_main` didn’t fail or to a double-free if the `delays` is always freed","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Possible double-free or memory leak in stbi__load_gif_main in stb_image","id":"CVE-2023-45666","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2023"},"n_packages":0,"n_references":6,"next":{"headline":"Null pointer dereference because of an uninitialized variable in stb_image","id":"CVE-2023-45667"},"packages":[],"prev":{"headline":"This CVE is a duplicate of another CVE.","id":"CVE-2023-45665"},"products":["stb"],"published":"2023-10-20","related":[{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2019-19777","kev_date_added":null,"published":"2019-12-13"},{"cvss_score":7.3,"headline":"Double-free in stbi__load_gif_main_outofmem in stb_image","id":"CVE-2023-45664","kev_date_added":null,"published":"2023-10-20"},{"cvss_score":6.5,"headline":"Use after free in n/a","id":"CVE-2023-43281","kev_date_added":null,"published":"2023-10-24"},{"cvss_score":6.5,"headline":"Wild address read in stbi__gif_load_next in stb_image","id":"CVE-2023-45661","kev_date_added":null,"published":"2023-10-20"},{"cvss_score":6.5,"headline":"Multi-byte read heap buffer overflow in stbi__vertical_flip in stb_image","id":"CVE-2023-45662","kev_date_added":null,"published":"2023-10-20"},{"cvss_score":6.5,"headline":"Denial of service in n/a","id":"CVE-2019-20056","kev_date_added":null,"published":"2019-12-29"}],"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-13","vendors":["nothings"]},"summary":"A double-free or memory leak in stb_image's GIF loader can cause crashes or potential code execution when processing malformed images.","url":"https://insights.sbomify.com/CVE-2023-45666/"}