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.

365,542

Total vulnerabilities in the database

Vulnerabilities for products matching "junos"

Found 1 matching product.

You can search for specific versions with /product/junos/1.2.3

juniper / junos

63259 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2014-3821	Low	July 11, 2014 7/11/14	== 12.1x46 == 12.1x45 == 12.1x47 == 11.4 == 12.1x44
CVE-2014-3822	Medium	July 11, 2014 7/11/14	== 11.4 == 12.1 == 12.1x44 == 12.1x45 == 12.1x46 == 12.1x47
CVE-2014-0612	Medium	April 14, 2014 4/14/14	== 11.4 == 12.1 == 12.1x44 == 12.1x45 == 12.1x46
CVE-2014-0614	High	April 14, 2014 4/14/14	== 13.3 == 13.2
CVE-2014-2711	Low	April 14, 2014 4/14/14	== 13.3 == 13.1 == 13.2 == 12.1x46 == 12.1 == 12.1x45 == 11.4x27 == 11.4 == 12.3 == 12.2 == 12.1x44
CVE-2014-2712	Low	April 14, 2014 4/14/14	== 10.4 == 12.1x46 == 12.1 == 12.1x45 == 11.4 == 12.2 == 12.1x44 == 10.0
CVE-2014-2713	Medium	April 14, 2014 4/14/14	== 13.3 == 13.1 == 13.2 == 12.1 == 11.4 == 12.3 == 12.2
CVE-2014-2714	High	April 14, 2014 4/14/14	== 10.4 == 12.1x46 == 12.1 == 12.1x45 == 11.4 == 12.1x44
CVE-2013-7313	Medium	January 23, 2014 1/23/14	== 5.5 == 7.1 == 8.0 == 13.3 == 11.0 == 5.0 == 8.2 == 9.4 == 9.6 == 7.6 == 4.2 == 7.3 == 4.4 == 5.2 == 6.1 == 10.4 == 5.0r4 == 10.3 == 7.4 == 4.3 == 11.2 == 4.1 == 13.1 == 8.1 == 10.2 == 10.1 == 10.4s == 13.2 == 11.1 == 6.4 == 8.3 == 12.1x46 == 12.1 == 5.7 == 11.3 == 9.5 == 12.1x45 == 11.4x27 == 10.4r == 11.4 == 9.0 == 6.0 == 5.0r3 == 5.3 == 12.3 == 8.4 == 12.2 == 5.4 == 7.2 == 12.1r == 12.1x44 == 5.6 == 7.5 == 9.2 == 9.1 == 5.1 == 6.3 == 4.0 == 7.0 == 10.0 == 6.2
CVE-2014-0613	High	January 15, 2014 1/15/14	== 13.3 == 10.4 == 13.1 == 13.2 == 12.1x46 == 12.1x45 == 11.4 == 12.3 == 12.2 == 12.1r == 12.1x44
CVE-2014-0615	High	January 15, 2014 1/15/14	== 13.3 == 10.4 == 13.1 == 13.2 == 12.1x46 == 12.1x45 == 11.4 == 12.3 == 12.2 == 12.1r == 12.1x44
CVE-2014-0616	High	January 15, 2014 1/15/14	== 13.3 == 10.4 == 13.1 == 13.2 == 12.1x46 == 12.1x45 == 11.4 == 12.3 == 12.2 == 12.1r == 12.1x44
CVE-2014-0617	High	January 15, 2014 1/15/14	== 10.4r == 10.4s == 11.4 == 12.1r
CVE-2014-0618	High	January 11, 2014 1/11/14	== 10.4 == 11.4 == 12.1r == 12.1x44 == 12.1x45
CVE-2013-6618	High	November 5, 2013 11/5/13	== 10.3 == 10.2 == 10.1 == 12.1 <= 10.4 == 11.4 == 12.3 == 12.2 == 10.0
CVE-2013-6012	High	October 28, 2013 10/28/13	== 12.1x45 == 12.1x44
CVE-2013-6014	Critical	October 28, 2013 10/28/13	== 10.4 == 13.1 == 13.2 == 12.1 == 12.1x45 == 11.4x27 == 11.4 == 12.3 == 12.2 == 12.1x44
CVE-2013-4689	Medium	October 17, 2013 10/17/13	== 5.5 == 7.1 == 8.0 == 5.0 == 8.2 == 9.4 == 9.6 == 7.6 == 4.2 == 7.3 == 4.4 == 5.2 == 6.1 == 7.4 == 4.3 == 4.1 == 13.1 == 8.1 == 6.4 == 8.3 == 12.1 == 5.7 == 9.5 == 12.1x45 <= 10.4 == 11.4 == 9.0 == 6.0 == 5.3 == 12.3 == 8.4 == 12.2 == 5.4 == 7.2 == 12.1x44 == 5.6 == 7.5 == 9.2 == 9.1 == 5.1 == 6.3 == 4.0 == 7.0 == 6.2
CVE-2013-6013	Medium	October 17, 2013 10/17/13	<= 10.4 == 4.0 == 4.1 == 4.2 == 4.3 == 4.4 == 5.0 == 5.1 == 5.2 == 5.3 == 5.4 == 5.5 == 5.6 == 5.7 == 6.0 == 6.1 == 6.2 == 6.3 == 6.4 == 7.0 == 7.1 == 7.2 == 7.3 == 7.4 == 7.5 == 7.6 == 8.0 == 8.1 == 8.2 == 8.3 == 8.4 == 9.0 == 9.1 == 9.2 == 9.4 == 9.5 == 9.6 == 11.4 == 12.1x44 == 12.1x45
CVE-2013-6015	Low	October 17, 2013 10/17/13	<= 10.4 == 4.0 == 4.1 == 4.2 == 4.3 == 4.4 == 5.0 == 5.1 == 5.2 == 5.3 == 5.4 == 5.5 == 5.6 == 5.7 == 6.0 == 6.1 == 6.2 == 6.3 == 6.4 == 7.0 == 7.1 == 7.2 == 7.3 == 7.4 == 7.5 == 7.6 == 8.0 == 8.1 == 8.2 == 8.3 == 8.4 == 9.0 == 9.1 == 9.2 == 9.4 == 9.5 == 9.6 == 11.4 == 12.1 == 12.1x44 == 12.1x45
CVE-2013-6170	Low	October 17, 2013 10/17/13	== 10.4 == 11.2 == 11.1 == 11.4 == 10.0
CVE-2013-4684	High	July 11, 2013 7/11/13	== 10.4 == 11.4 == 12.1 == 12.1x44
CVE-2013-4685	High	July 11, 2013 7/11/13	== 10.4 == 11.4 == 12.1 == 12.1x44
CVE-2013-4686	High	July 11, 2013 7/11/13	== 10.4 == 12.1 == 11.4x27 == 11.4 == 12.3 == 12.2 == 12.1x44
CVE-2013-4687	High	July 11, 2013 7/11/13	== 10.4 == 11.2 == 11.4 == 12.1
CVE-2013-4688	High	July 11, 2013 7/11/13	== 10.4
CVE-2013-4690	Medium	July 11, 2013 7/11/13	== 10.4 == 11.4 == 12.1 == 12.1x44 == 12.1x45
CVE-2009-3485	Low	September 30, 2009 9/30/09	== 9.0-r1.1 == 8.5-r1.14
CVE-2009-3486	Low	September 30, 2009 9/30/09	== 8.5-r1.14
CVE-2009-3487	Low	September 30, 2009 9/30/09	== 8.5-r1.14
CVE-2007-6372	High	December 15, 2007 12/15/07	== 8.0 == 8.2 == 7.6 == 7.3 == 7.4 == 8.1 == 8.3 == 8.4 == 7.5
CVE-2006-3529	Medium	July 12, 2006 7/12/06	== 6.9 == 7.1 == 8.0 == 7.6 == 7.3 == 7.4 == 6.4 == 6.8 == 7.9 == 6.7 == 7.7 == 7.8 == 6.6 == 7.2 == 7.5 == 7.0 == 6.5
CVE-2004-0467	Medium	December 31, 2004 12/31/04	== 5.5 == 5.0 == 5.2 == 6.1 == 5.7 == 5.3 == 5.4 == 5.6 == 5.1 == 6.3 == 6.2
CVE-2004-0468	Medium	December 6, 2004 12/6/04	*
CVE-2004-0230	Medium	August 18, 2004 8/18/04	== 12.2-r6 == 12.1x44-d20 == 12.2-r4 == 12.3-r2 == 13.3-r1 == 11.4-r1 == 11.4-r6 == 11.4-r9 == 12.1x45-d20 == 12.2-r1 == 12.2-r3 == 12.2-r7 == 12.3-r1 == 12.3-r4 == 13.1-r1 == 13.1-r2 == 13.1-r3 == 13.2-r3 == 11.4-r10 == 11.4-r2 == 11.4-r3 == 11.4-r4 == 11.4-r5 == 11.4-r7 == 11.4-r8 == 11.4x27 == 12.1r == 12.1x44-d10 == 12.1x44-d15 == 12.1x44-d25 == 12.1x44-d30 == 12.1x44-d35 == 12.1x45-d10 == 12.1x45-d15 == 12.1x46-d10 == 12.1x46-d15 == 12.2-r2 == 12.2-r5 == 12.3-r3 == 12.3-r5 == 13.2-r1 == 13.2-r2 == 11.4 < 11.4 == 11.4r13-s2 == 12.1 == 12.1x44 == 12.1x45 == 12.1x46 == 12.1x47 == 12.2 == 12.3 == 13.1 == 13.2 == 13.3

‹
1
2
...
15
16
17
...
1265
1266
›

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.