CVE-2022-1736
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 · uneditedUbuntu's configuration of gnome-control-center allowed Remote Desktop Sharing to be enabled by default.
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 · moderate confidenceUbuntu's gnome-control-center was configured to have Remote Desktop Sharing enabled by default, allowing unauthenticated remote attackers to potentially access the desktop session without user consent or awareness.
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= 18.04= 20.04= 22.04= 42.1.1= 42.1.1-1= 42.1.1-2CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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.
-
Check Ubuntu versionRun: cat /etc/lsb-release and look for DISTRIB_RELEASE=18.04, 20.04, or 22.04Affected if Running Ubuntu 18.04, 20.04, or 22.04 and Remote Desktop Sharing is enabled
-
Check gnome-remote-desktop package versionRun: dpkg -l gnome-remote-desktop | grep gnome-remote-desktopAffected if Version is 42.1.1, 42.1.1-1, or 42.1.1-2 AND Remote Desktop Sharing is enabled
-
Verify Remote Desktop Sharing statusOpen gnome-control-center, navigate to Sharing panel, or run: gsettings get org.gnome.desktop.remote-desktop enableAffected if Remote Desktop Sharing is turned ON (value is true)
-
Check for listening remote desktop portsRun: ss -tulpn | grep -E ':(5900|3389)' to see if VNC (5900) or RDP (3389) ports are listeningAffected if Ports 5900 or 3389 are open and listening, indicating remote desktop is active
A system is affected if it runs Ubuntu 18.04, 20.04, or 22.04 with gnome-remote-desktop installed AND Remote Desktop Sharing is enabled (either manually or by default), as this allows unauthenticated remote access.
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 dataConfigure gnome-control-center to disable Remote Desktop Sharing by default and ensure users must explicitly enable it; apply Ubuntu security updates.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1736 — 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-1736 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