CVE-2021-34690
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 · uneditediDrive RemotePC before 7.6.48 on Windows allows authentication bypass. A remote and unauthenticated attacker can bypass cloud authentication to connect and control a system via TCP port 5970 and 5980.
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 confidenceiDrive RemotePC before version 7.6.48 on Windows contains an authentication bypass vulnerability. A remote, unauthenticated attacker can bypass the cloud authentication mechanism and connect directly to victim systems via TCP ports 5970 and 5980, enabling full remote control of the compromised machine.
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< 7.6.48CVSS 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.
-
Verify iDrive RemotePC is installedOpen Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed programs and look for 'RemotePC' or 'iDrive' entriesAffected if iDrive RemotePC appears in the installed programs list
-
Determine installed versionIf RemotePC is found, note the DisplayVersion column from the program list, or right-click the RemotePC application in Program Files and select Properties > Details to view the File VersionAffected if The displayed version number is lower than 7.6.48 (for example, 7.6.47, 7.6.0, 7.5.x, etc.)
-
Check if vulnerable ports are listeningOpen Command Prompt and run 'netstat -an | findstr "LISTENING" | findstr "5970 5980"' to see if TCP ports 5970 or 5980 are in a LISTENING state, or use PowerShell: 'Get-NetTCPConnection -State Listen | Where-Object {$_.LocalPort -eq 5970 -or $_.LocalPort -eq 5980}'Affected if Ports 5970 or 5980 show as LISTENING, indicating the RemotePC service is active and potentially exploitable
You are affected if iDrive RemotePC is installed with a version lower than 7.6.48 AND the service is running with ports 5970/5980 listening.
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.
dbcve · scoped7.6.48
Update iDrive RemotePC to version 7.6.48 or later. As an immediate workaround, block inbound connections to TCP ports 5970 and 5980 at the network perimeter firewall.
RemotePC 7.6.48
- Verify the current RemotePC version installed on the Windows system
- Download RemotePC version 7.6.48 or later from the official vendor website (www.remotepc.com)
- Close any active RemotePC connections and ensure no active remote sessions are in progress
- Run the installer for the updated RemotePC version
- Follow the on-screen installation prompts to complete the upgrade
- Restart the system if prompted by the installer
- Verify the installed version shows 7.6.48 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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 $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34690 — 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-2021-34690 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