Skip to content

Traefik affected by Go oauth2/jws Improper Validation of Syntactic Correctness of Input vulnerability

High severity GitHub Reviewed Published Apr 18, 2025 in traefik/traefik • Updated Apr 18, 2025

Package

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

Affected versions

< 2.11.24

Patched versions

2.11.24
gomod github.com/traefik/traefik/v3 (Go)
< 3.3.6
= 3.4.0-rc1
3.3.6
3.4.0-rc2

Description

Summary

We have encountered a security vulnerability being reported by our scanners for Traefik 2.11.22.

Details

It seems to target oauth2/jws library.

PoC

No steps to replicate this vulnerability

Impact

We have a strict control on security and we always try to stay up-to-date with the fixes received for third-party solutions.

Patches

References

@emilevauge emilevauge published to traefik/traefik Apr 18, 2025
Published to the GitHub Advisory Database Apr 18, 2025
Reviewed Apr 18, 2025
Last updated Apr 18, 2025

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

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(16th percentile)

Weaknesses

CVE ID

CVE-2025-22868

GHSA ID

GHSA-3wqc-mwfx-672p

Source code

Credits

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