CVE-2017-10615
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA vulnerability in Junos OS PAM (pluggable authentication module) allows unauthenticated network-based attackers to execute arbitrary code or crash PAM-dependent daemons like telnetd and sshd, achieving critical severity via remote unauthenticated attack surface.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 14.1= 14.1x53= 14.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine Junos OS versionRun 'show version' or 'show version detail' on the Junos device CLIAffected if The displayed version matches exactly 14.1, 14.1x53, or 14.2 (without patches)
-
Identify PAM-dependent services enabledReview system services configuration using 'show configuration system services'Affected if telnetd or sshd services are configured and enabled on any interface
-
Check management interface exposureUse 'show configuration interfaces' and 'show configuration system services' to identify which IP addresses or interfaces the telnet and SSH services bind toAffected if SSH or telnet services are reachable from untrusted network interfaces (not loopback or dedicated management VLAN)
-
Verify PAM module statusCheck if the system uses PAM for authentication by reviewing authentication configuration: 'show configuration system login'Affected if PAM authentication method is in use (this is default in Junos)
-
Confirm network accessibility of vulnerable servicesTest connectivity to SSH (port 22) or telnet (port 23) from external network sources using 'telnet <device-ip>' or 'ssh -v <device-ip>'Affected if These services are accessible from untrusted networks without ACL filtering
A device is affected if it runs Junos version 14.1, 14.1x53, or 14.2 AND has SSH or telnet services exposed to network attackers, since the vulnerability allows remote code execution via unauthenticated PAM exploitation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Junos OS to patched versions: 14.1R8-S4 or later, 14.1X53-D50 or later (EX/QFX), 14.2R7-S8 or later. Until patched, restrict network access to management interfaces and PAM-authenticating services.
14.1R8-S4 or 14.1R9 (14.1 branch); 14.1X53-D50 (14.1X53 branch); 14.2R7-S8 or 14.2R8 (14.2 branch)
- Verify the current Junos OS version using 'show version' command
- Confirm the device is an EX series switch or QFX series switch if running 14.1X53, or a standard Junos device for 14.1/14.2 releases
- Download the appropriate fixed Junos OS release from the Juniper support portal: 14.1R8-S4 or 14.1R9 for 14.1 branch; 14.1X53-D50 for 14.1X53 branch; 14.2R7-S8 or 14.2R8 for 14.2 branch
- Transfer the Junos OS upgrade package to the device using SCP or FTP
- Perform a system backup and validate the backup is stored safely
- Initiate the Junos OS upgrade using 'request system software add <package-name>' command
- Reboot the device after upgrade completion using 'request system reboot' command
- Verify the new Junos version is installed using 'show version'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10615 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-10615 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data