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.

326,690

Total vulnerabilities in the database

Vulnerabilities for products matching "docker"

Found 4 matching products. Filters apply to all results.

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

docker / docker

37 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2022-25365	High	February 19, 2022 2/19/22	< 4.5.1
CVE-2021-21285	Medium	February 2, 2021 2/2/21	>= 20.0.0 < 20.10.3 < 19.03.15
CVE-2021-21284	Medium	February 2, 2021 2/2/21	>= 20.0.0 < 20.10.3 < 19.03.15
CVE-2021-3162	High	January 15, 2021 1/15/21	< 2.5.0.0
CVE-2020-27534	Medium	December 30, 2020 12/30/20	< 19.03.9
CVE-2020-14300	High	July 13, 2020 7/13/20	== 1.13.1
CVE-2020-14298	High	July 13, 2020 7/13/20	== 1.13.1
CVE-2014-5278	Medium	February 7, 2020 2/7/20	< 1.2.0
CVE-2014-0048	Critical	January 2, 2020 1/2/20	< 1.5.0
CVE-2014-8179	High	December 17, 2019 12/17/19	< 1.8.3
CVE-2014-8178	Medium	December 17, 2019 12/17/19	< 1.8.3
CVE-2014-9356	High	December 2, 2019 12/2/19	< 1.3.3
CVE-2019-16884	High	September 25, 2019 9/25/19	<= 19.03.2
CVE-2019-15752	High	August 28, 2019 8/28/19	< 2.1.0.1
CVE-2019-13139	Low	August 22, 2019 8/22/19	< 18.09.4
CVE-2019-14271	Critical	July 29, 2019 7/29/19	>= 19.03 < 19.03.1
CVE-2019-13509	Medium	July 18, 2019 7/18/19	== 17.03.2-8 == 17.03.2-7 == 17.06.2-1 == 17.06.2-2 == 17.06.2-3 == 17.06.2-4 == 17.06.2-5 == 17.06.2-6 == 17.06.2-7 == 17.06.2-8 == 17.06.2-9 == 17.06.2-10 == 17.06.2-11 == 17.06.2-12 == 17.06.2-13 == 17.06.2-15 == 17.06.2-16 == 17.06.2-17 == 17.06.2-18 == 17.06.2-19 == 17.06.2-20 == 17.06.2-21 == 17.06.2-22 == 18.03.1-1 == 18.03.1-2 == 18.03.1-3 == 18.03.1-4 == 18.03.1-5 == 18.03.1-6 == 18.03.1-7 == 18.03.1-8 == 18.03.1-9 >= 18.09.0 < 18.09.8 == 17.03.2-6 == 17.03.2-5 == 17.03.2-4 == 17.03.2-3 == 17.03.2-2 == 17.03.2-1 < 18.09.8
CVE-2018-15664	Medium	May 23, 2019 5/23/19	== 17.06.0-ce-rc1 == 17.06.0-ce-rc2 == 17.06.0-ce-rc3 == 17.06.0-ce-rc4 == 17.06.0-ce-rc5 == 17.06.0-ce == 17.06.1-ce == 17.06.1-ce-rc1 == 17.06.1-ce-rc2 == 17.06.1-ce-rc3 == 17.06.1-ce-rc4 == 17.06.2-ce-rc1 == 17.06.2-ce == 17.07.0-ce-rc1 == 17.07.0-ce-rc2 == 17.07.0-ce-rc3 == 17.07.0-ce-rc4 == 17.07.0-ce == 17.09.0-ce-rc1 == 17.09.0-ce-rc2 == 17.09.0-ce-rc3 == 17.09.0-ce == 17.09.1-ce--rc1 == 17.09.1-ce == 17.10.0-ce-rc1 == 17.10.0-ce-rc2 == 17.10.0-ce == 17.11.0-ce-rc1 == 17.11.0-ce-rc2 == 17.11.0-ce-rc3 == 17.11.0-ce-rc4 == 17.11.0-ce == 17.12.0-ce-rc1 == 17.12.0-ce-rc2 == 17.12.0-ce-rc3 == 17.12.0-ce-rc4 == 17.12.0-ce == 17.12.1-ce-rc1 == 17.12.1-ce-rc2 == 17.12.1-ce == 18.01.0-ce-rc1 == 18.01.0-ce == 18.02.0-ce-rc1 == 18.02.0-ce-rc2 == 18.02.0-ce == 18.03.0-ce-rc1 == 18.03.0-ce-rc2 == 18.03.0-ce-rc3 == 18.03.0-ce-rc4 == 18.03.0-ce == 18.03.1-ce-rc1 == 18.03.1-ce-rc2 == 18.03.1-ce == 18.04.0-ce-rc1 == 18.04.0-ce-rc2 == 18.04.0-ce == 18.05.0-ce-rc1 == 18.05.0-ce == 18.06.0-ce-rc1 == 18.06.0-ce-rc2 == 18.06.0-ce-rc3 == 18.06.0-ce == 18.06.1-ce-rc1 == 18.06.1-ce-rc2
CVE-2019-5736	High	February 11, 2019 2/11/19	< 18.09.2
CVE-2018-15514	Medium	September 1, 2018 9/1/18	== 18.03.0-win59 == 17.12.0-win47 == 17.12.0-win46 == 17.09.1-win42 == 17.09.0-win33 == 17.09.0-win32 == 17.06.2-win27 == 17.06.1-rc1-win24 == 17.06.0-win18 == 17.03.1-win12 == 17.03.0 == 18.03.1-win65 == 18.05.0-win66 == 18.05.0-rc1-win63 == 18.04.0-rc2-win61 == 18.03.0-win58 == 18.03.0-rc3-win56 == 18.02.0-win52 == 18.02.0-rc2-win51 == 18.02.0-rc1-win50 == 18.01.0-win48 == 17.12.0-win45 == 17.12.0-rc4-win44 == 17.12.0-rc3-win43 == 17.12.0-rc2-win41 == 17.11.0-win40 == 17.11.0-rc4-win39 == 17.11.0-rc3-win38 == 17.11.0-rc2-win37 == 17.10.0-win36 == 17.09.0-win34 == 17.09.0-win31 == 17.09.0-rc3-win30 == 17.09.0-rc2-win29 == 17.09.0-rc1-win28 == 17.07.0-win26 == 17.07.0-rc4-win25 == 17.07.0-rc3-win23 == 17.07.0-rc2-win22 == 17.07.0-rc1-win21 == 17.06.1-rc1-win20 == 17.06.0-win17 == 17.06.0-win16 == 17.06.0-win15 == 17.06.0-win14 == 17.06.0-win13 == 17.0.5-win9 == 17.0.4-win7 == 17.04.0-win6 == 17.03.0-rc1-win1 == 1.13.1 == 1.13.0 == 1.12.5 == 1.12.3 == 1.12.1 == 1.12.0 == 1.13.1-rc2-beta41 == 1.13.1-rc1-beta40 == 1.13.0-beta39 == 1.13.0-beta38 == 1.13.0-rc7-beta37 == 1.13.0-rc6-beta36 == 1.13.0-rc5-beta35 == 1.13.0-rc4-beta34 == 1.13.0-rc3-beta33 == 1.13.0-rc3-beta32.1 == 1.13.0-rc3-beta32 == 1.13.0-rc2-beta31 == 1.12.3-beta30 == 1.12.3-beta29.3 == 1.12.2-beta29.2 == 1.12.1-beta29.1 == 1.12.3-rc1-beta29 == 1.12.2-rc3-beta28 == 1.12.2-rc1-beta27 == 1.12.1-beta26 == 1.12.1-beta25 == 1.12.1-beta24 == 1.12.1-rc1-beta23 == 1.12.0-beta22 == 1.12.0-beta21 == 1.12.0-rc4-beta20 == 1.12.0-rc4-beta19 == 1.12.0-rc3-beta18.1 == 1.12.0-rc3-beta18 == 1.12.0-rc2-beta17 == 1.12.0-rc2-beta16 == 1.11.2-beta15 == 1.11.1-beta14 == 1.11.1-beta13 == 1.11.1-beta12 == 1.11.1-beta11b == 1.11.1-beta11 == 1.11.0-beta10 == 1.11.0-beta9 == 1.11.0-beta8 == 1.11.0-beta7 == 1.11.0 == 1.10.6 == 1.10.4.0 == 1.10.2.14 == 1.10.2.12 == 1.10.1.42-1 == 1.10.0.0-0
CVE-2018-10892	Medium	July 6, 2018 7/6/18	>= 1.11 <= 18.03.1
CVE-2014-5282	Medium	February 6, 2018 2/6/18	< 1.3
CVE-2017-14992	Low	November 1, 2017 11/1/17	<= 1.10.3 == 1.12.6-0 == 17.03.0 == 17.03.1 == 17.03.2 == 17.06.0 == 17.06.1 == 17.06.2 == 17.09.0
CVE-2014-0047	Low	October 6, 2017 10/6/17	<= 1.4.1
CVE-2016-9962	Low	January 31, 2017 1/31/17	>= 1.11.0 < 1.12.6
CVE-2016-6595	Low	January 4, 2017 1/4/17	== 1.12.0
CVE-2016-8867	Medium	October 28, 2016 10/28/16	== 1.12.2
CVE-2016-3697	High	June 1, 2016 6/1/16	<= 1.11.1
CVE-2015-3631	Low	May 18, 2015 5/18/15	<= 1.6
CVE-2015-3630	High	May 18, 2015 5/18/15	<= 1.6
CVE-2015-3627	High	May 18, 2015 5/18/15	<= 1.6
CVE-2014-9358	Medium	December 16, 2014 12/16/14	<= 1.3.2
CVE-2014-9357	High	December 16, 2014 12/16/14	== 1.3.2
CVE-2014-6408	Medium	December 12, 2014 12/12/14	== 1.3.0 == 1.3.1
CVE-2014-6407	High	December 12, 2014 12/12/14	== 1.3.0 <= 1.3.1 == 1.0.0
CVE-2014-5277	Medium	November 17, 2014 11/17/14	<= 1.3.0
CVE-2014-3499	High	July 11, 2014 7/11/14	== 1.0.0

redhat / docker

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2015-1843	Low		April 6, 2015 4/6/15	<= 1.5.0-27

jenkins / docker

3 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2019-10340	High	July 11, 2019 7/11/19	<= 1.1.6
CVE-2019-10341	Medium	July 11, 2019 7/11/19	<= 1.1.6
CVE-2019-10342	Low	July 11, 2019 7/11/19	<= 1.1.6

synology / docker

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2021-33183	High		June 1, 2021 6/1/21	< 18.09.0-0515

Showing vulnerabilities for 4 products matching "docker". Each product has independent pagination.

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.