CVE-2024-53427

Jqlang Jq type confusion

8.1 HIGHPublic exploitEPSS 0.36%

Published26 Feb 2025

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).

CVSS 3.1 breakdown

Attack vectorLocal

Attack complexityHigh

Privileges requiredNone

User interactionNone

ScopeChanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Affected products

Jqlang Jq≤ 1.7.1

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

Patch & vendor advisories

References

https://gist.github.com/Ekkosun/a83870ce7f3b7813b9b462a395e8ad92Third Party Advisory
https://github.com/jqlang/jq/blob/71c2ab509a8628dbbad4bc7b3f98a64aa90d3297/src/decNumber/decNumber.c#L3375Product
https://github.com/jqlang/jq/issues/3196ExploitIssue TrackingVendor Advisory
https://github.com/jqlang/jq/issues/3296Issue TrackingVendor Advisory
https://github.com/jqlang/jq/security/advisories/GHSA-x6c3-qv5r-7q22Vendor Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2024-53427 being actively exploited?

CVE-2024-53427 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.36%.

How severe is CVE-2024-53427?

CVE-2024-53427 has a CVSS 3.1 base score of 8.1, rated high. EPSS estimates a 0.36% probability of exploitation.

Which products are affected by CVE-2024-53427?

Affected products include Jqlang Jq.

How do I fix CVE-2024-53427?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-53427 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.