Skip to content
Fencer Intel
medium —

GHSA-7jmw-8259-q9jx json

Traefik has unexpected behavior with IPv4-mapped IPv6 addresses

published 2y ago modified 3mo ago also GO-2024-2917

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### Impact

There is a vulnerability in [Go managing various Is methods (IsPrivate, IsLoopback, etc) for IPv4-mapped IPv6 addresses](https://groups.google.com/g/golang-announce/c/XbxouI9gY7k/m/TuoGEhxIEwAJ).

They didn't work as expected returning false for addresses which would return true in their traditional IPv4 forms.

### References

- [CVE-2024-24790](https://www.cve.org/CVERecord?id=CVE-2024-24790)

### Patches

- https://github.com/traefik/traefik/releases/tag/v2.11.4 - https://github.com/traefik/traefik/releases/tag/v3.0.2

### Workarounds

No workaround.

### For more information

If you have any questions or comments about this advisory, please [open an issue](https://github.com/traefik/traefik/issues).

Patch / fix

  • go github.com/traefik/traefik/v3 3.0.2
  • go github.com/traefik/traefik/v2 2.11.4
  • go github.com/traefik/traefik 2.11.4

Is GHSA-7jmw-8259-q9jx 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 Fencer

Affected packages

ecosystem package affected fixed in
go github.com/traefik/traefik/v3
>=3.0.0-beta3, <3.0.2
3.0.2
go github.com/traefik/traefik/v2
<2.11.4
2.11.4
go github.com/traefik/traefik
<2.11.4
all versions
2.11.4

Classification

Weakness
  • CWE-180 Incorrect Behavior Order: Validate Before Canonicalize

References

Sources

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.