CVE-2021-29508

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.

• CVE ID
• CVE-2021-29508

• Assigner
• security-advisories@github.com

• Vulnerability Status
• Analyzed

• Published Version
• 2021-05-11T17:15:07

• Last Modified Date
• 2021-05-25T20:39:19

• Version
• 2.0

• Vector String
• AV:N/AC:L/Au:N/C:N/I:P/A:P

• Access Vector
• NETWORK

• Access Compatibility
• LOW

• Authentication
• NONE

• Confidentiality Impact
• NONE

• Integrity Impact
• PARTIAL

• Availability Impact
• PARTIAL

• Base Score
• 6.4

• Severity
• MEDIUM

• Exploitability Score
• 10

• Impact Score
• 4.9

• Version
• 3.1

• Vector String
• CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

• Attack Vector
• NETWORK

• Attack Compatibility
• LOW

• Privileges Required
• NONE

• User Interaction
• NONE

• Scope
• UNCHANGED

• Confidentiality Impact
• NONE

• Availability Impact
• HIGH

• Base Score
• 9.1

• Base Severity
• CRITICAL

• Exploitability Score
• 3.9

• Impact Score
• 5.2