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

> Arista CloudVision Portal logs user passwords in plain text under specific configurations, exposing credentials to privileged users with VM access.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jmhx-5gvj-3fgw

## What is CVE-2019-18615?

CVE-2019-18615 is a medium-severity vulnerability in n/a, published on 19 Dec 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

In CloudVision Portal (CVP) for all releases in the 2018.2 Train, under certain conditions, the application logs user passwords in plain text for certain API calls, potentially leading to user password exposure. This only affects CVP environments where: 1. Devices have enable mode passwords which are different from the user's login password, OR 2. There are configlet builders that use the Device class and specify username and password explicitly Application logs are not accessible or visible from the CVP GUI. Application logs can only be read by authorized users with privileged access to the VM hosting the CVP application.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-312 (Cleartext Storage of Sensitive Information)

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

It affects 1 product.


Products: Arista Cloudvision Portal.

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

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

## Is CVE-2019-18615 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-9012](https://insights.sbomify.com/CVE-2016-9012/): Missing authorization in n/a (high 8.8)
- [CVE-2023-24546](https://insights.sbomify.com/CVE-2023-24546/): Missing authorization in CloudVision (high 8.1)
- [CVE-2019-18181](https://insights.sbomify.com/CVE-2019-18181/): Missing authorization in n/a (high 7.8)
- [CVE-2020-13881](https://insights.sbomify.com/CVE-2020-13881/): Information disclosure in n/a (high 7.5)
- [CVE-2019-17596](https://insights.sbomify.com/CVE-2019-17596/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-18615 is a medium-severity vulnerability in n/a, published on 19 Dec 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-18615 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-18615/ (Markdown: https://insights.sbomify.com/CVE-2019-18615/index.md)
```

## Sources

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

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