CVE-2021-29508 Insecure deserialization in Wire

Critical 9.1 Published Updated

An attacker can execute arbitrary code by sending malicious serialized payloads to applications using the Wire library due to insecure type handling.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2021-29508?

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.

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

Weakness: CWE-502

Which versions are affected by CVE-2021-29508?

2 open source packages ship an affected version, including Wire. It affects 1 product.

PackageAffectedFixed in
Wire NuGetAll versions to 1.0.0None
Wire NuGetAll versions to 1.0.0None

Products include Asynkron Wire.

How do I fix CVE-2021-29508?

No fix has been published for CVE-2021-29508 yet. Limit exposure of the affected software until one is available.

Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.

Is CVE-2021-29508 being exploited?

There is no known exploitation of CVE-2021-29508 in the wild and no public exploit code.

Sources

Also known as GHSA-hpw7-3vq3-mmv6.

Is CVE-2021-29508 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free