| Package | Affected versions | Patched versions |
|---|---|---|
| jq | < 1.8.2 | 1.8.2 |
| ai inference server | ≥ 3.2.0, < 3.2.2≥ 3.3.0, < 3.3.5 | 3.2.23.3.5 |
| ansible automation platform | = 2.0 | |
| ceph storage | = 4.0 | |
| codeready linux builder | = 10.0= 8.0= 9.0 | |
| codeready linux builder eus | = 10.0= 9.4= 9.6 | |
| openshift ai | ≥ 3.4, < 3.4.3 | 3.4.3 |
| openshift container platform | ≥ 4.12, < 4.12.92≥ 4.13, < 4.13.68≥ 4.14, < 4.14.68≥ 4.15, < 4.15.65≥ 4.16, < 4.16.64≥ 4.17, < 4.17.55≥ 4.18, < 4.18.44≥ 4.19, < 4.19.33 | 4.12.924.13.684.14.684.15.654.16.644.17.554.18.444.19.33 |
jq is a command-line JSON processor. In commits before 2f09060afab23fe9390cce7cb860b10416e1bf5f, the jv_parse_sized() API in libjq accepts a counted buffer with an explicit length parameter, but its error-handling path formats the input buffer using %s in jv_string_fmt(), which reads until a NUL terminator is found rather than respecting the caller-supplied length. This means that when malformed JSON is passed in a non-NUL-terminated buffer, the error construction logic performs an out-of-bounds read past the end of the buffer. The vulnerability is reachable by any libjq consumer calling jv_parse_sized() with untrusted input, and depending on memory layout, can result in memory disclosure or process termination. The issue has been patched in commit 2f09060afab23fe9390cce7cb860b10416e1bf5f.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free