Outdated Java Runtime

Hosts or applications use a Java runtime that is missing security updates or comes from a release line that is no longer supported.

SeverityHigh
CVSS 3.17.5 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H Open in the calculator
CVSS 4.07.7 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N Open in the calculator
CWECWE-1395: Dependency on Vulnerable Third-Party Component
OWASP Top 10A03:2025 Software Supply Chain Failures
MITRE ATT&CKT1203 Exploitation for Client Execution, T1190 Exploit Public-Facing Application
CategoryOutdated Components

Description

One or more hosts or applications use a Java runtime (JRE or JDK) that is missing security updates, or a Java release line that its provider no longer supports. Oracle publishes Java SE fixes in its quarterly Critical Patch Updates, and OpenJDK builds from other providers, such as Eclipse Temurin, Amazon Corretto, Microsoft and Red Hat, release matching updates on the same schedule; each provider supports particular release lines for its own published period, and runtimes on unsupported release lines accumulate unfixed vulnerabilities, including in TLS and certificate handling.

Java vulnerabilities affect the core libraries, cryptography, networking and serialisation, and include flaws such as CVE-2022-21449, which allowed forged ECDSA signatures to pass verification. The impact depends on how the runtime is used. Where a server application processes untrusted data with an affected Java API, such as a web service parsing attacker-supplied input, an unauthenticated attacker may be able to cause denial of service, bypass cryptographic checks or, for some flaws, run code; where a desktop runtime opens untrusted content, a user who opens a crafted file or application may be compromised. Many Java flaws are difficult to exploit and need specific conditions.

The finding is identified by authenticated scans that find Java installations and read their version files, and scanners report one result per missing quarterly update. Hosts frequently have several runtimes: older versions left behind by earlier installers, private runtimes bundled inside applications, and JDKs installed by developers and build tools. Bundled runtimes are updated only by the application's vendor. Some scanners rate Java findings for the worst case of a browser plug-in running untrusted applets, a deployment model that has since been retired, so the rating should reflect how the runtime is actually used.

Remediation

Keep each runtime on the latest update of a supported release line:

  • Install the latest quarterly update for every Java runtime in use, from Oracle or the OpenJDK provider the organisation has chosen, and deploy it through the patch management tool.
  • Move applications on release lines the provider no longer supports to a supported long-term support release, after testing.
  • Uninstall runtimes that are no longer needed, including old versions left by earlier installers, and remove Java from hosts that do not need it.
  • Ask vendors of applications that bundle their own runtime for updated releases, and rebuild in-house applications and container images with the updated runtime.
  • Check the licence terms of the provider's builds before deploying updates widely, as the terms for Oracle's JDK have changed over time.

Confirm the fix with java -version for each installed runtime and by repeating the scan.

References


Add This Finding to Your Library

In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.

Free trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More Patching and Outdated Software Findings

Every Patching and Outdated Software finding