dbcve.org
JunosOperating system · Juniper

CVE-2022-22237

MEDIUM · 6.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 →
74/100
Remediation priority · Elevated
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 Authentication vulnerability in the kernel of Juniper Networks Junos OS allows an unauthenticated, network-based attacker to cause an impact on confidentiality or integrity. A vulnerability in the processing of TCP-AO will allow a BGP or LDP peer not configured with authentication to establish a session even if the peer is locally configured to use authentication. This could lead to untrusted or unauthorized sessions being established. This issue affects Juniper Networks Junos OS: 21.2 versions prior to 21.2R3-S1; 21.3 versions prior to 21.3R2-S2, 21.3R3; 21.4 versions prior to 21.4R2-S1, 21.4R3; 22.1 versions prior to 22.1R1-S1, 22.1R2. This issue does not affect Juniper Networks Junos OS Evolved.

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

An improper authentication vulnerability in the Juniper Networks Junos OS kernel allows unauthenticated network-based attackers to establish BGP or LDP sessions even when authentication is locally configured for those peers. The flaw in TCP-AO processing bypasses configured authentication requirements, enabling unauthorized sessions that compromise confidentiality and integrity.

MitigationUpgrade Junos OS to the fixed versions (21.2R3-S1, 21.3R2-S2/21.3R3, 21.4R2-S1/21.4R3, 22.1R1-S1/22.1R2 or later). Verify BGP and LDP peer configurations enforce authentication after upgrade.

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
JunosOperating system
Affected:= 21.2= 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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

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 installed Junos OS version
    Run 'show version' on the device CLI to retrieve the installed Junos version
    Affected if The version matches 21.2, 21.3, 21.4, or 22.1 (without S1/S2补丁 or R2/R3 suffix)
  2. Check for configured BGP peers
    Run 'show configuration protocols bgp' to review BGP peer configurations and identify which peers have authentication configured
    Affected if BGP peers are configured with authentication (e.g., md5 or tcp-ao) and the device runs an affected version
  3. Check for configured LDP peers
    Run 'show configuration protocols ldp' to review LDP peer configurations
    Affected if LDP peers are configured and the device runs an affected version
  4. Verify if TCP-AO is enabled for BGP
    Run 'show configuration protocols bgp group <group-name>' and look for 'authentication-key' or 'tcp-authentication' statements
    Affected if TCP-AO (tcp-authentication) is configured for BGP peers on an affected version

The environment is affected if the device runs Junos OS version 21.2, 21.3, 21.4, or 22.1 without the S1/S2/R2/R3 patches, and has BGP or LDP peers configured where authentication is expected but could be bypassed via the TCP-AO flaw.

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

Upgrade Junos OS to the fixed versions (21.2R3-S1, 21.3R2-S2/21.3R3, 21.4R2-S1/21.4R3, 22.1R1-S1/22.1R2 or later). Verify BGP and LDP peer configurations enforce authentication after upgrade.

Recommended fix High confidence

Junos OS 21.2R3-S1 or later, 21.3R2-S2/21.3R3 or later, 21.4R2-S1/21.4R3 or later, or 22.1R1-S1/22.1R2 or later (depending on starting version)

  1. 1. Verify the current Junos OS version running on the device using 'show version'
  2. 2. Identify the specific hardware platform and confirm it is not Junos OS Evolved (this issue only affects Junos OS)
  3. 3. Download the appropriate fixed Junos OS release from the Juniper Networks website based on the current version: for 21.2 upgrade to 21.2R3-S1 or later, for 21.3 upgrade to 21.3R2-S2 or 21.3R3 or later, for 21.4 upgrade to 21.4R2-S1 or 21.4R3 or later, for 22.1 upgrade to 22.1R1-S1 or 22.1R2 or later
  4. 4. Upload the Junos OS upgrade package to the device using 'file copy' or FTP/SCP
  5. 5. Initiate the software installation with 'request system software add <package-name> reboot'
  6. 6. After the device reboots, verify the new version is installed using 'show version'
  7. 7. Verify BGP and LDP sessions are operational and review authentication configuration
Caveat Standard Junos upgrade precautions apply - review release notes for any behavior changes, ensure configuration backup exists before upgrade

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

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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