CVE-2020-11091
What it is
In Weave Net before version 2.6.3, an attacker able to run a process as root in a container is able to respond to DNS requests from the host and thereby insert themselves as a fake service. In a cluster with an IPv4 internal network, if IPv6 is not totally disabled on the host (via ipv6.disable=1 on the kernel cmdline), it will be either unconfigured or configured on some interfaces, but it's pretty likely that ipv6 forwarding is disabled, ie /proc/sys/net/ipv6/conf//forwarding == 0. Also by default, /proc/sys/net/ipv6/conf//accept_ra == 1. The combination of these 2 sysctls means that the host accepts router advertisements and configure the IPv6 stack using them. By sending rogue router advertisements, an attacker can reconfigure the host to redirect part or all of the IPv6 traffic of the host to the attacker controlled container. Even if there was no IPv6 traffic before, if the DNS returns A (IPv4) and AAAA (IPv6) records, many HTTP libraries will try to connect via IPv6 first then fallback to IPv4, giving an opportunity to the attacker to respond. If by chance you also have on the host a vulnerability like last year's RCE in apt (CVE-2019-3462), you can now escalate to the host. Weave Net version 2.6.3 disables the accept_ra option on the veth devices that it creates.
At a glance
- Exploitability
- Can be exploited over the network with an admin-level account. High risk of data tampering.
- Exploit odds
- 0.9% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.9% in the next 30 days (EPSS).
- Severity: 5.8 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.9% · EPSS, next 30 days
- Weakness
- CWE-350
- Record status
- Modified
Affected
- Weave Net < 2.6.3
Attack profile CVSS 3.1 · 5.8
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- High
- Availability
- None
Raw vector
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2020-11091.md and follow it. Check whether this project is affected by CVE-2020-11091. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/weaveworks/weave/commit/15f21f1899060f7716c70a8555a084e836f39a60
- https://github.com/weaveworks/weave/security/advisories/GHSA-59qg-grp7-5r73
- https://github.com/weaveworks/weave/commit/15f21f1899060f7716c70a8555a084e836f39a60
- https://github.com/weaveworks/weave/security/advisories/GHSA-59qg-grp7-5r73
References
- https://github.com/weaveworks/weave/commit/15f21f1899060f7716c70a8555a084e836f39a60
- https://github.com/weaveworks/weave/security/advisories/GHSA-59qg-grp7-5r73
- https://github.com/weaveworks/weave/commit/15f21f1899060f7716c70a8555a084e836f39a60
- https://github.com/weaveworks/weave/security/advisories/GHSA-59qg-grp7-5r73