{"answers":{"affected":"2 open source packages ship an affected version, including node-twain.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-21525 exists.","fix":"No fix has been published for CVE-2024-21525 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-21525 is a high-severity memory corruption vulnerability in node-twain, published on 10 Jul 2024. 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-2024-21525 and fix it if it is affected.\n\nWhat it is: CVE-2024-21525 is a high-severity memory corruption vulnerability in node-twain, published on 10 Jul 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-21525 exists.\n\nAffected packages and fixed versions:\n- node-twain (npm): affected all versions up to 0.0.16; no fix listed\n- node-twain (npm): affected all versions up to 0.0.16; no fix listed\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-2024-21525/ (Markdown: https://insights.sbomify.com/CVE-2024-21525/index.md)","id":"CVE-2024-21525","markdown":"https://insights.sbomify.com/CVE-2024-21525/index.md","name":"CVE-2024-21525","record":{"aliases":["GHSA-wxr3-2hgv-qm8f"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js TWAIN library","requires_auth":"none","summary":"A buffer overflow in node-twain allows attackers to cause denial of service or potentially execute code via long input strings.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L/E:P","version":"3.1"},"cwes":[{"id":"CWE-703","name":"Improper Check or Handling of Exceptional Conditions"}],"description":"All versions of the package node-twain are vulnerable to Improper Check or Handling of Exceptional Conditions due to the length of the source data not being checked. Creating a new twain.TwainSDK with a productName or productFamily, manufacturer, version.info property of length \u003e= 34 chars leads to a buffer overflow vulnerability.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"node-twain vulnerable to Improper Check or Handling of Exceptional Conditions","id":"CVE-2024-21525","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"memory_corruption","year":"2024"},"n_packages":2,"n_references":2,"next":{"headline":"speaker vulnerable to Denial of Service","id":"CVE-2024-21526"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.0.16"],"package":"node-twain","purl":null,"source":"GHSA-wxr3-2hgv-qm8f"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.0.16"],"package":"node-twain","purl":"pkg:npm/node-twain","source":"GHSA-wxr3-2hgv-qm8f"}],"prev":{"headline":"node-stringbuilder vulnerable to Out-of-bounds Read","id":"CVE-2024-21524"},"products":["node-twain"],"published":"2024-07-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"2024-08-01","vendors":["n/a"]},"summary":"A buffer overflow in node-twain allows attackers to cause denial of service or potentially execute code via long input strings.","url":"https://insights.sbomify.com/CVE-2024-21525/"}