Mercure has a Topic Selector Cache Key Collision
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| dunglas | mercure | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Dunglas | Mercure |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-hwr4-mq23-wcv5 | mercure has Topic Selector Cache Key Collision |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.324% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Dunglas
Dunglas mercure |
|
| Vendors & Products |
Dunglas
Dunglas mercure |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Mercure is a protocol for pushing data updates to web browsers and other HTTP clients in a battery-efficient way. Prior to 0.22.0, a cache key collision vulnerability in TopicSelectorStore allows an attacker to poison the match result cache, potentially causing private updates to be delivered to unauthorized subscribers or blocking delivery to authorized ones. The cache key was constructed by concatenating the topic selector and topic with an underscore separator. Because both topic selectors and topics can contain underscores, two distinct pairs can produce the same key. An attacker who can subscribe to the hub or publish updates with crafted topic names can exploit this to bypass authorization checks on private updates. This vulnerability is fixed in 0.22.0. | |
| Title | Mercure has a Topic Selector Cache Key Collision | |
| Weaknesses | CWE-1289 | |
| References |
| |
| Metrics |
cvssV4_0
|