{"answers":{"affected":"2 open source packages ship an affected version, including Wire. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-29508 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-29508 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-29508 is a critical unsafe deserialization vulnerability in AsynkronIT Wire, published on 11 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-29508 and fix it if it is affected.\n\nWhat it is: CVE-2021-29508 is a critical unsafe deserialization vulnerability in AsynkronIT Wire, published on 11 May 2021. 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-2021-29508 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- Wire (NuGet): affected all versions up to 1.0.0; no fix listed\n- Wire (NuGet): affected all versions up to 1.0.0; no fix listed\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-2021-29508/ (Markdown: https://insights.sbomify.com/CVE-2021-29508/index.md)","id":"CVE-2021-29508","markdown":"https://insights.sbomify.com/CVE-2021-29508/index.md","name":"CVE-2021-29508","record":{"aliases":["GHSA-hpw7-3vq3-mmv6"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Wire serialization library","requires_auth":"none","summary":"An attacker can execute arbitrary code by sending malicious serialized payloads to applications using the Wire library due to insecure type handling.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"wire","vendor":"asynkron"}],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"Due to how Wire handles type information in its serialization format, malicious payloads can be passed to a deserializer. e.g. using a surrogate on the sender end, an attacker can pass information about a different type for the receiving end. And by doing so allowing the serializer to create any type on the deserializing end. This is the same issue that exists for .NET BinaryFormatter https://docs.microsoft.com/en-us/visualstudio/code-quality/ca2300?view=vs-2019. This also applies to the fork of Wire.","ecosystems":["NuGet"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Insecure deserialization in Wire","id":"CVE-2021-29508","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"NuGet","product":null,"products":[],"type":"deserialization","year":"2021"},"n_packages":2,"n_references":2,"next":{"headline":"Keepalive Connections Causing Denial Of Service in puma","id":"CVE-2021-29509"},"packages":[{"ecosystem":"NuGet","fixed":[],"introduced":["0"],"last_affected":["1.0.0"],"package":"Wire","purl":null,"source":"GHSA-hpw7-3vq3-mmv6"},{"ecosystem":"NuGet","fixed":[],"introduced":["0"],"last_affected":["1.0.0"],"package":"Wire","purl":"pkg:nuget/Wire","source":"GHSA-hpw7-3vq3-mmv6"}],"prev":{"headline":"dlt-daemon could crash if there is special character in dlt.conf","id":"CVE-2021-29507"},"products":["Wire"],"published":"2021-05-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-03","vendors":["AsynkronIT"]},"summary":"An attacker can execute arbitrary code by sending malicious serialized payloads to applications using the Wire library due to insecure type handling.","url":"https://insights.sbomify.com/CVE-2021-29508/"}