Gotenberg: Chromium URL conversion routes read arbitrary files under /tmp via file:// scheme
gotenberg
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/gotenberg/gotenberg/v8 Go |
|
|
| github.com/gotenberg/gotenberg/v7 Go |
| No fix yet |
gotenberg
| Product | Affected | Fixed in |
|---|---|---|
| github.com/gotenberg/gotenberg/v8 Go |
|
|
| github.com/gotenberg/gotenberg/v7 Go |
| No fix yet |
Gotenberg is a Docker-powered stateless API for PDF files. Prior to 8.32.0, the /forms/chromium/convert/url and /forms/chromium/screenshot/url routes accept url=file:///tmp/... from anonymous callers. The default Chromium deny-list intentionally exempts file:///tmp/ so HTML/Markdown routes can load their own request-local assets, and those routes apply a per-request AllowedFilePrefixes guard to scope the read. The URL routes never set AllowedFilePrefixes, so the scope guard silently skips. Alice enumerates /tmp/, walks Gotenberg's per-request working directories, and reads the raw source files of other in-flight conversions as rendered PDF output. This vulnerability is fixed in 8.32.0.
From the CVE record · GitHub_M
The Chromium URL conversion and screenshot routes accept file:///tmp/ URLs without applying the per-request file scope guard. An unauthenticated caller can read source files from other in-flight conversions by finding their temporary working directories, with the files returned as rendered PDF output.
Teams running github.com/gotenberg/gotenberg/v8 before 8.32.0 or any version of github.com/gotenberg/gotenberg/v7 should check their deployments.