First published: Sun Jan 29 2023(Updated: )
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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
All of | ||
WireGuard | =0.5.3 | |
Microsoft Windows Operating System | ||
WireGuard | =0.5.3 | |
Microsoft Windows Operating System |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2021-46873 is considered high due to the potential for a static private key to become permanently unusable.
To fix CVE-2021-46873, users should update to the latest version of WireGuard that addresses this time setting issue.
CVE-2021-46873 specifically affects WireGuard version 0.5.3 on Windows.
Yes, CVE-2021-46873 can be exploited if an attacker can manipulate the system time via unauthenticated NTP.
If your system time is set to a future value, it could render your static private key in WireGuard permanently useless.