Memory corruption via unbounded decryption-data logging
Published Jan 7, 2025 · Updated Jan 8, 2025
Stack overflow in Apple SmartCardServices before SCSSU-201801 allows physically proximate attackers to overwrite stack memory. GemaltoPrivateKeyRecord::computeDecrypt logs attacker-controlled bytes with repeated sprintf calls into a fixed 6,000-byte strData array without checking remaining capacity. A malicious smart card must supply oversized decryption data; the fixed sprintf format constrains control over the overwritten bytes.
Summary
What happened
Stack overflow in Apple SmartCardServices before SCSSU-201801 allows physically proximate attackers to overwrite stack memory. GemaltoPrivateKeyRecord::computeDecrypt logs attacker-controlled bytes with repeated sprintf calls into a fixed 6,000-byte strData array without checking remaining capacity. A malicious smart card must supply oversized decryption data; the fixed sprintf format constrains control over the overwritten bytes.
The record
- CVE
- CVE-2018-4301
- Published
- Jan 7, 2025
- Updated
- Jan 8, 2025
- Vendor
- Apple
- Product
- SmartCardServices
- Classifications
- CWE-120, T1200
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 7, 2025CVE publishedPublication date reported by the CVE source.
- Jan 8, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <201801
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo