CVE-2023-47633: Github.com/traefik/traefik/v2 Traefik Docker Container Using 100% Vulnerability
HIGHCVE-2023-47633 is a HIGH (CVSS 7.5) traefik docker container using 100% vulnerability (CWE-400: Uncontrolled Resource Consumption) affecting Github.com/traefik/traefik/v2 libraries in the Go ecosystem. The issue involves traefik docker container using 100% cpu. Remediation is available by upgrading affected packages to version 2.10.6, 3.0.0-beta5.
CVE-2023-47633 at a Glance
Security Impact
CVSS: 7.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
How to Fix CVE-2023-47633
To remediate this vulnerability, upgrade all affected Github.com/traefik/traefik/v2 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/traefik/traefik/v2 to 2.10.6
Upgrade github.com/traefik/traefik/v3 to 3.0.0-beta5
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/traefik/traefik/v2
How to Check if You Are Affected
To determine whether your application is affected by CVE-2023-47633, inspect your project dependencies for Github.com/traefik/traefik/v2:
inspect dependencies for github.com/traefik/traefik/v2
Analyze the terminal output to locate any version of Github.com/traefik/traefik/v2 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.10.6), 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-400: Uncontrolled Resource Consumption, where the product does not properly control the allocation and maintenance of a limited resource. In Github.com/traefik/traefik/v2, 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
CVE-2023-47633 Affected Github.com/traefik/traefik/v2 Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/traefik/traefik/v2
|
Go |
< 2.10.6
|
2.10.6
|
|
github.com/traefik/traefik/v3
|
Go |
< 3.0.0-beta5
|
3.0.0-beta5
|
References
Frequently Asked Questions
What is CVE-2023-47633?
Which Github.com/traefik/traefik/v2 versions are affected?
What version fixes CVE-2023-47633?
Is github.com/traefik/traefik/v2 affected?
Is github.com/traefik/traefik/v3 affected?
What is the CVSS score of CVE-2023-47633?
What CWE is associated with CVE-2023-47633?
How can I check Go dependencies for CVE-2023-47633?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-6fwg-jrfw-ff7p",
"modified" : "2023-12-05T18:13:54Z",
"published" : "2023-12-05T18:13:53Z",
"aliases" : [ "CVE-2023-47633" ],
"summary" : "Traefik docker container using 100% CPU",
"details" : "### Summary\n\nThe traefik docker container uses 100% CPU when it serves as its own backend, which is an automatically generated route resulting from the Docker integration in the default configuration.\n\n### Details\n\nWhile attempting to set up Traefik to handle traffic for Docker containers, I observed in the webUI a rule with the following information:\n\n`Host(traefik-service) | webwebsecure | traefik-service@docker | traefik-service`\n\nI assumed that this is something internal; however, I wondered why it would have a host rule on the web entrypoint configured.\n\nSo I have send a request with that hostname with `curl -v --resolve \"traefik-service:80:xxx.xxx.xxx.xxx\" http://traefik-service`. That made my whole server unresponsive.\n\nI assume the name comes from a docker container with that name, traefik itself:\n```\nlocalhost ~ # docker ps\nCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES\nd1414e74aec7 traefik:v2.10 \"/entrypoint.sh trae…\" 4 minutes ago Up 4 minutes 0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp, 127.0.0.1:8080->8080/tcp traefik.service\n```\n\n### PoC\n\n1. Start traefik with `docker run --rm -v /var/run/docker.sock:/var/run/docker.sock -p 80:80 --name foo -p 8080:8080 traefik:v2.10 --api.insecure=true --providers.docker`\n\n2. `curl -v --resolve \"foo:80:127.0.0.1\" http://foo`\n\nlooks like this creates an endless loop of request.\n\nKnowing the name of the docker container seems to be enough to trigger this, if the docker backend is used.\n\n### Impact\n\nServer is unreachable and uses 100% CPU",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/traefik/traefik/v2"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "2.10.6"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/traefik/traefik/v3"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "3.0.0-beta5"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/traefik/traefik/security/advisories/GHSA-6fwg-jrfw-ff7p"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2023-47633"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/traefik/traefik"
}, {
"type" : "WEB",
"url" : "https://github.com/traefik/traefik/releases/tag/v2.10.6"
}, {
"type" : "WEB",
"url" : "https://github.com/traefik/traefik/releases/tag/v3.0.0-beta5"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-400", "CWE-770" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2023-12-05T18:13:53Z",
"nvd_published_at" : "2023-12-04T21:15:34Z"
}
}