# CVE-2017-3613: Other in Oracle Berkeley DB

> An unauthenticated attacker with local access can compromise the Data Store component of Oracle Berkeley DB, leading to full takeover.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 24 Apr 2017
- **Updated:** 4 Oct 2024
- **Also known as:** AZL-34922, AZL-6625, GHSA-4648-f7wc-7jfm

## What is CVE-2017-3613?

CVE-2017-3613 is a high-severity vulnerability in Oracle Berkeley Db, published on 24 Apr 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official 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).

## Which versions are affected by CVE-2017-3613?

It affects 1 product.


Products: Oracle Berkeley Db.

## How do I fix CVE-2017-3613?

Upgrade to a fixed version.

## Is CVE-2017-3613 being exploited?

There is no known exploitation of CVE-2017-3613 in the wild and no public exploit code.

## Other vulnerabilities in Oracle Berkeley Db

- [CVE-2016-0682](https://insights.sbomify.com/CVE-2016-0682/): Other in n/a (high 7.8)
- [CVE-2016-0689](https://insights.sbomify.com/CVE-2016-0689/): Other in n/a (high 7.8)
- [CVE-2016-0692](https://insights.sbomify.com/CVE-2016-0692/): Other in n/a (high 7.8)
- [CVE-2016-0694](https://insights.sbomify.com/CVE-2016-0694/): Other in n/a (high 7.8)
- [CVE-2016-3418](https://insights.sbomify.com/CVE-2016-3418/): Other in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-3613 and fix it if it is affected.

What it is: CVE-2017-3613 is a high-severity vulnerability in Oracle Berkeley Db, published on 24 Apr 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-3613 in the wild and no public exploit code.

Affected product: Oracle Berkeley Db. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-3613/ (Markdown: https://insights.sbomify.com/CVE-2017-3613/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-3613
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-3613
- OSV: https://osv.dev/vulnerability/CVE-2017-3613

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-3613/
Summaries are generated and may contain mistakes; the official description above is the record.