dbcve.org
Remotedocs R ViewerApplication · Data Vision

CVE-2007-4750

HIGH · 9.3 CVSS v2.0 Published 2007-09-18
Fix available
A fix is available. Upgrade to after 1.6.2836 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Unspecified vulnerability in RemoteDocs R-Viewer before 1.6.3768 allows user-assisted remote attackers to execute arbitrary code via a crafted RDZ archive in which the first file has an executable extension.

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 confidence

This is a file parsing vulnerability in RemoteDocs R-Viewer where the application fails to properly validate files within a crafted RDZ archive. When the first file in the archive has an executable extension (such as .exe, .bat, .com), the application can be tricked into executing arbitrary code. This is a classic example of a type of zip slip or archive traversal vulnerability combined with insufficient extension validation.

MitigationUpgrade RemoteDocs R-Viewer to version 1.6.3768 or later. Do not open RDZ archive files from untrusted sources, as user interaction (opening the file) is required for exploitation.

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
Remotedocs R ViewerApplication
Affected:<= 1.6.2836

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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm RemoteDocs R-Viewer installation
    Look for R-Viewer in the Windows Start Menu, Program Files folder, or check registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries named 'RemoteDocs R Viewer' or 'R-Viewer'
    Affected if RemoteDocs R-Viewer is installed on the system
  2. Identify installed version
    Right-click the main R-Viewer executable (commonly RViewer.exe), select Properties, and view the Version tab. Alternatively, check the registry key under the uninstall entry for the version string
    Affected if The version displayed is 1.6.2836 or lower (any version up to and including 1.6.2836)
  3. Verify RDZ file handling is present
    Search for file associations or registered handlers for .rdz extension in Windows registry under HKCR\.rdz or check if R-Viewer includes RDZ parsing modules in its installation directory
    Affected if The application is configured to process or open RDZ archive files
  4. Check for recent RDZ file processing
    Review Windows Event Logs (Application log), recent documents, or file history for evidence of .rdz files having been opened with R-Viewer
    Affected if Users have opened RDZ files from the local system or received files using this application

The environment is affected if RemoteDocs R-Viewer version 1.6.2836 or lower is installed and the application is used to open RDZ archive files, since the vulnerability requires user interaction to open a crafted RDZ file.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 1.6.2836
Interim mitigation

Upgrade RemoteDocs R-Viewer to version 1.6.3768 or later. Do not open RDZ archive files from untrusted sources, as user interaction (opening the file) is required for exploitation.

Recommended fix Moderate confidence

RemoteDocs R-Viewer version 1.6.3768 or later

  1. 1. Verify current installation of RemoteDocs R-Viewer by checking the installed version in the application or system registry
  2. 2. If version is 1.6.2836 or lower, download the updated version 1.6.3768 or later from the official vendor website or trusted distribution channel
  3. 3. Backup all existing RDZ archives and configuration files before performing the upgrade
  4. 4. Uninstall the current version of RemoteDocs R-Viewer
  5. 5. Install version 1.6.3768 or the latest available stable release
  6. 6. Verify the new version number matches the patched release
  7. 7. Test that RDZ archives open correctly in the updated version
  8. 8. Monitor for any security events or anomalies after the upgrade
Caveat Specific breaking changes are not documented; upgrade should be routine patch for this version range

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Remotedocs R Viewer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-4750 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-4750 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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