OpenSSL ChangeCipherSpec Injection (CVE-2014-0224)
The service uses an OpenSSL version that accepts ChangeCipherSpec messages too early, letting an attacker in the middle force weak keys and read or alter traffic with vulnerable clients.
| Severity | High |
| CVSS 3.1 | 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N Open in the calculator |
| CVSS 4.0 | 9.1 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-841: Improper Enforcement of Behavioral Workflow |
| OWASP Top 10 | A06:2025 Insecure Design |
| MITRE ATT&CK | T1557 Adversary-in-the-Middle |
| CVE | CVE-2014-0224 |
| Category | Outdated Components |
Description
The service uses a version of OpenSSL affected by the ChangeCipherSpec (CCS) injection vulnerability (CVE-2014-0224): releases before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h. In the TLS handshake, the ChangeCipherSpec message tells the other side to switch to the newly agreed keys. Vulnerable versions accept this message before the master secret has been established, so an attacker in the middle of the connection can inject it early on both sides and cause them to derive their session keys from predictable values that the attacker can calculate.
The attacker can then decrypt and modify the session, exposing credentials, session tokens and data, and altering requests or responses without either side detecting it. The full attack works only when both ends are vulnerable, however. The OpenSSL advisory states that OpenSSL clients were vulnerable in all versions, but that servers were only known to be exploitable in the 1.0.1 series and the first 1.0.2 beta.
The risk therefore depends on which clients connect. Current browsers and other unaffected clients cannot be attacked this way, so the practical exposure is to scripts, command-line tools, automated integrations, older applications and embedded devices built on vulnerable OpenSSL releases, which are often the clients of services that have themselves gone unpatched for years.
The vulnerability can be confirmed with Nmap's ssl-ccs-injection script, testssl.sh or vulnerability scanners, which send an early ChangeCipherSpec message and observe whether the server accepts it.
Remediation
Upgrade OpenSSL on the server, and on any clients that connect to it, to a currently supported release; there is no configuration setting that removes the flaw:
- Apply the operating system vendor's OpenSSL update or move to a supported release from the OpenSSL project, then restart every service that uses the library.
- For appliances and software that bundle their own copy of OpenSSL, apply the vendor's patch or firmware update.
- Identify the clients that connect to the service, particularly scripts, integrations and devices, and upgrade any that use a vulnerable OpenSSL release.
- Review the host for other outdated components, as a library this far behind on updates is rarely the only one.
Until the upgrade is complete, restrict access to the service to trusted networks where interception is less likely. Confirm the fix by repeating the CCS injection check and confirming the OpenSSL version in use.
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.