CVE-2025-5024
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 · uneditedA flaw was found in gnome-remote-desktop. Once gnome-remote-desktop listens for RDP connections, an unauthenticated attacker can exhaust system resources and repeatedly crash the process. There may be a resource leak after many attacks, which will also result in gnome-remote-desktop no longer being able to open files even after it is restarted via systemd.
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 confidencegnome-remote-desktop lacks proper authentication controls on its RDP listener, allowing unauthenticated remote attackers to repeatedly crash the service via resource exhaustion. This results in a persistent resource leak that prevents the service from functioning even after systemd restart.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:N/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.
-
Verify gnome-remote-desktop is installedCheck for package presence: rpm -q gnome-remote-desktop (RHEL/Fedora) or dpkg -l gnome-remote-desktop (Debian/Ubuntu). Also check if /usr/bin/gnome-remote-desktop exists.Affected if Package is installed or executable exists on the system
-
Identify if RDP listener is configuredCheck user configuration: look for files in ~/.config/gnome-remote-desktop/ or run 'gnome-remote-desktop --list' if available. Inspect dconf keys under /org/gnome/remote-desktop/Affected if RDP share or listener is configured and enabled for a user or system-wide
-
Confirm the RDP service is running and listeningRun 'ss -tlnp | grep -E "3389|rdp"' or 'netstat -tlnp | grep -E "3389|rdp"' to check if port 3389 (RDP) is listening. Also check 'systemctl status gnome-remote-desktop.service' if it exists.Affected if gnome-remote-desktop service or daemon is running and listening on network ports
-
Assess network exposureReview firewall rules: 'iptables -L -n' or 'firewall-cmd --list-all'. Check if port 3389 is open to non-localhost. Verify the service bind address in configuration files.Affected if RDP listener is bound to 0.0.0.0 or accessible from network interfaces other than localhost, or firewall permits external access to port 3389
System is affected if gnome-remote-desktop is installed with RDP listener enabled and exposed to network access, allowing unauthenticated remote attackers to trigger resource exhaustion.
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 dataRestrict network access to the RDP listener via firewall rules or network segmentation; disable gnome-remote-desktop if remote desktop functionality is not required.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5024 — 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-2025-5024 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