{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-53427 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2024-53427 is a high-severity memory corruption vulnerability in jqlang jq, published on 26 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-53427 and fix it if it is affected.\n\nWhat it is: CVE-2024-53427 is a high-severity memory corruption vulnerability in jqlang jq, published on 26 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-53427 exists.\n\nAffected product: jqlang jq. 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-2024-53427/ (Markdown: https://insights.sbomify.com/CVE-2024-53427/index.md)","id":"CVE-2024-53427","markdown":"https://insights.sbomify.com/CVE-2024-53427/index.md","name":"CVE-2024-53427","record":{"aliases":["ALPINE-CVE-2024-53427","AZL-57376","BELL-CVE-2024-53427","CVE-2024-23338","CVE-2025-25726","DEBIAN-CVE-2024-53427","ECHO-9e32-4170-f69d","GHSA-8mxc-vqrq-gcm8","GHSA-x6c3-qv5r-7q22","UBUNTU-CVE-2024-53427","openSUSE-SU-2025:15161-1"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"jq JSON processor","requires_auth":"none","summary":"A stack-based buffer overflow in jq allows attackers to execute arbitrary code or cause denial of service via crafted 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":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-843","name":"Access of Resource Using Incompatible Type"}],"description":"decNumberCopy in decNumber.c in jq through 1.7.1 does not properly consider that NaN is interpreted as numeric, which has a resultant stack-based buffer overflow and out-of-bounds write, as demonstrated by use of --slurp with subtraction, such as a filter of .-. when the input has a certain form of digit string with NaN (e.g., \"1 NaN123\" immediately followed by many more digits).","ecosystems":["openSUSE:Tumbleweed"],"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 jq","id":"CVE-2024-53427","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2024"},"n_packages":1,"n_references":5,"next":{"headline":"Denial of service in n/a","id":"CVE-2024-53429"},"packages":[{"ecosystem":"openSUSE:Tumbleweed","fixed":["1.7.1-3.1"],"introduced":["0"],"last_affected":[],"package":"jq","purl":"pkg:rpm/opensuse/jq\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2025:15161-1"}],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2024-53426"},"products":["jq"],"published":"2025-02-26","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":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.5,"headline":"Memory corruption in n/a","id":"CVE-2023-49355","kev_date_added":null,"published":"2023-12-11"},{"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":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"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-03-28","vendors":["jqlang"]},"summary":"A stack-based buffer overflow in jq allows attackers to execute arbitrary code or cause denial of service via crafted input.","url":"https://insights.sbomify.com/CVE-2024-53427/"}