Skip to content

Gin Web Framework does not properly sanitize filename parameter of Context.FileAttachment function

Moderate severity GitHub Reviewed Published May 12, 2023 to the GitHub Advisory Database • Updated Nov 5, 2023

Package

gomod github.com/gin-gonic/gin (Go)

Affected versions

>= 1.3.1-0.20190301021747-ccb9e902956d, < 1.9.1

Patched versions

1.9.1

Description

The filename parameter of the Context.FileAttachment function is not properly sanitized. A maliciously crafted filename can cause the Content-Disposition header to be sent with an unexpected filename value or otherwise modify the Content-Disposition header. For example, a filename of "setup.bat";x=.txt" will be sent as a file named "setup.bat".

If the FileAttachment function is called with names provided by an untrusted source, this may permit an attacker to cause a file to be served with a name different than provided. Maliciously crafted attachment file name can modify the Content-Disposition header.

References

Published to the GitHub Advisory Database May 12, 2023
Reviewed May 12, 2023
Published by the National Vulnerability Database Jun 8, 2023
Last updated Nov 5, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

EPSS score

0.159%
(53rd percentile)

Weaknesses

CVE ID

CVE-2023-29401

GHSA ID

GHSA-2c4m-59x9-fr2g

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.