CVE-2017-3607
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-3607?
CVE-2017-3607 is classified as a difficult to exploit vulnerability with potential impact on data integrity.
How do I fix CVE-2017-3607?
To fix CVE-2017-3607, upgrade to Oracle Berkeley DB version 6.2.32 or later.
Who is affected by CVE-2017-3607?
Organizations using Oracle Berkeley DB versions prior to 6.2.32 are at risk of CVE-2017-3607.
What types of attacks are possible with CVE-2017-3607?
CVE-2017-3607 allows unauthenticated attackers with access to the infrastructure to potentially compromise the Data Store.
What component of Oracle is impacted by CVE-2017-3607?
CVE-2017-3607 affects the Data Store component of Oracle Berkeley DB.
- collector/nvd-index
- agent/references
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/severity
- agent/author
- agent/remedy
- agent/description
- agent/first-publish-date
- agent/softwarecombine
- agent/event
- agent/tags
- agent/source
- vendor/oracle
- canonical/oracle berkeley db