CVE-2017-3610
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-3610?
CVE-2017-3610 is classified as a difficult to exploit vulnerability that allows compromise of the Data Store.
How do I fix CVE-2017-3610?
The recommended fix for CVE-2017-3610 is to upgrade Oracle Berkeley DB to version 6.2.32 or later.
Who is affected by CVE-2017-3610?
CVE-2017-3610 affects users of Oracle Berkeley DB versions prior to 6.2.32.
What component is affected by CVE-2017-3610?
CVE-2017-3610 affects the Data Store component of Oracle Berkeley DB.
Can CVE-2017-3610 be exploited by unauthenticated users?
CVE-2017-3610 can be exploited by unauthenticated attackers who have logon access to the infrastructure where Data Store executes.
- collector/nvd-index
- agent/references
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/severity
- agent/remedy
- agent/tags
- agent/author
- agent/event
- agent/description
- agent/first-publish-date
- agent/source
- vendor/oracle
- canonical/oracle berkeley db