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.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Privileges Required
Low
Basic privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
None
No data leak
Integrity
Low
Partial data modification
Availability
Low
Partial disruption
CVSS Vector v3.1
Weakness Type (CWE)
Vulnerable Products
m1k1o:neko
References 4
https://github.com/m1k1o/neko/security/advisories/GHSA-5cp7-fp4j-wwcv
https://github.com/m1k1o/neko/security/advisories/GHSA-5cp7-fp4j-wwcv
https://github.com/m1k1o/neko/pull/675
https://github.com/m1k1o/neko/pull/675
https://github.com/m1k1o/neko/commit/395ca1a6f62b7b0e270e654d366a2d57b8042efd
https://github.com/m1k1o/neko/commit/395ca1a6f62b7b0e270e654d366a2d57b8042efd
https://github.com/m1k1o/neko/releases/tag/v3.1.5
https://github.com/m1k1o/neko/releases/tag/v3.1.5