Skip to main content
Public proof of conceptFix available

CVE-2023-49298

A public proof of concept exists; no exploitation attested.

  • Published2023-11-24
  • WeaknessCWE-639

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2023-11-2419:15CVE publishedNVD

Versions per branch

NVD · CISA-ADP
Openzfsversion to verify
BranchAffectedFixed in
2.1≤ 2.1.13no fix published
2.2= 2.2.0no fix published
2.2≥ 2.2.0, ≤ 2.2.1no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • zfsCleanStartall versions · fixed in 2.2.1-r1
  • zfsAlpine:v3.24all versions · fixed in 2.2.1-r1and 2 other packages
  • zfsAlpine:v3.23all versions · fixed in 2.2.1-r1and 2 other packages
  • zfsAlpine:v3.22all versions · fixed in 2.2.1-r1and 2 other packages
  • zfsAlpine:v3.21all versions · fixed in 2.2.1-r1and 2 other packages
  • zfsAlpine:v3.20all versions · fixed in 2.2.1-r1and 2 other packages
  • zfsAlpine:v3.19all versions · fixed in 2.2.1-r1and 2 other packages
  • zfs-linuxUbuntu:Pro:18.04:LTSall versions · no fixed version listed

9 more package ranges on OSV.dev

Full record on NVD

Fix

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

  • EUVD-2023-53284same flawENISA EUVD · LicenseRef-ENISA-legal-notice
  • GHSA-mvg7-8xh2-47rfsame flawGitHub Advisory Database · CC-BY-4.0
  • DLA-3766-1advisory covering several CVEsDebian · LicenseRef-unstated
  • DLA-4114-1advisory covering several CVEsDebian · LicenseRef-unstated

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Published
2023-11-24
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-mvg7-8xh2-47rf

Frequently asked questions

What is CVE-2023-49298?

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.

Is CVE-2023-49298 actively exploited?

A proof-of-concept exploit exists for CVE-2023-49298, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2023-49298?

CVE-2023-49298 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.

Running zfs? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record