dbcve.org
Hospitality Opera 5Application · Oracle

CVE-2024-21172

CRITICAL · 9.0 CVSS v3.1 Published 2024-10-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
99/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
Vulnerability in the Oracle Hospitality OPERA 5 product of Oracle Hospitality Applications (component: Opera Servlet). Supported versions that are affected are 5.6.19.19, 5.6.25.8 and 5.6.26.4. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Hospitality OPERA 5. While the vulnerability is in Oracle Hospitality OPERA 5, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle Hospitality OPERA 5. CVSS 3.1 Base Score 9.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H).

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 · moderate confidence

Unauthenticated remote code execution vulnerability in the Opera Servlet component of Oracle Hospitality OPERA 5, exploitable via HTTP network requests. The high-severity flaw (CVSS 9.0) requires no authentication and allows complete system takeover, with scope change potentially impacting additional products beyond the initially affected Oracle OPERA 5 installation.

MitigationApply Oracle Critical Patch Updates for Oracle Hospitality OPERA 5; if no patch available, restrict network access to the Opera Servlet endpoints and implement web application firewall protections until official patch is obtained.

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 Opera 5Application
Affected:= 5.6.19.19= 5.6.25.8= 5.6.26.4

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

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

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

  1. Identify Oracle Hospitality OPERA 5 installation path
    Locate the OPERA installation directory, typically found in C:\Oracle\OPERA or /opt/oracle/opera on Linux systems. Check for version information in installation logs, registry entries (Windows), or configuration files within the installation directory.
    Affected if The product directory exists and contains Oracle Hospitality OPERA 5 files.
  2. Determine installed OPERA 5 version
    Check the version file or About information within the OPERA 5 application. Common locations include version.txt in the installation root, the OPERA administrator interface, or the application's built-in version lookup feature accessible via Help > About.
    Affected if The installed version matches exactly: 5.6.19.19, 5.6.25.8, or 5.6.26.4.
  3. Verify Opera Servlet component is exposed
    Identify if the Opera Servlet is accessible via HTTP by checking the web application's deployment descriptor (web.xml) and testing access to common servlet endpoints such as /opera/servlet/* or the application's main HTTP listener port (typically 8080 or 8443).
    Affected if The Opera Servlet responds to HTTP requests on the network.
  4. Check network accessibility of OPERA web interface
    Use a browser or curl command to attempt HTTP connectivity to the OPERA web interface from external network locations. Verify if the servlet endpoints are reachable without authentication.
    Affected if The Opera Servlet is reachable over the network without requiring credentials.

A user is affected if Oracle Hospitality OPERA 5 is installed with version 5.6.19.19, 5.6.25.8, or 5.6.26.4 and the Opera Servlet component is network-accessible via 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Updates for Oracle Hospitality OPERA 5; if no patch available, restrict network access to the Opera Servlet endpoints and implement web application firewall protections until official patch is obtained.

Fix this in Hospitality Opera 5 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing24.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,520
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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