{"answers":{"affected":"3 open source packages ship an affected version, including github.com/weaveworks/weave. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-11091 in the wild and no public exploit code.","fix":"Upgrade github.com/weaveworks/weave to a fixed version for your release line: 2.6.3 or 2.6.3+incompatible.","what":"CVE-2020-11091 is a medium-severity vulnerability in weaveworks Weave, published on 3 Jun 2020. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-11091 and fix it if it is affected.\n\nWhat it is: CVE-2020-11091 is a medium-severity vulnerability in weaveworks Weave, published on 3 Jun 2020. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-11091 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/weaveworks/weave (Go): affected all versions; fixed in 2.6.3\n- github.com/weaveworks/weave (Go): affected all versions; fixed in 2.6.3\n- github.com/weaveworks/weave (Go): affected all versions; fixed in 2.6.3+incompatible\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2020-11091/ (Markdown: https://insights.sbomify.com/CVE-2020-11091/index.md)","id":"CVE-2020-11091","markdown":"https://insights.sbomify.com/CVE-2020-11091/index.md","name":"CVE-2020-11091","record":{"aliases":["GHSA-59qg-grp7-5r73","GO-2022-0794"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["security_bypass","code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Weave Net CNI plugin","requires_auth":"high_privilege","summary":"An attacker with root in a container can send rogue IPv6 router advertisements to intercept host traffic, enabling man-in-the-middle attacks and potential host compromise.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"weave_net","vendor":"weave"}],"cvss":{"score":5.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-350","name":"Reliance on Reverse DNS Resolution for a Security-Critical Action"}],"description":"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.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Weave Net clusters susceptible to MitM attacks via IPv6 rogue router advertisements","id":"CVE-2020-11091","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"other","year":"2020"},"n_packages":3,"n_references":2,"next":{"headline":"Authorization bypass in Hyperledger Indy","id":"CVE-2020-11093"},"packages":[{"ecosystem":"Go","fixed":["2.6.3"],"introduced":["0"],"last_affected":[],"package":"github.com/weaveworks/weave","purl":null,"source":"GHSA-59qg-grp7-5r73"},{"ecosystem":"Go","fixed":["2.6.3"],"introduced":["0"],"last_affected":[],"package":"github.com/weaveworks/weave","purl":"pkg:golang/github.com/weaveworks/weave","source":"GHSA-59qg-grp7-5r73"},{"ecosystem":"Go","fixed":["2.6.3+incompatible"],"introduced":["0"],"last_affected":[],"package":"github.com/weaveworks/weave","purl":"pkg:golang/github.com/weaveworks/weave","source":"GO-2022-0794"}],"prev":{"headline":"Uncontrolled Resource Consumption in Indy Node","id":"CVE-2020-11090"},"products":["Weave"],"published":"2020-06-03","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["weaveworks"]},"summary":"An attacker with root in a container can send rogue IPv6 router advertisements to intercept host traffic, enabling man-in-the-middle attacks and potential host compromise.","url":"https://insights.sbomify.com/CVE-2020-11091/"}