CVE-2024-23218: An attacker may be able to decrypt legacy RSA PKCS#1 v1.5 ciphertexts without having the private key in Apple iOS and iPadOS
A timing side-channel issue was addressed with improvements to constant-time computation in cryptographic functions. This issue is fixed in macOS Sonoma 14.3, watchOS 10.3, tvOS 17.3, iOS 17.3 and iPadOS 17.3. An attacker may be able to decrypt legacy RSA PKCS#1 v1.5 ciphertexts without having the private key.
AI Analysis
Technical Summary
CVE-2024-23218 is a cryptographic vulnerability identified in Apple iOS and iPadOS, specifically targeting the legacy RSA PKCS#1 v1.5 encryption scheme. The flaw is a timing side-channel issue where the cryptographic functions do not consistently execute in constant time, allowing an attacker to infer information about the plaintext by measuring the time taken to decrypt ciphertexts. This side-channel leakage can enable an attacker to decrypt RSA-encrypted messages without possessing the private key, undermining the confidentiality of communications or stored data encrypted with this legacy scheme. The vulnerability affects multiple Apple operating systems, including iOS, iPadOS, macOS Sonoma, watchOS, and tvOS, with fixes released in versions 17.3 and 14.3 respectively. The CVSS 3.1 base score is 5.9, reflecting medium severity, with an attack vector of network (remote attacker), high attack complexity, no privileges required, no user interaction, and high impact on confidentiality but no impact on integrity or availability. The root cause is the failure to implement constant-time cryptographic operations for RSA PKCS#1 v1.5 decryption, a known best practice to prevent timing attacks. While modern cryptographic standards have moved away from PKCS#1 v1.5 due to its known weaknesses, legacy systems and applications may still rely on it, increasing the risk surface. No public exploits have been reported yet, but the vulnerability's existence necessitates prompt patching and review of cryptographic practices.
Potential Impact
For European organizations, the primary impact of CVE-2024-23218 is the potential compromise of confidentiality for data encrypted using legacy RSA PKCS#1 v1.5 on affected Apple devices. This could include sensitive communications, authentication tokens, or stored encrypted data. Organizations in sectors such as finance, healthcare, government, and critical infrastructure that rely on Apple devices for secure communications or data handling are at heightened risk. The vulnerability does not affect data integrity or availability directly but could facilitate further attacks if attackers gain decrypted sensitive information. Since the attack requires network access but no privileges or user interaction, remote exploitation is feasible, increasing the threat surface. The medium severity rating suggests a moderate but non-trivial risk, especially where legacy cryptographic protocols remain in use. Failure to patch could lead to data breaches, loss of trust, and regulatory non-compliance under GDPR and other data protection laws. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate the potential for future exploitation.
Mitigation Recommendations
European organizations should immediately ensure all Apple devices are updated to iOS 17.3, iPadOS 17.3, macOS Sonoma 14.3, watchOS 10.3, and tvOS 17.3 or later to apply the patch that enforces constant-time cryptographic operations. Beyond patching, organizations should audit their cryptographic usage to identify and phase out legacy RSA PKCS#1 v1.5 encryption in favor of modern, secure schemes such as RSA-PSS or elliptic curve cryptography (ECC). Network-level protections such as intrusion detection systems (IDS) and anomaly detection can help identify unusual timing or traffic patterns that might indicate exploitation attempts. Organizations should also review and tighten access controls to limit exposure of cryptographic operations to untrusted networks. For critical systems, consider implementing hardware security modules (HSMs) or secure enclaves that enforce constant-time cryptographic operations. Finally, conduct employee training to raise awareness about timely patching and cryptographic hygiene, and maintain an incident response plan to address potential data breaches stemming from cryptographic vulnerabilities.
Affected Countries
United Kingdom, Germany, France, Italy, Spain, Netherlands, Sweden, Belgium, Ireland, Denmark
CVE-2024-23218: An attacker may be able to decrypt legacy RSA PKCS#1 v1.5 ciphertexts without having the private key in Apple iOS and iPadOS
Description
A timing side-channel issue was addressed with improvements to constant-time computation in cryptographic functions. This issue is fixed in macOS Sonoma 14.3, watchOS 10.3, tvOS 17.3, iOS 17.3 and iPadOS 17.3. An attacker may be able to decrypt legacy RSA PKCS#1 v1.5 ciphertexts without having the private key.
AI-Powered Analysis
Technical Analysis
CVE-2024-23218 is a cryptographic vulnerability identified in Apple iOS and iPadOS, specifically targeting the legacy RSA PKCS#1 v1.5 encryption scheme. The flaw is a timing side-channel issue where the cryptographic functions do not consistently execute in constant time, allowing an attacker to infer information about the plaintext by measuring the time taken to decrypt ciphertexts. This side-channel leakage can enable an attacker to decrypt RSA-encrypted messages without possessing the private key, undermining the confidentiality of communications or stored data encrypted with this legacy scheme. The vulnerability affects multiple Apple operating systems, including iOS, iPadOS, macOS Sonoma, watchOS, and tvOS, with fixes released in versions 17.3 and 14.3 respectively. The CVSS 3.1 base score is 5.9, reflecting medium severity, with an attack vector of network (remote attacker), high attack complexity, no privileges required, no user interaction, and high impact on confidentiality but no impact on integrity or availability. The root cause is the failure to implement constant-time cryptographic operations for RSA PKCS#1 v1.5 decryption, a known best practice to prevent timing attacks. While modern cryptographic standards have moved away from PKCS#1 v1.5 due to its known weaknesses, legacy systems and applications may still rely on it, increasing the risk surface. No public exploits have been reported yet, but the vulnerability's existence necessitates prompt patching and review of cryptographic practices.
Potential Impact
For European organizations, the primary impact of CVE-2024-23218 is the potential compromise of confidentiality for data encrypted using legacy RSA PKCS#1 v1.5 on affected Apple devices. This could include sensitive communications, authentication tokens, or stored encrypted data. Organizations in sectors such as finance, healthcare, government, and critical infrastructure that rely on Apple devices for secure communications or data handling are at heightened risk. The vulnerability does not affect data integrity or availability directly but could facilitate further attacks if attackers gain decrypted sensitive information. Since the attack requires network access but no privileges or user interaction, remote exploitation is feasible, increasing the threat surface. The medium severity rating suggests a moderate but non-trivial risk, especially where legacy cryptographic protocols remain in use. Failure to patch could lead to data breaches, loss of trust, and regulatory non-compliance under GDPR and other data protection laws. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate the potential for future exploitation.
Mitigation Recommendations
European organizations should immediately ensure all Apple devices are updated to iOS 17.3, iPadOS 17.3, macOS Sonoma 14.3, watchOS 10.3, and tvOS 17.3 or later to apply the patch that enforces constant-time cryptographic operations. Beyond patching, organizations should audit their cryptographic usage to identify and phase out legacy RSA PKCS#1 v1.5 encryption in favor of modern, secure schemes such as RSA-PSS or elliptic curve cryptography (ECC). Network-level protections such as intrusion detection systems (IDS) and anomaly detection can help identify unusual timing or traffic patterns that might indicate exploitation attempts. Organizations should also review and tighten access controls to limit exposure of cryptographic operations to untrusted networks. For critical systems, consider implementing hardware security modules (HSMs) or secure enclaves that enforce constant-time cryptographic operations. Finally, conduct employee training to raise awareness about timely patching and cryptographic hygiene, and maintain an incident response plan to address potential data breaches stemming from cryptographic vulnerabilities.
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- apple
- Date Reserved
- 2024-01-12T22:22:21.477Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 68406659182aa0cae2b37ac5
Added to database: 6/4/2025, 3:29:29 PM
Last enriched: 11/5/2025, 12:03:57 AM
Last updated: 12/1/2025, 4:18:07 AM
Views: 39
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.
Related Threats
CVE-2025-13800: Command Injection in ADSLR NBR1005GPEV2
MediumCVE-2025-13805: Deserialization in nutzam NutzBoot
MediumCVE-2025-13804: Information Disclosure in nutzam NutzBoot
MediumCVE-2025-13803: Improper Neutralization of HTTP Headers for Scripting Syntax in MediaCrush
MediumCVE-2025-13802: Cross Site Scripting in jairiidriss RestaurantWebsite
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.