dbcve.org
Hospitality SimphonyApplication · Oracle

CVE-2024-20997

CRITICAL · 9.9 CVSS v3.1 Published 2024-04-16
Fix available
A fix is available. Upgrade to after 19.5.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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 Simphony product of Oracle Food and Beverage Applications (component: Simphony Enterprise Server). Supported versions that are affected are 19.1.0-19.5.4. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Hospitality Simphony. While the vulnerability is in Oracle Hospitality Simphony, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle Hospitality Simphony. CVSS 3.1 Base Score 9.9 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/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 · high confidence

A critical HTTP-based vulnerability in Oracle Hospitality Simphony Enterprise Server (versions 19.1.0-19.5.4) allows authenticated low-privileged attackers to achieve complete system compromise via network access, resulting in full confidentiality, integrity, and availability takeover.

MitigationApply Oracle's available security patches for this vulnerability; restrict network access to Simphony Enterprise Server and implement least-privilege access controls until patching is complete.

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 SimphonyApplication
Affected:>= 19.1.0, <= 19.5.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
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 Simphony installation
    Check for Simphony Enterprise Server by looking for the installation directory (commonly at C:\Oracle\Simphony or /opt/oracle/simphony), or query Windows services for 'Simphony' named services. On Linux, check for simphony user/processes.
    Affected if Simphony Enterprise Server is found running on the system
  2. Determine installed Simphony version
    Check the version by inspecting the Simphony installation: look for version info in the installation directory, check the Simphony client 'About' dialog, or query the Simphony configuration database. Common locations: installation folder\version.txt or in the application's help/about section.
    Affected if Installed version is 19.1.0 through 19.5.4 inclusive
  3. Verify HTTP/Enterprise Server interface is enabled
    Check if the Simphony Enterprise Server HTTP service is running and accessible. Look for configured web service ports (default 8080, 8443) in Simphony configuration files (enterprise.properties, web.xml) or by checking if the Simphony web application is accessible on the network.
    Affected if HTTP interface is enabled and exposed on network accessible ports
  4. Confirm network exposure of Simphony service
    Check network configuration to determine if Simphony HTTP ports are bound to non-localhost interfaces. Run 'netstat -an | grep -E "8080|8443"' or review firewall rules to see if these ports are accessible from outside the localhost.
    Affected if Simphony HTTP ports are listening on external interfaces or are not blocked by firewall

A system is affected if it runs Oracle Hospitality Simphony Enterprise Server version 19.1.0 through 19.5.4 with the HTTP interface exposed to the network.

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 19.5.4
Interim mitigation

Apply Oracle's available security patches for this vulnerability; restrict network access to Simphony Enterprise Server and implement least-privilege access controls until patching is complete.

Fix this in Hospitality Simphony Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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