{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-45663 exists.","fix":"Apply the vendor's patch.","what":"CVE-2023-45663 is a medium-severity 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-45663 and fix it if it is affected.\n\nWhat it is: CVE-2023-45663 is a medium-severity 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-45663 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-45663/ (Markdown: https://insights.sbomify.com/CVE-2023-45663/index.md)","id":"CVE-2023-45663","markdown":"https://insights.sbomify.com/CVE-2023-45663/index.md","name":"CVE-2023-45663","record":{"aliases":["DEBIAN-CVE-2023-45663","UBUNTU-CVE-2023-45663"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"stb image library","requires_auth":"none","summary":"An attacker can read uninitialized memory by providing a crafted TGA image to the stb_image library, potentially exposing sensitive data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"stb_image.h","vendor":"nothings"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-908","name":"Use of Uninitialized Resource"}],"description":"stb_image is a single file MIT licensed library for processing images. The stbi__getn function reads a specified number of bytes from context (typically a file) into the specified buffer. In case the file stream points to the end, it returns zero. There are two places where its return value is not checked: In the `stbi__hdr_load` function and in the `stbi__tga_load` function. The latter of the two is likely more exploitable as an attacker may also control the size of an uninitialized buffer.","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":"Disclosure of uninitialized memory in stbi__tga_load in stb_image","id":"CVE-2023-45663","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":7,"next":{"headline":"Double-free in stbi__load_gif_main_outofmem in stb_image","id":"CVE-2023-45664"},"packages":[],"prev":{"headline":"Multi-byte read heap buffer overflow in stbi__vertical_flip in stb_image","id":"CVE-2023-45662"},"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":7.3,"headline":"Possible double-free or memory leak in stbi__load_gif_main in stb_image","id":"CVE-2023-45666","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":"An attacker can read uninitialized memory by providing a crafted TGA image to the stb_image library, potentially exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2023-45663/"}