MariaDB up to 5.5.46/10.0.22/10.1.9 sql-common/client.c ssl_verify_server_cert /CN= 7pk security
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in MariaDB up to 5.5.46/10.0.22/10.1.9. It has been classified as critical. This affects the function ssl_verify_server_cert of the file sql-common/client.c. Performing a manipulation of the argument /CN= with the input /OU=/CN=bar.com/CN=foo.com. results in 7pk security.
This vulnerability is known as CVE-2016-2047. Remote exploitation of the attack is possible. No exploit is available.
Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as critical, was found in MariaDB up to 5.5.46/10.0.22/10.1.9 (Database Software). This affects the function ssl_verify_server_cert of the file sql-common/client.c. The manipulation of the argument /CN= with the input value /OU=/CN=bar.com/CN=foo.com. leads to a 7pk security vulnerability. CWE is classifying the issue as CWE-254. This is going to have an impact on confidentiality, and integrity. The summary by CVE is:
The ssl_verify_server_cert function in sql-common/client.c in MariaDB before 5.5.47, 10.0.x before 10.0.23, and 10.1.x before 10.1.10, Oracle MySQL, and Percona Server do not properly verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via a "/CN=" string in a field in a certificate, as demonstrated by "/OU=/CN=bar.com/CN=foo.com."
The weakness was published 01/27/2016 by Alex Gaynor (Website). It is possible to read the advisory at mariadb.com. This vulnerability is uniquely identified as CVE-2016-2047 since 01/22/2016. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1211 according to MITRE ATT&CK.
The vulnerability scanner Nessus provides a plugin with the ID 88389 (Debian DSA-3453-1 : mariadb-10.0 - security update), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 168788 (SUSE Enterprise Linux Security update for mysql (SUSE-SU-2016:1279-1)).
Upgrading to version 5.5.47, 10.0.23 or 10.1.10 eliminates this vulnerability. A possible mitigation has been published even before and not after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at Tenable (88389), SecurityFocus (BID 81810†) and Vulnerability Center (SBV-56229†). Similar entries are available at VDB-80586, VDB-80590, VDB-80592 and VDB-80584. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
- 5.5.0
- 5.5.1
- 5.5.2
- 5.5.3
- 5.5.4
- 5.5.5
- 5.5.6
- 5.5.7
- 5.5.8
- 5.5.9
- 5.5.10
- 5.5.11
- 5.5.12
- 5.5.13
- 5.5.14
- 5.5.15
- 5.5.16
- 5.5.17
- 5.5.18
- 5.5.19
- 5.5.20
- 5.5.21
- 5.5.22
- 5.5.23
- 5.5.24
- 5.5.25
- 5.5.26
- 5.5.27
- 5.5.28
- 5.5.29
- 5.5.30
- 5.5.31
- 5.5.32
- 5.5.33
- 5.5.34
- 5.5.35
- 5.5.36
- 5.5.37
- 5.5.38
- 5.5.39
- 5.5.40
- 5.5.41
- 5.5.42
- 5.5.43
- 5.5.44
- 5.5.45
- 5.5.46
- 10.0.0
- 10.0.1
- 10.0.2
- 10.0.3
- 10.0.4
- 10.0.5
- 10.0.6
- 10.0.7
- 10.0.8
- 10.0.9
- 10.0.10
- 10.0.11
- 10.0.12
- 10.0.13
- 10.0.14
- 10.0.15
- 10.0.16
- 10.0.17
- 10.0.18
- 10.0.19
- 10.0.20
- 10.0.21
- 10.0.22
- 10.1.0
- 10.1.1
- 10.1.2
- 10.1.3
- 10.1.4
- 10.1.5
- 10.1.6
- 10.1.7
- 10.1.8
- 10.1.9
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.8
VulDB Base Score: 5.9
VulDB Temp Score: 5.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.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: 7pk securityCWE: CWE-254
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: 88389
Nessus Name: Debian DSA-3453-1 : mariadb-10.0 - security update
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
OpenVAS ID: 703453
OpenVAS Name: Debian Security Advisory DSA 3453-1 (mariadb-10.0 - security update)
OpenVAS File: 🔍
OpenVAS Family: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: MariaDB 5.5.47/10.0.23/10.1.10
Timeline
11/30/2015 🔍01/22/2016 🔍
01/25/2016 🔍
01/27/2016 🔍
01/27/2016 🔍
01/27/2016 🔍
01/27/2016 🔍
01/28/2016 🔍
01/28/2016 🔍
07/06/2022 🔍
Sources
Advisory: RHSA-2016:1132Researcher: Alex Gaynor
Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-2047 (🔍)
GCVE (CVE): GCVE-0-2016-2047
GCVE (VulDB): GCVE-100-80715
OVAL: 🔍
SecurityFocus: 81810 - MariaDB/MySQL/Percona Server CVE-2016-2047 SSL Certificate Validation Security Bypass Vulnerability
SecurityTracker: 1035606
Vulnerability Center: 56229 - MariaDB Remote Security Bypass in the Ssl_verify_server_cert Function, Medium
See also: 🔍
Entry
Created: 01/28/2016 10:20Updated: 07/06/2022 14:24
Changes: 01/28/2016 10:20 (73), 07/22/2018 10:11 (15), 07/06/2022 14:20 (5), 07/06/2022 14:24 (1)
Complete: 🔍
Cache ID: 216:CCC:103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.