{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-11105 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2020-11105 is a critical use after free vulnerability in n/a, published on 30 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-11105 and fix it if it is affected.\n\nWhat it is: CVE-2020-11105 is a critical use after free vulnerability in n/a, published on 30 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-11105 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2020-11105/ (Markdown: https://insights.sbomify.com/CVE-2020-11105/index.md)","id":"CVE-2020-11105","markdown":"https://insights.sbomify.com/CVE-2020-11105/index.md","name":"CVE-2020-11105","record":{"aliases":["GHSA-wgww-fh2f-c855","openSUSE-SU-2024:12197-1"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"C++ serialization library","requires_auth":"none","summary":"The cereal library uses raw pointer addresses for shared_ptr caching, leading to use-after-free issues and potential memory corruption or data leakage.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"cereal","vendor":"usc"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-763","name":"Release of Invalid Pointer or Reference"}],"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.","ecosystems":["openSUSE:Tumbleweed"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Use after free in n/a","id":"CVE-2020-11105","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2020"},"n_packages":1,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2020-11106"},"packages":[{"ecosystem":"openSUSE:Tumbleweed","fixed":["1.3.2-1.1"],"introduced":["0"],"last_affected":[],"package":"cereal","purl":"pkg:rpm/opensuse/cereal\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2024:12197-1"}],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2020-11104"},"products":["n/a"],"published":"2020-03-30","related":[{"cvss_score":5.3,"headline":"Information disclosure in n/a","id":"CVE-2020-11104","kev_date_added":null,"published":"2020-03-30"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"The cereal library uses raw pointer addresses for shared_ptr caching, leading to use-after-free issues and potential memory corruption or data leakage.","url":"https://insights.sbomify.com/CVE-2020-11105/"}