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 "qts"

Found 1 matching product.

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

qnap / qts

272 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2023-23355	Medium	March 29, 2023 3/29/23	< 5.0.1.2346
CVE-2022-27596	Critical	January 30, 2023 1/30/23	>= 5.0.1 < 5.0.1.2234
CVE-2021-44051	High	May 5, 2022 5/5/22	>= 5.0.0.1716 < 5.0.0.1986 >= 4.4.0.0883 < 4.5.4.1991 >= 4.3.6.0895 < 4.3.6.1965 >= 4.3.4.0899 < 4.3.4.1976 >= 4.3.3.0174 < 4.3.3.1945 == 4.2.6-build_20170517 == 4.2.6-build_20190322 == 4.2.6-build_20190730 == 4.2.6-build_20190921 == 4.2.6-build_20191107 == 4.2.6-build_20200109 == 4.2.6-build_20200421 == 4.2.6-build_20200611 == 4.2.6-build_20200821 == 4.2.6-build_20210327 == 4.2.6-build_20211215
CVE-2021-44052	Medium	May 5, 2022 5/5/22	>= 5.0.0.1716 < 5.0.0.1986 >= 4.4.0.0883 < 4.5.4.1991 >= 4.3.6.0895 < 4.3.6.1965 >= 4.3.4.0899 < 4.3.4.1976 >= 4.3.3.0174 < 4.3.3.1945 == 4.2.6-build_20170517 == 4.2.6-build_20190322 == 4.2.6-build_20190730 == 4.2.6-build_20190921 == 4.2.6-build_20191107 == 4.2.6-build_20200109 == 4.2.6-build_20200421 == 4.2.6-build_20200611 == 4.2.6-build_20200821 == 4.2.6-build_20210327 == 4.2.6-build_20211215
CVE-2021-44053	Medium	May 5, 2022 5/5/22	>= 5.0.0.1716 < 5.0.0.1986 >= 4.4.0.0883 < 4.5.4.1991 >= 4.3.6.0895 < 4.3.6.1965 >= 4.3.4.0899 < 4.3.4.1976 >= 4.3.3.0174 < 4.3.3.1945 == 4.2.6-build_20170517 == 4.2.6-build_20190322 == 4.2.6-build_20190730 == 4.2.6-build_20190921 == 4.2.6-build_20191107 == 4.2.6-build_20200109 == 4.2.6-build_20200421 == 4.2.6-build_20200611 == 4.2.6-build_20200821 == 4.2.6-build_20210327 == 4.2.6-build_20211215
CVE-2021-44054	Low	May 5, 2022 5/5/22	>= 5.0.0.1716 < 5.0.0.1986 >= 4.4.0.0883 < 4.5.4.1991 >= 4.3.6.0895 < 4.3.6.1965 >= 4.3.4.0899 < 4.3.4.1976 >= 4.3.3.0174 < 4.3.3.1945 == 4.2.6-build_20170517 == 4.2.6-build_20190322 == 4.2.6-build_20190730 == 4.2.6-build_20190921 == 4.2.6-build_20191107 == 4.2.6-build_20200109 == 4.2.6-build_20200421 == 4.2.6-build_20200611 == 4.2.6-build_20200821 == 4.2.6-build_20210327 == 4.2.6-build_20211215
CVE-2021-38693	Medium	May 5, 2022 5/5/22	< 4.5.4.1991 >= 5.0.0.1716 < 5.0.0.1986
CVE-2021-38674	Low	January 7, 2022 1/7/22	< 4.5.4.1787
CVE-2021-34343	Medium	September 10, 2021 9/10/21	< 4.3.3.1693 >= 4.3.4 < 4.3.6.1750 >= 4.4.0 < 4.5.4.1715 >= 5.0.0 < 5.0.0.1716
CVE-2021-28816	High	September 10, 2021 9/10/21	< 4.3.3.1693 >= 4.3.4 < 4.3.6.1750 >= 4.4.0 < 4.5.4.1715 >= 5.0.0 < 5.0.0.1716
CVE-2018-19957	Medium	September 10, 2021 9/10/21	< 4.5.4.1715
CVE-2020-36194	Medium	July 1, 2021 7/1/21	< 4.5.2.1566
CVE-2021-28802	Critical	July 1, 2021 7/1/21	< 4.5.1.1540
CVE-2021-28804	Critical	July 1, 2021 7/1/21	<= 4.5.1.1540
CVE-2021-28800	High	June 24, 2021 6/24/21	>= 4.3.4 < 4.3.6.1663 < 4.3.3.1624
CVE-2021-28806	Medium	June 3, 2021 6/3/21	< 4.5.3.1652
CVE-2021-28798	High	May 21, 2021 5/21/21	>= 4.3.2.0144 < 4.3.3.1624 >= 4.3.4.0000 < 4.3.6.1663 >= 4.4.0000 < 4.5.2.1630
CVE-2020-2509	Critical	April 17, 2021 4/17/21	== 4.3.4.0387-beta2 == 4.3.4.0370-beta1 == 4.3.4.0372-beta1 == 4.3.4.0374-beta1 == 4.3.4.0358-beta1 == 4.3.4.0604 == 4.3.4.0597 == 4.3.4.0593 == 4.3.4.0569 == 4.3.4.0561 == 4.3.4.0516 == 4.3.4.0526 == 4.3.4.0551 == 4.3.4.0557 == 4.3.6.1033 == 4.3.6.1013 == 4.3.6.0993 == 4.3.6.0979 == 4.3.6.0959 == 4.3.6.0944 == 4.3.6.0923 == 4.3.6.0907 == 4.3.6.0895 == 4.3.4.1029 == 4.3.4.0899 == 4.2.6 == 4.2.6-build_20170517 == 4.2.6-build_20190322 == 4.2.6-build_20190730 == 4.2.6-build_20190921 == 4.2.6-build_20191107 == 4.2.6-build_20200109 == 4.2.6-build_20200421 == 4.2.6-build_20200611 == 4.2.6-build_20200821 < 4.2.6 == 4.3.4.1368 == 4.3.4.1417 == 4.3.4.0358 == 4.3.4.0370 == 4.3.4.0372 == 4.3.4.0374 == 4.3.4.0387 == 4.3.4.0411 == 4.3.4.0416 == 4.3.4.0427 == 4.3.4.0434 == 4.3.4.0435 == 4.3.4.0451 == 4.3.4.0483 == 4.3.4.0486 == 4.3.4.0506 == 4.3.4.1082 == 4.3.4.1190 == 4.3.4.1282 == 4.5.2 == 4.5.1 >= 4.4.0 < 4.5.1 == 4.3.6.1286 == 4.3.6.1333 == 4.3.6.1411 >= 4.3.5 < 4.3.6 == 4.3.6 == 4.3.6.1070 == 4.3.6.1154 == 4.3.6.1218 == 4.3.6.1263 == 4.3.6.1446 == 4.5.1.1456 == 4.5.1.1461 == 4.5.1.1465 == 4.5.1.1480 == 4.3.4.1463 == 4.3.3.0174 == 4.3.3.0868 == 4.3.3.0998 == 4.3.3.1051 == 4.3.3.1098 == 4.3.3.1161 == 4.3.3.1252 == 4.3.3.1315 == 4.3.3.1386 == 4.3.3.1432
CVE-2020-36195	Critical	April 17, 2021 4/17/21	== 4.3.3.0229 == 4.3.3 == 4.3.3.0570 == 4.3.3.0546 == 4.3.3.0514 == 4.3.6.1033 == 4.3.6.1013 == 4.3.6.0993 == 4.3.6.0979 == 4.3.6.0959 == 4.3.6.0944 == 4.3.6.0923 == 4.3.6.0907 == 4.3.6.0895 == 4.3.3.0998 == 4.3.3.0868 == 4.3.3.1315 == 4.3.3.1386 == 4.3.3.0095 == 4.3.3.0096 == 4.3.3.0136 == 4.3.3.0154 == 4.3.3.0174 == 4.3.3.0188 == 4.3.3.0210 == 4.3.3.0238 == 4.3.3.0262 == 4.3.3.0299 == 4.3.3.0351 == 4.3.3.0353 == 4.3.3.0361 == 4.3.3.0369 == 4.3.3.0378 == 4.3.3.0396 == 4.3.3.0404 == 4.3.3.0416 == 4.3.3.0418 == 4.3.3.0448 == 4.3.3.1051 == 4.3.3.1098 == 4.3.3.1161 == 4.3.3.1252 == 4.3.6.1286 == 4.3.6.1333 == 4.3.6.1411 == 4.3.6 == 4.3.6.1070 == 4.3.6.1154 == 4.3.6.1218 == 4.3.6.1263 == 4.3.6.1446 == 4.3.3.1432 < 4.3.3 >= 4.3.4 < 4.3.6
CVE-2018-19942	Medium	April 16, 2021 4/16/21	== 4.3.3.0229 == 4.3.3 == 4.3.4 == 4.3.4.0387-beta2 == 4.3.4.0370-beta1 == 4.3.4.0372-beta1 == 4.3.4.0374-beta1 == 4.3.4.0358-beta1 == 4.3.4.0604 == 4.3.3.0570 == 4.3.4.0597 == 4.3.4.0593 == 4.3.3.0546 == 4.3.4.0569 == 4.3.4.0561 == 4.3.4.0516 == 4.3.3.0514 == 4.3.4.0526 == 4.3.4.0551 == 4.3.4.0557 == 4.3.6.1033 == 4.3.6.1013 == 4.3.6.0993 == 4.3.6.0979 == 4.3.6.0959 == 4.3.6.0944 == 4.3.6.0923 == 4.3.6.0907 == 4.3.6.0895 == 4.3.3.0998 == 4.3.3.0868 == 4.3.4.1029 == 4.3.4.0899 == 4.2.6 == 4.2.6-build_20170517 == 4.2.6-build_20190322 == 4.2.6-build_20190730 == 4.2.6-build_20190921 == 4.2.6-build_20191107 == 4.2.6-build_20200109 == 4.2.6-build_20200421 == 4.2.6-build_20200611 == 4.2.6-build_20200821 < 4.2.6 == 4.3.4.1368 == 4.3.4.1417 == 4.3.4.0358 == 4.3.4.0370 == 4.3.4.0372 == 4.3.4.0374 == 4.3.4.0387 == 4.3.4.0411 == 4.3.4.0416 == 4.3.4.0427 == 4.3.4.0434 == 4.3.4.0435 == 4.3.4.0451 == 4.3.4.0483 == 4.3.4.0486 == 4.3.4.0506 == 4.3.4.1082 == 4.3.4.1190 == 4.3.4.1282 == 4.3.3.1315 == 4.3.3.1386 == 4.3.3.0095 == 4.3.3.0096 == 4.3.3.0136 == 4.3.3.0154 == 4.3.3.0174 == 4.3.3.0188 == 4.3.3.0210 == 4.3.3.0238 == 4.3.3.0262 == 4.3.3.0299 == 4.3.3.0351 == 4.3.3.0353 == 4.3.3.0361 == 4.3.3.0369 == 4.3.3.0378 == 4.3.3.0396 == 4.3.3.0404 == 4.3.3.0416 == 4.3.3.0418 == 4.3.3.0448 == 4.3.3.1051 == 4.3.3.1098 == 4.3.3.1161 == 4.3.3.1252 == 4.5.2 == 4.5.1 >= 4.4.0 < 4.5.1 == 4.3.6.1286 == 4.3.6.1333 == 4.3.6.1411 >= 4.3.5 < 4.3.6 == 4.3.6 == 4.3.6.1070 == 4.3.6.1154 == 4.3.6.1218 == 4.3.6.1263
CVE-2020-2508	High	January 11, 2021 1/11/21	< 4.5.1.1456
CVE-2018-19941	High	December 31, 2020 12/31/20	< 4.5.1.1456
CVE-2018-19944	High	December 31, 2020 12/31/20	< 4.4.3.1354
CVE-2018-19945	Critical	December 31, 2020 12/31/20	>= 4.3.5 < 4.3.6.0895 >= 4.3.4 < 4.3.4.0899
CVE-2020-25847	High	December 29, 2020 12/29/20	< 4.5.1.1495
CVE-2020-2498	Medium	December 10, 2020 12/10/20	< 4.5.1.1456 < 4.4.3.1354 < 4.3.6.1333 < 4.3.4.1368 < 4.3.3.1315 < 4.2.6
CVE-2019-7198	Critical	December 10, 2020 12/10/20	< 4.4.3.1354 < 4.5.1.1456
CVE-2020-2495	Medium	December 10, 2020 12/10/20	< 4.5.1.1456 < 4.4.3.1354 < 4.3.6.1333 < 4.3.4.1368 < 4.3.3.1315 < 4.2.6
CVE-2020-2496	Medium	December 10, 2020 12/10/20	< 4.5.1.1456 < 4.4.3.1354 < 4.3.6.1333 < 4.3.4.1368 < 4.3.3.1315 < 4.2.6
CVE-2020-2497	Medium	December 10, 2020 12/10/20	< 4.5.1.1456 < 4.4.3.1354 < 4.3.6.1333 < 4.3.4.1368 < 4.3.3.1315 < 4.2.6
CVE-2020-2492	High	November 16, 2020 11/16/20	< 4.4.3.1421
CVE-2020-2490	High	November 16, 2020 11/16/20	< 4.4.3.1421
CVE-2018-19943	High	October 28, 2020 10/28/20	>= 4.4.2 < 4.4.2.1270 >= 4.4.0 < 4.4.1.1261 >= 4.3.6 < 4.3.6.1263 >= 4.3.4 < 4.3.4.1282 >= 4.3.1.0013 < 4.3.3.1252 == 4.2.6 == 4.2.6-build_20170517 == 4.2.6-build_20190322 == 4.2.6-build_20190730 == 4.2.6-build_20190921 == 4.2.6-build_20191107 == 4.2.6-build_20200109 == 4.2.6-build_20200421 == 4.2.6-build_20200611 == 4.2.6-build_20200821 < 4.2.6
CVE-2018-19949	Critical	October 28, 2020 10/28/20	== 4.2.6 == 4.2.6-build_20170517 == 4.2.6-build_20190322 == 4.2.6-build_20190730 == 4.2.6-build_20190921 == 4.2.6-build_20191107 < 4.2.6 >= 4.3.1.0013 < 4.3.3.1161 >= 4.3.4 < 4.3.4.1190 >= 4.3.6 < 4.3.6.1218 >= 4.4.0 < 4.4.1.1201 >= 4.4.2 < 4.4.2.1231
CVE-2018-19953	Medium	October 28, 2020 10/28/20	== 4.2.6 == 4.2.6-build_20170517 == 4.2.6-build_20190322 == 4.2.6-build_20190730 == 4.2.6-build_20190921 == 4.2.6-build_20191107 < 4.2.6 >= 4.3.1.0013 < 4.3.3.1161 >= 4.3.4 < 4.3.4.1190 >= 4.3.6 < 4.3.6.1218 >= 4.4.0 < 4.4.1.1201 >= 4.4.2 < 4.4.2.1231
CVE-2019-7193	Critical	December 5, 2019 12/5/19	== 4.4.1.1033-beta_4 == 4.4.1.1031-beta_4 == 4.4.1.0999-beta_3 == 4.4.1.0998-beta_3 == 4.4.1.0978-beta_2 == 4.4.1.0949-beta == 4.4.1.0948-beta == 4.3.6.1033 == 4.3.6.1013 == 4.3.6.0993 == 4.3.6.0979 == 4.3.6.0959 == 4.3.6.0944 == 4.3.6.0923 == 4.3.6.0907 == 4.3.6.0895
CVE-2019-7183	Critical	December 5, 2019 12/5/19	== 4.2.6 == 4.4.1.1033-beta_4 == 4.4.1.1031-beta_4 == 4.4.1.0999-beta_3 == 4.4.1.0998-beta_3 == 4.4.1.0978-beta_2 == 4.4.1.0949-beta == 4.4.1.0948-beta == 4.3.6.1033 == 4.3.6.1013 == 4.3.6.0993 == 4.3.6.0979 == 4.3.6.0959 == 4.3.6.0944 == 4.3.6.0923 == 4.3.6.0907 == 4.3.6.0895 == 4.3.3.0998 == 4.3.3.0868 == 4.3.4.1029 == 4.3.4.0899 == 4.4.1.1101 == 4.4.1.1086 == 4.4.1.1081 == 4.4.1.1064
CVE-2019-7197	Low	December 4, 2019 12/4/19	== 4.3.3 == 4.3.4 == 4.2.6 == 4.3.6 == 4.4.1
CVE-2018-0730	Critical	December 4, 2019 12/4/19	== 4.2.6 == 4.4.1.1033-beta_4 == 4.4.1.1031-beta_4 == 4.4.1.0999-beta_3 == 4.4.1.0998-beta_3 == 4.4.1.0978-beta_2 == 4.4.1.0949-beta == 4.4.1.0948-beta == 4.3.6.1033 == 4.3.6.1013 == 4.3.6.0993 == 4.3.6.0979 == 4.3.6.0959 == 4.3.6.0944 == 4.3.6.0923 == 4.3.6.0907 == 4.3.6.0895 == 4.3.3.0998 == 4.3.3.0868 == 4.3.4.1029 == 4.3.4.0899 == 4.4.1.1101 == 4.4.1.1086 == 4.4.1.1081 == 4.4.1.1064
CVE-2018-0716	Low	November 30, 2018 11/30/18	== 4.3.3 == 4.3.4 == 4.2.6 == 4.3.5
CVE-2018-14746	High	November 28, 2018 11/28/18	== 4.3.3 == 4.3.4 == 4.2.6 == 4.3.5
CVE-2018-14747	Medium	November 28, 2018 11/28/18	== 4.3.3 == 4.3.4 == 4.2.6 == 4.3.5
CVE-2018-14748	High	November 28, 2018 11/28/18	== 4.3.3 == 4.3.4 == 4.2.6 == 4.3.5
CVE-2018-14749	High	November 28, 2018 11/28/18	== 4.3.3 == 4.3.4 == 4.2.6 == 4.3.5
CVE-2018-0721	High	November 27, 2018 11/27/18	== 4.3.3 == 4.3.4 == 4.2.6
CVE-2018-0719	Medium	November 27, 2018 11/27/18	== 4.3.3 == 4.3.4 == 4.2.6
CVE-2017-13072	Low	June 21, 2018 6/21/18	== 4.3.3 == 4.3.4 == 4.2.6
CVE-2018-0712	High	June 21, 2018 6/21/18	== 4.3.3 == 4.2.6 <= 4.3.4
CVE-2018-0711	Low	April 30, 2018 4/30/18	== 4.3.4.0604 == 4.3.3.0570 == 4.3.4.0597 == 4.3.4.0593 == 4.3.3.0546 == 4.3.4.0569 == 4.3.4.0561 == 4.3.4.0516 == 4.3.3.0514 == 4.3.4.0526 == 4.3.4.0551 == 4.3.4.0557
CVE-2017-7630	Medium	March 27, 2018 3/27/18	== 4.3.3 == 4.2.6

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.