CVE-2024-45410
Public on
Last Modified:
Description
A flaw was found in Traefik. When a HTTP request is processed by Traefik, certain HTTP headers such as X-Forwarded-Host or X-Forwarded-Port are added by Traefik before the request is routed to the application. For a HTTP client, it should not be possible to remove or modify these headers. Since the application trusts the value of these headers, security implications might arise if they can be modified. For HTTP/1.1, however, it was found that some of theses custom headers can indeed be removed and in certain cases manipulated.
Statement
This vulnerability in Traefik is important due to its impact on the integrity of HTTP headers that are often used for security-sensitive operations. When the X-Forwarded headers, such as X-Forwarded-Host or X-Forwarded-Tls-Client-Cert, can be removed or manipulated by the client, applications relying on these headers for trust validation, client authentication, or access control are exposed to potential privilege escalation or unauthorized access. The ability to bypass or alter these headers compromises the security model that many backend services depend on, particularly in reverse proxy or load balancer setups.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Additional Information
- This content is not included.Bugzilla 2313584: traefik: HTTP client can manipulate custom HTTP headers that are added by Traefik
- (Content from cwe.mitre.org is not included.CWE-345|Content from cwe.mitre.org is not included.CWE-348): Insufficient Verification of Data Authenticity or Use of Less Trusted Source
- FAQ: Frequently asked questions about CVE-2024-45410
- Offline Security Data data is available for integration with other systems. See Offline Security Data API to get started.
External References
Content from www.cve.org is not included.https://www.cve.org/CVERecord?id=CVE-2024-45410
Content from nvd.nist.gov is not included.https://nvd.nist.gov/vuln/detail/CVE-2024-45410
Content from github.com is not included.https://github.com/traefik/traefik
Content from github.com is not included.https://github.com/traefik/traefik/releases/tag/v2.11.9
Content from github.com is not included.https://github.com/traefik/traefik/releases/tag/v3.1.3
Affected Packages and Issued Red Hat Security Errata
| Products / Services | Components | State | Errata |
|---|---|---|---|
| Red Hat OpenShift Dev Spaces | devspaces/devspaces-rhel8-operator | Not affected | |
| Red Hat OpenShift Dev Spaces 3 Containers | devspaces-tech-preview/idea-rhel9 | Fixed | RHSA-2025:8244 |
| Red Hat OpenShift Dev Spaces 3 Containers | devspaces-tech-preview/jetbrains-ide-rhel9 | Fixed | RHSA-2025:8244 |
| Red Hat OpenShift Dev Spaces 3 Containers | devspaces/code-rhel9 | Fixed | RHSA-2025:8244 |
| Red Hat OpenShift Dev Spaces 3 Containers | devspaces/configbump-rhel9 | Fixed | RHSA-2025:8244 |
| Red Hat OpenShift Dev Spaces 3 Containers | devspaces/dashboard-rhel9 | Fixed | RHSA-2025:8244 |
| Red Hat OpenShift Dev Spaces 3 Containers | devspaces/devspaces-operator-bundle | Fixed | RHSA-2025:8244 |
| Red Hat OpenShift Dev Spaces 3 Containers | devspaces/devspaces-rhel9-operator | Fixed | RHSA-2025:8244 |
| Red Hat OpenShift Dev Spaces 3 Containers | devspaces/imagepuller-rhel9 | Fixed | RHSA-2025:8244 |
| Red Hat OpenShift Dev Spaces 3 Containers | devspaces/machineexec-rhel9 | Fixed | RHSA-2025:8244 |
| Red Hat OpenShift Dev Spaces 3 Containers | devspaces/pluginregistry-rhel9 | Fixed | RHSA-2025:8244 |
| Red Hat OpenShift Dev Spaces 3 Containers | devspaces/server-rhel9 | Fixed | RHSA-2025:8244 |
| Red Hat OpenShift Dev Spaces 3 Containers | devspaces/traefik-rhel9 | Fixed | RHSA-2025:8244 |
| Red Hat OpenShift Dev Spaces 3 Containers | devspaces/udi-base-rhel9 | Fixed | RHSA-2025:8244 |
| Red Hat OpenShift Dev Spaces 3 Containers | devspaces/udi-rhel9 | Fixed | RHSA-2025:8244 |
| Red Hat OpenShift GitOps | openshift-gitops-1/argo-rollouts-rhel8 | Not affected |
Common Vulnerability Scoring System (CVSS) Score Details
Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authorities (CNA) source for its products and services (see Red Hat classifications ).
| CVSS v3 Score Breakdown | Red Hat | NVD |
|---|---|---|
| CVSS v3 Base Score | 8.6 | 7.5 |
| Attack Vector | Network | Network |
| Attack Complexity | Low | Low |
| Privileges Required | None | None |
| User Interaction | None | None |
| Scope | Changed | Unchanged |
| Confidentiality Impact | None | None |
| Integrity Impact | High | High |
| Availability Impact | None | None |
CVSS v3 Vector
Red Hat CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N
NVD CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Red Hat CVSS v3 Score Explanation
Redhat identifies that the scope of this vulnerability is changed as headers are used as security mechanism in the application,removing or changing of these headers can result in further security degradation of the system.
Frequently Asked Questions
Why is Red Hat's CVSS v3 score or Impact different from other vendors?
For more information, see https://access.redhat.com/solutions/762393.
My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?
- "Under investigation" doesn't necessarily mean that the product is affected by this vulnerability. It only means that our Analysis Team is still working on determining whether the product is affected and how it is affected.
- "Affected" means that our Analysis Team has determined that this product is affected by this vulnerability and might release a fix to address this in the near future.
What can I do if my product is listed as "Will not fix"?
Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
- Upgrade to a supported product version that includes a fix for this vulnerability (recommended).
- Apply a mitigation (if one exists).
- Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
What can I do if my product is listed as "Fix deferred"?
Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
- Apply a mitigation (if one exists).
- Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
- Red Hat Engineering focuses on addressing high-priority issues based on their complexity or limited lifecycle support. Therefore, lower-priority issues will not receive immediate fixes.
What is a mitigation?
I have a Red Hat product but it is not in the above list, is it affected?
Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?
Not sure what something means? Check out our Security Glossary.