# CVE-2018-15717: Weak cryptography in Open Dental

> Open Dental stores passwords using weak MD5 hashing, allowing attackers to potentially recover user credentials from the database.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Dec 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-vxh8-h4fx-wwhc

## What is CVE-2018-15717?

CVE-2018-15717 is a medium-severity vulnerability in Open Dental, published on 12 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Open Dental before version 18.4 stores user passwords as base64 encoded MD5 hashes.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-916 (Use of Password Hash With Insufficient Computational Effort)

## Which versions are affected by CVE-2018-15717?

It affects 1 product.


Products: Opendental Opendental.

## How do I fix CVE-2018-15717?

No fix has been published for CVE-2018-15717 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-15717 being exploited?

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

## Other vulnerabilities in Open Dental

- [CVE-2018-15719](https://insights.sbomify.com/CVE-2018-15719/): Hardcoded credentials in Open Dental (critical 9.8)
- [CVE-2016-6531](https://insights.sbomify.com/CVE-2016-6531/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2018-15718](https://insights.sbomify.com/CVE-2018-15718/): Information disclosure in Open Dental (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-15717 and fix it if it is affected.

What it is: CVE-2018-15717 is a medium-severity vulnerability in Open Dental, published on 12 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-15717 in the wild and no public exploit code.

Affected product: Open Dental. 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-2018-15717/ (Markdown: https://insights.sbomify.com/CVE-2018-15717/index.md)
```

## Sources

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

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