{
  "affected": [
    {
      "ranges": [
        {
          "database_specific": {
            "cpe": "cpe:2.3:a:usc:cereal:*:*:*:*:*:*:*:*",
            "extracted_events": [
              {
                "introduced": "0"
              },
              {
                "last_affected": "1.3.0"
              }
            ],
            "source": "CPE_RANGE"
          },
          "events": [
            {
              "introduced": "0"
            },
            {
              "last_affected": "02eace19a99ce3cd564ca4e379753d69af08c2c8"
            }
          ],
          "repo": "https://github.com/uscilab/cereal",
          "type": "GIT"
        }
      ]
    }
  ],
  "database_specific": {},
  "details": "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.",
  "id": "CVE-2020-11105",
  "modified": "2026-07-08T05:39:25.258426170Z",
  "published": "2020-03-30T22:15:15.180Z",
  "references": [
    {
      "type": "EVIDENCE",
      "url": "https://github.com/USCiLab/cereal/issues/636"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}