Bugsink: DOS using large numbers of event tags
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| bugsink | bugsink | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Bugsink | Bugsink |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-5x67-j5xg-c5gj | Bugsink: DOS using large numbers of event tags |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.560% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Bugsink
Bugsink bugsink |
|
| Vendors & Products |
Bugsink
Bugsink bugsink |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Bugsink is a self-hosted error tracking tool. Prior to version 2.2.2, Bugsink stores every set of custom tags supplied with an incoming event, allowing a caller with a valid project DSN to submit an unusually large tag set and force excessive tag-row writes. Because Bugsink uses a single-writer database architecture, the expensive write transaction delays digestion of other events and causes a temporary ingestion denial of service. Version 2.2.2 applies the configurable MAX_EVENT_TAGS limit before storage. The impact is limited to availability for an instance accepting the event and does not expose stored data, modify existing events, or allow code execution. This issue is fixed in version 2.2.2. | |
| Title | Bugsink: DOS using large numbers of event tags | |
| Weaknesses | CWE-400 | |
| References |
| |
| Metrics |
cvssV3_1
|