CVE-2017-10601
No exploitation reported by the sources we read.
- Published2017-07-17
- WeaknessCWE-287
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « 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
A specific device configuration can result in a commit failure condition. When this occurs, a user is logged in without being prompted for a password while trying to login through console, ssh, ftp, telnet or su, etc., This issue relies upon a device configuration precondition to occur. Typically, device configurations are the result of a trusted administrative change to the system's running configuration. The following error messages may be seen when this failure occurs: mgd: error: commit failed: (statements constraint check failed) Warning: Commit failed, activating partial configuration. Warning: Edit the router configuration to fix these errors. If the administrative changes are not made that result in such a failure, then this issue is not seen. No other Juniper Networks products or platforms are affected by this issue. Affected releases are Juniper Networks Junos OS 12.3 prior to 12.3R10, 12.3R11; 12.3X48 prior to 12.3X48-D20; 13.2 prior to 13.2R8; 13.3 prior to 13.3R7; 14.1 prior to 14.1R4-S12, 14.1R5, 14.1R6; 14.1X53 prior to 14.1X53-D30; 14.2 prior to 14.2R4; 15.1 prior to 15.1F2, 15.1F3, 15.1R2.
Timeline
dates in UTC- 2017-07-1713:18CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-10601?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-10601?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 12.3 | = 12.3 | no fix published | NVD |
| 12.3 | = 12.3x48 | no fix published | NVD |
| 13.2 | = 13.2 | no fix published | NVD |
| 13.3 | = 13.3 | no fix published | NVD |
| 14.1 | = 14.1 | no fix published | NVD |
| 14.1 | = 14.1x53 | no fix published | NVD |
| 14.2 | = 14.2 | no fix published | NVD |
| 15.1 | = 15.1 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
Advisories and patches
- kb.juniper.netMitigation · Vendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- CNACVSS 3.09.8read 2026-10-23
- NVDCVSS 3.09.8read 2026-10-23
- NVDCVSS 2.010read 2026-10-23
- NVDweakness (CWE)CWE-287read 2026-10-23
- FIRST EPSSEPSS score1.8 %2026-10-22
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2017-07-17
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2017-10601?
Is CVE-2017-10601 actively exploited?
What is the CVSS score for CVE-2017-10601?
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
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.