dbcve.org
Junos Os EvolvedOperating system · Juniper

CVE-2022-22247

HIGH · 7.5 CVSS v3.1 Published 2022-10-18
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 Input Validation vulnerability in ingress TCP segment processing of Juniper Networks Junos OS Evolved allows a network-based unauthenticated attacker to send a crafted TCP segment to the device, triggering a kernel panic, leading to a Denial of Service (DoS) condition. Continued receipt and processing of this TCP segment could create a sustained Denial of Service (DoS) condition. This issue affects Juniper Networks Junos OS Evolved: 21.3 versions prior to 21.3R3-EVO; 21.4 versions prior to 21.4R2-EVO; 22.1 versions prior to 22.1R2-EVO. This issue does not affect Juniper Networks Junos OS Evolved versions prior to 21.3R1-EVO.

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 input validation in the ingress TCP segment processing logic of Juniper Networks Junos OS Evolved allows a network-based unauthenticated attacker to send specially crafted TCP segments that trigger a kernel panic, causing a Denial of Service condition that can be sustained through continued receipt of malicious packets.

MitigationApply the vendor-supplied software updates (21.3R3-EVO, 21.4R2-EVO, 22.1R2-EVO or later) to address the improper input validation vulnerability in TCP segment processing. Consider implementing network-level filtering or intrusion detection as a compensating control until the update can be applied.

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:= 21.3= 21.4= 22.1

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. Identify the installed Junos OS Evolved version
    Execute the command 'show version' or 'show version detail' on the device CLI to display the software version information
    Affected if The displayed version matches exactly 21.3, 21.4, or 22.1 (or falls within these specific release trains if the = notation indicates the entire release train)
  2. Confirm TCP ingress processing is active
    Verify the device is functioning as a network device with TCP routing/switching capabilities enabled - this is the default operational state for Junos OS Evolved
    Affected if TCP processing is enabled, which is the default state for any routing platform
  3. Determine network exposure
    Review the device's interface configuration and network topology to confirm it can receive TCP traffic from untrusted network segments
    Affected if The device has network-facing interfaces accepting TCP traffic, which is standard for network equipment

A system is affected if it runs Junos OS Evolved version 21.3, 21.4, or 22.1 (or the corresponding release train) with TCP processing enabled and network exposure to untrusted traffic sources.

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 (21.3R3-EVO, 21.4R2-EVO, 22.1R2-EVO or later) to address the improper input validation vulnerability in TCP segment processing. Consider implementing network-level filtering or intrusion detection as a compensating control until the update can be applied.

Recommended fix High confidence

21.3R3-EVO, 21.4R2-EVO, or 22.1R2-EVO (depending on your current branch)

  1. Upgrade Junos OS Evolved to version 21.3R3-EVO or later for the 21.3 branch
  2. Alternatively, upgrade to version 21.4R2-EVO or later for the 21.4 branch
  3. Alternatively, upgrade to version 22.1R2-EVO or later for the 22.1 branch
  4. After upgrade, verify the device is operational and the vulnerability is remediated
Caveat Standard Junos OS Evolved upgrade procedures apply; ensure compatibility with your deployment and review Juniper upgrade documentation

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

Fix this in Junos Os Evolved Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22247 — 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-22247 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