Bugsink is vulnerable to Path Traversal attacks via event_id in ingestion
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.7.4, 1.6.4, 1.5.5, 1.4.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Bugsink is a self-hosted error tracking service. In versions 1.4.2 and below, 1.5.0 through 1.5.4, 1.6.0 through 1.6.3, and 1.7.0 through 1.7.3, ingestion paths construct file locations directly from untrusted event_id input without validation. A specially crafted event_id can result in paths outside the intended directory, potentially allowing file overwrite or creation in arbitrary locations. Submitting such input requires access to a valid DSN, potentially exposing them. If Bugsink runs in a container, the effect is confined to the container’s filesystem. In non-containerized setups, the overwrite may affect other parts of the system accessible to that user. This is fixed in versions 1.4.3, 1.5.5, 1.6.4 and 1.7.4.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- bugsink bugsink
From 1.7.0 · fixed in 1.7.4; From 1.6.0 · fixed in 1.6.4; From 1.5.0 · fixed in 1.5.5; fixed in 1.4.3
- bugsinkPyPI
From 1.7.0 · fixed in 1.7.4
- bugsinkPyPI
From 1.6.0 · fixed in 1.6.4
- bugsinkPyPI
From 1.5.0 · fixed in 1.5.5
- bugsinkPyPI
fixed in 1.4.3
- bugsinkPyPI
fixed in 1.4.3; From 1.5.0 · fixed in 1.5.5; From 1.6.0 · fixed in 1.6.4; From 1.7.0 · fixed in 1.7.4; From 1.6.0 · fixed in 1.6.4