CVE-2024-20989
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 · uneditedVulnerability in the Oracle Hospitality Simphony product of Oracle Food and Beverage Applications (component: Simphony POS). Supported versions that are affected are 19.1.0-19.5.4. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Hospitality Simphony. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Hospitality Simphony accessible data as well as unauthorized update, insert or delete access to some of Oracle Hospitality Simphony accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Hospitality Simphony. CVSS 3.1 Base Score 7.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/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 confidenceHTTP-based vulnerability in Oracle Hospitality Simphony POS (versions 19.1.0-19.5.4) allowing unauthenticated network attackers to compromise the system. Successful exploitation grants unauthorized access to critical data, full data access, and partial denial of service capability. High attack complexity indicates specific conditions must be met for exploitation.
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>= 19.1.0, <= 19.5.4CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Oracle Hospitality Simphony installationCheck for Simphony installation directories, services, or application pools on the system. Common paths include C:\Oracle\Simphony or C:\Micros\Simphony. On Linux, check /u01/oracle or /opt/simphony. Use 'sc query' on Windows or check running processes for Simphony-related services.Affected if Oracle Hospitality Simphony POS software is found on the system
-
Determine installed Simphony versionLocate the version information in the Simphony installation directory, typically in an About or version file, or check the Windows Registry under HKLM\SOFTWARE\MICROS\Simphony\Version. Query the Simphony database if direct database access is available.Affected if Installed version falls within 19.1.0 through 19.5.4 inclusive
-
Verify HTTP service exposureReview network configuration to determine if Simphony HTTP-based interfaces are enabled and accessible. Check IIS configuration, Apache, or nginx reverse proxy settings that expose Simphony endpoints. Common ports include 80, 443, 8080, or custom ports configured during installation.Affected if HTTP-based interfaces for Simphony are enabled and accessible over the network
-
Assess network accessibilityPerform a port scan or review firewall rules to determine if Simphony HTTP ports are exposed to untrusted networks. Check if the system is directly internet-facing or behind appropriate network segmentation.Affected if Simphony HTTP services are accessible from untrusted or external network segments
The environment is affected if Oracle Hospitality Simphony POS version 19.1.0 through 19.5.4 is installed AND HTTP-based interfaces are network-accessible to attackers.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply Oracle Critical Patch Update (CPU) for January 2024. Implement network segmentation and WAF rules to limit HTTP exposure to Simphony POS interfaces until patch deployment.
Upgrade to the latest available Simphony release beyond 19.5.4 after applying the CPU patch
- Apply Oracle Critical Patch Update (CPU) released January 2024 which addresses CVE-2024-20989
- Obtain the specific patch from Oracle Support using your Oracle Support SID
- After applying the patch, verify the Simphony POS application functions normally
- Implement network segmentation to limit HTTP exposure to the Simphony POS interface as an additional compensating control
- Review Oracle Hospitality Simphony security best practices documentation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20989 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-20989 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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