GHSA-vr5f-2r24-w5hc

Parse Server: File upload Content-Type override via extension mismatch

En bref

Publiée
Mise à jour
CVE
CVE-2026-35200
Alias
BIT-parse-2026-35200
CVSS_V4
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

Description

### Impact A file can be uploaded with a filename extension that passes the file extension allowlist (e.g., `.txt`) but with a `Content-Type` header that differs from the extension (e.g., `text/html`). The `Content-Type` is passed to the storage adapter without consistency validation. Storage adapters that store and serve the provided Content-Type (such as S3 or GCS) serve the file with the mismatched Content-Type. The default GridFS adapter is not affected because it derives Content-Type from the filename at serving time. ### Patches The file upload now derives the Content-Type from the filename extension, overriding any user-provided Content-Type when the file has an extension. ### Workarounds Configure the storage adapter or CDN to derive Content-Type from the filename extension instead of using the stored Content-Type.

Paquets affectés

PaquetVersions
npm · parse-serverintroduced 9.0.0, fixed 9.7.1-alpha.4
npm · parse-serverintroduced 0, fixed 8.6.73

Références

Sources

SourceLicence
OSV.devCC-BY 4.0 — GitHub Advisory Database