CVE-2024-25124
published 2024-02-21CVE-2024-25124: Fiber is a web framework written in go. Prior to version 2.52.1, the CORS middleware allows for insecure configurations that could potentially expose the…
PriorityP355critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EPSS
0.66%
46.9th percentile
Fiber is a web framework written in go. Prior to version 2.52.1, the CORS middleware allows for insecure configurations that could potentially expose the application to multiple CORS-related vulnerabilities. Specifically, it allows setting the Access-Control-Allow-Origin header to a wildcard (`*`) while also having the Access-Control-Allow-Credentials set to true, which goes against recommended security best practices. The impact of this misconfiguration is high as it can lead to unauthorized access to sensitive user data and expose the system to various types of attacks listed in the PortSwigger article linked in the references. Version 2.52.1 contains a patch for this issue. As a workaround, users may manually validate the CORS configurations in their implementation to ensure that they do not allow a wildcard origin when credentials are enabled. The browser fetch api, as well as browsers and utilities that enforce CORS policies, are not affected by this.
Affected
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| github.com | gofiber_fiber_v2 | >= 0 < 2.52.1 | 2.52.1 |
| gofiber | fiber | < 2.52.1 | 2.52.1 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Insecure CORS Configuration allowing wildcard origin with credentials in github.com/gofiber/fiber/v2
osv·2024-05-20
CVE-2024-25124 Insecure CORS Configuration allowing wildcard origin with credentials in github.com/gofiber/fiber/v2
Insecure CORS Configuration allowing wildcard origin with credentials in github.com/gofiber/fiber/v2
The CORS middleware allows for insecure configurations that could potentially expose the application to multiple CORS-related vulnerabilities. Specifically, it allows setting the Access-Control-Allow-Origin header to a wildcard ("*") while also having the Access-Control-Allow-Credentials set to true, which goes against recommended security best practices.
GHSA
Fiber has Insecure CORS Configuration, Allowing Wildcard Origin with Credentials
ghsa·2024-02-22
CVE-2024-25124 [CRITICAL] CWE-346 Fiber has Insecure CORS Configuration, Allowing Wildcard Origin with Credentials
Fiber has Insecure CORS Configuration, Allowing Wildcard Origin with Credentials
The CORS middleware allows for insecure configurations that could potentially expose the application to multiple CORS-related vulnerabilities. Specifically, it allows setting the Access-Control-Allow-Origin header to a wildcard ("*") while also having the Access-Control-Allow-Credentials set to true, which goes against recommended security best practices.
## Impact
The impact of this misconfiguration is high as it can lead to unauthorized access to sensitive user data and expose the system to various types of attacks listed in the PortSwigger article linked in the references.
## Proof of Concept
The code in cors.go allows setting a wildcard in the AllowOrigins while having AllowCredentials set to true, whic
OSV
Fiber has Insecure CORS Configuration, Allowing Wildcard Origin with Credentials
osv·2024-02-22
CVE-2024-25124 [CRITICAL] Fiber has Insecure CORS Configuration, Allowing Wildcard Origin with Credentials
Fiber has Insecure CORS Configuration, Allowing Wildcard Origin with Credentials
The CORS middleware allows for insecure configurations that could potentially expose the application to multiple CORS-related vulnerabilities. Specifically, it allows setting the Access-Control-Allow-Origin header to a wildcard ("*") while also having the Access-Control-Allow-Credentials set to true, which goes against recommended security best practices.
## Impact
The impact of this misconfiguration is high as it can lead to unauthorized access to sensitive user data and expose the system to various types of attacks listed in the PortSwigger article linked in the references.
## Proof of Concept
The code in cors.go allows setting a wildcard in the AllowOrigins while having AllowCredentials set to true, whic
No detection rules found.
No public exploits indexed.
http://blog.portswigger.net/2016/10/exploiting-cors-misconfigurations-for.htmlhttps://codeql.github.com/codeql-query-help/javascript/js-cors-misconfiguration-for-credentialshttps://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors/CORSNotSupportingCredentialshttps://fetch.spec.whatwg.org/#cors-protocol-and-credentialshttps://github.com/gofiber/fiber/commit/f0cd3b44b086544a37886232d0530601f2406c23https://github.com/gofiber/fiber/releases/tag/v2.52.1https://github.com/gofiber/fiber/security/advisories/GHSA-fmg4-x8pw-hjhghttps://saturncloud.io/blog/cors-cannot-use-wildcard-in-accesscontrolalloworigin-when-credentials-flag-is-truehttp://blog.portswigger.net/2016/10/exploiting-cors-misconfigurations-for.htmlhttps://codeql.github.com/codeql-query-help/javascript/js-cors-misconfiguration-for-credentialshttps://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors/CORSNotSupportingCredentialshttps://fetch.spec.whatwg.org/#cors-protocol-and-credentialshttps://github.com/gofiber/fiber/commit/f0cd3b44b086544a37886232d0530601f2406c23https://github.com/gofiber/fiber/releases/tag/v2.52.1https://github.com/gofiber/fiber/security/advisories/GHSA-fmg4-x8pw-hjhghttps://saturncloud.io/blog/cors-cannot-use-wildcard-in-accesscontrolalloworigin-when-credentials-flag-is-true
2024-02-21
Published