Skip to content

Insecure deserialization in Wire

Critical severity GitHub Reviewed Published May 11, 2021 in asynkron/Wire • Updated Feb 1, 2023

Package

nuget Wire (NuGet)

Affected versions

<= 1.0.0

Patched versions

None

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, AkkaDotNet/Hyperion.

References

@rogeralsing rogeralsing published to asynkron/Wire May 11, 2021
Published by the National Vulnerability Database May 11, 2021
Reviewed May 19, 2021
Published to the GitHub Advisory Database May 19, 2021
Last updated Feb 1, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

EPSS score

0.101%
(43rd percentile)

Weaknesses

CVE ID

CVE-2021-29508

GHSA ID

GHSA-hpw7-3vq3-mmv6

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.