CVE-2017-3611
CVE-2017-3611 is a high-severity vulnerability in Oracle Berkeley Db with a CVSS 3.x base score of 7.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.
Key facts
- Severity: High (CVSS 3.x base score 7.0)
- CVSS v2: 3.7
- EPSS exploit prediction: 0% (35th percentile)
- Actively exploited: Not listed in CISA KEV
- Affected product: Oracle Berkeley Db
- Published:
- Last modified:
Description
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).
Frequently asked questions
- What is CVE-2017-3611?
- 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).
- How severe is CVE-2017-3611?
- CVE-2017-3611 has a CVSS 3.x base score of 7.0, rated high severity. It is exploitable over local access with high attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2017-3611 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (35th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2017-3611?
- CVE-2017-3611 affects Oracle Berkeley Db. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2017-3611?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- When was CVE-2017-3611 published?
- CVE-2017-3611 was published on 2017-04-24 and last updated on 2026-06-17.
References
- http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html
- http://www.securityfocus.com/bid/97859
Affected products (1)
- cpe:2.3:a:oracle:berkeley_db:*:*:*:*:*:*:*:*
More vulnerabilities in Oracle Berkeley Db
- CVE-2016-3418 — High (CVSS 7.8): Unspecified vulnerability in the DataStore component in Oracle Berkeley DB 11.2.5.0.32, 11.2.5.1.29, 11.2.5.2.42,…
- CVE-2016-0694 — High (CVSS 7.8): Unspecified vulnerability in the DataStore component in Oracle Berkeley DB 11.2.5.0.32, 11.2.5.1.29, 11.2.5.2.42,…
- CVE-2016-0692 — High (CVSS 7.8): Unspecified vulnerability in the DataStore component in Oracle Berkeley DB 11.2.5.0.32, 11.2.5.1.29, 11.2.5.2.42,…
- CVE-2016-0689 — High (CVSS 7.8): Unspecified vulnerability in the DataStore component in Oracle Berkeley DB 11.2.5.0.32, 11.2.5.1.29, 11.2.5.2.42,…
- CVE-2016-0682 — High (CVSS 7.8): Unspecified vulnerability in the DataStore component in Oracle Berkeley DB 11.2.5.0.32, 11.2.5.1.29, 11.2.5.2.42,…
- CVE-2020-2981 — High (CVSS 7.0): Vulnerability in the Data Store component of Oracle Berkeley DB. The supported version that is affected is Prior to…