CVE-2021-46873
Published: 29 January 2023
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.
Notes
| Author | Note |
|---|---|
| evancaville |
as of 2024-02-02, doesn't appear to be an upstream fix available for this issue. |
Priority
Status
| Package | Release | Status |
|---|---|---|
|
wireguard
Launchpad, Ubuntu, Debian |
bionic |
Deferred
|
| focal |
Deferred
|
|
| jammy |
Deferred
|
|
| kinetic |
Ignored
(end of life, was needs-triage)
|
|
| lunar |
Ignored
(end of life, was deferred [2023-12-22])
|
|
| mantic |
Ignored
(end of life, was deferred)
|
|
| noble |
Deferred
|
|
| trusty |
Ignored
(end of standard support)
|
|
| upstream |
Needs triage
|
|
| xenial |
Deferred
|
Severity score breakdown
| Parameter | Value |
|---|---|
| Base score | 5.3 |
| Attack vector | Network |
| Attack complexity | Low |
| Privileges required | None |
| User interaction | None |
| Scope | Unchanged |
| Confidentiality | None |
| Integrity impact | None |
| Availability impact | Low |
| Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |