Approved changes feed: RSS · Atom
cpe:2.3:a:asynkron:wire:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Asynkron (79e63bcc-aa11-5b86-8788-7f3ba5f6ad7d) |
|---|---|
| Product | Wire (d8bd1a5c-53d5-53e8-ba6a-69894ad454c9) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/asynkronit/wire |
purl2cpe | 2026-06-01 10:10:55.425393 |
pkg:nuget/Wire |
purl2cpe | 2026-06-01 10:10:55.425399 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2021-29508 |
vulnerable | 2026-06-08 05:31:26.508438 |
Insecure deserialization in Wire
CRITICAL (9.1)
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-11T16:35:10.000Z
Updated: 2024-08-03T22:11:05.408Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.