# CVE-2023-49298: Other in n/a

> OpenZFS may zero out file contents during copy operations, potentially disabling security mechanisms like access control lists.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Nov 2023
- **Updated:** 3 Nov 2025
- **Also known as:** ALPINE-CVE-2023-49298, DEBIAN-CVE-2023-49298, GHSA-mvg7-8xh2-47rf, UBUNTU-CVE-2023-49298

## What is CVE-2023-49298?

CVE-2023-49298 is a high-severity vulnerability in n/a, published on 24 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2023-49298?

It affects 1 product.


Products: Openzfs Openzfs.

## How do I fix CVE-2023-49298?

Upgrade to a fixed version.

## Is CVE-2023-49298 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-49298 exists.

## Other vulnerabilities in n/a

- [CVE-2020-24716](https://insights.sbomify.com/CVE-2020-24716/): Misconfiguration in n/a (high 7.8)
- [CVE-2020-24717](https://insights.sbomify.com/CVE-2020-24717/): Auth bypass in n/a (high 7.8)
- [CVE-2013-20001](https://insights.sbomify.com/CVE-2013-20001/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-49298 and fix it if it is affected.

What it is: CVE-2023-49298 is a high-severity vulnerability in n/a, published on 24 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-49298 exists.

Affected product: n/a. 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/CVE-2023-49298/ (Markdown: https://insights.sbomify.com/CVE-2023-49298/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-49298
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-49298
- OSV: https://osv.dev/vulnerability/CVE-2023-49298

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-49298/
Summaries are generated and may contain mistakes; the official description above is the record.