Vulnerability in Oracle Java SE (CVE-2020-2816)

Summary

Vulnerability in Oracle Java SE (CVE-2020-2816). Data can be tampered with by attackers.

Original description

The description as published by the source.

Vulnerability in the Java SE product of Oracle Java SE (component: JSSE). Supported versions that are affected are Java SE: 11.0.6 and 14. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTPS to compromise Java SE. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Java SE accessible data. Note: This vulnerability can only be exploited by supplying data to APIs in the specified Component without using Untrusted Java Web Start applications or Untrusted Java applets, such as through a web service. CVSS 3.0 Base Score 7.5 (Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N).

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-2816 has been found in Oracle Java SE.
Data can be tampered with by attackers.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Oracle Java SE CVE-2020-2816" on the vendor's site.

CVE-2020-2816 (Oracle Java SE)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
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 Oracle Java SE.

📍 Affected scope

Check the vendor advisory for the affected versions of Oracle Java SE.

🔥 Severity

Severity: ?. Data can be tampered with by attackers.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ 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・依存マニフェストで Oracle Java SE を使っているサービスとバージョンを洗い出す。
2
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Bitnami java-min

[{"type":"SEMVER","events":[{"introduced":"9.0.0"},{"fixed":"11.0.7"},{"introduced":"12.0.0"},{"fixed":"14.0.1"}]}]

Bitnami jre

[{"type":"SEMVER","events":[{"introduced":"9.0.0"},{"fixed":"11.0.7"},{"introduced":"12.0.0"},{"fixed":"14.0.1"}]}]

Bitnami java

[{"type":"SEMVER","events":[{"introduced":"9.0.0"},{"fixed":"11.0.7"},{"introduced":"12.0.0"},{"fixed":"14.0.1"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

Debian DEBIAN-CVE-2020-2816 openjdk-11 Fixed in: 11.0.7+10-1

References

advisory lists.opensuse.org
advisory security.netapp.com
advisory usn.ubuntu.com
advisory debian.org
advisory oracle.com
web nvd.nist.gov