LiveActive security incident?Get immediate response
CVE Record

CVE-2019-25211: parseWildcardRules in Gin-Gonic CORS middleware before 1.6.0 mishandles a wildcard at the end of an origin...

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.

CriticalCVSS 9.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This flaw can make a web service trust more websites than intended for browser cross-origin access. If an application used vulnerable Gin-Gonic CORS middleware with affected wildcard origin rules, hostile or unintended origins could be accepted. The business risk is unauthorized exposure or modification of data through a user’s browser session.

Executive priority

Prioritize internet-facing or customer-facing services that use Gin with CORS and handle authenticated or sensitive data. Treat remediation as urgent where vulnerable versions and wildcard origin rules coexist.

Technical view

CVE-2019-25211 affects Gin-Gonic CORS middleware before 1.6.0. The wildcard rule parser mishandles trailing wildcards in origin strings, causing broader matches than intended. The CVE maps to CWE-346 and has CVSS 3.1 score 9.1 for network, unauthenticated impact to confidentiality and integrity.

Likely exposure

Exposure is likely limited to Go services using gin-contrib/cors before 1.6.0 and configured with wildcard origin allow rules. Services with strict exact-origin CORS policies or no browser-facing sensitive endpoints are less exposed.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Practical abuse would depend on a vulnerable CORS configuration, a browser-accessible service, and user/session context where unintended origins can read or influence protected responses.

Researcher notes

The key issue is incorrect origin validation, not general remote code execution. The affected metadata in the bundle is sparse, but references identify gin-contrib/cors before 1.6.0, related pull requests, compare diff, release, commit, and Debian LTS notice.

Mitigation direction

  • Upgrade gin-contrib/cors to version 1.6.0 or later.
  • Review CORS allow-lists for trailing wildcard origin patterns.
  • Prefer exact trusted origins where possible.
  • Check Debian or vendor package guidance if using packaged dependencies.

Validation and detection

  • Inventory applications using gin-contrib/cors and identify versions below 1.6.0.
  • Review runtime CORS configuration for wildcard origin allow rules.
  • Add regression tests rejecting unintended lookalike origins.
  • Confirm browser responses do not allow unexpected origins.
Prepared
Confidence
medium
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-346: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-25211 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.1 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2019-25211Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE-346

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-346 · source CWE mapping

Origin Validation Error

Origin Validation Error represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs