Parse Server 9.0.0 Stored XSS via malformed Content-Type
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 8.6.84, 9.10.0-alpha.2, parse-server 8.6.84 and 1 more.
Parse Server is affected by a stored cross-site scripting (XSS) vulnerability in versions >= 9.0.0, < 9.10.0-alpha.2 and <= 8.6.83. When an uploaded file's extension is not recognized by the mime package, Parse Server preserves the client-supplied Content-Type. A malformed Content-Type that is not a valid type/subtype media type (e.g., 'image', 'image/', or 'image//svg+xml') bypasses the fileUpload.fileExtensions blocklist and is stored unchanged. On storage adapters that persist and serve the uploaded Content-Type (such as Amazon S3, Google Cloud Storage, or Azure Blob Storage), a browser cannot parse the malformed value and falls back to MIME-sniffing; a file whose body begins with HTML is rendered as HTML, executing embedded script in the application's origin against other users who open the file URL. The default GridFS storage adapter is not affected. Fixed in 9.10.0-alpha.2 and 8.6.84.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| parse-community | <8.6.84, >=9.0.0 <9.10.0-alpha.2 | 8.6.84, 9.10.0-alpha.2 | |
| npm: parse-server | <=8.6.83, >=9.0.0 <9.10.0-alpha.2 | 8.6.84, 9.10.0-alpha.2 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in parse-server (npm), strongest first
Embed
A live severity badge for an advisory, README or ticket