# CVE-2017-8919: Information disclosure in n/a

> Remote authenticated users can obtain sensitive LDAP passwords from logs in NetApp OnCommand API Services.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-wc85-c4qp-j929

## What is CVE-2017-8919?

CVE-2017-8919 is a medium-severity vulnerability in n/a, published on 25 Jul 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

NetApp OnCommand API Services before 1.2P3 logs the LDAP BIND password when a user attempts to log in using the REST API, which allows remote authenticated users to obtain sensitive password information via unspecified vectors.

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

It affects 1 product.


Products: Netapp Oncommand Api Services.

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

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

## Is CVE-2017-8919 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-15518](https://insights.sbomify.com/CVE-2017-15518/): Information disclosure in OnCommand API Services and NetApp Service Level Manager (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-8919 is a medium-severity vulnerability in n/a, published on 25 Jul 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-8919 in the wild and no public exploit code.

Affected product: n/a. 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-8919/ (Markdown: https://insights.sbomify.com/CVE-2017-8919/index.md)
```

## Sources

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

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