dbcve.org
Hospitality Reporting And AnalyticsApplication · Oracle

CVE-2021-1997

HIGH · 8.1 CVSS v3.1 Published 2021-01-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
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 Reporting and Analytics product of Oracle Food and Beverage Applications (component: Report). The supported version that is affected is 9.1.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Hospitality Reporting and Analytics. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Hospitality Reporting and Analytics accessible data as well as unauthorized access to critical data or complete access to all Oracle Hospitality Reporting and Analytics accessible data. CVSS 3.1 Base Score 8.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N).

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

A vulnerability in Oracle Hospitality Reporting and Analytics (version 9.1.0) allows low-privileged authenticated users to create, delete, or modify critical data through the Report component via HTTP. The flaw enables both unauthorized data modification and access to sensitive or all accessible data due to insufficient access controls or input validation in the reporting module.

MitigationApply the Oracle Critical Patch Update (CPU) that addresses CVE-2021-1997. If no patch is immediately available, restrict network access to the Report component using network segmentation and implement additional authentication controls until the patch can be applied.

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 Reporting And AnalyticsApplication
Affected:= 9.1

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

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. Confirm Oracle Hospitality Reporting and Analytics is installed
    Check the installed software inventory or look for Oracle Hospitality applications in the system. Common installation paths may be in Oracle middleware directories or application servers.
    Affected if The product is not present in the environment, the user is not affected.
  2. Identify the exact version number
    Check the application version through the Oracle Enterprise Manager, the application's About page, or by querying the installed packages. Look for version 9.1.0 or 9.1 specifically.
    Affected if The installed version is 9.1 or 9.1.0, proceed to next checks. If the version is different (higher or lower), compare to the affected range.
  3. Verify the Report component is enabled
    Check the application configuration or admin console to determine if the Report component module is active. Look for reporting module settings in the Oracle Hospitality configuration files or web interface.
    Affected if The Report component is disabled or not present, the user may not be affected by this specific flaw.
  4. Check HTTP access to the Report component
    Attempt to access the reporting module via HTTP/HTTPS endpoints. Look for URLs such as /reports, /reporting, or similar paths in the application's web interface. Verify if the HTTP listener is bound to any network interface.
    Affected if The Report component is not accessible via HTTP, the attack surface is reduced but the vulnerability may still exist if the component is enabled internally.
  5. Review user access controls for the reporting module
    Examine the application's user role configuration and access control lists for the Report component. Check if low-privileged users have elevated permissions to create, delete, or modify reporting data.
    Affected if Low-privileged (non-admin) authenticated users have permissions to modify or delete reporting data, the user is likely affected by this vulnerability.

The environment is affected if Oracle Hospitality Reporting and Analytics version 9.1.0 is installed, the Report component is enabled, and low-privileged users can access or modify reporting data 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 the Oracle Critical Patch Update (CPU) that addresses CVE-2021-1997. If no patch is immediately available, restrict network access to the Report component using network segmentation and implement additional authentication controls until the patch can be applied.

Fix this in Hospitality Reporting And Analytics Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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