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.
Published 2021-05-11 17:15:08
Updated 2021-05-25 20:39:20
Source GitHub, Inc.
View at NVD,   CVE.org

Products affected by CVE-2021-29508

Exploit prediction scoring system (EPSS) score for CVE-2021-29508

0.10%
Probability of exploitation activity in the next 30 days EPSS Score History
~ 43 %
Percentile, the proportion of vulnerabilities that are scored at or less

CVSS scores for CVE-2021-29508

Base Score Base Severity CVSS Vector Exploitability Score Impact Score Score Source First Seen
6.4
MEDIUM AV:N/AC:L/Au:N/C:N/I:P/A:P
10.0
4.9
NIST
9.1
CRITICAL CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
3.9
5.2
NIST
9.1
CRITICAL CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
3.9
5.2
GitHub, Inc.

CWE ids for CVE-2021-29508

  • The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
    Assigned by: security-advisories@github.com (Primary)

References for CVE-2021-29508

Jump to
This web site uses cookies for managing your session, storing preferences, website analytics and additional purposes described in our privacy policy.
By using this web site you are agreeing to CVEdetails.com terms of use!