Vulnerability in golang-github-gin-contrib-cors
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as DEBIAN-CVE-2019-25211 has been found in golang-github-gin-contrib-cors.
Confidential information can be exposed externally.
What to do: upgrade golang-github-gin-contrib-cors to 1.4.0-1+deb12u1 or later.
If unsure, ask your IT team or search "golang-github-gin-contrib-cors DEBIAN-CVE-2019-25211" on the vendor's site.
DEBIAN-CVE-2019-25211 (golang-github-gin-contrib-cors)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.4.0-1+deb12u1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) exists in golang-github-gin-contrib-cors.
Check the vendor advisory for the affected versions of golang-github-gin-contrib-cors.
Severity: ?. Confidential information can be exposed externally.
Update to 1.4.0-1+deb12u1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'golang-github-gin-contrib-cors' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1
Identify exposureidentify
grep -r 'golang-github-gin-contrib-cors' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
golang-github-gin-contrib-corsを grep し、稼働しているサービス・バージョンを把握する。 -
2
Apply patchpatch
Upgrade golang-github-gin-contrib-cors to 1.4.0-1+deb12u1ステージング環境で 1.4.0-1+deb12u1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3
Post-deployment verificationverify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| Debian:12 | golang-github-gin-contrib-cors |
< 1.4.0-1+deb12u1 |
1.4.0-1+deb12u1 |
| Debian:13 | golang-github-gin-contrib-cors |
< 1.4.0-1+deb13u1 |
1.4.0-1+deb13u1 |
Original description The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) OSV
References
- advisory security-tracker.debian.org