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

> A Guardian user can read installation files to discover passwords for users acknowledging events, exposing sensitive credentials.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jan 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mh9g-8cm9-c5wj

## What is CVE-2019-19539?

CVE-2019-19539 is a medium-severity vulnerability in n/a, published on 27 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in Idelji Web ViewPoint H01ABO-H01BY and L01ABP-L01ABZ, Web ViewPoint Plus H01AAG-H01AAQ and L01AAH-L01AAR, and Web ViewPoint Enterprise H01-H01AAE and L01-L01AAF. By reading ADB or AADB file content within the Installation subvolume, a Guardian user can discover the password of the group.user or alias who acknowledges events from the WVP Events screen.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

It affects 3 products.


Products: Hp Web Viewpoint T0320, Hp Web Viewpoint T0952, Hp Web Viewpoint T0986.

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

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

## Is CVE-2019-19539 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-19539 is a medium-severity vulnerability in n/a, published on 27 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-19539 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-19539/ (Markdown: https://insights.sbomify.com/CVE-2019-19539/index.md)
```

## Sources

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

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