Categories
CVE-2021-29482

Vulnerability in github.com/ulikunitz/xz (CVE-2021-29482)

Summary

Vulnerability in github.com/ulikunitz/xz (CVE-2021-29482). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.5.8 or later.

Original description

The description as published by the source.

Impact

xz is a compression and decompression library focusing on the xz format completely written in Go. The function readUvarint used to read the xz container format may not terminate a loop provide malicous input.

Patches

The problem has been fixed in release v0.5.8.

Workarounds

Limit the size of the compressed file input to a reasonable size for your use case.

References

The standard library had recently the same issue and got the CVE-2020-16845 allocated.

For more information

If you have any questions or comments about this advisory:

  • Open an issue in xz.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2021-29482 has been found in github.com/ulikunitz/xz.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/ulikunitz/xz to 0.5.8 or later.
If unsure, ask your IT team or search "github.com/ulikunitz/xz CVE-2021-29482" on the vendor's site.

CVE-2021-29482 (github.com/ulikunitz/xz) — CWE-835
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.5.8 — apply immediately
Workaround: Limit the size of the compressed file input to a reasonable size for your use case.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-835) exists in github.com/ulikunitz/xz.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/ulikunitz/xz.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.5.8.

🛡️ Workaround

Workaround: Limit the size of the compressed file input to a reasonable size for your use case.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/ulikunitz/xz' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'github.com/ulikunitz/xz' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/ulikunitz/xz を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate
    Limit the size of the compressed file input to a reasonable size for your use case.

    パッチが適用されるまでの応急処置として、Limit the size of the compressed file input to a reasonable size for your use case. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch
    Upgrade github.com/ulikunitz/xz to 0.5.8

    ステージング環境で 0.5.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Go github.com/ulikunitz/xz
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.5.8"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details