CVE-2013-20001 json
An issue was discovered in OpenZFS through 2.0.3.
published 5y ago modified 4mo ago also EUVD-2013-1988
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.1%
- EPSS 2.1% chance of exploitation in 30 days, percentile 81%
- public exploits
- 0
- none known
Summary
An issue was discovered in OpenZFS through 2.0.3. When an NFS share is exported to IPv6 addresses via the sharenfs feature, there is a silent failure to parse the IPv6 address data, and access is allowed to everyone. IPv6 restrictions from the configuration are not applied.
Patch / fix
- zfs-linux Debian 12 2.1.11-1+deb12u1
- zfs-linux Debian 14, Debian 13 2.2.2-1
debian advisories DEBIAN-CVE-2013-20001
- zfs-linux Ubuntu 20.04 LTS 0.8.3-1ubuntu12.16
- zfs-linux Ubuntu 22.04 LTS 2.1.5-1ubuntu6~22.04.2
ubuntu advisories UBUNTU-CVE-2013-20001
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Is CVE-2013-20001 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
2.11% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/openzfs/zfs/issues/1894#issuecomment-30693652 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
References
-
github.com
/openzfs/zfs/issues/1894#issuecomment-30693652
exploit, third-party-advisory
-
github.com
/openzfs/zfs/releases
release-notes, third-party-advisory
-
lists.debian.org
/debian-lts-announce/2024/03/msg00019.html
mailing-list
- lists.debian.org /debian-lts-announce/2025/04/msg00009.html
Sources
- CVE List CVE-2013-20001
- NVD CVE-2013-20001
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.