CVE-2022-25226
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThinVNC version 1.0b1 allows an unauthenticated user to bypass the authentication process via 'http://thin-vnc:8080/cmd?cmd=connect' by obtaining a valid SID without any kind of authentication. It is possible to achieve code execution on the server by sending keyboard or mouse events to the server.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThinVNC 1.0b1 contains an authentication bypass vulnerability where unauthenticated users can obtain a valid session ID (SID) by accessing the '/cmd?cmd=connect' endpoint, completely bypassing the login mechanism. Once authenticated by proxy, an attacker can send keyboard and mouse events to achieve remote code execution on the server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm ThinVNC is installed and runningCheck for processes named ThinVNC.exe or services listening on VNC default ports (typically 5900, 5901 or HTTP port 80/8080). Use commands like 'tasklist | findstr ThinVNC' or 'netstat -an | grep -E "590[0-9]|80|8080"'Affected if ThinVNC process is found running on the system
-
Verify the ThinVNC versionCheck the installed version against the affected range. For ThinVNC, the version is typically displayed in the application title bar, in the executable's properties, or in the installation directory's version info. Compare to the affected version: 1.0Affected if The installed version is exactly 1.0 (or 1.0b1)
-
Test for the vulnerable endpoint accessibilityIf ThinVNC has a web interface, attempt to access the '/cmd?cmd=connect' endpoint via HTTP (e.g., http://<server>/cmd?cmd=connect). A valid response indicates the vulnerable endpoint is exposedAffected if The '/cmd?cmd=connect' endpoint responds without requiring authentication
-
Check network exposureReview firewall rules and network access controls to determine if ThinVNC web interface (port 80/8080 or configured HTTP port) is accessible from untrusted networks. Use 'netsh advfirewall firewall show rule name=all' or review inbound firewall rulesAffected if ThinVNC HTTP interface is accessible from untrusted/external IP addresses or the internet
You are affected if ThinVNC version 1.0 is running and the '/cmd?cmd=connect' endpoint is accessible without authentication from an untrusted network.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImmediately restrict network access to ThinVNC to trusted IPs only, or if possible, upgrade to a patched version. Consider deploying a reverse proxy with strong authentication in front of ThinVNC or migrating to a supported VNC solution with proper authentication.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25226 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-25226 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data