{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-45681 exists.","fix":"Apply the vendor's patch.","what":"CVE-2023-45681 is a high-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-45681 and fix it if it is affected.\n\nWhat it is: CVE-2023-45681 is a high-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-45681 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-45681/ (Markdown: https://insights.sbomify.com/CVE-2023-45681/index.md)","id":"CVE-2023-45681","markdown":"https://insights.sbomify.com/CVE-2023-45681/index.md","name":"CVE-2023-45681","record":{"aliases":["DEBIAN-CVE-2023-45681","UBUNTU-CVE-2023-45681"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Vorbis audio library","requires_auth":"none","summary":"An integer overflow in stb_vorbis allows attackers to trigger a heap buffer overflow via crafted files, potentially leading to arbitrary code execution.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"stb_vorbis.c","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-190","name":"Integer Overflow or Wraparound"},{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"stb_vorbis is a single file MIT licensed library for processing ogg vorbis files. A crafted file may trigger memory write past an allocated heap buffer in `start_decoder`. The root cause is a potential integer overflow in `sizeof(char*) * (f-\u003ecomment_list_length)` which may make `setup_malloc` allocate less memory than required. Since there is another integer overflow an attacker may overflow it too to force `setup_malloc` to return 0 and make the exploit more reliable. This issue may lead to code execution.","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":"Out of bounds heap buffer write in stb_vorbis","id":"CVE-2023-45681","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2023"},"n_packages":0,"n_references":5,"next":{"headline":"Wild address read in vorbis_decode_packet_rest in stb_vorbis","id":"CVE-2023-45682"},"packages":[],"prev":{"headline":"Null pointer dereference in vorbis_deinit in stb_vorbis","id":"CVE-2023-45680"},"products":["stb"],"published":"2023-10-20","related":[{"cvss_score":7.3,"headline":"Multi-byte write heap buffer overflow in start_decoder in stb_vorbis","id":"CVE-2023-45676","kev_date_added":null,"published":"2023-10-20"},{"cvss_score":7.3,"headline":"Heap buffer out of bounds write in start_decoder in stb_vorbis","id":"CVE-2023-45677","kev_date_added":null,"published":"2023-10-20"},{"cvss_score":7.3,"headline":"Attempt to free an uninitialized memory pointer in vorbis_deinit in stb_vorbis","id":"CVE-2023-45679","kev_date_added":null,"published":"2023-10-20"},{"cvss_score":6.5,"headline":"0 byte write heap buffer overflow in start_decoder in stb_vorbis","id":"CVE-2023-45675","kev_date_added":null,"published":"2023-10-20"},{"cvss_score":6.5,"headline":"Off-by-one heap buffer write in start_decoder in stb_vorbis","id":"CVE-2023-45678","kev_date_added":null,"published":"2023-10-20"},{"cvss_score":5.3,"headline":"Nothings stb stb_vorbis.c setup_free allocation of resources","id":"CVE-2026-5316","kev_date_added":null,"published":"2026-04-02"}],"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-02-13","vendors":["nothings"]},"summary":"An integer overflow in stb_vorbis allows attackers to trigger a heap buffer overflow via crafted files, potentially leading to arbitrary code execution.","url":"https://insights.sbomify.com/CVE-2023-45681/"}