CVE-2019-25211

unknown

Published 2024-06-29 · Modified 2024-07-02

💬 Discuss on Community ✚ Propose mitigation

CVSS v3

—

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

CVSS v4 NEW

—

not yet in upstream

VIR risk

—

Description

parseWildcardRules in Gin-Gonic CORS middleware before 1.6.0 mishandles a wildcard at the end of an origin string, e.g., https://example.community/* is allowed when the intention is that only https://example.com/* should be allowed, and http://localhost.example.com/* is allowed when the intention is that only http://localhost/* should be allowed.

Predictions

Exploit likelihood

30%

Patch ETA

—

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.

✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

Debian Fixed 5 releases

Version	Status	Fixed in
trixie	Fixed	`1.4.0-1+deb13u1`
sid	Fixed	`1.7.6-1`
forky	Fixed	`1.7.6-1`
bullseye	Fixed	`1.3.1-1+deb11u1`
bookworm	Fixed	`1.4.0-1+deb12u1`

Package impact

Ecosystem	Package	Vulnerable	Fixed
Go	github.com/gin-gonic/gin	`<1.6.0`	`1.6.0`
Go	github.com/gin-contrib/cors	`<1.6.0`	`1.6.0`

References

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.