Juniper ATP: Password hashing uses DES and a hardcoded salt

published 2019-01-15 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-0837

cvss: 6.7; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.5%; EPSS 0.5% chance of exploitation in 30 days, percentile 45%
public exploits: 0; none known

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.

Patch / fix

fixed in 1

Juniper Networks Juniper ATP 5.0.3

Exploit prediction

0.53% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.0	6.7	CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
NVD	3.1	7.2	CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	4.0	AV:N/AC:L/Au:S/C:P/I:N/A:N

Affected products

Juniper Networks Juniper ATP

Classification

Weakness

CWE-327 Use of a Broken or Risky Cryptographic Algorithm
CWE-916 Use of Password Hash With Insufficient Computational Effort

References

kb.juniper.net /JSA10918
vendor-advisory

Sources

CVE List CVE-2019-0030
NVD CVE-2019-0030

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary