Oracle Hospitality Cruise AffairWhere 2.2.05.062 AWExport access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Oracle Hospitality Cruise AffairWhere 2.2.05.062. It has been rated as critical. The impacted element is an unknown function of the component AWExport. This manipulation causes access control. This vulnerability is tracked as CVE-2017-10231. The attack is restricted to local execution. No exploit exists. Upgrading the affected component is advised.
Details
A vulnerability was found in Oracle Hospitality Cruise AffairWhere 2.2.05.062 (Hospitality Software). It has been declared as critical. Affected by this vulnerability is an unknown function of the component AWExport. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. As an impact it is known to affect confidentiality.
The bug was discovered 07/18/2017. The weakness was disclosed 07/19/2017 with Oracle as Oracle Critical Patch Update Advisory - July 2017 as confirmed advisory (Website). The advisory is shared at oracle.com. This vulnerability is known as CVE-2017-10231 since 06/21/2017. An attack has to be approached locally. The successful exploitation requires a single authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
Upgrading eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 99830†). The entries VDB-74371, VDB-89670, VDB-96591 and VDB-99569 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.oracle.com
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Oracle): 5.5
Vendor Vector (Oracle): 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
06/21/2017 🔍07/18/2017 🔍
07/18/2017 🔍
07/19/2017 🔍
07/19/2017 🔍
07/19/2017 🔍
08/08/2017 🔍
01/03/2021 🔍
Sources
Vendor: oracle.comAdvisory: Oracle Critical Patch Update Advisory - July 2017
Researcher: Oracle
Organization: Oracle
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2017-10231 (🔍)
GCVE (CVE): GCVE-0-2017-10231
GCVE (VulDB): GCVE-100-103957
SecurityFocus: 99830 - Oracle Hospitality Applications CVE-2017-10231 Local Security Vulnerability
SecurityTracker: 1038941
See also: 🔍
Entry
Created: 07/20/2017 00:10Updated: 01/03/2021 10:39
Changes: 07/20/2017 00:10 (71), 10/28/2019 09:29 (6), 01/03/2021 10:36 (3), 01/03/2021 10:39 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.