CVE-2022-21340

What it actually does

The flaw permits an unauthenticated network attacker to trigger a partial denial of service condition against the Java Libraries component by supplying crafted input through multiple protocols or by executing untrusted code inside the Java sandbox.

Why it matters to the business

Java-based applications and services may experience intermittent availability loss, increasing operational overhead for organizations that rely on Oracle JDK, JRE, GraalVM, or downstream NetApp and Debian products.

How an attack unfolds

An attacker reaches exposed Java endpoints or supplies data to Java APIs over the network; the Libraries component processes the input and crashes or degrades the JVM, resulting in partial loss of service without requiring credentials or user interaction.

How to fix it

Upgrade affected Oracle Java SE installations to versions later than 7u321, 8u311, 11.0.13 or 17.0.1 and GraalVM Enterprise Edition beyond 20.3.4 or 21.3.0; apply corresponding patches to all listed NetApp and Debian packages; restrict untrusted code execution and network exposure of Java APIs where upgrades are delayed.

How to confirm the fix worked

Inventory all Java runtimes and confirm they exceed the listed vulnerable versions; run vendor-supplied regression tests or synthetic workloads that previously triggered the partial DoS condition to verify absence of the crash path.

Typical attack path

1. Identify network-accessible Java deployments or services consuming untrusted data via the Libraries component
2. Craft and transmit malicious payloads through supported protocols or embed them in sandboxed applets/Web Start applications
3. Trigger the vulnerable code path causing partial JVM resource exhaustion or termination
4. Observe service degradation or restart cycles without further authentication

How to detect it

Review application and JVM logs for unexpected partial process terminations or resource exhaustion events correlated with inbound network traffic to Java services; examine audit trails for API calls that supply data to the Libraries component.

What your security team should do

• Prioritize patching of internet-facing or multi-tenant Java deployments given the low attack complexity and network vector
• Implement network segmentation and input validation around Java API endpoints until upgrades complete
• Monitor EPSS and threat intelligence feeds for any future increase in exploit maturity despite current low scores