Skip to main content
No exploitation reportedFix available

CVE-2019-0039

No exploitation reported by the sources we read.

  • Published2019-04-10
  • Fixed in18.3r1-s1 · 18.2r1-s5 · 18.2x75-d30 · 18.1r2-s4 · 17.4r1-s6 · 17.3r3-s2
  • WeaknessCWE-307

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

If REST API is enabled, the Junos OS login credentials are vulnerable to brute force attacks. The high default connection limit of the REST API may allow an attacker to brute-force passwords using advanced scripting techniques. Additionally, administrators who do not enforce a strong password policy can increase the likelihood of success from brute force attacks. Affected releases are Juniper Networks Junos OS: 14.1X53 versions prior to 14.1X53-D49; 15.1 versions prior to 15.1F6-S12, 15.1R7-S3; 15.1X49 versions prior to 15.1X49-D160; 15.1X53 versions prior to 15.1X53-D236, 15.1X53-D495, 15.1X53-D591, 15.1X53-D69; 16.1 versions prior to 16.1R3-S10, 16.1R4-S12, 16.1R6-S6, 16.1R7-S3; 16.1X65 versions prior to 16.1X65-D49; 16.2 versions prior to 16.2R2-S7; 17.1 versions prior to 17.1R2-S10, 17.1R3; 17.2 versions prior to 17.2R1-S8, 17.2R3-S1; 17.3 versions prior to 17.3R3-S2; 17.4 versions prior to 17.4R1-S6, 17.4R2-S2; 18.1 versions prior to 18.1R2-S4, 18.1R3-S1; 18.2 versions prior to 18.2R1-S5; 18.2X75 versions prior to 18.2X75-D30; 18.3 versions prior to 18.3R1-S1.

Timeline

dates in UTC
  1. 2019-04-1020:29CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2019-0039?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2019-0039?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Juniper junos
BranchAffectedFixed in
18.3≥ 18.3, < 18.3r1-s118.3r1-s1
18.2≥ 18.2, < 18.2r1-s518.2r1-s5
18.2≥ 18.2x75, < 18.2x75-d3018.2x75-d30
18.1≥ 18.1, < 18.1r2-s418.1r2-s4
17.4≥ 17.4, < 17.4r1-s617.4r1-s6
17.3≥ 17.3, < 17.3r3-s217.3r3-s2
17.2≥ 17.2, < 17.2r1-s817.2r1-s8
17.1≥ 17.1, < 17.1r2-s1017.1r2-s10
16.2≥ 16.2, < 16.2r2-s716.2r2-s7
16.1≥ 16.1, < 16.1r3-s1016.1r3-s10
16.1≥ 16.1x65, < 16.1x65-d4916.1x65-d49
15.1≥ 15.1, < 15.1f6-s1215.1f6-s12

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

  1. Update Juniper junos to 18.3r1-s1 · 18.2r1-s5 · 18.2x75-d30 · 18.1r2-s4 · 17.4r1-s6 · 17.3r3-s2 · 17.2r1-s8 · 17.1r2-s10

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • NVDCVSS 3.18.1read 2026-10-23
  • CNACVSS 3.05.3read 2026-10-23
  • NVDCVSS 2.04.3read 2026-10-23
  • CNAweakness (CWE)CWE-307read 2026-10-23
  • NVDweakness (CWE)CWE-307read 2026-10-23
  • FIRST EPSSEPSS score1.3 %2026-10-23

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2019-04-10
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2019-0039?

If REST API is enabled, the Junos OS login credentials are vulnerable to brute force attacks. The high default connection limit of the REST API may allow an attacker to brute-force passwords using advanced scripting techniques. Additionally, administrators who do not enforce a strong password policy can increase the likelihood of success from brute force attacks. Affected releases are Juniper Networks Junos OS: 14.1X53 versions prior to 14.1X53-D49; 15.1 versions prior to 15.1F6-S12, 15.1R7-S3; 15.1X49 versions prior to 15.1X49-D160; 15.1X53 versions prior to 15.1X53-D236, 15.1X53-D495, 15.1X53-D591, 15.1X53-D69; 16.1 versions prior to 16.1R3-S10, 16.1R4-S12, 16.1R6-S6, 16.1R7-S3; 16.1X65 versions prior to 16.1X65-D49; 16.2 versions prior to 16.2R2-S7; 17.1 versions prior to 17.1R2-S10, 17.1R3; 17.2 versions prior to 17.2R1-S8, 17.2R3-S1; 17.3 versions prior to 17.3R3-S2; 17.4 versions prior to 17.4R1-S6, 17.4R2-S2; 18.1 versions prior to 18.1R2-S4, 18.1R3-S1; 18.2 versions prior to 18.2R1-S5; 18.2X75 versions prior to 18.2X75-D30; 18.3 versions prior to 18.3R1-S1.

Is CVE-2019-0039 actively exploited?

Active exploitation of CVE-2019-0039 has not been confirmed. Its EPSS score was 1.3% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2019-0039?

CVE-2019-0039 has a CVSS v3 base score of 8.1 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month