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.

328,409

Total vulnerabilities in the database

Vulnerabilities for products matching "ar200_firmware"

Found 1 matching product.

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

huawei / ar200_firmware

43 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2019-19415	High	July 8, 2020 7/8/20	== 200r006c10 == 200r007c00 == 200r007c01 == 200r008c20 == 200r008c30
CVE-2019-19416	High	July 8, 2020 7/8/20	== 200r006c10 == 200r007c00 == 200r007c01 == 200r008c20 == 200r008c30
CVE-2019-19417	High	July 8, 2020 7/8/20	== 200r006c10 == 200r007c00 == 200r007c01 == 200r008c20 == 200r008c30
CVE-2020-9071	Medium	June 1, 2020 6/1/20	== 200r007c00spc900 == 200r007c00spc900pwe == 200r007c00spcb00 == 200r007c00spcb00pwe == 200r007c00spcc00
CVE-2019-5304	High	January 3, 2020 1/3/20	== 200r003c01 == 200r005c20 == 200r006c10 == 200r007c00 == 200r008c20 == 200r008c50
CVE-2019-5259	Medium	December 16, 2019 12/16/19	== 200r005c20 == 200r005c32 == 200r006c10 == 200r007c00 == 200r008c50 == 200r009c00
CVE-2019-5291	Medium	December 13, 2019 12/13/19	== 200r005c20 == 200r006c10 == 200r007c00 == 200r008c50
CVE-2019-5293	Medium	November 13, 2019 11/13/19	== 200r005c20 == 200r006c10
CVE-2019-5294	High	November 13, 2019 11/13/19	== 200r005c20 == 200r006c10 == 200r007c00
CVE-2019-5300	Low	June 4, 2019 6/4/19	== 200r007c00 == 200r008c20 == 200r008c50 == 200r009c00 == 200r010c00
CVE-2017-17251	Medium	April 24, 2018 4/24/18	== 200r006c10 == 200r007c00 == 200r007c01 == 200r008c20 == 200r008c30
CVE-2017-17252	Medium	April 24, 2018 4/24/18	== 200r006c10 == 200r007c00 == 200r007c01 == 200r008c20 == 200r008c30
CVE-2017-17253	Medium	April 24, 2018 4/24/18	== 200r006c10 == 200r007c00 == 200r007c01 == 200r008c20 == 200r008c30
CVE-2017-17254	Medium	April 24, 2018 4/24/18	== 200r006c10 == 200r007c00 == 200r007c01 == 200r008c20 == 200r008c30
CVE-2017-17255	Medium	April 24, 2018 4/24/18	== 200r006c10 == 200r007c00 == 200r007c01 == 200r008c20 == 200r008c30
CVE-2017-17256	Medium	April 24, 2018 4/24/18	== 200r006c10 == 200r007c00 == 200r007c01 == 200r008c20 == 200r008c30
CVE-2017-17257	Medium	April 24, 2018 4/24/18	== 200r006c10 == 200r007c00 == 200r007c01 == 200r008c20 == 200r008c30
CVE-2017-17258	Medium	April 24, 2018 4/24/18	== 200r006c10 == 200r007c00 == 200r007c01 == 200r008c20 == 200r008c30
CVE-2018-7920	Medium	April 19, 2018 4/19/18	== 200r006c10spc300
CVE-2017-17250	High	March 9, 2018 3/9/18	== 200r005c32
CVE-2017-17291	Low	February 15, 2018 2/15/18	== 200r006c10 == 200r007c00 == 200r007c01 == 200r008c20 == 200r008c30
CVE-2017-17292	Low	February 15, 2018 2/15/18	== 200r006c10 == 200r007c00 == 200r007c01 == 200r008c20 == 200r008c30
CVE-2017-17293	Low	February 15, 2018 2/15/18	== 200r006c10 == 200r007c00 == 200r007c01 == 200r008c20 == 200r008c30
CVE-2017-17294	Low	February 15, 2018 2/15/18	== 200r006c10 == 200r007c00 == 200r007c01 == 200r008c20 == 200r008c30
CVE-2017-17295	Medium	February 15, 2018 2/15/18	== 200r006c10 == 200r007c00 == 200r007c01 == 200r008c20 == 200r008c30
CVE-2017-17296	Medium	February 15, 2018 2/15/18	== 200r006c10 == 200r007c00 == 200r007c01 == 200r008c20 == 200r008c30
CVE-2017-17297	Medium	February 15, 2018 2/15/18	== 200r006c10 == 200r007c00 == 200r007c01 == 200r008c20 == 200r008c30
CVE-2017-17298	Medium	February 15, 2018 2/15/18	== 200r006c10 == 200r007c00 == 200r007c01 == 200r008c20 == 200r008c30
CVE-2017-17299	Medium	February 15, 2018 2/15/18	== 200r006c10 == 200r007c00
CVE-2017-17301	High	February 15, 2018 2/15/18	== 200r005c32 == 200r006c10 == 200r007c00 == 200r007c01 == 200r008c20
CVE-2017-17160	High	February 15, 2018 2/15/18	== 200r006c10 == 200r007c00
CVE-2017-17202	Medium	February 15, 2018 2/15/18	== 200r005c32 == 200r006c10 == 200r007c00 == 200r007c01 == 200r008c20 == 200r008c30
CVE-2017-17286	Medium	February 15, 2018 2/15/18	== 200r005c32 == 200r006c10 == 200r007c00 == 200r007c01 == 200r008c20 == 200r008c30
CVE-2017-17287	Medium	February 15, 2018 2/15/18	== 200r005c32 == 200r006c10 == 200r007c00 == 200r007c01 == 200r008c20 == 200r008c30
CVE-2017-17151	Low	February 15, 2018 2/15/18	== 200r006c10 == 200r006c10pwe == 200r006c10spc100 == 200r006c10spc300 == 200r006c10spc300pwe == 200r007c00 == 200r007c00pwe == 200r007c00spc100 == 200r007c00spc200 == 200r007c00spc600 == 200r007c00spc600pwe == 200r007c00spc900 == 200r007c00spc900pwe == 200r007c00spcb00 == 200r007c00spcb00pwe == 200r007c01 == 200r008c20 == 200r008c20spc600 == 200r008c20spc700 == 200r008c20spc800 == 200r008c20spc900 == 200r008c20spc900pwe == 200r008c30
CVE-2017-15331	Medium	February 15, 2018 2/15/18	== 200r006c10 == 200r007c00 == 200r007c01 == 200r008c20 == 200r008c30
CVE-2017-15332	Medium	February 15, 2018 2/15/18	== 200r006c10 == 200r007c00 == 200r007c01 == 200r008c20 == 200r008c30
CVE-2014-4705	High	January 30, 2018 1/30/18	== 200r003c00spc100 == 200r003c00spc200 == 200r003c01spc100 == 200r003c01spc300 == 200r003c01spc900 == 200r005c00spc100 == 200r005c00spc200
CVE-2017-15317	High	December 22, 2017 12/22/17	== 200r006c10 == 200r007c00 == 200r007c01 == 200r008c20 == 200r008c30
CVE-2017-8147	Medium	November 22, 2017 11/22/17	== 200r005c20spc026t
CVE-2017-8162	Low	November 22, 2017 11/22/17	== 200r006c10 == 200r007c00 == 200r007c01 == 200r008c20 == 200r008c30
CVE-2017-8163	Medium	November 22, 2017 11/22/17	== 200r006c10 == 200r007c00 == 200r007c01 == 200r008c20 == 200r008c30
CVE-2015-7846	Low	September 25, 2017 9/25/17	== 200r003c00spc100 == 200r003c00spc200 == 200r003c01spc100 == 200r003c01spc200 == 200r003c01spc300 == 200r003c01spc500 == 200r003c01spc600 == 200r003c01spc800 == 200r003c01spc900

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.