{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-49355 exists.","fix":"Apply the vendor's patch.","what":"CVE-2023-49355 is a high-severity memory corruption vulnerability in n/a, published on 11 Dec 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-49355 and fix it if it is affected.\n\nWhat it is: CVE-2023-49355 is a high-severity memory corruption vulnerability in n/a, published on 11 Dec 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-49355 exists.\n\nAffected product: n/a. 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-49355/ (Markdown: https://insights.sbomify.com/CVE-2023-49355/index.md)","id":"CVE-2023-49355","markdown":"https://insights.sbomify.com/CVE-2023-49355/index.md","name":"CVE-2023-49355","record":{"aliases":["DEBIAN-CVE-2023-49355","GHSA-4c3j-f924-rc7v"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"jq JSON processor","requires_auth":"none","summary":"A one-byte out-of-bounds write in jq's decToString function allows attackers to cause memory corruption via crafted scientific notation input.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"jq","vendor":"jqlang"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","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-787","name":"Out-of-bounds Write"}],"description":"decToString in decNumber/decNumber.c in jq 88f01a7 has a one-byte out-of-bounds write via the \" []-1.2e-1111111111\" input. NOTE: this is not the same as CVE-2023-50246. The CVE-2023-50246 71c2ab5 reference mentions -10E-1000010001, which is not in normalized scientific notation.","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":"Memory corruption in n/a","id":"CVE-2023-49355","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2023-49356"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2023-49351"},"products":["n/a"],"published":"2023-12-11","related":[{"cvss_score":8.2,"headline":"jq: Integer overflow in jvp_string_append() allows Heap-based Buffer Overflow","id":"CVE-2026-32316","kev_date_added":null,"published":"2026-04-13"},{"cvss_score":8.1,"headline":"Memory corruption in jq","id":"CVE-2024-53427","kev_date_added":null,"published":"2025-02-26"},{"cvss_score":7.7,"headline":"AddressSanitizer: stack-buffer-overflow in jq_fuzz_execute (jv_string_vfmt)","id":"CVE-2025-48060","kev_date_added":null,"published":"2025-05-21"},{"cvss_score":7.1,"headline":"jq --rawfile invalid-state reuse after String too long causes heap-buffer-overflow","id":"CVE-2026-49839","kev_date_added":null,"published":"2026-06-25"},{"cvss_score":6.9,"headline":"jq: potential integer overflow in jvp_string_append","id":"CVE-2026-54679","kev_date_added":null,"published":"2026-06-25"},{"cvss_score":6.9,"headline":"jq: Out-of-Bounds Read in jv_parse_sized() Error Formatting for Non-NUL-Terminated Counted Buffers","id":"CVE-2026-39979","kev_date_added":null,"published":"2026-04-13"}],"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":"2024-10-09","vendors":["n/a"]},"summary":"A one-byte out-of-bounds write in jq's decToString function allows attackers to cause memory corruption via crafted scientific notation input.","url":"https://insights.sbomify.com/CVE-2023-49355/"}