CVE-2017-2343
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 · uneditedThe Integrated User Firewall (UserFW) feature was introduced in Junos OS version 12.1X47-D10 on the Juniper SRX Series devices to provide simple integration of user profiles on top of the existing firewall polices. As part of an internal security review of the UserFW services authentication API, hardcoded credentials were identified and removed which can impact both the SRX Series device, and potentially LDAP and Active Directory integrated points. An attacker may be able to completely compromise SRX Series devices, as well as Active Directory servers and services. When Active Directory is compromised, it may allow access to user credentials, workstations, servers performing other functions such as email, database, etc. Inter-Forest Active Directory deployments may also be at risk as the attacker may gain full administrative control over one or more Active Directories depending on the credentials supplied by the administrator of the AD domains and SRX devices performing integrated authentication of users, groups and devices. To identify if your device is potentially vulnerable to exploitation, check to see if the service is operating; from CLI review the following output: root@SRX-Firewall# run show services user-identification active-directory-access domain-controller status extensive A result of "Status: Connected" will indicate that the service is active on the device. To evaluate if user authentication is occurring through the device: root@SRX-Firewall# run show services user-identification active-directory-access active-directory-authentication-table all Next review the results to see if valid users and groups are returned. e.g. Domain: juniperlab.com Total entries: 3 Source IP Username groups state 172.16.26.1 administrator Valid 192.168.26.2 engg01 engineers Valid 192.168.26.3 guest01 guests Valid Domain: NULL Total entries: 8 Source IP Username groups state 192.168.26.4 Invalid 192.168.26.5 Invalid This will also indicate that Valid users and groups are authenticating through the device. Affected releases are Juniper Networks Junos OS 12.3X48 from 12.3X48-D30 and prior to 12.3X48-D35 on SRX series; 15.1X49 from 15.1X49-D40 and prior to 15.1X49-D50 on SRX series. Devices on any version of Junos OS 12.1X46, or 12.1X47 are unaffected 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 confidenceHardcoded credentials were discovered in the UserFW (Integrated User Firewall) authentication API on Juniper SRX Series devices running affected Junos OS versions. The vulnerability allows remote unauthenticated attackers to completely compromise affected SRX devices and potentially gain administrative access to integrated Active Directory servers, exposing user credentials, workstations, and inter-Forest AD deployments.
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= 12.3x48= 15.1x49CVSS 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 the Junos OS versionRun 'show version' or 'show system information' on the SRX device CLIAffected if The version shown is in the 12.3X48 or 15.1X49 release line before the fixed releases (12.3X48-D35 or later, 15.1X49-D50 or later)
-
Verify UserFW service is enabledRun 'show configuration | match userfw' or 'show configuration services user-wall | display set' to check for UserFW (User Firewall) configurationAffected if UserFW/User Wall service is configured and enabled on the device
-
Confirm UserFW authentication API is accessibleCheck the service listener status using 'show services user-wall status' or examine the configuration for authentication API endpoints under services user-wallAffected if The UserFW authentication API service is active and listening for authentication requests
-
Review UserFW authentication methodsExamine the UserFW configuration for integrated authentication sources using 'show configuration services user-wall authentication'Affected if UserFW is configured to use integrated authentication (such as Active Directory integration) rather than purely local authentication
The device is vulnerable if it runs a Junos OS version in the 12.3X48 or 15.1X49 line AND has UserFW service enabled with its authentication API accessible.
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 12.3X48-D35 or later, or 15.1X49-D50 or later. Verify service status using the provided CLI commands; if vulnerable and unable to upgrade immediately, disable the UserFW service to prevent exploitation.
Junos OS 12.3X48-D35 or later; Junos OS 15.1X49-D50 or later
- 1. Identify the current Junos OS version by running 'show version' on the SRX device CLI
- 2. Determine if the device is running an affected version: 12.3X48-D30 or earlier, or 15.1X49-D40 or earlier
- 3. Check if the UserFW service is active by running 'run show services user-identification active-directory-access domain-controller status extensive' - look for 'Status: Connected'
- 4. If vulnerable, schedule a maintenance window for the upgrade
- 5. Download the fixed Junos OS release: 12.3X48-D35 or later for the 12.3X48 train, OR 15.1X49-D50 or later for the 15.1X49 train
- 6. Upload the Junos upgrade package to the SRX device
- 7. Install the upgrade using 'request system software add <package-name>' and reboot
- 8. After reboot, verify the new 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-2343 — 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-2343 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