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.
References
Link | Resource |
---|---|
https://github.com/AsynkronIT/Wire/security/advisories/GHSA-hpw7-3vq3-mmv6 | Exploit Third Party Advisory |
https://www.nuget.org/packages/Wire/ | Third Party Advisory |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: GitHub_M
Published: 2021-05-11T16:35:10
Updated: 2021-05-11T16:35:10
Reserved: 2021-03-30T00:00:00
Link: CVE-2021-29508
JSON object: View
NVD Information
Status : Analyzed
Published: 2021-05-11T17:15:07.570
Modified: 2021-05-25T20:39:19.567
Link: CVE-2021-29508
JSON object: View
Redhat Information
No data.
CWE