Project jq-1.6-11.el8_10
content_copy
Name
jq
Epoch
0
Version
1.6
Release
11.el8_10
Website/URL
http://stedolan.github.io/jq/
License
MIT and ASL 2.0 and CC-BY and GPLv3
Build Time
2025-07-09 09:03:57
Build Host
builder-x86-03.inferitos.ru
Summary
Command-line JSON processor
Repositories
AppStream
Description
lightweight and flexible command-line JSON processor
jq is like sed for JSON data – you can use it to slice
and filter and map and transform structured data with
the same ease that sed, awk, grep and friends let you
play with text.
It is written in portable C, and it has zero runtime
dependencies.
jq can mangle the data format that you have into the
one that you want with very little effort, and the
program to do so is often shorter and simpler than
you'd expect.
Errata
INFSA-2025:10618
×
Found 2 old versions
* Mon Jun 30 2025 Tomas Halman <thalman@redhat.com> - 1.6-11
- Fix CVE-2025-48060 AddressSanitizer: stack-buffer-overflow in jq_fuzz_execute (jv_string_vfmt)
- Resolves: RHEL-92987
* Mon Jun 30 2025 Tomas Halman <thalman@redhat.com> - 1.6-10
- Fix CVE-2024-23337 jq has signed integer overflow in jv.c:jvp_array_write
- Resolves: RHEL-92968
* Fri May 03 2024 Tomas Halman <thalman@redhat.com> - 1.6-9
- Fix SAST findings in jq 1.6
- Resolves: RHEL-37827
* Fri Oct 13 2023 Tomas Halman <thalman@redhat.com> - 1.6-8
- Make jq 1.6 fast
- Resolves: RHEL-5052
* Wed Jul 26 2023 MSVSphere Packaging Team <packager@msvsphere.ru> - 1.6-7
- Rebuilt for MSVSphere 8.8
* Tue Mar 14 2023 Tomas Halman <thalman@redhat.com> - 1.6-7
- Fix jq segfault when used in threads
- Resolves: rhbz#2092160
* Fri Nov 04 2022 Tomas Halman <thalman@redhat.com> - 1.6-6
- Add mantest to the gating
- Related: rhbz#2049601
* Tue Oct 11 2022 Tomas Halman <thalman@redhat.com> - 1.6-5
- Remove rpath from jq binary
- Related: rhbz#2049601
* Tue Oct 11 2022 Tomas Halman <thalman@redhat.com> - 1.6-4
- Fix iterration problem for non decimal string
- Resolves: rhbz#2049601
* Mon Oct 04 2021 Tomas Halman <thalman@redhat.com>
- Fix big integers issue
- Resolves: bug#2008717