Vulnerability in TLS specification (CVE-2020-1968)

Summary

Vulnerability in TLS specification (CVE-2020-1968). Risk of unauthorized operations or information disclosure.

Original description

The description as published by the source.

The Raccoon attack exploits a flaw in the TLS specification which can lead to an attacker being able to compute the pre-master secret in connections which have used a Diffie-Hellman (DH) based ciphersuite. In such a case this would result in the attacker being able to eavesdrop on all encrypted communications sent over that TLS connection. The attack can only be exploited if an implementation re-uses a DH secret across multiple TLS connections. Note that this issue only impacts DH ciphersuites and not ECDH ciphersuites. This issue affects OpenSSL 1.0.2 which is out of support and no longer receiving public updates. OpenSSL 1.1.1 is not vulnerable to this issue. Fixed in OpenSSL 1.0.2w (Affected 1.0.2-1.0.2v).

Source: OSV.dev (Open Source Vulnerabilities) NVD OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2020-1968 has been found in TLS specification.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "TLS specification CVE-2020-1968" on the vendor's site.

CVE-2020-1968 (TLS specification)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Affected: 1.0.2 - 1.0.2v
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in TLS specification.

📍 Affected scope

Affected versions of TLS specification: 1.0.2 - 1.0.2v.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory. (If a vulnerable version 1.0.2 - 1.0.2v is in production, plan an immediate maintenance window.)

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで TLS specification を使っているサービスとバージョンを洗い出す。
2
Match against affected range verify
```
Confirm if version satisfies `1.0.2 - 1.0.2v`
```
Step 1 で見つかったバージョンが影響範囲 1.0.2 - 1.0.2v に該当するか照合。本番で稼働中ならインシデント扱い。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Fix status by distribution

Fixed packages published by each distribution for this CVE

Debian DEBIAN-CVE-2020-1968 openssl Fixed in: 1.1.0c-1
Ubuntu UBUNTU-CVE-2020-1968 openssl Fixed in: 1.0.1f-1ubuntu2.27+esm10

References

advisory lists.debian.org
advisory security.gentoo.org
advisory security.netapp.com
advisory usn.ubuntu.com
advisory openssl.org
advisory oracle.com
patch oracle.com
patch oracle.com
patch oracle.com
patch oracle.com