Vulnerability 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.
CVSS Score
CRITICAL
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Asynkron | Wire | All versions |
Related Weaknesses (CWE)
References
- https://github.com/AsynkronIT/Wire/security/advisories/GHSA-hpw7-3vq3-mmv6ExploitThird Party Advisory
- https://www.nuget.org/packages/Wire/Third Party Advisory
- https://github.com/AsynkronIT/Wire/security/advisories/GHSA-hpw7-3vq3-mmv6ExploitThird Party Advisory
- https://www.nuget.org/packages/Wire/Third Party Advisory
FAQ
What is CVE-2021-29508?
CVE-2021-29508 is a vulnerability with a CVSS score of 9.1 (CRITICAL). 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 abo...
How severe is CVE-2021-29508?
CVE-2021-29508 has been rated CRITICAL with a CVSS base score of 9.1/10. This is considered a critical vulnerability requiring immediate attention.
Is there a patch for CVE-2021-29508?
Check the references section above for vendor advisories and patch information. Affected products include: Asynkron Wire.