What is CVE-2017-10615?A critical-severity flaw in Junos, explained.
CVE-2017-10615 is a critical-severity flaw (CVSS 9.8) in Junos from Juniper, published on 13 October 2017. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 2.5%. If you run an affected version, plan in the vendor’s fix.
Published 13 October 2017. Record last updated 20 April 2025. We keep this page's data up to date.
What is CVE-2017-10615? In plain terms.
It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.
A vulnerability in the pluggable authentication module (PAM) of Juniper Networks Junos OS may allow an unauthenticated network based attacker to potentially execute arbitrary code or crash daemons such as telnetd or sshd that make use of PAM. Affected Juniper Networks Junos OS releases are: 14.1 from 14.1R5 prior to 14.1R8-S4, 14.1R9; 14.1X53 prior to 14.1X53-D50 on EX and QFX series; 14.2 from 14.2R3 prior to 14.2R7-S8, 14.2R8; No other Junos OS releases are affected by this issue. No other Juniper Networks products are affected by this issue.
What kind of flaw is it?
- CWE-20Improper Input Validation
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAnywhere on the internet
- How hard it is to pull offEasy: no special conditions
- Login needed firstNo login needed
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan read data, change data and take it offline
Severity vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Is CVE-2017-10615 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 2.5%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
CVE-2017-10615 scores 55. Action: Plan remediation.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2017-10615 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2017-10615? 17 products.
The published record lists 17 products from 1 vendor. If you run one of these, check your version, then go to the fix below.
- Operating system
Junos
by Juniper
Affected versions14.114.1-r114.1-r214.1-r314.1-r414.1-r514.1-r614.1-r714.1-r914.1x5314.1x53-d1014.1x53-d1514.1x53-d1614.1x53-d25 - Hardware
Ex3200
by Juniper
Affected versionsversion not specified - Hardware
Ex3300
by Juniper
Affected versionsversion not specified - Hardware
Ex3300-Vc
by Juniper
Affected versionsversion not specified - Hardware
Ex4200
by Juniper
Affected versionsversion not specified - Hardware
Ex4200-Vc
by Juniper
Affected versionsversion not specified - Hardware
Ex4300
by Juniper
Affected versionsversion not specified - Hardware
Ex4300-Vc
by Juniper
Affected versionsversion not specified - Hardware
Ex4500
by Juniper
Affected versionsversion not specified
How do I fix CVE-2017-10615? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
Does CVE-2017-10615 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
A vulnerability in the pluggable authentication module (PAM) of Juniper Networks Junos OS may allow an unauthenticated network based attacker to potentially ...
- Matched to
- Junos on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2017-10615 is a critical-severity flaw in Junos from Juniper, published on 13 October 2017. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.
It scores 9.8 out of 10 on the CVSS severity scale, which is critical. Our risk score for CVE-2017-10615 is 55 out of 100, which is Medium. Its action is "Plan remediation". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 2.5%. That can change at any time, which is why we keep watching.
For Junos from Juniper: 14.1, 14.1-r1, 14.1-r2, 14.1-r3, 14.1-r4, 14.1-r5 and 23 more. The record lists 17 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.