dbcve.org
Hospitality SimphonyApplication · Oracle

CVE-2024-21010

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

Critical vulnerability in Oracle Hospitality Simphony Enterprise Server allowing low-privileged attackers with network access via HTTP to achieve complete system takeover. The CVSS 9.9 with scope change indicates the vulnerability enables full compromise of confidentiality, integrity, and availability, potentially affecting additional connected products.

MitigationApply Oracle's patch for Simphony versions 19.1.0-19.5.4 immediately. Until patch is available, restrict network access to Simphony Enterprise Server to trusted IPs only and monitor for indicators of compromise.

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 if Oracle Hospitality Simphony is installed
    Check for Simphony installation directories or review installed software on the server. Common paths may include C:\Oracle\Simphony or /opt/oracle/simphony. Check Windows Services for 'Simphony' services or use 'wmic product get name,version' on Windows systems.
    Affected if Oracle Hospitality Simphony Enterprise Server is present on the system
  2. Determine the installed Simphony version
    Locate version information in the Simphony installation, typically found in configuration files, registry entries, or the application itself. Check for a version file or launch the application to view its About/Version information.
    Affected if Installed version falls within 19.1.0 through 19.5.4 inclusive
  3. Verify HTTP network exposure of Simphony Enterprise Server
    Check if the Simphony web interface or Enterprise Server is accessible over HTTP on typical ports such as 8080, 8443, or port 80/443. Use netstat or telnet to confirm listening HTTP services: 'netstat -an | grep -E "(8080|8443|80|443)"' or scan the server's IP for open web ports.
    Affected if Simphony Enterprise Server HTTP interface is exposed to the network
  4. Confirm the Enterprise Server component is running
    Verify the Simphony Enterprise Server service is running. On Windows, check via Services.msc or command 'sc query SimphonyEnterpriseServer'. On Linux, check with 'ps aux | grep -i simphony' or systemctl status for Simphony services.
    Affected if Simphony Enterprise Server service is active and the HTTP interface is reachable

A system is affected if Oracle Hospitality Simphony Enterprise Server is installed with a version between 19.1.0 and 19.5.4 and its HTTP interface is network-accessible.

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
Upgrade available Upgrade to a release after 19.5.4
Interim mitigation

Apply Oracle's patch for Simphony versions 19.1.0-19.5.4 immediately. Until patch is available, restrict network access to Simphony Enterprise Server to trusted IPs only and monitor for indicators of compromise.

Recommended fix Moderate confidence

19.5.5 or later (contact Oracle Support for exact fixed version)

  1. 1. Identify the current Oracle Hospitality Simphony version in use by checking the Simphony Enterprise Server.
  2. 2. Contact Oracle Support to obtain the specific patch or upgrade path for CVE-2024-21010.
  3. 3. Review Oracle's Critical Patch Update (CPU) documentation for the quarter containing this vulnerability fix.
  4. 4. Apply the recommended patch or upgrade to a version beyond 19.5.4 (e.g., 19.5.5 or later as specified by Oracle).
  5. 5. Verify the fix by confirming the Simphony version and testing the authorization controls.
  6. 6. Document the remediation in the change management system.
Caveat Review Oracle upgrade documentation for Simphony for any configuration or compatibility changes between versions

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

Fix this in Hospitality Simphony Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing16.0 h
  • Review / QA8.0 h
36.0 hours of engineering $6,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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