{"id":"CVE-2020-11105","aliases":["EUVD-2020-3463","GHSA-wgww-fh2f-c855","openSUSE-SU-2024:12197-1"],"status":"published","title":"An issue was discovered in USC iLab cereal through 1.3.0. It employs caching of std::shared_ptr...","description":"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.","severity":{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-12","score":0.02044,"percentile":0.81456,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-763"],"published":"2020-03-30T21:30:10Z","modified":"2026-10-20T10:51:45Z","fixes":[{"ecosystem":"openSUSE:Tumbleweed","package":"cereal","fixed_in":["1.3.2-1.1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"cereal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.3.2-1.1"}]}]}],"products":[{"vendor":"usc","product":"cereal"}],"references":[{"url":"https://github.com/USCiLab/cereal/issues/636","tags":["x_refsource_MISC","x_transferred","Exploit","Third Party Advisory","evidence"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2020-11105"},{"url":"https://github.com/advisories/GHSA-wgww-fh2f-c855"},{"url":"","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2020-11105","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2020-11105","description":"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.","status":"published","published":"2020-03-30T21:30:10Z","modified":"2024-08-04T11:21:14.533Z","updated_at":"2026-11-02T14:35:57.67317Z"}],"euvd":[{"id":"EUVD-2020-3463","description":"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.","status":"published","published":"2020-03-30T21:30:10Z","modified":"2024-08-04T11:21:14Z","updated_at":"2026-11-03T03:07:48.03567Z"}],"ghsa":[{"id":"GHSA-wgww-fh2f-c855","title":"An issue was discovered in USC iLab cereal through 1.3.0. It employs caching of std::shared_ptr...","description":"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.","status":"published","published":"2022-05-24T17:12:59Z","modified":"2023-01-29T05:02:16Z","updated_at":"2026-11-02T14:45:02.058324Z"}],"nvd":[{"id":"CVE-2020-11105","description":"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.","status":"published","published":"2020-03-30T22:15:15.18Z","modified":"2026-06-17T02:49:03.6Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical","assessor":"primary"},{"version":"2.0","score":7.5,"vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","level":"high","assessor":"primary"}],"cwes":["CWE-763"],"updated_at":"2026-11-02T14:05:56.580228Z"}],"osv":[{"id":"CVE-2020-11105","description":"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.","status":"published","published":"2020-03-30T22:15:15.18Z","modified":"2026-10-20T10:51:45.974010415Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:44:13.492058Z"},{"id":"openSUSE-SU-2024:12197-1","title":"cereal-devel-1.3.2-1.1 on GA media","description":"These are all security issues fixed in the cereal-devel-1.3.2-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-06-15T00:00:00Z","modified":"2026-02-04T02:47:00.990891Z","updated_at":"2026-11-02T16:58:35.485255Z"}]}}