OmniFaces: SSE push channels are not bound to their owning HTTP session
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| omnifaces | omnifaces | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Omnifaces | Omnifaces |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Omnifaces
Omnifaces omnifaces |
|
| Vendors & Products |
Omnifaces
Omnifaces omnifaces |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | OmniFaces is a utility library for Faces. From 5.2 until 5.4.3, applications using <o:sse> or @Push(type=SSE) with session scope, view scope, or a user attribute can expose pushed messages because org.omnifaces.cdi.push.SseEndpoint#doGet accepts a channel identifier registered by SseChannelManager and PushSessionManager without verifying that the caller's HTTP session owns it. An attacker who obtains the victim's channel identifier from a logged URL, report, Referer header, or shared link can connect from a foreign or absent session and receive messages intended for the victim. Application-scoped channels are intentionally unbound, and this issue permits message receipt but not message injection. This issue is fixed in version 5.4.3. | |
| Title | OmniFaces: SSE push channels are not bound to their owning HTTP session | |
| Weaknesses | CWE-862 | |
| References |
| |
| Metrics |
cvssV3_1
|