CVE-2020-11091: Github.com/weaveworks/weave Weave Net Clusters Susceptible To Vulnerability

MODERATE
Advisory Identifier: GHSA-59qg-grp7-5r73
CVSS 5.8
CWE-350
Published
Advisory Summary

CVE-2020-11091 is a MODERATE (CVSS 5.8) weave net clusters susceptible to vulnerability (CWE-350: Reliance on Reverse DNS Resolution for a Security-Critical Action) affecting Github.com/weaveworks/weave libraries in the Go ecosystem. The issue involves weave net clusters susceptible to mitm attacks via ipv6 rogue router advertisements. Remediation is available by upgrading affected packages to version 2.6.3.

CVE-2020-11091 at a Glance

CVE Identifier CVE-2020-11091
GHSA Identifier GHSA-59qg-grp7-5r73
Severity MODERATE
CVSS v3.1 Base Score 5.8
CWE Classification CWE-350: Reliance on Reverse DNS Resolution for a Security-Critical Action
Affected Product Github.com/weaveworks/weave
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 5.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required High (PR:H)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality None (C:N)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2020-11091

To remediate this vulnerability, upgrade all affected Github.com/weaveworks/weave dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/weaveworks/weave fixed: 2.6.3
Upgrade github.com/weaveworks/weave to 2.6.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/weaveworks/weave

How to Check if You Are Affected

To determine whether your application is affected by CVE-2020-11091, inspect your project dependencies for Github.com/weaveworks/weave:

inspect dependencies for github.com/weaveworks/weave

Analyze the terminal output to locate any version of Github.com/weaveworks/weave in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.6.3), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-350: Reliance on Reverse DNS Resolution for a Security-Critical Action, where the product performs reverse dns resolution on an ip address to obtain the hostname and make a security decision, but it does not properly ensure that the ip address is truly associated with the hostname. In Github.com/weaveworks/weave, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact 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. ### Patches Weave Net version 2.6.3 (to be released soon) will disable the accept_ra option on the veth devices that it creates. ### Workarounds Users should not run containers with CAP_NET_RAW capability. This has been the advice from Weave Net for years. https://www.weave.works/docs/net/latest/kubernetes/kube-addon/#-securing-the-setup ### For more information If you have any questions or comments about this advisory: * Open an issue in [the Weave Net repo](https://github.com/weaveworks/weave/issues/new) * Join the <a href="https://slack.weave.works/" target="_blank">Weave Users Slack</a>.

CVE-2020-11091 Affected Github.com/weaveworks/weave Versions

1 component(s)
Fixed Versions:
2.6.3
Product / Package Ecosystem Affected Versions Fixed Version
github.com/weaveworks/weave
Go
< 2.6.3
2.6.3

References

Frequently Asked Questions

What is CVE-2020-11091?
CVE-2020-11091 is a security vulnerability in Github.com/weaveworks/weave involving Weave Net clusters susceptible to MitM attacks via IPv6 rogue router advertisements under CWE-350: Reliance on Reverse DNS Resolution for a Security-Critical Action.
Which Github.com/weaveworks/weave versions are affected?
Affected versions include releases prior to 2.6.3 across affected packages: github.com/weaveworks/weave.
What version fixes CVE-2020-11091?
Upgrading to 2.6.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/weaveworks/weave affected?
Yes, github.com/weaveworks/weave is affected in releases prior to 2.6.3. Upgrade your dependency to 2.6.3 or later.
What is the CVSS score of CVE-2020-11091?
CVE-2020-11091 has a CVSS v3.1 base score of 5.8 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N.
What CWE is associated with CVE-2020-11091?
CVE-2020-11091 is classified under CWE-350: Reliance on Reverse DNS Resolution for a Security-Critical Action (The product performs reverse DNS resolution on an IP address to obtain the hostname and make a security decision, but it does not properly ensure that the IP address is truly associated with the hostname.).
How can I check Go dependencies for CVE-2020-11091?
Run the dependency tree command: 'inspect dependencies for github.com/weaveworks/weave'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-59qg-grp7-5r73",
  "modified" : "2021-05-24T21:05:31Z",
  "published" : "2021-05-27T19:00:08Z",
  "aliases" : [ "CVE-2020-11091" ],
  "summary" : "Weave Net clusters susceptible to MitM attacks via IPv6 rogue router advertisements",
  "details" : "### Impact\nAn 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.\n\nIn 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.\n\nBy 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.\nEven 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.\nIf 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.\n\n### Patches\nWeave Net version 2.6.3 (to be released soon) will disable the accept_ra option on the veth devices that it creates.\n\n### Workarounds\nUsers should not run containers with CAP_NET_RAW capability.  This has been the advice from Weave Net for years.\nhttps://www.weave.works/docs/net/latest/kubernetes/kube-addon/#-securing-the-setup\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the Weave Net repo](https://github.com/weaveworks/weave/issues/new)\n* Join the <a href=\"https://slack.weave.works/\" target=\"_blank\">Weave Users Slack</a>.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/weaveworks/weave"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.6.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/weaveworks/weave/security/advisories/GHSA-59qg-grp7-5r73"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2020-11091"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/weaveworks/weave/commit/15f21f1899060f7716c70a8555a084e836f39a60"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-350" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2021-05-24T21:05:31Z",
    "nvd_published_at" : null
  }
}