You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
CVE-2024-25124 - Critical Severity Vulnerability
Vulnerable Library - github.com/gofiber/fiber/v2-v2.1.4
⚡️ Express inspired web framework written in Go
Library home page: https://proxy.golang.org/github.com/gofiber/fiber/v2/@v/v2.1.4.zip
Path to dependency file: /infrastructure/health-check/go.mod
Path to vulnerable library: /infrastructure/health-check/go.mod
Dependency Hierarchy:
Found in base branch: master
Vulnerability Details
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.Publish Date: 2024-02-21
URL: CVE-2024-25124
CVSS 3 Score Details (9.4)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-fmg4-x8pw-hjhg
Release Date: 2024-02-21
Fix Resolution: v2.52.1
⛑️ Automatic Remediation will be attempted for this issue.
The text was updated successfully, but these errors were encountered: