CVE-2019-25211: GO-2024-2955 - Gin mishandles a wildcard in the origin string in github.com/gin-contrib/cors

CVE-2019-25211 · Severity: low · CVSS 3.1 · Published 2024-07-02

Gin mishandles a wildcard in the origin string in github.com/gin-contrib/cors

Technologies: github.com/gin-gonic/gin (Go). Vendors: Go.

Quick answers

Is CVE-2019-25211 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2019-25211 being exploited in the wild.
How severe is CVE-2019-25211?
Low severity, with a CVSS score of 3.1, published 2 July 2024.
Which products and versions are affected?
github.com/gin-contrib/cors (Go) SEMVER:introduced=0,fixed=1.6.0; github.com/gin-gonic/gin (Go) SEMVER:introduced=0,fixed=1.6.0.
Is there a fix for CVE-2019-25211?
Yes. github.com/gin-contrib/cors (Go): upgrade to 1.6.0 or later; github.com/gin-gonic/gin (Go): upgrade to 1.6.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2019-25211?
Check whether you run github.com/gin-contrib/cors (Go) or github.com/gin-gonic/gin (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/gin-contrib/cors (Go): upgrade to 1.6.0 or later
    go get github.com/gin-contrib/cors@v1.6.0
  • github.com/gin-gonic/gin (Go): upgrade to 1.6.0 or later
    go get github.com/gin-gonic/gin@v1.6.0

Affected products

  • github.com/gin-contrib/cors (Go) SEMVER:introduced=0,fixed=1.6.0
  • github.com/gin-gonic/gin (Go) SEMVER:introduced=0,fixed=1.6.0

Identifiers

  • CVE-2019-25211
  • GHSA-869c-j7wc-8jqv
  • GO-2024-2955

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.