# CVE-2019-0032: Junos Space Service Now and Service Insight: Organization username and password stored in plaintext in log files.

> Locally authenticated attackers can read plaintext credentials from log files to gain unauthorized access to Juniper Service Now and Service Insight.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/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:** 10 Apr 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-vxwr-95xc-xxrg

## What is CVE-2019-0032?

CVE-2019-0032 is a medium-severity vulnerability in Juniper Networks Service Insight, published on 10 Apr 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A password management issue exists where the Organization authentication username and password were stored in plaintext in log files. A locally authenticated attacker who is able to access these stored plaintext credentials can use them to login to the Organization. Affected products are: Juniper Networks Service Insight versions from 15.1R1, prior to 18.1R1. Service Now versions from 15.1R1, prior to 18.1R1.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File), CWE-522 (Insufficiently Protected Credentials), CWE-256 (Plaintext Storage of a Password)

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

It affects 2 products.


Products: Juniper Service Insight, Juniper Service Now.

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

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

## Is CVE-2019-0032 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-0032 is a medium-severity vulnerability in Juniper Networks Service Insight, published on 10 Apr 2019. 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-0032 in the wild and no public exploit code.

Affected product: Juniper Networks Service Insight. 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-0032/ (Markdown: https://insights.sbomify.com/CVE-2019-0032/index.md)
```

## Sources

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

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