Bugsink is vulnerable to Path Traversal attacks via event_id in ingestion
bugsink
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| bugsink PyPI |
|
|
bugsink
| Product | Affected | Fixed in |
|---|---|---|
| bugsink PyPI |
|
|
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.
From the CVE record · GitHub_M
Bugsink ingestion paths use an unvalidated event_id to construct file locations. An attacker with access to a valid DSN can submit a crafted event_id to create or overwrite files outside the intended directory. In containers, the effect is confined to the container filesystem; otherwise, it may affect other locations accessible to the Bugsink user.
Operators running the PyPI bugsink package should check installations before 1.4.3, from 1.5.0 to 1.5.4, from 1.6.0 to 1.6.3, or from 1.7.0 to 1.7.3.