dbcve.org
Hospitality SimphonyApplication · Oracle

CVE-2024-21014

CRITICAL · 9.8 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 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 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 unauthenticated attacker with network access via HTTP to compromise Oracle Hospitality Simphony. Successful attacks of this vulnerability can result in takeover of Oracle Hospitality Simphony. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 unauthenticated remote code execution vulnerability in Oracle Hospitality Simphony's Simphony Enterprise Server component. Attackers can exploit this flaw via HTTP requests without any credentials, achieving complete system takeover including full confidentiality, integrity, and availability compromise.

MitigationApply Oracle's security patch for CVE-2024-21014 to affected versions 19.1.0-19.5.4. As an immediate workaround, restrict network access to the Simphony Enterprise Server and implement web application firewall rules to block malicious HTTP requests.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 version
    Locate the Simphony installation and check the version. This is typically found in the application itself (Help > About), in installation directories, or in registry keys under HKLM\Software\Oracle\Simphony or similar Oracle paths. Also check the Simphony Enterprise Server component version specifically.
    Affected if The installed version is 19.1.0 through 19.5.4 inclusive.
  2. Confirm Simphony Enterprise Server component is present
    Verify that the Simphony Enterprise Server component is installed. Check for services named 'Simphony Enterprise Server' or similar Oracle Simphony services running on the system. Look in Windows Services or via command: sc query type= service state= all | findstr -i simphony
    Affected if The Enterprise Server component is installed and running.
  3. Check HTTP listener configuration
    Examine the Simphony Enterprise Server configuration to determine if HTTP listener is enabled. Check configuration files in the Simphony installation directory (often under C:\Program Files\Oracle\Simphony\ or similar), specifically looking for web.config, server.config, or similar files that define HTTP/HTTPS endpoints and ports.
    Affected if HTTP listener is enabled and configured to accept remote connections (typically on ports 80, 443, or custom ports like 8080, 8443).
  4. Verify network exposure
    Determine if the Simphony Enterprise Server HTTP port is bound to all network interfaces (0.0.0.0) or is accessible from outside localhost. Use netstat -an | findstr <port> or check the network binding configuration in the server settings. Confirm whether the server is accessible from untrusted networks.
    Affected if The HTTP service is listening on external IP addresses and is reachable from untrusted network segments.

A user is affected if their Oracle Hospitality Simphony installation has the Enterprise Server component running with an HTTP listener in version 19.1.0 through 19.5.4 and that HTTP endpoint 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 security patch for CVE-2024-21014 to affected versions 19.1.0-19.5.4. As an immediate workaround, restrict network access to the Simphony Enterprise Server and implement web application firewall rules to block malicious HTTP requests.

Recommended fix Moderate confidence

Oracle Hospitality Simphony 19.5.5 or later (or apply January 2024/April 2024 CPU patch for Simphony)

  1. Check Oracle Critical Patch Update advisories for January 2024 or April 2024 for Oracle Hospitality Simphony patches
  2. Identify the appropriate patch for version 19.5.4 or determine the minimum fixed version (19.5.5 or later) from Oracle's advisory
  3. Apply the CPU patch following Oracle's standard patch application process for Simphony Enterprise Server
  4. Verify the patch was applied successfully by reviewing applied patches in Simphony
  5. Test that the authentication mechanism is now properly enforced
Caveat Review Oracle patch readme for any post-installation requirements or known issues specific to Simphony

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

Fix this in Hospitality Simphony 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 upgrade done

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-2024-21014 — 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-21014 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