github.com/dunglas/mercure/caddy is vulnerable to Exposure of Resource to Wrong Sphere
78
CVE Score
High
Exposure of Resource to Wrong Sphere
Caddy's pooled transports for the Mercure module and its deprecated transport key are shared across every hub configured in the same process, keyed only by target or path and not by hub name. Two differently named hubs in one Caddy instance reuse the same pooled transport, local subscriber list, or BoltDB handle, so one hub's subscribers can receive another hub's private updates. The fix includes the configured hub name in the key for every pooled transport so differently named hubs never share subscribers or history.
Upgrade the github.com/dunglas/mercure/caddy library to the patch version.
You are affected if you are using a version that falls within the vulnerable range and you run more than one hub in the same Caddy process.
0.11.3 - 1.0.0
Fixed in 1.0.1github.com/dunglas/mercure/caddy is vulnerable to Exposure of Resource to Wrong Sphere in versions 0.11.3 - 1.0.0.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.