SUSE-SU-2023:4000-1 Security update for yq
Not scored
Published
Check this codebase for SUSE-SU-2023:4000-1 and fix it if it is affected.
What it is: SUSE-SU-2023:4000-1 is a vulnerability in yq, published on 6 Oct 2023.
Exploitation: There is no known exploitation of SUSE-SU-2023:4000-1 in the wild and no public exploit code.
Affected product: yq. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/SUSE-SU-2023-4000-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2023-4000-1/index.md)
Update yq to fix parsing bugs and potential crashes, ensuring stability for developers using this command-line tool.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- Available
What is SUSE-SU-2023:4000-1?
SUSE-SU-2023:4000-1 is a vulnerability in yq, published on 6 Oct 2023.
Official description
This update for yq fixes the following issues:
yq was updated to 4.35.2 (bsc#1215808):
- Fixed number parsing as float bug in JSON #1756
- Fixed string, null concatenation consistency #1712
- Fixed expression parsing issue #1711
Update to 4.35.1:
- Added Lua output support
- Added BSD checksum format
Update to 4.34.1:
- Added shell output format
- Fixed nil pointer dereference
Update to 4.33.3:
- Fixed bug when splatting empty array #1613
- Added scalar output for TOML (#1617)
- Fixed passing of read-only context in pipe (partial fix for #1631)
Update to 4.33.2:
- Add
--nul-output|-0flag to separate element with NUL character (#1550) Thanks @vaab! - Add removable-media interface plug declaration to the snap packaging(#1618) Thanks @brlin-tw!
- Scalar output now handled in csv, tsv and property files
Update to 4.33.1:
- Added read-only TOML support! #1364. Thanks @pelletier for making your API available in your toml lib :)
- Added warning when auto detect by file type is outputs JSON
Update to 4.32.2:
- Fixes parsing terraform tfstate files results in 'unknown' format
- Added divide and modulo operators (#1593)
- Add support for decoding base64 strings without padding
- Add filter operation (#1588) - thanks @rbren!
- Detect input format based on file name extension (#1582)
- Auto output format when input format is automatically detected
- Fixed npe in log #1596
- Improved binary file size!
Update to 4.31.2:
- Fixed merged anchor reference problem #1482
- Fixed xml encoding of ProcInst #1563, improved XML comment handling
- Allow build without json and xml support (#1556) Thanks
Update to 4.31.1:
- Added shuffle command #1503
- Added ability to sort by multiple fields #1541
- Added @sh encoder #1526
- Added @uri/@urid encoder/decoder #1529
- Fixed date comparison with string date #1537
- Added from_unix/to_unix Operators
Which versions are affected by SUSE-SU-2023:4000-1?
Linux distribution packages (2)
yq SUSE:Linux Enterprise Module for Package Hub 15 SP5 | All versions | 4.35.2-150500.3.3.1 |
yq openSUSE:Leap 15.5 | All versions | 4.35.2-150500.3.3.1 |
How do I fix SUSE-SU-2023:4000-1?
Upgrade to a fixed version.
Is SUSE-SU-2023:4000-1 being exploited?
There is no known exploitation of SUSE-SU-2023:4000-1 in the wild and no public exploit code.