CVE-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 ...

Description

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.

Metrics

CVSS 3.1

9.8/10

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

EPSS Probability

0.66%

46.9th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

Vendor	Product	Versions
Gofiber	Fiber	< 2.52.1

References

http://blog.portswigger.net/2016/10/exploiting-cors-misconfigurations-for.htmlExploit, Third Party Advisory
https://codeql.github.com/codeql-query-help/javascript/js-cors-misconfiguration-for-credentialsTechnical Description
https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors/CORSNotSupportingCredentialsTechnical Description
https://fetch.spec.whatwg.org/#cors-protocol-and-credentialsTechnical Description
https://github.com/gofiber/fiber/commit/f0cd3b44b086544a37886232d0530601f2406c23Patch
https://github.com/gofiber/fiber/releases/tag/v2.52.1Release Notes
https://github.com/gofiber/fiber/security/advisories/GHSA-fmg4-x8pw-hjhgExploit, Vendor Advisory
https://saturncloud.io/blog/cors-cannot-use-wildcard-in-accesscontrolalloworigin-when-credentials-flag-is-trueBroken Link
http://blog.portswigger.net/2016/10/exploiting-cors-misconfigurations-for.htmlExploit, Third Party Advisory
https://codeql.github.com/codeql-query-help/javascript/js-cors-misconfiguration-for-credentialsTechnical Description
https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors/CORSNotSupportingCredentialsTechnical Description
https://fetch.spec.whatwg.org/#cors-protocol-and-credentialsTechnical Description
https://github.com/gofiber/fiber/commit/f0cd3b44b086544a37886232d0530601f2406c23Patch
https://github.com/gofiber/fiber/releases/tag/v2.52.1Release Notes
https://github.com/gofiber/fiber/security/advisories/GHSA-fmg4-x8pw-hjhgExploit, Vendor Advisory
https://saturncloud.io/blog/cors-cannot-use-wildcard-in-accesscontrolalloworigin-when-credentials-flag-is-trueBroken Link

Timeline

Published: Feb 21, 2024
Last Modified: Jun 17, 2026
Status: Analyzed

Frequently Asked Questions

What is CVE-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 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.

How severe is CVE-2024-25124?

CVE-2024-25124 has a CVSS score of 9.8/10 (CRITICAL severity). The EPSS model estimates a 0.66% probability of exploitation in the next 30 days.

How do I fix CVE-2024-25124?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2024

View all 2024CVEs →