CVE-2022-22218
Last modified
CVE-2022-22218 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. 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. EPSS estimates a 0.41% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Juniper | Junos | < 19.1 |
| Juniper | Junos | 19.1 |
| Juniper | Junos | 19.2 |
| Juniper | Junos | 19.3 |
| Juniper | Junos | 19.4 |
| Juniper | Junos | 20.2 |
| Juniper | Junos | 20.3 |
| Juniper | Junos | 20.4 |
| Juniper | Junos | 21.1 |
| Juniper | Junos | 21.2 |
| Juniper | Junos | 21.3 |
| Juniper | Junos | 21.4 |
References
- https://kb.juniper.net/JSA69901Vendor Advisory
- https://kb.juniper.net/JSA69901Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-22218?
How severe is CVE-2022-22218?
How do I fix CVE-2022-22218?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-22212An Allocation of Resources Without Limits or Throttling vuln…7.5
- CVE-2022-22213A vulnerability in Handling of Undefined Values in the routi…5.9
- CVE-2022-22214An Improper Input Validation vulnerability in the Packet For…6.5
- CVE-2022-22215A Missing Release of File Descriptor or Handle after Effecti…5.5
- CVE-2022-22216An Exposure of Sensitive Information to an Unauthorized Acto…4.3
- CVE-2022-22217An Improper Check for Unusual or Exceptional Conditions vuln…6.5
- CVE-2022-22219Due to the Improper Handling of an Unexpected Data Type in t…5.9
- CVE-2022-2222The Download Monitor WordPress plugin before 4.5.91 does not…4.9
- CVE-2022-22220A Time-of-check Time-of-use (TOCTOU) Race Condition vulnerab…5.9
- CVE-2022-22221An Improper Neutralization of Special Elements vulnerability…7.8
- CVE-2022-22223On QFX10000 Series devices using Juniper Networks Junos OS w…7.5
- CVE-2022-22224An Improper Check or Handling of Exceptional Conditions vuln…6.5
Are you affected by CVE-2022-22218?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
