CVE-2017-3612
First published: Mon Apr 24 2017(Updated: )
Vulnerability in the Data Store component of Oracle Berkeley DB. The supported version that is affected is Prior to 6.2.32. Difficult to exploit vulnerability allows unauthenticated attacker with logon to the infrastructure where Data Store executes to compromise Data Store. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of Data Store. CVSS 3.0 Base Score 7.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H).
Credit: secalert_us@oracle.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Oracle Berkeley DB | <6.2.32 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2017-3612?
The severity of CVE-2017-3612 is rated as high with a score of 7.
How do I fix CVE-2017-3612?
To fix CVE-2017-3612, upgrade Oracle Berkeley DB to version 6.2.32 or later.
What is the main impact of CVE-2017-3612?
The main impact of CVE-2017-3612 is the potential for unauthenticated attackers to compromise the Data Store.
Which versions of Oracle Berkeley DB are affected by CVE-2017-3612?
Versions of Oracle Berkeley DB prior to 6.2.32 are affected by CVE-2017-3612.
Who can exploit CVE-2017-3612?
CVE-2017-3612 can be exploited by unauthenticated attackers who have logon access to the infrastructure where Data Store executes.
- collector/nvd-index
- agent/references
- agent/severity
- agent/author
- agent/description
- agent/type
- agent/event
- agent/first-publish-date
- agent/softwarecombine
- agent/remedy
- agent/tags
- agent/last-modified-date
- collector/mitre-cve
- source/MITRE
- vendor/oracle
- canonical/oracle berkeley db