Summary
In affected versions, Bugsink stores every tag supplied with an incoming event. An event with an unusually large number
of custom (i.e. supplied by an attacker) tags can therefore make ingestion spend more time than intended writing tag rows.
Bugsink uses a single-writer database architecture. That keeps the implementation simple, but it also means one
expensive write transaction can delay other event digestion while it is running. In this case, it makes ingestion of
other events wait until the transaction that writes the tags finishes, which effectively causes a temporary denial of
service for other events.
Impact
Submitting such an event requires a valid project DSN. DSNs are sometimes visible in client-side applications, so they
should not be treated as a strong security boundary, but the issue is still limited to ingestion for a Bugsink instance
that accepts the event.
The impact is availability-only. The issue does not expose stored data, modify existing events, or allow code execution.
Mitigation
Update to version 2.2.2, which caps the number of tags stored for a single event. The default cap is 100 tags and can
be changed with MAX_EVENT_TAGS.
References
seankohjs Reporter
Summary
In affected versions, Bugsink stores every tag supplied with an incoming event. An event with an unusually large number
of custom (i.e. supplied by an attacker) tags can therefore make ingestion spend more time than intended writing tag rows.
Bugsink uses a single-writer database architecture. That keeps the implementation simple, but it also means one
expensive write transaction can delay other event digestion while it is running. In this case, it makes ingestion of
other events wait until the transaction that writes the tags finishes, which effectively causes a temporary denial of
service for other events.
Impact
Submitting such an event requires a valid project DSN. DSNs are sometimes visible in client-side applications, so they
should not be treated as a strong security boundary, but the issue is still limited to ingestion for a Bugsink instance
that accepts the event.
The impact is availability-only. The issue does not expose stored data, modify existing events, or allow code execution.
Mitigation
Update to version 2.2.2, which caps the number of tags stored for a single event. The default cap is 100 tags and can
be changed with
MAX_EVENT_TAGS.References