dbcve.org
JunosOperating system · Juniper

CVE-2024-30397

HIGH · 7.5 CVSS v3.1 Published 2024-04-12
Fix available
A fix is available. Upgrade to 20.4 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
An Improper Check for Unusual or Exceptional Conditions vulnerability in the the Public Key Infrastructure daemon (pkid) of Juniper Networks Junos OS allows an unauthenticated networked attacker to cause Denial of Service (DoS). The pkid is responsible for the certificate verification. Upon a failed verification, the pkid uses all CPU resources and becomes unresponsive to future verification attempts. This means that all subsequent VPN negotiations depending on certificate verification will fail. This CPU utilization of pkid can be checked using this command:   root@srx> show system processes extensive | match pkid   xxxxx  root  103  0  846M  136M  CPU1  1 569:00 100.00% pkid This issue affects: Juniper Networks Junos OS * All versions prior to 20.4R3-S10; * 21.2 versions prior to 21.2R3-S7; * 21.4 versions prior to 21.4R3-S5; * 22.1 versions prior to 22.1R3-S4; * 22.2 versions prior to 22.2R3-S3; * 22.3 versions prior to 22.3R3-S1; * 22.4 versions prior to 22.4R3; * 23.2 versions prior to 23.2R1-S2, 23.2R2.

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

A denial-of-service vulnerability exists in the pkid (Public Key Infrastructure daemon) of Juniper Networks Junos OS where an unauthenticated remote attacker can cause CPU exhaustion by sending a specially crafted certificate that triggers failed verification, rendering pkid unresponsive and causing all dependent VPN negotiations to fail.

MitigationApply the vendor-provided patches for Junos OS to the affected devices, as listed in the version-specific remediation table. Monitor pkid CPU utilization using the provided command and schedule maintenance windows for the 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:< 20.4= 20.4= 21.2= 21.4= 22.1= 22.2= 22.3= 22.4= 23.2

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 installed Junos OS version
    Execute the command 'show version' on the device CLI to retrieve the current Junos OS version
    Affected if The displayed version matches one of the affected ranges: < 20.4, 20.4, 21.2, 21.4, 22.1, 22.2, 22.3, 22.4, or 23.2
  2. Confirm pkid daemon is running
    Execute 'show system processes process pkid' or check via 'show system processes extensive | match pkid' to verify the pkid process is active
    Affected if The pkid process is running on the device (the vulnerability requires pkid to be active for the DoS to be exploitable)
  3. Monitor pkid CPU utilization
    Execute 'show system processes extensive | match pkid' repeatedly or use 'monitor start pkid*' to observe CPU usage of the pkid process over time
    Affected if CPU usage for pkid is abnormally high (near 100% sustained) indicating potential exploitation
  4. Check for VPN negotiation failures
    Review logs with 'show log messages | match VPN' or check 'show vpn ipsec status' to identify failed VPN negotiations
    Affected if Multiple VPN peers are failing to negotiate, especially if pkid CPU is elevated and the version is in the affected list

A device is affected if it runs a Junos OS version in the list (20.4, 21.2, 21.4, 22.1, 22.2, 22.3, 22.4, 23.2, or any version below 20.4) and has the pkid daemon enabled for certificate handling.

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 20.4 or later
Fixed in 20.4
Interim mitigation

Apply the vendor-provided patches for Junos OS to the affected devices, as listed in the version-specific remediation table. Monitor pkid CPU utilization using the provided command and schedule maintenance windows for the upgrade.

Recommended fix High confidence

Upgrade to 20.4R3-S10 / 21.2R3-S7 / 21.4R3-S5 / 22.1R3-S4 / 22.2R3-S3 / 22.3R3-S1 / 22.4R3 / 23.2R2 (depending on current version branch)

  1. 1. Identify the current Junos OS version by running 'show version'
  2. 2. Based on the current version line, upgrade to the minimum fixed release: 20.4R3-S10, 21.2R3-S7, 21.4R3-S5, 22.1R3-S4, 22.2R3-S3, 22.3R3-S1, 22.4R3, or 23.2R2 (or 23.2R1-S2)
  3. 3. Download the appropriate upgrade image from Juniper Networks support portal
  4. 4. Upload the upgrade image to the device using 'request system software add <path-to-image>'
  5. 5. Reboot the device after upgrade completes using 'request system reboot'
  6. 6. After reboot, verify pkid process is running normally using 'show system processes extensive | match pkid'
Caveat Standard Junos upgrade considerations apply - review release notes for compatibility, test in lab first, and plan maintenance window as upgrade requires reboot

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

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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