Bug 2276026 (CVE-2024-32473)
Summary: | CVE-2024-32473 moby: IPv6 enabled on IPv4-only network interfaces | ||
---|---|---|---|
Product: | [Other] Security Response | Reporter: | Robb Gatica <rgatica> |
Component: | vulnerability | Assignee: | Product Security <prodsec-ir-bot> |
Status: | NEW --- | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | gparvin, lbainbri, njean, owatkins, pahickey, rhaigner |
Target Milestone: | --- | Keywords: | Security |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | moby 26.0.2 | Doc Type: | If docs needed, set a value |
Doc Text: |
A flaw was found in Moby, an open source container framework that is a key component of Docker Engine, Docker Desktop, and other distributions of container tooling and runtimes. In certain versions, IPv6 is not disabled on network interfaces, including those belonging to networks where "--ipv6=false". A container with an "ipvlan" or "macvlan" interface will normally be configured to share an external network link with the host machine, and because of this direct access, containers may be able to communicate with other hosts on the local network over link-local IPv6 addresses. Additionally, if router advertisements are being broadcast over the local network, containers may get SLAAC-assigned addresses and the interface will be a member of IPv6 multicast groups. This means interfaces IPv4-only networks present an unexpectedly and unnecessarily increased attack surface
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | Type: | --- | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 2290430 | ||
Bug Blocks: | 2276009 |
Description
Robb Gatica
2024-04-19 04:10:40 UTC
Created golang-github-docker tracking bugs for this issue: Affects: fedora-all [bug 2290430] |