Memory disclosure via long-double serialization
Published Mar 30, 2020 · Updated Aug 4, 2024
Information disclosure in USC iLab cereal through 1.3.0 allows attackers to read leaked memory via BinaryArchive serialization. BinaryArchive and PortableBinaryArchive serialize initialized C/C++ long double values with padding bytes that contain stack or heap data. The leak requires an archive to leave a trusted context and can expose memory layout details or private keys without altering data or interrupting service.
Summary
What happened
Information disclosure in USC iLab cereal through 1.3.0 allows attackers to read leaked memory via BinaryArchive serialization. BinaryArchive and PortableBinaryArchive serialize initialized C/C++ long double values with padding bytes that contain stack or heap data. The leak requires an archive to leave a trusted context and can expose memory layout details or private keys without altering data or interrupting service.
The record
- CVE
- CVE-2020-11104
- Published
- Mar 30, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-908
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 30, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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