dbcve.org
Oculus BrowserApplication · Oculus

CVE-2019-3562

MEDIUM · 6.1 CVSS v3.0 Published 2019-04-29
Fix available
A fix is available. Upgrade to after 5.7.11 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
A remote web page could inject arbitrary HTML code into the Oculus Browser UI, allowing an attacker to spoof UI and potentially execute code. This affects the Oculus Browser starting from version 5.2.7 until 5.7.11.

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

A remote HTML injection vulnerability in the Oculus Browser (versions 5.2.7-5.7.11) allows malicious web pages to inject arbitrary HTML into the browser's UI context, enabling UI spoofing attacks and potentially arbitrary code execution through the injected content.

MitigationUpdate Oculus Browser to version 5.7.12 or later. Users should avoid visiting untrusted websites until the browser is updated.

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
Oculus BrowserApplication
Affected:>= 5.2.7, <= 5.7.11

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
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checks

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

  1. Verify Oculus Browser is installed
    Check the system for Oculus Browser application - typically found in the Oculus software package or VR headset applications
    Affected if Oculus Browser software is present on the device
  2. Identify the installed Oculus Browser version
    Access the browser's settings or about section to find the version number, or check the application metadata through the Oculus software management interface
    Affected if Unable to determine the version or version information is unavailable
  3. Compare version against affected range
    Check if the installed version falls between 5.2.7 and 5.7.11 (inclusive)
    Affected if Version number is 5.2.7, 5.7.11, or any version in between these two releases
  4. Assess exposure to untrusted web content
    Review browser usage history and determine whether untrusted or malicious websites may have been visited
    Affected if The browser has been used to visit web pages while running a vulnerable version

The environment is affected if Oculus Browser version 5.2.7 through 5.7.11 is installed and the browser has been used to access web content.

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.

From vendor data
Upgrade available Upgrade to a release after 5.7.11
Interim mitigation

Update Oculus Browser to version 5.7.12 or later. Users should avoid visiting untrusted websites until the browser is updated.

Fix this in Oculus Browser Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-3562 — 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-2019-3562 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