OpenSSH up to 8.3 Algorithm Negotiation information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $5k-$25k | 0.00 |
Summary
A vulnerability was found in OpenSSH up to 8.3. It has been declared as problematic. This issue affects some unknown processing of the component Algorithm Negotiation. Such manipulation leads to information disclosure. This vulnerability is documented as CVE-2020-14145. The attack can be executed remotely. There is not any exploit available.
Details
A vulnerability was found in OpenSSH up to 8.3 (Connectivity Software). It has been rated as problematic. Affected by this issue is some unknown processing of the component Algorithm Negotiation. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. CVE summarizes:
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.
The weakness was released 06/29/2020. This vulnerability is handled as CVE-2020-14145 since 06/15/2020. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 12/18/2025). The MITRE ATT&CK project declares the attack technique as T1592.
The vulnerability scanner Nessus provides a plugin with the ID 239762 (TencentOS Server 3: openssh (TSSA-2022:0215)), which helps to determine the existence of the flaw in a target environment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at Tenable (239762). Once again VulDB remains the best source for vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.8VulDB Meta Temp Score: 4.8
VulDB Base Score: 3.7
VulDB Temp Score: 3.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.9
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 239762
Nessus Name: TencentOS Server 3: openssh (TSSA-2022:0215)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
06/15/2020 🔍06/29/2020 🔍
06/30/2020 🔍
12/18/2025 🔍
Sources
Status: Not definedConfirmation: 🔍
CVE: CVE-2020-14145 (🔍)
GCVE (CVE): GCVE-0-2020-14145
GCVE (VulDB): GCVE-100-157436
Entry
Created: 06/30/2020 08:43Updated: 12/18/2025 16:32
Changes: 06/30/2020 08:43 (34), 06/30/2020 08:48 (18), 10/28/2020 06:31 (1), 06/20/2025 20:37 (17), 12/18/2025 16:32 (2)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.