Neko: Authorization bypass in legacy WebRTC input handling
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| m1k1o | neko | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| M1k1o | Neko |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-5cp7-fp4j-wwcv | Neko: Authorization bypass in legacy WebRTC input handling |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.311% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
M1k1o
M1k1o neko |
|
| Vendors & Products |
M1k1o
M1k1o neko |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Neko is a a self-hosted virtual browser that runs in Docker and uses WebRTC. From version 3.0.0 until 3.1.5, Neko deployments with legacy mode and session.implicit_hosting enabled incorrectly authorize legacy WebRTC data-channel input because LegacyIsHost() evaluates host status incorrectly. An authenticated room member who establishes a WebRTC connection can send mouse and keyboard events through the legacy control channel while controls are locked or the member is otherwise unauthorized by the modern control API. This issue is fixed in version 3.1.5. | |
| Title | Neko: Authorization bypass in legacy WebRTC input handling | |
| Weaknesses | CWE-863 | |
| References |
| |
| Metrics |
cvssV3_1
|