Deserialization in Asynkron Wire
CVE-2021-29508
- CVSS v3
- 9.1 Critical
- Public exploits
- None known
- EPSS
- 0.016 · 76.2th percentile
- Published
- 2021-05-11
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.
Vulnerability class: Insecure Deserialization
Published · last modified .
CVSS v3 metric
CVSS v3 base score 9.1 (Critical). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H.
- Attack Vector
- Network
AV:N - Attack Complexity
- Low
AC:L - Privileges Required
- None
PR:N - User Interaction
- None
UI:N - Scope
- Unchanged
S:U - Confidentiality
- None
C:N - Integrity
- High
I:H - Availability
- High
A:H
EPSS exploit prediction
EPSS 0.016, 76.2th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Asynkron Wire
- Asynkronit Wire — versions <= 1.0.0
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (SohelParashar/.Net-Deserialization-Cheat-Sheet). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- github.com/AsynkronIT/Wire/security/advisories/GHSA-hpw7-3vq3-mmv6 (Exploit, Third Party Advisory)
- www.nuget.org/packages/Wire/ (Third Party Advisory)