{"answers":{"affected":"2 open source packages ship an affected version, including detect-character-encoding. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-39157 in the wild and no public exploit code.","fix":"Upgrade detect-character-encoding to 0.7.0 or later.","what":"CVE-2021-39157 is a high-severity denial of service vulnerability in sonicdoe detect-character-encoding, published on 24 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-39157 and fix it if it is affected.\n\nWhat it is: CVE-2021-39157 is a high-severity denial of service vulnerability in sonicdoe detect-character-encoding, published on 24 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-39157 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- detect-character-encoding (npm): affected all versions; fixed in 0.7.0\n- detect-character-encoding (npm): affected all versions; fixed in 0.7.0\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-2021-39157/ (Markdown: https://insights.sbomify.com/CVE-2021-39157/index.md)","id":"CVE-2021-39157","markdown":"https://insights.sbomify.com/CVE-2021-39157/index.md","name":"CVE-2021-39157","record":{"aliases":["GHSA-jqfh-8hw5-fqjr"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js encoding library","requires_auth":"none","summary":"An attacker can crash the Node.js process by providing data that matches no charset, requiring users to upgrade the library.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"detect-character-encoding","vendor":"detect-character-encoding_project"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-755","name":"Improper Handling of Exceptional Conditions"}],"description":"detect-character-encoding is an open source character encoding inspection library. In detect-character-encoding v0.6.0 and earlier, data matching no charset causes the Node.js process to crash. The problem has been patched in [detect-character-encoding v0.7.0](https://github.com/sonicdoe/detect-character-encoding/releases/tag/v0.7.0). No workaround are available and all users should update to resolve this issue.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Improper Handling of Exceptional Conditions in detect-character-encoding","id":"CVE-2021-39157","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2021"},"n_packages":2,"n_references":3,"next":{"headline":"Dependency injection in NVCaffe","id":"CVE-2021-39158"},"packages":[{"ecosystem":"npm","fixed":["0.7.0"],"introduced":["0"],"last_affected":[],"package":"detect-character-encoding","purl":null,"source":"GHSA-jqfh-8hw5-fqjr"},{"ecosystem":"npm","fixed":["0.7.0"],"introduced":["0"],"last_affected":[],"package":"detect-character-encoding","purl":"pkg:npm/detect-character-encoding","source":"GHSA-jqfh-8hw5-fqjr"}],"prev":{"headline":"Fragments in Path May Lead to Authorization Policy Bypass","id":"CVE-2021-39156"},"products":["detect-character-encoding"],"published":"2021-08-24","related":[{"cvss_score":7.5,"headline":"Missing Release of Memory after Effective Lifetime in detect-character-encoding","id":"CVE-2021-39176","kev_date_added":null,"published":"2021-08-31"}],"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":"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-04","vendors":["sonicdoe"]},"summary":"An attacker can crash the Node.js process by providing data that matches no charset, requiring users to upgrade the library.","url":"https://insights.sbomify.com/CVE-2021-39157/"}