Oracle Berkeley DB up to 6.2.31 Data Store access control

CVSS Meta Temp Score CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.	Current Exploit Price (≈) Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.	CTI Interest Score Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.9	$0-$5k	0.00

Summaryinfo

A vulnerability marked as critical has been reported in Oracle Berkeley DB up to 6.2.31. Affected by this vulnerability is an unknown functionality of the component Data Store. Performing a manipulation results in access control. This vulnerability is reported as CVE-2017-3611. The attack requires a local approach. No exploit exists. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, was found in Oracle Berkeley DB up to 6.2.31 (Software Library). This affects an unknown code of the component Data Store. 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 confidentiality, integrity, and availability.

The bug was discovered 04/18/2017. The weakness was disclosed 04/19/2017 by Hanno Bock as Oracle Critical Patch Update Advisory - April 2017 as confirmed advisory (Website). The advisory is shared at oracle.com. This vulnerability is uniquely identified as CVE-2017-3611 since 12/06/2016. The exploitability is told to be difficult. An attack has to be approached locally. No form of authentication is needed for 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 97859†). The entries VDB-95628, VDB-95669, VDB-95670 and VDB-95704 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Software Library

Vendor

• Oracle

Name

• Berkeley DB

Version

• 6.2.0
• 6.2.1
• 6.2.2
• 6.2.3
• 6.2.4
• 6.2.5
• 6.2.6
• 6.2.7
• 6.2.8
• 6.2.9
• 6.2.10
• 6.2.11
• 6.2.12
• 6.2.13
• 6.2.14
• 6.2.15
• 6.2.16
• 6.2.17
• 6.2.18
• 6.2.19
• 6.2.20
• 6.2.21
• 6.2.22
• 6.2.23
• 6.2.24
• 6.2.25
• 6.2.26
• 6.2.27
• 6.2.28
• 6.2.29
• 6.2.30
• 6.2.31

License

• open-source

Website

• Vendor: https://www.oracle.com

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.0
VulDB Meta Temp Score: 6.9

VulDB Base Score: 7.0
VulDB Temp Score: 6.7
VulDB Vector: 🔍
VulDB Reliability: 🔍

Vendor Base Score (Oracle): 7.0
Vendor Vector (Oracle): 🔍

NVD Base Score: 7.0
NVD Vector: 🔍

CVSSv2info

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: 🔍

Exploitinginfo

Class: Access control
CWE: CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Partially

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 Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Timelineinfo

12/06/2016 🔍
04/18/2017 +133 days 🔍
04/18/2017 +0 days 🔍
04/19/2017 +0 days 🔍
04/19/2017 +0 days 🔍
04/19/2017 +0 days 🔍
04/24/2017 +5 days 🔍
11/29/2022 +2045 days 🔍

Sourcesinfo

Vendor: oracle.com

Advisory: Oracle Critical Patch Update Advisory - April 2017
Researcher: Hanno Bock
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2017-3611 (🔍)
GCVE (CVE): GCVE-0-2017-3611
GCVE (VulDB): GCVE-100-99957
SecurityFocus: 97859 - Oracle Berkeley DB CVE-2017-3611 Local Security Vulnerability
OSVDB: - CVE-2017-3611 - Oracle - Berkeley DB - Unspecified Issue

See also: 🔍

Entryinfo

Created: 04/19/2017 19:11
Updated: 11/29/2022 17:28
Changes: 04/19/2017 19:11 (71), 09/16/2020 12:19 (7), 11/29/2022 17:28 (4)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

Might our Artificial Intelligence support you?

Check our Alexa App!