WireGuard, such as WireGuard 0.5.3 on Windows, does not fully account for the possibility that an adversary might be able to set a victim's system time to a future value, e.g., because unauthenticated NTP is used. This can lead to an outcome in which one static private key becomes permanently useless.
References
Link | Resource |
---|---|
https://lists.zx2c4.com/pipermail/wireguard/2021-August/006916.html | Mailing List Third Party Advisory |
https://lists.zx2c4.com/pipermail/wireguard/2021-August/006916.html | Mailing List Third Party Advisory |
Configurations
Configuration 1 (hide)
AND |
|
History
28 Mar 2025, 16:15
Type | Values Removed | Values Added |
---|---|---|
CWE | CWE-362 |
21 Nov 2024, 06:34
Type | Values Removed | Values Added |
---|---|---|
References | () https://lists.zx2c4.com/pipermail/wireguard/2021-August/006916.html - Mailing List, Third Party Advisory |
Information
Published : 2023-01-29 23:15
Updated : 2025-03-28 16:15
NVD link : CVE-2021-46873
Mitre link : CVE-2021-46873
CVE.ORG link : CVE-2021-46873
JSON object : View
Products Affected
wireguard
- wireguard
microsoft
- windows
CWE
NVD-CWE-noinfo
CWE-362
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')