Data corruption via reused shared-pointer addresses
Published Mar 30, 2020 · Updated Aug 4, 2024
Serialization flaw in USC iLab cereal 1.3.0 and earlier allows attackers to deserialize incorrect shared-pointer values via address reuse. OutputArchive registers a shared pointer's raw address as its ID without retaining the pointer, so a later allocation at the same address reuses the prior ID. The error requires a shared pointer to be freed during an archive's lifetime and its address to be reused, causing application-dependent data integrity failures.
Summary
What happened
Serialization flaw in USC iLab cereal 1.3.0 and earlier allows attackers to deserialize incorrect shared-pointer values via address reuse. OutputArchive registers a shared pointer's raw address as its ID without retaining the pointer, so a later allocation at the same address reuses the prior ID. The error requires a shared pointer to be freed during an archive's lifetime and its address to be reused, causing application-dependent data integrity failures.
The record
- CVE
- CVE-2020-11105
- Published
- Mar 30, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-763
- 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
- Shared-pointer serialization asymmetry reproducerproof of concept · demonstrated
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