CVE-2017-2349
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 command injection vulnerability in the IDP feature of Juniper Networks Junos OS on SRX series devices potentially allows a user with login access to the device to execute shell commands and elevate privileges. Affected releases are Juniper Networks Junos OS 12.1X44 prior to 12.1X44-D60; 12.1X46 prior to 12.1X46-D50; 12.1X47 prior to 12.1X47-D30, 12.1X47-D35; 12.3X48 prior to 12.3X48-D20, 12.3X48-D30; 15.1X49 prior to 15.1X49-D20, 15.1X49-D30.
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 command injection vulnerability in the IDP (Intrusion Detection and Prevention) feature of Juniper Networks Junos OS on SRX series devices allows an authenticated user with login access to execute arbitrary shell commands and potentially elevate privileges. The vulnerability stems from improper input validation within the IDP subsystem.
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.1x44= 12.1x46= 12.1x47= 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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.
-
Check Junos OS versionRun `show version` on the device CLI and note the version string (e.g., 12.1X44-D50). Compare it against the affected ranges: 12.1x44, 12.1x46, 12.1x47, 12.3x48, 15.1x49.Affected if The installed version exactly matches one of the listed versions (e.g., 12.1X44, 12.3X48, 15.1X49) or falls within those release trains before the fixed builds.
-
Confirm SRX series deviceRun `show chassis hardware` or `show system information` and verify the model is an SRX platform (SRX100, SRX210, SRX240, SRX550, SRX1500, etc.).Affected if The device is NOT an SRX series device, as this vulnerability affects only SRX platforms.
-
Verify IDP is licensed and enabledRun `show system services idp` or `show license` to check if the IDP feature is licensed and active. Also run `show security idp status` to see if IDP is loaded.Affected if IDP is NOT licensed or NOT loaded; the command injection only applies when the IDP subsystem is operational.
-
Inspect IDP policy configurationRun `show security idp policy` and review all IDP rulebase configurations for any suspicious or unexpected command strings, shell metacharacters, or pipe/redirect operators in rule actions.Affected if The IDP policy contains rule actions or parameters with embedded shell commands (e.g., ;, |, `, $()) that were not intentionally configured.
A user is affected if the device runs an SRX series with a Junos version matching 12.1x44, 12.1x46, 12.1x47, 12.3x48, or 15.1x49, has an active IDP license, and has IDP configured.
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.
From vendor dataUpgrade Junos OS to the fixed versions (12.1X44-D60 or later, 12.1X46-D50 or later, 12.1X47-D35 or later, 12.3X48-D30 or later, 15.1X49-D30 or later) as specified in the Juniper advisory.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2349 — 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-2349 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