# CVE-2019-9976: Information disclosure in n/a

> Logged-in users can read administrative credentials from temporary log files on DASAN H660RM devices.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 11 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-w56x-q3jg-3926

## What is CVE-2019-9976?

CVE-2019-9976 is a high-severity vulnerability in n/a, published on 11 Apr 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Boa server configuration on DASAN H660RM devices with firmware 1.03-0022 logs POST data to the /tmp/boa-temp file, which allows logged-in users to read the credentials of administration web interface users.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2019-9976?

It affects 1 product.


Products: Dasannetworks H660rm Firmware.

## How do I fix CVE-2019-9976?

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

## Is CVE-2019-9976 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-9974](https://insights.sbomify.com/CVE-2019-9974/): Missing authorization in n/a (critical 9.1)
- [CVE-2019-9975](https://insights.sbomify.com/CVE-2019-9975/): Hardcoded credentials in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-9976 and fix it if it is affected.

What it is: CVE-2019-9976 is a high-severity vulnerability in n/a, published on 11 Apr 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-9976 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-2019-9976/ (Markdown: https://insights.sbomify.com/CVE-2019-9976/index.md)
```

## Sources

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

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