CVE-2024-2467: Observable Timing Discrepancy
A timing-based side-channel flaw exists in the perl-Crypt-OpenSSL-RSA package, which could be sufficient to recover plaintext across a network in a Bleichenbacher-style attack. To achieve successful decryption, an attacker would have to be able to send a large number of trial messages. The vulnerability affects the legacy PKCS#1v1.5 RSA encryption padding mode.
AI Analysis
Technical Summary
CVE-2024-2467 identifies a timing side-channel vulnerability in the perl-Crypt-OpenSSL-RSA package, specifically targeting the legacy PKCS#1 v1.5 RSA encryption padding mode. This vulnerability arises from observable timing discrepancies during the decryption process, which can be exploited in a Bleichenbacher-style adaptive chosen ciphertext attack. In such an attack, an adversary sends a large number of crafted ciphertexts to a target system and measures the response times to infer information about the plaintext. Over many iterations, this timing information can leak enough data to recover the original plaintext without requiring the private key directly. The attack vector is network-based, requiring no privileges or user interaction, but it demands high attack complexity due to the need for numerous trial messages and precise timing measurements. The vulnerability primarily impacts confidentiality, as it allows plaintext recovery, but does not affect data integrity or system availability. While no known exploits have been reported in the wild, the presence of this flaw in a widely used cryptographic package poses a significant risk to systems relying on PKCS#1 v1.5 padding, which is considered legacy and less secure compared to modern padding schemes like OAEP. The CVSS 3.1 score of 5.9 reflects a medium severity rating, balancing the high confidentiality impact against the complexity and conditions required for exploitation.
Potential Impact
The primary impact of CVE-2024-2467 is the potential compromise of confidentiality through plaintext recovery in systems using the vulnerable perl-Crypt-OpenSSL-RSA package with PKCS#1 v1.5 padding. Organizations that rely on this legacy padding mode for RSA encryption may expose sensitive data to remote attackers capable of performing timing measurements over the network. This could lead to leakage of cryptographic secrets, user credentials, or other confidential information. Although the attack does not affect data integrity or availability, the breach of confidentiality can have severe consequences, including unauthorized data disclosure, regulatory non-compliance, and reputational damage. The requirement for a large number of trial messages and high precision timing measurements limits the feasibility of the attack in noisy or restricted network environments, but targeted attackers with sufficient resources could still exploit this vulnerability. Systems that have not transitioned to more secure padding schemes or that expose RSA decryption services over the network are at elevated risk.
Mitigation Recommendations
To mitigate CVE-2024-2467, organizations should: 1) Transition away from the legacy PKCS#1 v1.5 RSA padding mode to more secure alternatives such as RSA-OAEP, which is resistant to Bleichenbacher-style attacks. 2) Update or patch the perl-Crypt-OpenSSL-RSA package to versions that address this timing side-channel vulnerability once available. 3) Implement network-level protections such as rate limiting and anomaly detection to reduce the feasibility of sending large volumes of trial ciphertexts. 4) Employ constant-time cryptographic operations to minimize timing discrepancies observable by attackers. 5) Restrict access to cryptographic decryption services to trusted networks or authenticated users to reduce exposure. 6) Monitor cryptographic service logs for unusual patterns indicative of adaptive chosen ciphertext attacks. 7) Educate developers and system administrators about the risks of legacy padding schemes and encourage the adoption of modern cryptographic best practices.
Affected Countries
United States, Germany, United Kingdom, France, Japan, India, Canada, Australia, Netherlands, South Korea
CVE-2024-2467: Observable Timing Discrepancy
Description
A timing-based side-channel flaw exists in the perl-Crypt-OpenSSL-RSA package, which could be sufficient to recover plaintext across a network in a Bleichenbacher-style attack. To achieve successful decryption, an attacker would have to be able to send a large number of trial messages. The vulnerability affects the legacy PKCS#1v1.5 RSA encryption padding mode.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2024-2467 identifies a timing side-channel vulnerability in the perl-Crypt-OpenSSL-RSA package, specifically targeting the legacy PKCS#1 v1.5 RSA encryption padding mode. This vulnerability arises from observable timing discrepancies during the decryption process, which can be exploited in a Bleichenbacher-style adaptive chosen ciphertext attack. In such an attack, an adversary sends a large number of crafted ciphertexts to a target system and measures the response times to infer information about the plaintext. Over many iterations, this timing information can leak enough data to recover the original plaintext without requiring the private key directly. The attack vector is network-based, requiring no privileges or user interaction, but it demands high attack complexity due to the need for numerous trial messages and precise timing measurements. The vulnerability primarily impacts confidentiality, as it allows plaintext recovery, but does not affect data integrity or system availability. While no known exploits have been reported in the wild, the presence of this flaw in a widely used cryptographic package poses a significant risk to systems relying on PKCS#1 v1.5 padding, which is considered legacy and less secure compared to modern padding schemes like OAEP. The CVSS 3.1 score of 5.9 reflects a medium severity rating, balancing the high confidentiality impact against the complexity and conditions required for exploitation.
Potential Impact
The primary impact of CVE-2024-2467 is the potential compromise of confidentiality through plaintext recovery in systems using the vulnerable perl-Crypt-OpenSSL-RSA package with PKCS#1 v1.5 padding. Organizations that rely on this legacy padding mode for RSA encryption may expose sensitive data to remote attackers capable of performing timing measurements over the network. This could lead to leakage of cryptographic secrets, user credentials, or other confidential information. Although the attack does not affect data integrity or availability, the breach of confidentiality can have severe consequences, including unauthorized data disclosure, regulatory non-compliance, and reputational damage. The requirement for a large number of trial messages and high precision timing measurements limits the feasibility of the attack in noisy or restricted network environments, but targeted attackers with sufficient resources could still exploit this vulnerability. Systems that have not transitioned to more secure padding schemes or that expose RSA decryption services over the network are at elevated risk.
Mitigation Recommendations
To mitigate CVE-2024-2467, organizations should: 1) Transition away from the legacy PKCS#1 v1.5 RSA padding mode to more secure alternatives such as RSA-OAEP, which is resistant to Bleichenbacher-style attacks. 2) Update or patch the perl-Crypt-OpenSSL-RSA package to versions that address this timing side-channel vulnerability once available. 3) Implement network-level protections such as rate limiting and anomaly detection to reduce the feasibility of sending large volumes of trial ciphertexts. 4) Employ constant-time cryptographic operations to minimize timing discrepancies observable by attackers. 5) Restrict access to cryptographic decryption services to trusted networks or authenticated users to reduce exposure. 6) Monitor cryptographic service logs for unusual patterns indicative of adaptive chosen ciphertext attacks. 7) Educate developers and system administrators about the risks of legacy padding schemes and encourage the adoption of modern cryptographic best practices.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- redhat
- Date Reserved
- 2024-03-14T17:31:30.419Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 691f65fd40b920e2707f5ff2
Added to database: 11/20/2025, 7:03:25 PM
Last enriched: 2/27/2026, 9:24:01 AM
Last updated: 3/25/2026, 11:03:42 PM
Views: 147
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.