Miggo Logo

CVE-2025-32428:
TigerVNC accessible via the network and not just via a UNIX socket as intended

9

CVSS Score
4.0

Basic Information

EPSS Score
0.04726%
Published
4/12/2025
Updated
4/15/2025
KEV Status
No
Technology
TechnologyPython

Technical Details

CVSS Vector
CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Package NameEcosystemVulnerable VersionsFirst Patched Version
jupyter-remote-desktop-proxypip= 3.0.03.0.1

Vulnerability Intelligence
Miggo AIMiggo AI

Miggo AIRoot Cause Analysis

The vulnerability lies in how jupyter-remote-desktop-proxy configured TigerVNC. The provided commit 7dd54c25a4253badd8ea68895437e5a66a59090d directly addresses this by modifying the setup_websockify function in jupyter_remote_desktop_proxy/setup_websockify.py. This function prepares the arguments for launching the VNC server. The patch introduces a check to identify if the VNC server is TigerVNC (by checking for the absence of 'turbovnc' in its script content) and adds the -rfbport -1 argument. This argument explicitly tells TigerVNC not to open a TCP port. The absence of this argument in the vulnerable version (3.0.0) for TigerVNC is the root cause of the vulnerability, making the setup_websockify function the direct location where the vulnerable configuration was applied.

Vulnerable functions

Only Mi**o us*rs **n s** t*is s**tion

WAF Protection Rules

WAF Rule

## Summ*ry `jupyt*r-r*mot*-**sktop-proxy` w*s m**nt to r*ly on UNIX so*k*ts r*****l* only *y t** *urr*nt us*r sin** v*rsion *.*.*, *ut w**n us** wit* Ti**rVN*, t** VN* s*rv*r st*rt** *y `jupyt*r-r*mot*-**sktop-proxy` w*r* still ****ssi*l* vi* t** n*

Reasoning

T** vuln*r**ility li*s in *ow `jupyt*r-r*mot*-**sktop-proxy` *on*i*ur** Ti**rVN*. T** provi*** *ommit `****************************************` *ir**tly ***r*ss*s t*is *y mo*i*yin* t** `s*tup_w**so*ki*y` *un*tion in `jupyt*r_r*mot*_**sktop_proxy/s*t