CVE-2022-22221
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 · uneditedAn Improper Neutralization of Special Elements vulnerability in the download manager of Juniper Networks Junos OS on SRX Series and EX Series allows a locally authenticated attacker with low privileges to take full control over the device. One aspect of this vulnerability is that the attacker needs to be able to execute any of the "request ..." or "show system download ..." commands. This issue affects Juniper Networks Junos OS on SRX Series and EX Series: All versions prior to 19.2R1-S9, 19.2R3-S5; 19.3 versions prior to 19.3R3-S6; 19.4 versions prior to 19.4R3-S8; 20.1 versions prior to 20.1R3-S4; 20.2 versions prior to 20.2R3-S4; 20.3 versions prior to 20.3R3-S3; 20.4 versions prior to 20.4R3-S2, 20.4R3-S3; 21.1 versions prior to 21.1R3-S1; 21.2 versions prior to 21.2R2-S2, 21.2R3; 21.3 versions prior to 21.3R2, 21.3R3; 21.4 versions prior to 21.4R1-S1, 21.4R2.
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 confidenceThis is a command injection vulnerability in the Junos OS download manager on SRX and EX Series devices. A low-privilege authenticated attacker can execute arbitrary commands and gain full device control by leveraging the 'request ...' or 'show system download ...' commands due to improper neutralization of special elements in user input.
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< 19.2= 19.2= 19.3= 19.4= 20.1= 20.2= 20.3= 20.4= 21.1= 21.2= 21.3= 21.4CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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.
-
Identify the installed Junos OS versionExecute 'show version' or 'show system information' on the device CLIAffected if The version output matches any of these: 19.2, 19.3, 19.4, 20.1, 20.2, 20.3, 20.4, 21.1, 21.2, 21.3, 21.4, or any version below 19.2
-
Confirm the device is an SRX or EX Series modelExecute 'show chassis hardware' or 'show system information' to identify the hardware modelAffected if The device model is an SRX Series firewall or EX Series switch
-
Verify the download manager functionality is accessibleAttempt to access 'request system download' or 'show system download' commands with low-privilege authenticated accessAffected if The download manager commands are available to the authenticated user context being assessed
-
Check for evidence of command injection in download logsReview system logs for 'download' related entries using 'show log messages | match download'Affected if Unexpected or malformed download commands appear in the logs
A user is affected if the device runs a Junos OS version in the 19.2 through 21.4 range on SRX or EX Series hardware and the download manager feature is accessible to the attacker.
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 · scoped19.2
Upgrade Junos OS to one of the fixed versions listed (19.2R1-S9, 19.2R3-S5, 19.3R3-S6, 19.4R3-S8, 20.1R3-S4, 20.2R3-S4, 20.3R3-S3, 20.4R3-S2, 21.1R3-S1, 21.2R2-S2, 21.2R3, 21.3R2, 21.3R3, 21.4R1-S1, 21.4R2 or later).
19.4R3-S8 (or later stable release within the 19.4 branch, or 20.1R3-S4/20.2R3-S4/20.3R3-S3/20.4R3-S3/21.1R3-S1/21.2R3/21.3R3/21.4R2 depending on compatibility)
- 1. Identify the current Junos OS version on the SRX Series or EX Series device using 'show version'
- 2. Review the Juniper KB article at kb.juniper.net for complete patch information
- 3. Plan maintenance window for upgrade (requires device reboot)
- 4. Backup current configuration using 'request system snapshot' or configuration export
- 5. Download the appropriate fixed Junos OS version (19.2R1-S9, 19.2R3-S5, 19.3R3-S6, or 19.4R3-S8 or later) from Juniper Networks
- 6. Transfer the Junos OS upgrade package to the device
- 7. Install the upgrade using 'request system software add <package-name>'
- 8. Reboot the device using 'request system reboot'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.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 $6,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22221 — 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-2022-22221 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