pretalx 2.3.1 before 2.3.2 allows path traversal in HTML export (a non-default feature). Organizers can trigger the overwriting (with the standard pretalx 404 page content) of an arbitrary file.
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
| Link | Tags |
|---|---|
| https://pretalx.com/p/news/security-release-232/ | vendor advisory |
| https://github.com/pretalx/pretalx/commit/60722c43cf975f319e94102e6bff320723776890 | patch |
| https://github.com/pretalx/pretalx/releases/tag/v2.3.2 | release notes |
| https://www.sonarsource.com/blog/pretalx-vulnerabilities-how-to-get-accepted-at-every-conference/ | exploit third party advisory patch |