| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Oracle MySQL Server up to 5.7.18. This affects an unknown part of the component DML. Performing a manipulation results in access control. This vulnerability was named CVE-2017-3639. The attack may be initiated remotely. There is no available exploit. It is suggested to upgrade the affected component.
Details
A vulnerability was found in Oracle MySQL Server up to 5.7.18 (Database Software). It has been classified as problematic. This affects an unknown code of the component DML. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. This is going to have an impact on availability.
The bug was discovered 07/18/2017. The weakness was presented 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 uniquely identified as CVE-2017-3639 since 12/06/2016. It is possible to initiate the attack remotely. Additional levels of successful authentication are necessary for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 101828 (FreeBSD : MySQL -- multiple vulnerabilities (cda2f3c2-6c8b-11e7-867f-b499baebfeaf)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family FreeBSD Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 20043 (Oracle MySQL JULY 2017 Critical Patch Update (CPUJUL2017)).
Upgrading eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at Tenable (101828) and SecurityFocus (BID 99753†). See VDB-74371, VDB-89670, VDB-96591 and VDB-99569 for similar entries. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
- 5.7.0
- 5.7.1
- 5.7.2
- 5.7.3
- 5.7.4
- 5.7.5
- 5.7.6
- 5.7.7
- 5.7.8
- 5.7.9
- 5.7.10
- 5.7.11
- 5.7.12
- 5.7.13
- 5.7.14
- 5.7.15
- 5.7.16
- 5.7.17
- 5.7.18
License
Website
- Vendor: https://www.oracle.com
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.9VulDB Meta Temp Score: 4.8
VulDB Base Score: 4.9
VulDB Temp Score: 4.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Oracle): 4.9
Vendor Vector (Oracle): 🔍
NVD Base Score: 4.9
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 |
Nessus ID: 101828
Nessus Name: FreeBSD : MySQL -- multiple vulnerabilities (cda2f3c2-6c8b-11e7-867f-b499baebfeaf)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
OpenVAS ID: 801205
OpenVAS Name: Oracle Mysql Security Updates (jul2017-3236622) 01 - Windows
OpenVAS File: 🔍
OpenVAS Family: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
12/06/2016 🔍07/18/2017 🔍
07/18/2017 🔍
07/19/2017 🔍
07/19/2017 🔍
07/19/2017 🔍
07/20/2017 🔍
08/08/2017 🔍
01/04/2021 🔍
Sources
Vendor: oracle.comAdvisory: Oracle Critical Patch Update Advisory - July 2017
Researcher: Oracle
Organization: Oracle
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2017-3639 (🔍)
GCVE (CVE): GCVE-0-2017-3639
GCVE (VulDB): GCVE-100-104073
OVAL: 🔍
SecurityFocus: 99753 - Oracle MySQL Server CVE-2017-3639 Remote Security Vulnerability
SecurityTracker: 1038928
See also: 🔍
Entry
Created: 07/20/2017 00:10Updated: 01/04/2021 08:55
Changes: 07/20/2017 00:10 (85), 10/27/2019 13:42 (6), 01/04/2021 08:49 (4), 01/04/2021 08:55 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.