Threats / Oracle / CVE-2020-14871
CVE-2020-14871
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Oracle Solaris and Zettabyte File System (ZFS) vulnerability
Oracle Solaris and ZFS contain an out-of-bounds write vulnerability affecting confidentiality, integrity, and availability. The flaw is actively exploited in the wild.
Verdict
Today item — known-exploited.
An out-of-bounds write in Oracle Solaris and ZFS enables memory corruption with high impact across confidentiality, integrity, and availability. Active exploitation in the wild indicates immediate risk to deployed systems.
CISA KEV Yes · 2021-11-035EPSS 0.79842 (verify live)6Exploit Weaponized · public PoC7CVSS 103CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
2 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03).
Probability (EPSS)
EPSS 0.79842 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 10 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H) · Affected: Oracle, Solaris and Zettabyte File System (ZFS). Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-787 Out-of-bounds Write — weakness family: Memory safety.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 378 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft input that triggers an out-of-bounds write in the vulnerable code path, corrupting adjacent memory regions.
Business
System memory integrity is compromised, creating conditions for privilege escalation or denial of service.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I leverage the memory corruption to escalate privileges or execute arbitrary code with elevated context.
Business
Attackers gain unauthorized access to sensitive data and system controls, violating confidentiality and integrity.
3
Lateral reach — past segmentation narrative 3
Attacker
I maintain persistence or pivot to other systems using the compromised host as a foothold.
Business
Infrastructure availability is degraded; incident response and recovery costs escalate across affected deployments.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05