7.3
CVSSv3

CVE-2023-26125

Published: 04/05/2023 Updated: 07/11/2023
CVSS v3 Base Score: 7.3 | Impact Score: 3.4 | Exploitability Score: 3.9
VMScore: 0

Vulnerability Summary

Versions of the package github.com/gin-gonic/gin prior to 1.9.0 are vulnerable to Improper Input Validation by allowing an malicious user to use a specially crafted request via the X-Forwarded-Prefix header, potentially leading to cache poisoning. **Note:** Although this issue does not pose a significant threat on its own it can serve as an input vector for other more impactful vulnerabilities. However, successful exploitation may depend on the server configuration and whether the header is used in the application logic.

Vulnerability Trend

Vulnerable Product Search on Vulmon Subscribe to Product

gin-gonic gin

Vendor Advisories

Debian Bug report logs - #1035498 golang-github-gin-gonic-gin: CVE-2023-26125 Package: src:golang-github-gin-gonic-gin; Maintainer for src:golang-github-gin-gonic-gin is Debian Go Packaging Team <team+pkg-go@trackerdebianorg>; Reported by: Salvatore Bonaccorso <carnil@debianorg> Date: Thu, 4 May 2023 09:00:01 UTC ...
Synopsis Important: Migration Toolkit for Applications security and bug fix update Type/Severity Security Advisory: Important Topic Migration Toolkit for Applications 620 releaseRed Hat Product Security has rated this update as having a security impact of Important A Common Vulnerability Scoring System (CVSS) base score, which gives a deta ...
Synopsis Moderate: Migration Toolkit for Containers (MTC) 1711 security and bug fix update Type/Severity Security Advisory: Moderate Topic The Migration Toolkit for Containers (MTC) 1711 is now availableRed Hat Product Security has rated this update as having a security impact of Moderate A Common Vulnerability Scoring System (CVSS) bas ...
DescriptionThe MITRE CVE dictionary describes this issue as: Versions of the package githubcom/gin-gonic/gin before 190 are vulnerable to Improper Input Validation by allowing an attacker to use a specially crafted request via the X-Forwarded-Prefix header, potentially leading to cache poisoning **Note:** Although this issue does not pose a sig ...