CVE-2017-3573
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 OPERA 5 Property Services component of Oracle Hospitality Applications (subcomponent: OPERA Printing). 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 unauthenticated attacker with network access via HTTP to compromise Oracle Hospitality OPERA 5 Property Services. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Hospitality OPERA 5 Property Services, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Hospitality OPERA 5 Property Services accessible data as well as unauthorized read access to a subset of Oracle Hospitality OPERA 5 Property Services accessible data. CVSS 3.0 Base Score 6.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 · moderate confidenceUnauthenticated network attacker can exploit the OPERA Printing subcomponent in Oracle Hospitality OPERA 5 via HTTP to achieve unauthorized read and partial data modification (insert/update/delete) on accessible data. Exploitation requires human interaction (e.g., tricking a user to click a malicious link). Scope changed indicates impact extends beyond the vulnerable subcomponent.
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= 5.4.0= 5.4.1= 5.4.2= 5.4.3= 5.5.0= 5.5.1CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Oracle Hospitality OPERA 5 is installedCheck for OPERA 5 installation directories, services, or consult your Oracle licensing/inventory for property management systems. Look for 'OPERA' or 'Oracle Hospitality' in installed software listings.Affected if OPERA 5 Property Services is not installed on the system
-
Identify installed OPERA versionUse Oracle's standard version identification methods for OPERA 5, such as checking the application About/Version dialog, consulting the system administrator, or reviewing Oracle support documentation for version location.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
-
Determine if OPERA HTTP interface is enabledCheck the OPERA configuration settings or web server configuration for the property services application. Verify whether the HTTP/HTTPS listener is active for the OPERA Printing subcomponent.Affected if The HTTP interface for the printing service is enabled and listening
-
Assess network accessibility of the printing serviceReview network firewall rules, reverse proxy configurations, and access control lists to determine if the OPERA HTTP port (typically 8080 or 443 for Oracle OPERA) is reachable from untrusted networks.Affected if The OPERA HTTP interface is exposed to network segments accessible to unauthenticated attackers
-
Verify human interaction requirementReview the application topology and consider whether end users would be likely to access the HTTP interface through crafted links, particularly in scenarios where phishing or social engineering could be attempted.Affected if Users have network access to the OPERA HTTP interface and could be targeted with malicious links
A system is affected if Oracle Hospitality OPERA 5 Property Services versions 5.4.0 through 5.5.1 are installed with the OPERA Printing subcomponent accessible via HTTP to potentially vulnerable users.
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.
From vendor dataApply Oracle's relevant security patch from the CPU. If unavailable, restrict network access to the OPERA HTTP interface and implement additional input validation/authentication layers for the printing service.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3573 — 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-2017-3573 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