First published: Thu May 04 2023(Updated: )
A flaw was found in Gin-Gonic Gin. This flaw allows a remote attacker to bypass security restrictions caused by improper input validation. An attacker can perform cache poisoning attacks by sending a specially-crafted request using the X-Forwarded-Prefix header.
Credit: report@snyk.io report@snyk.io
Affected Software | Affected Version | How to fix |
---|---|---|
Gin-Gonic Gin | <1.9.0 | |
go/github.com/gin-gonic/gin | <1.9.0 | 1.9.0 |
redhat/github.com/gin-gonic/gin | <1.9.0 | 1.9.0 |
IBM Planning Analytics Local - IBM Planning Analytics Workspace | <=2.1 | |
IBM Planning Analytics Local - IBM Planning Analytics Workspace | <=2.0 |
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID for this flaw in Gin-Gonic Gin is CVE-2023-26125.
The severity of CVE-2023-26125 is high with a severity value of 7.3.
CVE-2023-26125 affects versions of the Gin-Gonic Gin package before version 1.9.0.
An attacker can exploit CVE-2023-26125 by using a specially crafted request via the X-Forwarded-Prefix header, potentially leading to cache poisoning.
Yes, the fix for CVE-2023-26125 is to upgrade to version 1.9.0 or later of the Gin-Gonic Gin package.