Incorrect messages from Juniper Identity Management Service (JIMS) can trigger Denial of Service or firewall bypass conditions for SRX series devices

published 2019-04-10 7y ago modified 2026-06-17 4mo ago also EUVD-2019-0849

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

Juniper Identity Management Service (JIMS) for Windows versions prior to 1.1.4 may send an incorrect message to associated SRX services gateways. This may allow an attacker with physical access to an existing domain connected Windows system to bypass SRX firewall policies, or trigger a Denial of Service (DoS) condition for the network.

Patch / fix

fixed in 1

Juniper Networks Juniper Identity Management Service 1.1.4

Is CVE-2019-0042 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.0	5.7	CVSS:3.0/AV:P/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:H
NVD	3.1	4.2	CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD	2.0	1.9	AV:L/AC:M/Au:N/C:N/I:N/A:P

Affected products

Juniper Networks Juniper Identity Management Service

Classification

Weakness

CWE-404 Improper Resource Shutdown or Release
CWE-305 Authentication Bypass by Primary Weakness
CWE-669 Incorrect Resource Transfer Between Spheres

References

kb.juniper.net /JSA10934
mitigation, vendor-advisory

Sources

CVE List CVE-2019-0042
NVD CVE-2019-0042

Fencer Intel 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.