NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

CVE-2023-29401 — gin

MEDIUMFix: gin-gonic/gin#3556

CVE-2023-29401 is a medium-severity (CVSS 4.3) CWE-494 vulnerability in github.com/gin-gonic/gin. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for github.com/gin-gonic/gin — see the affected versions and patch details below.

Improper handling of filenames in Content-Disposition HTTP header in github.com/gin-gonic/gin

Also known asGHSA-2c4m-59x9-fr2gGO-2023-1737
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-29401.

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs42th percentile — riskier than 42% of all scored CVEsHighest risk
0.00%0.33%0.66%0.99%0.4%0.5%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐹github.com/gin-gonic/gin

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/gin-gonic/gin≥ 1.3.1-0.20190301021747-ccb9e902956d&&< 1.9.11.9.1go get github.com/gin-gonic/gin@v1.9.1

Affected Products

1 product · 1 configurations
Application
gingin-gonic
≥ 1.3.1-0.20190301021747-ccb9e902956d && < 1.9.1
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The filename parameter of the Context.FileAttachment function is not pro…

github.comNVDJun 2023

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/gin-gonic/gin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/gin-gonic/gin to 1.9.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-29401 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate
ProductFixed inAdvisory
Migration Toolkit for Virtualization 2.5migration-toolkit-virtualization/mtv-controller-rhel9:2.5.2-5RHBA-2023:6078
Red Hat Migration Toolkit for Containers 1.7rhmtc/openshift-migration-controller-rhel8:v1.7.11-4RHSA-2023:4293
Red Hat OpenShift Container Platform 4.14openshift4/ose-image-customization-controller-rhel8:v4.14.0-202310201027.p0.g2dda87a.assembly.streamRHSA-2023:5006
Red Hat OpenShift Container Platform 4.14openshift4/ose-agent-installer-api-server-rhel8:v4.14.0-202410151739.p0.gcb552db.assembly.stream.el8RHSA-2024:8235
Red Hat OpenShift Container Platform 4.14openshift4/ose-agent-installer-csr-approver-rhel8:v4.14.0-202410220407.p0.g53ccc48.assembly.stream.el8RHSA-2024:8697

Frequently Asked Questions

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&quot;;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-Dispo
O3 Security · Impact-Aware SCA

Is CVE-2023-29401 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2023-29401: gin — Fixed in 1.9.1