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 |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: mitre
Published: 2020-03-30T21:30:10
Updated: 2020-03-30T21:30:10
Reserved: 2020-03-30T00:00:00
Link: CVE-2020-11105
JSON object: View
NVD Information
Status : Analyzed
Published: 2020-03-30T22:15:15.180
Modified: 2020-04-01T20:11:13.233
Link: CVE-2020-11105
JSON object: View
Redhat Information
No data.
CWE