An issue was discovered in USC iLab cereal through 1.3.0. It employs caching of std::shared_ptr values, using the raw pointer address as a unique identifier. This becomes problematic if an std::shared_ptr variable goes out of scope and is freed, and a new std::shared_ptr is allocated at the same address. Serialization fidelity thereby becomes dependent upon memory layout. In short, serialized std::shared_ptr variables cannot always be expected to serialize back into their original values. This can have any number of consequences, depending on the context within which this manifests.
References
Link | Resource |
---|---|
https://github.com/USCiLab/cereal/issues/636 | Exploit Third Party Advisory |
https://github.com/USCiLab/cereal/issues/636 | Exploit Third Party Advisory |
Configurations
History
21 Nov 2024, 04:56
Type | Values Removed | Values Added |
---|---|---|
References | () https://github.com/USCiLab/cereal/issues/636 - Exploit, Third Party Advisory |
Information
Published : 2020-03-30 22:15
Updated : 2024-11-21 04:56
NVD link : CVE-2020-11105
Mitre link : CVE-2020-11105
CVE.ORG link : CVE-2020-11105
JSON object : View
Products Affected
usc
- cereal
CWE
CWE-763
Release of Invalid Pointer or Reference