Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2022-21299 medium CVSS 5.3

Vulnerability in java (CVE-2022-21299)

Summary

Vulnerability in java (CVE-2022-21299). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.7.0, 1.8.0, 7.0.331, 8.0.321, 11.0.14, 17.0.2 or later.

Original description

The description as published by the source.

Vulnerability in the Oracle Java SE, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: JAXP). Supported versions that are affected are Oracle Java SE: 7u321, 8u311, 11.0.13, 17.01; Oracle GraalVM Enterprise Edition: 20.3.4 and 21.3.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Java SE, Oracle GraalVM Enterprise Edition. Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. This vulnerability can also be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. CVSS 3.1 Base Score 5.3 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L).

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory 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-2022-21299 has been found in java.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade java to 1.7.0, 1.8.0, 7.0.331, 8.0.321, 11.0.14, 17.0.2 or later.
If unsure, ask your IT team or search "java CVE-2022-21299" on the vendor's site.

CVE-2022-21299 (java) — CWE-400 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.7.0, 1.8.0, 7.0.331, 8.0.321, 11.0.14, 17.0.2 — apply immediately
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 (CWE-400) exists in java.

📍 Affected scope

Check the vendor advisory for the affected versions of java.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.7.0, 1.8.0, 7.0.331, 8.0.321, 11.0.14, 17.0.2.

🛡️ 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. Run grep -r 'java' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

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

  1. 1
    Identify exposure identify 
    grep -r 'java' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で java を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade java to 1.7.0, 1.8.0, 7.0.331, 8.0.321, 11.0.14, 17.0.2

    ステージング環境で 1.7.0, 1.8.0, 7.0.331, 8.0.321, 11.0.14, 17.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Bitnami java
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.7.0"},{"introduced":"1.8.0"},{"fixed":"1.8.0"},{"introduced":"1.9.0"},{"fixed":"7.0.331"},{"introduced":"8.0.0"},{"fixed":"8.0.321"},{"introduced":"9.0.0"},{"fixed":"11.0.14"},{"introduced":"12.0.0"},{"fixed":"17.0.2"}]}]
Bitnami java-min
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.7.0"},{"introduced":"1.8.0"},{"fixed":"1.8.0"},{"introduced":"1.9.0"},{"fixed":"7.0.331"},{"introduced":"8.0.0"},{"fixed":"8.0.321"},{"introduced":"9.0.0"},{"fixed":"11.0.14"},{"introduced":"12.0.0"},{"fixed":"17.0.2"}]}]
Bitnami jre
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.7.0"},{"introduced":"1.8.0"},{"fixed":"1.8.0"},{"introduced":"1.9.0"},{"fixed":"7.0.331"},{"introduced":"8.0.0"},{"fixed":"8.0.321"},{"introduced":"9.0.0"},{"fixed":"11.0.14"},{"introduced":"12.0.0"},{"fixed":"17.0.2"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details