dbcve.org
Hospitality Opera 5 Property ServicesApplication · Oracle

CVE-2017-3574

HIGH · 7.1 CVSS v3.0 Published 2017-04-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/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 OPERA 5 Property Services component of Oracle Hospitality Applications (subcomponent: OPERA License code configuration). Supported versions that are affected are 5.4.0.x, 5.4.1.x, 5.4.2.x, 5.4.3.x, 5.5.0.x and 5.5.1.x. Easily "exploitable" vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Hospitality OPERA 5 Property Services. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Hospitality OPERA 5 Property Services accessible data as well as unauthorized update, insert or delete access to some of Oracle Hospitality OPERA 5 Property Services accessible data. CVSS 3.0 Base Score 7.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/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 · high confidence

Access control vulnerability in Oracle Hospitality OPERA 5 Property Services license code configuration subcomponent. Low-privileged authenticated users can bypass intended authorization boundaries via HTTP to access critical data and perform unauthorized updates/inserts/deletes.

MitigationApply Oracle Critical Patch Update (CPU) for April 2017 that addresses this vulnerability. Verify license configuration permissions and review user role assignments after patching.

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 Opera 5 Property ServicesApplication
Affected:= 5.4.0= 5.4.1= 5.4.2= 5.4.3= 5.5.0= 5.5.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
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/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. Identify installed Oracle OPERA 5 version
    Locate the version information for Oracle Hospitality OPERA 5 Property Services in the application or system information panel, typically accessible through the OPERA administration interface or about screen
    Affected if The installed version is 5.4.0, 5.4.1, 5.4.2, 5.4.3, 5.5.0, or 5.5.1
  2. Verify HTTP access to license configuration interface
    Attempt to access the license code configuration endpoint via HTTP using a low-privileged authenticated user account
    Affected if Low-privileged users can reach and interact with the license code configuration subcomponent via HTTP without elevated permissions
  3. Confirm license configuration access permissions
    Review the access control settings for the license code configuration module within OPERA's role-based access control (RBAC) settings
    Affected if The license code configuration subcomponent permits access by users lacking the required authorization level
  4. Test unauthorized data operations
    Using a low-privileged account, attempt to perform create, read, update, or delete operations on critical data through the license configuration interface
    Affected if Low-privileged authenticated users can execute updates, inserts, or deletes on critical data they should not have access to

You are affected if your Oracle Hospitality OPERA 5 Property Services version is 5.4.0 through 5.5.1 AND low-privileged users can access the license code configuration subcomponent via HTTP to view or modify critical data.

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 Oracle Critical Patch Update (CPU) for April 2017 that addresses this vulnerability. Verify license configuration permissions and review user role assignments after patching.

Fix this in Hospitality Opera 5 Property Services 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 help mitigating

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-2017-3574 — 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-2017-3574 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