# CVE-2019-0030: Juniper ATP: Password hashing uses DES and a hardcoded salt

> Attackers can trivially recover passwords from Juniper ATP files due to weak DES hashing with a hardcoded salt.

- **Severity:** Medium 6.7 (`CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jan 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-4877-h7j8-9393

## What is CVE-2019-0030?

CVE-2019-0030 is a medium-severity vulnerability in Juniper ATP, published on 15 Jan 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Juniper ATP uses DES and a hardcoded salt for password hashing, allowing for trivial de-hashing of the password file contents. This issue affects Juniper ATP 5.0 versions prior to 5.0.3.

Weakness: CWE-916 (Use of Password Hash With Insufficient Computational Effort), CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

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

It affects 1 product.


Products: Juniper Advanced Threat Prevention Firmware.

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

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

## Is CVE-2019-0030 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-0030 is a medium-severity vulnerability in Juniper ATP, published on 15 Jan 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-0030 in the wild and no public exploit code.

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

## Sources

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

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