dbcve.org
JunosOperating system · Juniper

CVE-2022-22218

HIGH · 7.5 CVSS v3.1 Published 2022-10-18
Fix available
A fix is available. Upgrade to 19.1 or later.
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
On SRX Series devices, an Improper Check for Unusual or Exceptional Conditions when using Certificate Management Protocol Version 2 (CMPv2) auto re-enrollment, allows a network-based, unauthenticated attacker to cause a Denial of Service (DoS) by crashing the pkid process. The pkid process cannot handle an unexpected response from the Certificate Authority (CA) server, leading to crash. A restart is required to restore services. This issue affects: Juniper Networks Junos OS on SRX Series: All versions prior to 19.1R3-S9; 19.2 versions prior to 19.2R3-S6; 19.3 versions prior to 19.3R3-S7; 19.4 versions prior to 19.4R3-S9; 20.2 versions prior to 20.2R3-S5; 20.3 versions prior to 20.3R3-S4; 20.4 versions prior to 20.4R3-S4; 21.1 versions prior to 21.1R3-S1; 21.2 versions prior to 21.2R3; 21.3 versions prior to 21.3R2; 21.4 versions prior to 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 confidence

On Juniper SRX Series devices, the pkid process (certificate management daemon) crashes when handling unexpected responses from a Certificate Authority during CMPv2 auto re-enrollment. This improper check for unusual conditions allows an unauthenticated network attacker to cause denial of service by sending malicious CA responses.

MitigationUpgrade Junos OS to a fixed version (19.1R3-S9, 19.2R3-S6, 19.3R3-S7, 19.4R3-S9, 20.2R3-S5, 20.3R3-S4, 20.4R3-S4, 21.1R3-S1, 21.2R3, 21.3R2, or 21.4R2 or later). Schedule a maintenance window for the upgrade and ensure certificate services are tested post-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:< 19.1= 19.1= 19.2= 19.3= 19.4= 20.2= 20.3= 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 device model and platform
    Run 'show version' and identify if the device is a Juniper SRX Series or other Junos device that runs the pkid certificate management daemon
    Affected if Device is a Juniper SRX or Junos platform with pkid daemon
  2. Check installed Junos version
    Run 'show version' and locate the exact Junos OS version string (for example, 19.1, 19.2, 20.3, 21.4)
    Affected if Version matches any of: 19.1, 19.2, 19.3, 19.4, 20.2, 20.3, 20.4, 21.1, 21.2, 21.3, 21.4, or any version earlier than 19.1
  3. Verify CMPv2 auto-reenrollment is configured
    Run 'show configuration | display set | match cmp' or review 'show configuration security pki' to see if CMPv2 auto-reenrollment is enabled
    Affected if CMPv2 auto-reenrollment is actively configured on the device
  4. Check pkid process status
    Run 'show system processes extensive | match pkid' to verify if the pkid daemon is currently running or has crashed
    Affected if pkid process is not running or has recently crashed

A device is affected if it is a Juniper SRX or Junos device running any affected version (19.1 through 21.4) with CMPv2 auto-reenrollment enabled, or if the pkid process has crashed.

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
Upgrade available Upgrade to 19.1 or later
Fixed in 19.1
Interim mitigation

Upgrade Junos OS to a fixed version (19.1R3-S9, 19.2R3-S6, 19.3R3-S7, 19.4R3-S9, 20.2R3-S5, 20.3R3-S4, 20.4R3-S4, 21.1R3-S1, 21.2R3, 21.3R2, or 21.4R2 or later). Schedule a maintenance window for the upgrade and ensure certificate services are tested post-upgrade.

Recommended fix High confidence

Upgrade to the earliest fixed release for your version branch (19.1R3-S9, 19.2R3-S6, 19.3R3-S7, or later)

  1. 1. Identify the current Junos OS version on the SRX Series device using 'show version'
  2. 2. Based on the current version, determine the minimum fixed release from: 19.1R3-S9, 19.2R3-S6, 19.3R3-S7, 19.4R3-S9, 20.2R3-S5, 20.3R3-S4, 20.4R3-S4, 21.1R3-S1, 21.2R3, 21.3R2, or 21.4R2
  3. 3. Download the appropriate Junos OS upgrade package from the Juniper Networks support portal
  4. 4. Transfer the upgrade package to the SRX device using FTP/SCP
  5. 5. Install the upgrade using 'request system software add <package-name>'
  6. 6. Reboot the device using 'request system reboot'
  7. 7. After reboot, verify the pkid process is running using 'show system processes | match pkid'
  8. 8. Confirm the new version is installed using 'show version'
Caveat Review Junos OS upgrade documentation for your hardware model; ensure configuration compatibility before upgrading

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

Fix this in Junos Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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