Vulnerability in zfs-linux (UBUNTU-CVE-2023-49298)

Summary

Vulnerability in zfs-linux (UBUNTU-CVE-2023-49298). Data can be tampered with by attackers. Mitigation: upgrade to 0.8.3-1ubuntu12.17 or later.

Original description

The description as published by the source.

OpenZFS through 2.1.13 and 2.2.x through 2.2.1, in certain scenarios involving applications that try to rely on efficient copying of file data, can replace file contents with zero-valued bytes and thus potentially disable security mechanisms. NOTE: this issue is not always security related, but can be security related in realistic situations. A possible example is cp, from a recent GNU Core Utilities (coreutils) version, when attempting to preserve a rule set for denying unauthorized access. (One might use cp when configuring access control, such as with the /etc/hosts.deny file specified in the IBM Support reference.) NOTE: this issue occurs less often in version 2.2.1, and in versions before 2.1.4, because of the default configuration in those versions.

Source: OSV.dev (Open Source Vulnerabilities) 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 UBUNTU-CVE-2023-49298 has been found in zfs-linux.
Data can be tampered with by attackers.
What to do: upgrade zfs-linux to 0.8.3-1ubuntu12.17 or later.
If unsure, ask your IT team or search "zfs-linux UBUNTU-CVE-2023-49298" on the vendor's site.

UBUNTU-CVE-2023-49298 (zfs-linux)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.8.3-1ubuntu12.17 — apply immediately
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 (unclassified) exists in zfs-linux.

📍 Affected scope

Check the vendor advisory for the affected versions of zfs-linux.

🔥 Severity

Severity: ?. Data can be tampered with by attackers.

🔧 How to fix

Update to 0.8.3-1ubuntu12.17.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'zfs-linux' . 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
Identify exposure identify
```
grep -r 'zfs-linux' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で zfs-linux を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade zfs-linux to 0.8.3-1ubuntu12.17
```
ステージング環境で 0.8.3-1ubuntu12.17 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Ubuntu:16.04:LTS zfs-linux

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:Pro:18.04:LTS zfs-linux

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:20.04:LTS zfs-linux

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.8.3-1ubuntu12.17"}]}]

Ubuntu:22.04:LTS zfs-linux

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.1.5-1ubuntu6~22.04.4"}]}]

Ubuntu:24.04:LTS zfs-linux

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.2-0ubuntu2"}]}]

References

report ubuntu.com
report news.ycombinator.com
report web.archive.org
report github.com
report gist.github.com
report cve.org