Skip to content

Traefik HTTP/2 connections management could cause a denial of service

High severity GitHub Reviewed Published Oct 10, 2022 in traefik/traefik • Updated Jul 14, 2023

Package

gomod github.com/traefik/traefik/v2 (Go)

Affected versions

< 2.8.8
>= 2.9.0-rc1, < 2.9.0-rc5

Patched versions

2.8.8
2.9.0-rc5

Description

Impact

There is a potential vulnerability in Traefik managing HTTP/2 connections.
A closing HTTP/2 server connection could hang forever because of a subsequent fatal error. This failure mode could be exploited to cause a denial of service.

Patches

Traefik v2.8.x: https://github.com/traefik/traefik/releases/tag/v2.8.8
Traefik v2.9.x: https://github.com/traefik/traefik/releases/tag/v2.9.0-rc5

Workarounds

No workaround.

For more information

If you have any questions or comments about this advisory, please open an issue.

References

@nmengin nmengin published to traefik/traefik Oct 10, 2022
Published to the GitHub Advisory Database Oct 10, 2022
Reviewed Oct 10, 2022
Published by the National Vulnerability Database Oct 11, 2022
Last updated Jul 14, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.085%
(37th percentile)

Weaknesses

CVE ID

CVE-2022-39271

GHSA ID

GHSA-c6hx-pjc3-7fqr

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.