dbcve.org
Junos Os EvolvedOperating system · Juniper

CVE-2022-22183

HIGH · 7.5 CVSS v3.1 Published 2022-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
An Improper Access Control vulnerability in Juniper Networks Junos OS Evolved allows a network-based unauthenticated attacker who is able to connect to a specific open IPv4 port, which in affected releases should otherwise be unreachable, to cause the CPU to consume all resources as more traffic is sent to the port to create a Denial of Service (DoS) condition. Continued receipt and processing of these packets will create a sustained Denial of Service (DoS) condition. This issue affects: Juniper Networks Junos OS Evolved 20.4 versions prior to 20.4R3-S2-EVO; 21.1 versions prior to 21.1R3-S1-EVO; 21.2 versions prior to 21.2R3-EVO; 21.3 versions prior to 21.3R2-EVO; 21.4 versions prior to 21.4R2-EVO. This issue does not affect Junos OS.

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 confidence

Improper Access Control in Juniper Networks Junos OS Evolved allows an unauthenticated network attacker who can reach a specific IPv4 port (that should be unreachable) to cause CPU resource exhaustion, resulting in Denial of Service. Continued traffic to this port sustains the DoS condition.

MitigationApply the vendor-supplied software updates: upgrade to 20.4R3-S2-EVO, 21.1R3-S1-EVO, 21.2R3-EVO, 21.3R2-EVO, or 21.4R2-EVO or later. Additionally, ensure network filtering blocks unauthorized access to the affected port.

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
Junos Os EvolvedOperating system
Affected:= 20.4= 21.1= 21.2= 21.3= 21.4

CVSS 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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Junos OS Evolved is running
    Run 'show version' or 'show system version' and verify the operating system is Junos OS Evolved (not Junos OS)
    Affected if The device is running Junos OS Evolved (the vulnerability only affects Evolved variant)
  2. Check installed version against affected ranges
    Run 'show version' or 'cat /etc/version' to obtain the exact version number, then compare against affected versions: 20.4, 21.1, 21.2, 21.3, 21.4
    Affected if The installed version matches any of the affected versions listed (20.4, 21.1, 21.2, 21.3, 21.4)
  3. Identify and locate the affected service port
    Consult Juniper advisory documentation to identify the specific IPv4 port associated with this CVE; use 'show system connections' or review service listening configuration
    Affected if A specific service is listening on the port identified in the CVE advisory
  4. Verify port accessibility from untrusted networks
    Review firewall rules, ACLs, and interface configurations using 'show firewall' or 'show configuration interfaces' to determine if the affected port is reachable from external/untrusted networks
    Affected if The vulnerable port is accessible from untrusted network segments (the CVE requires the port to be reachable when it should not be)

A user is affected if the device runs Junos OS Evolved with a version matching 20.4, 21.1, 21.2, 21.3, or 21.4 AND the specific port referenced in the CVE advisory is accessible from untrusted networks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied software updates: upgrade to 20.4R3-S2-EVO, 21.1R3-S1-EVO, 21.2R3-EVO, 21.3R2-EVO, or 21.4R2-EVO or later. Additionally, ensure network filtering blocks unauthorized access to the affected port.

Recommended fix High confidence

21.4R2-EVO (or the appropriate fixed version for your branch: 20.4R3-S2-EVO, 21.1R3-S1-EVO, 21.2R3-EVO, 21.3R2-EVO)

  1. 1. Identify the current Junos OS Evolved version running on the device using 'show version'
  2. 2. Schedule a maintenance window for the upgrade operation
  3. 3. Download the appropriate fixed version image (20.4R3-S2-EVO, 21.1R3-S1-EVO, 21.2R3-EVO, 21.3R2-EVO, or 21.4R2-EVO) from the Juniper Networks support portal
  4. 4. Upload the new software package to the device using 'file copy' or similar method
  5. 5. Verify the software package integrity using 'request system software validate <package>'
  6. 6. Install the new software using 'request system software add <package> reboot'
  7. 7. After reboot, confirm the new version is installed using 'show version'
  8. 8. Verify that the previously vulnerable port is now properly restricted or that the fix is active
Caveat Standard Junos OS Evolved upgrade risks apply - ensure configuration backup and compatibility review before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Junos Os Evolved Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22183 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-22183 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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