How should we interpret CVSS severity scores?

CVSS estimates technical severity, but it does not automatically equal business risk. Prioritize using context like internet exposure, asset criticality, known exploitation, and whether compensating controls exist. A Medium CVSS on an exposed production system can be more urgent than a Critical on an isolated non-production host.

Vulnerability Database

Q: What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

Q: What's the difference between a vulnerability, an exploit, and a zero-day?

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. Risk increases sharply when exploitation becomes reliable or widespread.

Q: Why do vulnerabilities keep reappearing in our environment?

Recurring findings usually come from incomplete asset discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host.

Q: How do we prioritize remediation without burning out the team?

Use a repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress so remediation is steady, not reactive.

Q: How can SynScan help reduce vulnerability risk over time?

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.

346,508

Total vulnerabilities in the database

CVE-2020-1662 — juniper / junos

Improper Input Validation

On Juniper Networks Junos OS and Junos OS Evolved devices, BGP session flapping can lead to a routing process daemon (RPD) crash and restart, limiting the attack surface to configured BGP peers. This issue only affects devices with BGP damping in combination with accepted-prefix-limit configuration. When the issue occurs the following messages will appear in the /var/log/messages: rpd[6046]: %DAEMON-4-BGP_PREFIX_THRESH_EXCEEDED: XXXX (External AS x): Configured maximum accepted prefix-limit threshold(1800) exceeded for inet6-unicast nlri: 1984 (instance master) rpd[6046]: %DAEMON-3-BGP_CEASE_PREFIX_LIMIT_EXCEEDED: 2001:x:x:x::2 (External AS x): Shutting down peer due to exceeding configured maximum accepted prefix-limit(2000) for inet6-unicast nlri: 2001 (instance master) rpd[6046]: %DAEMON-4: bgp_rt_maxprefixes_check_common:9284: NOTIFICATION sent to 2001:x:x:x::2 (External AS x): code 6 (Cease) subcode 1 (Maximum Number of Prefixes Reached) AFI: 2 SAFI: 1 prefix limit 2000 kernel: %KERN-5: mastership_relinquish_on_process_exit: RPD crashed on master RE. Sending SIGUSR2 to chassisd (5612:chassisd) to trigger RE switchover This issue affects: Juniper Networks Junos OS: 17.2R3-S3; 17.3 version 17.3R3-S3 and later versions, prior to 17.3R3-S8; 17.4 version 17.4R2-S4, 17.4R3 and later versions, prior to 17.4R2-S10, 17.4R3-S2; 18.1 version 18.1R3-S6 and later versions, prior to 18.1R3-S10; 18.2 version 18.2R3 and later versions, prior to 18.2R3-S4; 18.2X75 version 18.2X75-D50, 18.2X75-D60 and later versions, prior to 18.2X75-D53, 18.2X75-D65; 18.3 version 18.3R2 and later versions, prior to 18.3R2-S4, 18.3R3-S2; 18.4 version 18.4R2 and later versions, prior to 18.4R2-S5, 18.4R3-S2; 19.1 version 19.1R1 and later versions, prior to 19.1R2-S2, 19.1R3-S1; 19.2 version 19.2R1 and later versions, prior to 19.2R1-S5, 19.2R2; 19.3 versions prior to 19.3R2-S3, 19.3R3; 19.4 versions prior to 19.4R1-S3, 19.4R2; 20.1 versions prior to 20.1R1-S2, 20.1R2. Juniper Networks Junos OS Evolved prior to 20.1R2-EVO. This issue does not affect Juniper Networks Junos OS versions prior to 17.2R3-S3.

Published: Oct 16, 2020
Updated: Nov 16, 2025
CVE: CVE-2020-1662
Severity: High
Exploit:

CVSS v3:

Severity: High
Score: 7.5
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CVSS v2:

Severity: Low
Score: 4.3
AV:N/AC:M/Au:N/C:N/I:N/A:P

CWEs:

CWE-20

Affected Software
References

Software	From	Fixed in
juniper / junos	18.3-r2	18.3-r2.x
juniper / junos	17.4-r3	17.4-r3.x
juniper / junos	17.3-r3-s3	17.3-r3-s3.x
juniper / junos	17.3-r3-s4	17.3-r3-s4.x
juniper / junos	17.4-r2-s4	17.4-r2-s4.x
juniper / junos	19.1-r1	19.1-r1.x
juniper / junos	17.4-r2-s5	17.4-r2-s5.x
juniper / junos	17.4-r2-s6	17.4-r2-s6.x
juniper / junos	17.4-r2-s7	17.4-r2-s7.x
juniper / junos	19.2-r1	19.2-r1.x
juniper / junos	18.4-r2	18.4-r2.x
juniper / junos	18.2-r3	18.2-r3.x
juniper / junos	18.1-r3-s6	18.1-r3-s6.x
juniper / junos	18.1-r3-s7	18.1-r3-s7.x
juniper / junos	19.1-r1-s1	19.1-r1-s1.x
juniper / junos	19.1-r1-s3	19.1-r1-s3.x
juniper / junos	19.1-r1-s2	19.1-r1-s2.x
juniper / junos	19.2-r1-s1	19.2-r1-s1.x
juniper / junos	19.2-r1-s2	19.2-r1-s2.x
juniper / junos	18.2-r3-s1	18.2-r3-s1.x
juniper / junos	18.3-r2-s1	18.3-r2-s1.x
juniper / junos	18.3-r2-s2	18.3-r2-s2.x
juniper / junos	17.4-r2-s8	17.4-r2-s8.x
juniper / junos	18.4-r2-s1	18.4-r2-s1.x
juniper / junos	19.3	19.3.x
juniper / junos	19.3-r1	19.3-r1.x
juniper / junos	18.4-r2-s2	18.4-r2-s2.x
juniper / junos	18.2-r3-s2	18.2-r3-s2.x
juniper / junos	18.1-r3-s8	18.1-r3-s8.x
juniper / junos	19.2-r1-s3	19.2-r1-s3.x
juniper / junos	18.3-r3	18.3-r3.x
juniper / junos	19.4-r1	19.4-r1.x
juniper / junos	19.3-r2	19.3-r2.x
juniper / junos	19.1-r2	19.1-r2.x
juniper / junos	18.4-r3	18.4-r3.x
juniper / junos	18.4-r2-s3	18.4-r2-s3.x
juniper / junos	18.3-r3-s1	18.3-r3-s1.x
juniper / junos	18.1-r3-s9	18.1-r3-s9.x
juniper / junos	17.3-r3-s7	17.3-r3-s7.x
juniper / junos	19.3-r2-s1	19.3-r2-s1.x
juniper / junos	19.3-r1-s1	19.3-r1-s1.x
juniper / junos	20.1-r1	20.1-r1.x
juniper / junos	19.4-r1-s1	19.4-r1-s1.x
juniper / junos	19.3-r2-s2	19.3-r2-s2.x
juniper / junos	19.1-r1-s4	19.1-r1-s4.x
juniper / junos	18.3-r2-s3	18.3-r2-s3.x
juniper / junos	18.2-r3-s3	18.2-r3-s3.x
juniper / junos	17.4-r3-s1	17.4-r3-s1.x
juniper / junos	17.4-r2-s9	17.4-r2-s9.x
juniper / junos	17.2-r3-s3	17.2-r3-s3.x
juniper / junos	18.2x75-d51	18.2x75-d51.x
juniper / junos	18.4-r3-s1	18.4-r3-s1.x
juniper / junos	18.4-r2-s4	18.4-r2-s4.x
juniper / junos	19.1-r2-s1	19.1-r2-s1.x
juniper / junos	19.1-r3	19.1-r3.x
juniper / junos	19.4-r1-s2	19.4-r1-s2.x
juniper / junos	20.1-r1-s1	20.1-r1-s1.x
juniper / junos	18.2x75-d60	18.2x75-d60.x
juniper / junos	18.2x75-d50	18.2x75-d50.x

https://kb.juniper.net/JSA11059

Deep Security Visibility Without the Complexity

SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.

No setup fees
5-min deployment
Cancel anytime

Book a Demo

Frequently Asked Questions

What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.