dbcve.org
Hospitality Reporting And AnalyticsApplication · Oracle

CVE-2017-10405

CRITICAL · 10.0 CVSS v3.0 Published 2017-10-19
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
Vulnerability in the Oracle Hospitality Reporting and Analytics component of Oracle Hospitality Applications (subcomponent: Report). Supported versions that are affected are 8.5.1 and 9.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Hospitality Reporting and Analytics. While the vulnerability is in Oracle Hospitality Reporting and Analytics, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Hospitality Reporting and Analytics accessible data and unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle Hospitality Reporting and Analytics. CVSS 3.0 Base Score 8.2 (Confidentiality and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L).

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

Unauthenticated remote vulnerability in the Report subcomponent of Oracle Hospitality Reporting and Analytics (versions 8.5.1 and 9.0.0). Exploitable via HTTP with network access, allowing attackers to gain unauthorized access to critical data or cause complete denial of service. The low attack complexity and no privileges required makes it easily exploitable.

MitigationApply the Oracle Critical Patch Update that addresses CVE-2017-10405. If patching is immediately infeasible, restrict network access to the Report component via firewall or network segmentation.

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
Hospitality Reporting And AnalyticsApplication
Affected:= 8.5.1= 9.0.0

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
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
High

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

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

  1. Identify Oracle Hospitality Reporting and Analytics installation
    Search for the application in the system inventory or check for its installation directory. Common locations may include C:\Oracle\Hospitality or /opt/oracle/hospitality on Windows or Linux servers respectively.
    Affected if The product is not found in the system inventory or no installation directory exists.
  2. Verify installed version matches affected releases
    Locate the version file or check the product's about/registration information. Look for version 8.5.1 or 9.0.0 specifically, as these are the exact affected versions.
    Affected if The installed version is exactly 8.5.1 or exactly 9.0.0.
  3. Confirm Report subcomponent is present and enabled
    Check for the Report module within the Oracle Hospitality Reporting and Analytics installation. This may be a web service endpoint, a dedicated Report application folder, or a Report configuration file.
    Affected if The Report subcomponent exists and is configured within the installation.
  4. Determine if HTTP interface is exposed
    Check network configuration, IIS/WebLogic/WebSphere settings, or firewall rules to see if the Report component is accessible over HTTP/HTTPS from the network. Look for ports typically used by the application (commonly 80, 443, or application-specific ports).
    Affected if The Report component is reachable via HTTP from network locations.

You are affected if Oracle Hospitality Reporting and Analytics versions 8.5.1 or 9.0.0 are installed with the Report subcomponent exposed over HTTP.

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
Patch available Apply the vendor patch
Vendor patch www.oracle.com →
Interim mitigation

Apply the Oracle Critical Patch Update that addresses CVE-2017-10405. If patching is immediately infeasible, restrict network access to the Report component via firewall or network segmentation.

Recommended fix Moderate confidence
  1. Review the October 2017 Critical Patch Update (CPU) advisory at http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html for CVE-2017-10405
  2. Identify the specific patch identifier (PSU/one-off patch) for Oracle Hospitality Reporting and Analytics
  3. Apply the October 2017 CPU patch or the specific identified patch to both affected versions (8.5.1 and 9.0.0)
  4. After patching, verify the vulnerability is resolved by testing the Report component functionality
  5. Ensure network access to the Report component is restricted to authorized users only as an additional defensive measure

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

Fix this in Hospitality Reporting And Analytics Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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