CVE-2021-34687
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 information disclosure. A man in the middle can recover a system's Personal Key when a client attempts to make a LAN connection. The Personal Key is transmitted over the network while only being encrypted via a substitution cipher.
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 information disclosure vulnerability. When a client attempts a LAN connection, the Personal Key is transmitted over the network but only protected by a weak substitution cipher, which a man-in-the-middle attacker can easily reverse to recover the key.
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
- Adjacent
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
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 RemotePC is installedCheck the Windows system for the presence of iDrive RemotePC application - look in Program Files, Program Files (x86), or use the Windows Programs and Features list to confirm RemotePC is installed.Affected if RemotePC is not installed on the system.
-
Determine installed RemotePC versionLocate the RemotePC application and check its version property. This is typically found in the application's properties, installation directory, or by right-clicking the executable and selecting Properties > Details.Affected if The installed version cannot be determined or the application is not found.
-
Compare version to affected rangeCompare the installed RemotePC version number against the affected range. The vulnerability affects versions before 7.6.48.Affected if The installed version is lower than 7.6.48 (for example, 7.6.40, 7.5.x, etc.).
-
Identify LAN connection usageReview RemotePC configuration or connection logs to determine if LAN (local network) connections have been attempted or configured. The vulnerability specifically occurs during LAN connection attempts where the Personal Key is transmitted.Affected if LAN connections are used or configured on an affected version (version < 7.6.48).
A user is affected if RemotePC version 7.6.48 or higher is not installed AND LAN connections are used, as the weak substitution cipher protection applies specifically to LAN-attempted Personal Key transmission.
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 data7.6.48
Update iDrive RemotePC to version 7.6.48 or later. Until updated, avoid untrusted network connections for RemotePC LAN operations.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34687 — 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-34687 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