Outdated OpenSSL
A service or application uses an OpenSSL release that is missing security fixes or belongs to a series that is no longer supported.
| Severity | High |
| CVSS 3.1 | 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H Open in the calculator |
| CVSS 4.0 | 8.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-1395: Dependency on Vulnerable Third-Party Component |
| OWASP Top 10 | A03:2025 Software Supply Chain Failures |
| MITRE ATT&CK | T1190 Exploit Public-Facing Application, T1499.004 Application or System Exploitation |
| Category | Outdated Components |
Description
A service or application uses a release of the OpenSSL cryptographic library that predates fixes for one or more published vulnerabilities, or a release series that the OpenSSL project no longer supports, in which newly found flaws will remain unfixed. OpenSSL implements TLS and other cryptography for web servers, mail servers, VPNs and a great many applications, and because it processes connections before any authentication takes place, its flaws are often reachable by anyone who can open a connection to an exposed TLS service.
The project rates each issue from Low to Critical, and the impact depends on the vulnerabilities present and how the library is used. Most recent issues allow an unauthenticated attacker to crash a service or tie up its processor during the TLS handshake or certificate processing, causing denial of service, as the infinite loop in certificate parsing tracked as CVE-2022-0778 does. Others have allowed fragments of process memory, which can contain private keys, session data or credentials, to be read, as Heartbleed did, and, rarely, memory to be corrupted in a way that could lead to code execution.
The finding is raised from version strings, such as the OpenSSL version that some web servers include in their Server header, from installed packages in authenticated scans, or from library files bundled with applications, and scanners report one result per advisory affecting that version. Linux distributions backport OpenSSL fixes without changing the version number and continue to support series that the OpenSSL project has retired, so results based on the version alone should be confirmed against the distribution's advisories. Applications that bundle their own copy of OpenSSL, including many on Windows, are not updated by the operating system and are a common source of genuine findings.
Remediation
Update OpenSSL wherever it is present:
- Where OpenSSL comes from the operating system, install the distribution's latest OpenSSL packages, then restart every service that loads the library, or reboot the host, so that no process keeps using the old copy in memory; tools such as
needrestarton Debian-based systems andneeds-restartingon Red Hat-based ones list the processes affected. - Where an application or appliance bundles its own copy of OpenSSL, apply the vendor's update, and ask the vendor for one where none exists.
- Where OpenSSL is built from source or statically linked into in-house software, upgrade to the current release of a supported series, preferably a long-term support series, and rebuild the software that uses it.
- Move off release series that the OpenSSL project no longer supports, unless the distribution or a paid extended support arrangement still provides fixes for them.
Confirm the fix with openssl version or the installed package version for system copies, and by checking the library version that each affected service actually loads, then repeat 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 trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.