CVE Intelligence
Medium Info disclosure

CVE-2020-14145 — The client side in OpenSSH 5.7 through 8.3 has an Observable Discrepancy leading to an...

The client side in OpenSSH 5.7 through 8.4 has an Observable Discrepancy leading to an information leak in the algorithm negotiation. This allows man-in-the-middle attackers to target initial connection attempts (where no host key for the server has been cached by the client). NOTE: some reports state that 8.5 and 8.6 are also affected.

Published Jun 29, 2020 · Updated Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: mitre

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 2.9% (30-day exploitation probability)+13
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
2.95%
ahead of 87% of scored CVEs · Oct 14, 2026
Affects
Netapp
Active Iq Unified Manager and 8 more
CVSS base
5.9
Medium · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — www.openwall.com (NIST National Vulnerability Database)
  • Documented patch — anongit.mindrot.org (NIST National Vulnerability Database)
  • Documented patch — github.com (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Netapp Active Iq Unified Manager, Netapp Aff A700s Firmware, Netapp Hci Compute Node…).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. Apply the fixed version or the patch documented under Remediation.
  4. Search available logs for exploit probes matching the vulnerability class (info disclosure), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Netapp Active Iq Unified Manager ≥ 9.5 Vulnerable NIST National Vulnerability Database
Netapp Aff A700s Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp Hci Compute Node versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp Hci Management Node versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp Hci Storage Node versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp Ontap Select Deploy Administration Utility versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp Solidfire versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp Steelstore Cloud Integrated Storage versions not specified by the source Vulnerable NIST National Vulnerability Database
Openbsd Openssh ≥ 5.7 and < 8.4version 8.4version 8.5version 8.6 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
5.9 CVSS 3.1 Medium 2.2 3.6 nvd@nist.gov via NIST National Vulnerability Database
5.9 CVSS 3.1 Medium 2.2 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
5.9 CVSS 3.1 Medium — — GitHub, Inc. via GitHub Security Advisories
5.9 CVSS 3.1 Medium — — CISA-ADP via CVE Program (cve.org) e CISA ADP
4.3 CVSS 2.0 Medium 8.6 2.9 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-203 · Observable Discrepancy

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 2.95%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Look for anomalous data read/export volumes and access to sensitive records.
web/proxy/WAF logsnetwork IDS/IPSapplication logsauthentication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 14, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 14, 2026
  • Fix documented
    Oct 14, 2026 · NIST National Vulnerability Database
  • Affected products added · openbsd/openssh, netapp/aff a700s firmware, netapp/active iq unified manager, netapp/hci management node, netapp/ontap s
    Oct 14, 2026 · NIST National Vulnerability Database
  • CVSS changed · 5.9
    Oct 14, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 14, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 14, 2026 · Alertas do Telegram
  • 2020
  • CVE published
    Jun 29, 2020 · mitre

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 14, 2026 – Oct 14, 2026
  • 1× Official description updated · Oct 14, 2026 – Oct 14, 2026

References

13 on the record

Elsewhere on this site

Netapp
every CVE for this vendor
Info disclosure
same class
CWE-203
other pages naming this weakness

Related CVEs (same products)

  • High CVE-2026-106583 In ssh in OpenSSH before 10.6, a $ or \ character can occur in a command-line username, leading... 8d
  • Low CVE-2026-106588 In sshd in OpenSSH through 10.6, use of the macOS 27 (or later) SDK has the side effect… 9d
  • Low CVE-2026-106589 In sshd in OpenSSH through 10.6, in certain environments such as QNX 6 and SCO… 9d
  • Low CVE-2026-106587 Type Confusion in Openbsd Openssh 9d
  • Low CVE-2026-106584 In ssh-keygen in OpenSSH before 10.6, certificates could have incorrect expiration times… 9d
  • Low CVE-2026-106582 In sshd and ssh in OpenSSH before 10.6, an LZ77 dictionary coder can be used even though… 9d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2020-14145 is "The client side in OpenSSH 5.7 through 8.3 has an Observable Discrepancy leading to an...", rated Medium. It affects Active Iq Unified Manager (Netapp); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.9 describes technical severity. EPSS 2.95% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.