CVE-2023-26125: Input Validation

Published May 4, 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.

Other sources

Gin-Gonic Gin could allow a remote attacker to bypass security restrictions, caused by improper input validation. By sending a specially-crafted request using the X-Forwarded-Prefix header, an attacker could exploit this vulnerability to perform cache poisoning attacks.

IBM

Versions of the package github.com/gin-gonic/gin before 1.9.0 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 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.

https://github.com/t0rchwo0d/gin/commit/fd9f98e70fb4107ee68c783482d231d35e60507b https://github.com/gin-gonic/gin/pull/3500 https://security.snyk.io/vuln/SNYK-GOLANG-GITHUBCOMGINGONICGIN-3324285 https://github.com/gin-gonic/gin/pull/3503 https://github.com/gin-gonic/gin/releases/tag/v1.9.0

Red Hat

Versions of the package github.com/gin-gonic/gin before version 1.9.0 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 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.

GitHub

Affected Software

5 affected componentsFixes available
redhat/github.com/gin-gonic/gin<1.9.0
1.9.0
gin-gonic gin<1.9.0
go/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

Remediation

Information

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.

Event History

May 4, 2023
CVE Published
12:00 AM
Data Sourced
12:00 AM
RemedyDescriptionSeverityWeaknessAffected Software
CVE Published
via MITRE·05:00 AM
Data Sourced
via MITRE·05:00 AM
DescriptionSeverityWeakness
Advisory Published
via GitHub·06:30 AM
May 15, 2023
Data Sourced
via Red Hat·08:25 AM
DescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the vulnerability ID for this flaw in Gin-Gonic Gin?

The vulnerability ID for this flaw in Gin-Gonic Gin is CVE-2023-26125.

2

What is the severity of CVE-2023-26125?

The severity of CVE-2023-26125 is high with a severity value of 7.3.

3

How does CVE-2023-26125 affect the Gin-Gonic Gin package?

CVE-2023-26125 affects versions of the Gin-Gonic Gin package before version 1.9.0.

4

How can an attacker exploit CVE-2023-26125?

An attacker can exploit CVE-2023-26125 by using a specially crafted request via the X-Forwarded-Prefix header, potentially leading to cache poisoning.

5

Is there a fix available for CVE-2023-26125?

Yes, the fix for CVE-2023-26125 is to upgrade to version 1.9.0 or later of the Gin-Gonic Gin package.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203