GHSA-3wqc-mwfx-672p json
Traefik affected by Go oauth2/jws Improper Validation of Syntactic Correctness of Input vulnerability
published last yr. modified 2mo ago
- cvss
- 7.5
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
### Summary We have encountered a security vulnerability being reported by our scanners for Traefik 2.11.22. - https://security.snyk.io/vuln/SNYK-CHAINGUARDLATEST-TRAEFIK33-9403297
### 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
- https://github.com/traefik/traefik/releases/tag/v2.11.24 - https://github.com/traefik/traefik/releases/tag/v3.3.6 - https://github.com/traefik/traefik/releases/tag/v3.4.0-rc2
Patch / fix
- go github.com/traefik/traefik/v3 3.3.6, 3.4.0-rc2
- go github.com/traefik/traefik/v2 2.11.24
Is GHSA-3wqc-mwfx-672p in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/traefik/traefik/v3 | <3.3.6 >=3.4.0-rc1, <3.4.0-rc2 |
3.3.6 3.4.0-rc2 |
| go | github.com/traefik/traefik/v2 | <2.11.24 |
2.11.24 |
Classification
- Weakness
-
- CWE-1286 Improper Validation of Syntactic Correctness of Input
References
-
github.com
/traefik/traefik/security/advisories/GHSA-3wqc-mwfx-672p
web
-
github.com
/traefik/traefik
package
-
github.com
/traefik/traefik/releases/tag/v2.11.24
web
-
github.com
/traefik/traefik/releases/tag/v3.3.6
web
-
github.com
/traefik/traefik/releases/tag/v3.4.0-rc2
web
-
security.snyk.io
/vuln/SNYK-CHAINGUARDLATEST-TRAEFIK33-9403297
web
Sources
- GitHub Advisory GHSA-3wqc-mwfx-672p
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.