| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Oracle Siebel Core CRM 16.0/17.0. It has been rated as critical. The affected element is an unknown function of the component Search. The manipulation leads to access control. This vulnerability is documented as CVE-2017-10049. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is advised.
Details
A vulnerability was found in Oracle Siebel Core CRM 16.0/17.0 (Customer Relationship Management System) and classified as critical. This issue affects an unknown function of the component Search. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is confidentiality, and integrity.
The bug was discovered 07/18/2017. The weakness was released 07/19/2017 with Oracle as Oracle Critical Patch Update Advisory - July 2017 as confirmed advisory (Website). The advisory is shared at oracle.com. The identification of this vulnerability is CVE-2017-10049 since 06/21/2017. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. 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 99626†). Entries connected to this vulnerability are available at VDB-74371, VDB-89670, VDB-96591 and VDB-99569. 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: 6.1VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.1
VulDB Temp Score: 5.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Oracle): 6.1
Vendor Vector (Oracle): 🔍
NVD Base Score: 6.1
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: No
Local: No
Remote: Yes
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/02/2021 🔍
Sources
Vendor: oracle.comAdvisory: Oracle Critical Patch Update Advisory - July 2017
Researcher: Oracle
Organization: Oracle
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2017-10049 (🔍)
GCVE (CVE): GCVE-0-2017-10049
GCVE (VulDB): GCVE-100-103901
SecurityFocus: 99626 - Oracle Siebel Applications CVE-2017-10049 Remote Security Vulnerability
SecurityTracker: 1038936
See also: 🔍
Entry
Created: 07/20/2017 00:10Updated: 01/02/2021 21:40
Changes: 07/20/2017 00:10 (71), 10/28/2019 15:41 (6), 01/02/2021 21:37 (3), 01/02/2021 21:40 (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.