CVE-2020-1885
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 · uneditedWriting to an unprivileged file from a privileged OVRRedir.exe process in Oculus Desktop before 1.44.0.32849 on Windows allows local users to write to arbitrary files and consequently gain privileges via vectors involving a hard link to a log file.
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 confidenceOVRRedir.exe in Oculus Desktop versions before 1.44.0.32849 runs with elevated privileges and writes to a log file without proper validation, allowing local attackers to exploit hard link relationships to redirect writes to arbitrary files and achieve privilege escalation.
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< 1.44.0.32849CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 Oculus Desktop is installedCheck for Oculus Desktop installation by looking in Program Files for an Oculus folder, or check for the Oculus app in Add/Remove ProgramsAffected if Oculus Desktop software is present on the system
-
Identify installed Oculus Desktop versionOpen Windows Settings > Apps > Apps & features, locate Oculus Desktop, and note the version number displayedAffected if The displayed version number is less than 1.44.0.32849
-
Locate OVRRedir.exeSearch for OVRRedir.exe in the Oculus installation directory, typically found in the Oculus folder under Program FilesAffected if OVRRedir.exe exists in the Oculus installation folder
-
Check OVRRedir.exe versionRight-click OVRRedir.exe, select Properties, and view the File version on the Details tabAffected if The file version is lower than 1.44.0.32849
-
Confirm service runs with elevated privilegesOpen Services, locate any Oculus-related service, right-click and select Properties, and check if it runs under an elevated account such as LocalSystemAffected if The service runs under an account with elevated privileges (e.g., LocalSystem, Administrator)
A system is affected if Oculus Desktop version is present and is lower than 1.44.0.32849, with OVRRedir.exe existing and running with elevated privileges.
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 data1.44.0.32849
Upgrade Oculus Desktop to version 1.44.0.32849 or later to remediate this vulnerability.
- Consultation3.0 h
- Implementation2.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,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-1885 — 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-2020-1885 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