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 "389_directory_server"

Found 2 matching products. Filters apply to all results.

You can search for specific versions with /product/389_directory_server/1.2.3

redhat / 389_directory_server

5 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2024-1062	Medium	February 12, 2024 2/12/24	< 2.2.0
CVE-2022-1949	High	June 2, 2022 6/2/22	>= 1.3.0.0 <= 2.0.0
CVE-2022-0996	Medium	March 23, 2022 3/23/22	== 1.4.0.0
CVE-2020-35518	Medium	March 26, 2021 3/26/21	>= 2.0.0 < 2.0.3 >= 1.4.4.0 < 1.4.4.13 < 1.4.3.19
CVE-2018-10935	Medium	September 11, 2018 9/11/18	>= 1.3.0.0 < 1.3.8.7 >= 1.4.0.0 < 1.4.0.14

fedoraproject / 389_directory_server

37 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2010-3282	Low	January 9, 2020 1/9/20	< 1.2.7.1
CVE-2019-10224	Low	November 25, 2019 11/25/19	>= 1.4.0.0 < 1.4.1.3
CVE-2019-10171	High	August 2, 2019 8/2/19	>= 1.4.0.0 < 1.4.0.17
CVE-2019-3883	High	April 17, 2019 4/17/19	<= 1.4.1.2
CVE-2018-14648	High	September 28, 2018 9/28/18	< 1.4.0.17
CVE-2018-14638	Medium	September 14, 2018 9/14/18	< 1.3.8.4
CVE-2018-14624	Medium	September 6, 2018 9/6/18	>= 1.4.0.0 <= 1.4.0.16 >= 1.3.8.0 <= 1.3.8.8 <= 1.3.7.10
CVE-2018-10871	Low	July 18, 2018 7/18/18	>= 1.4.0.0 < 1.4.0.12 < 1.3.8.5
CVE-2017-2668	Low	June 22, 2018 6/22/18	>= 1.3.5.0 < 1.3.5.17 >= 1.3.6.0 < 1.3.6.10
CVE-2018-10850	High	June 13, 2018 6/13/18	< 1.4.0.10
CVE-2018-1089	Medium	May 9, 2018 5/9/18	== 1.3.8.1 >= 1.4.0.0 < 1.4.0.9 >= 1.3.6.0 < 1.3.6.15 == 1.3.8.2
CVE-2011-0704	Low	May 4, 2018 5/4/18	== 1.2.7.5
CVE-2017-2591	Medium	April 30, 2018 4/30/18	< 1.3.6
CVE-2018-1054	Medium	March 7, 2018 3/7/18	<= 1.4.0.6
CVE-2017-15134	Medium	March 1, 2018 3/1/18	>= 1.4.0.0 < 1.4.0.5 >= 1.3.7.1 < 1.3.7.9 >= 1.3.6.1 < 1.3.6.13
CVE-2017-15135	Low	January 24, 2018 1/24/18	>= 1.3.6.1 <= 1.4.0.3
CVE-2015-1854	Medium	September 19, 2017 9/19/17	<= 1.3.3.9
CVE-2017-7551	Medium	August 16, 2017 8/16/17	== 1.3.6.7 == 1.3.5.19
CVE-2016-0741	High	April 19, 2016 4/19/16	== 1.3.4.1 == 1.3.4.5 == 1.3.4.0 == 1.3.4.4
CVE-2015-3230	High	October 29, 2015 10/29/15	<= 1.3.3.10
CVE-2014-8112	Low	March 10, 2015 3/10/15	== 1.3.2.19 == 1.3.2.5 == 1.3.1.22 == 1.3.1.4 == 1.3.2.24 == 1.3.1.10 == 1.3.1.9 == 1.3.1.12 == 1.3.1.18 == 1.3.1.1 == 1.3.2.3 == 1.3.2.7 == 1.3.2.2 == 1.3.1.11 == 1.3.1.16 == 1.3.3.0 == 1.3.1.14 == 1.3.1.6 == 1.3.1.13 == 1.3.1.7 == 1.3.1.17 == 1.3.2.13 == 1.3.2.8 == 1.3.1.19 == 1.3.1.15 == 1.3.3.5 == 1.3.2.26 == 1.3.1.8 == 1.3.2.6 == 1.3.3.2 == 1.3.2.22 == 1.3.3.3 == 1.3.1.2 == 1.3.2.10 == 1.3.2.23 == 1.3.2.11 == 1.3.2.4 == 1.3.2.16 == 1.3.2.9 == 1.3.3.8 == 1.3.1.3 == 1.3.1.5 == 1.3.1.0
CVE-2014-8105	Medium	March 10, 2015 3/10/15	<= 1.3.2.26 == 1.3.3.0 == 1.3.3.5 == 1.3.3.2 == 1.3.3.3 == 1.3.3.8
CVE-2014-3562	Medium	August 21, 2014 8/21/14	== 1.3.0.3 == 1.2.5-rc4 == 1.2.3 == 1.2.11.9 == 1.3.0.7 == 1.2.5-rc1 == 1.3.0.5 == 1.2.8-rc2 == 1.2.11.23 == 1.2.8-rc1 == 1.2.9.9 == 1.2.11.8 == 1.2.8.3 == 1.2.6-rc3 == 1.2.6-a3 == 1.2.10 == 1.2.11.13 == 1.2.6-rc1 == 1.2.8.2 == 1.2.11.22 == 1.3.0.8 == 1.2.11.21 == 1.3.0.4 == 1.2.7.5 == 1.2.1 == 1.2.11.25 == 1.2.11.20 == 1.2.11.26 == 1.2.2 == 1.2.5 == 1.2.8-alpha2 == 1.2.6-rc6 == 1.2.11.17 == 1.3.0.2 == 1.2.10-rc1 == 1.2.11.19 == 1.2.11.12 == 1.2.8-alpha3 == 1.2.6.1 == 1.2.11.6 == 1.2.11.10 == 1.2.5-rc3 == 1.2.6-a4 == 1.2.11.11 == 1.2.10.3 == 1.2.11.1 == 1.2.11.5 == 1.2.10.4 == 1.2.5-rc2 == 1.2.10.11 == 1.2.10.2 == 1.2.8-alpha1 == 1.2.6-rc2 == 1.2.6-a2 == 1.2.6 == 1.2.6-rc7 == 1.2.11.14 == 1.3.0.6 == 1.2.8.1 == 1.2.10-alpha8 == 1.2.11.15 == 1.2.7-alpha3
CVE-2014-0132	Medium	March 18, 2014 3/18/14	== 1.2.11.9 == 1.2.11.23 == 1.2.11.8 == 1.2.11.13 <= 1.2.11.25 == 1.2.11.22 == 1.2.11.21 == 1.2.11.20 == 1.2.11.17 == 1.2.11.19 == 1.2.11.12 == 1.2.11.6 == 1.2.11.10 == 1.2.11.11 == 1.2.11.1 == 1.2.11.5 == 1.2.11.14 == 1.2.11.15
CVE-2013-4485	Low	November 23, 2013 11/23/13	== 1.2.11.15
CVE-2013-4283	Medium	September 10, 2013 9/10/13	== 1.3.0.3 == 1.3.0.5 == 1.3.0.4 <= 1.3.0.7 == 1.3.0.2 == 1.3.0.6
CVE-2013-1897	Low	May 13, 2013 5/13/13	== 1.2.5-rc4 == 1.2.3 == 1.2.11.9 == 1.2.5-rc1 == 1.2.8-rc2 == 1.2.8-rc1 == 1.2.9.9 == 1.2.11.8 == 1.2.8.3 == 1.2.6-rc3 == 1.2.6-a3 == 1.2.10 == 1.2.11.13 == 1.2.6-rc1 == 1.2.8.2 == 1.2.7.5 == 1.2.1 == 1.2.2 == 1.2.5 == 1.2.8-alpha2 == 1.2.6-rc6 == 1.2.11.17 == 1.2.10-rc1 == 1.2.11.19 == 1.2.11.12 == 1.2.8-alpha3 == 1.2.6.1 == 1.2.11.6 == 1.2.11.10 == 1.2.5-rc3 == 1.2.6-a4 == 1.2.11.11 == 1.2.10.3 == 1.2.11.1 == 1.2.11.5 == 1.2.10.4 == 1.2.5-rc2 == 1.2.10.11 == 1.2.10.2 == 1.2.8-alpha1 == 1.2.6-rc2 == 1.2.6-a2 == 1.2.6 == 1.2.6-rc7 == 1.2.11.14 == 1.2.8.1 == 1.2.10-alpha8 == 1.2.11.15 == 1.2.7-alpha3 == 1.3.0.3 == 1.3.0.4 == 1.3.0.2
CVE-2013-0312	Medium	March 13, 2013 3/13/13	<= 1.3.0.3
CVE-2012-4450	Medium	October 1, 2012 10/1/12	== 1.2.10
CVE-2012-2746	Low	July 3, 2012 7/3/12	== 1.2.5-rc4 == 1.2.3 == 1.2.5-rc1 == 1.2.8-rc2 == 1.2.8-rc1 == 1.2.9.9 == 1.2.8.3 == 1.2.6-rc3 == 1.2.6-a3 <= 1.2.11.5 == 1.2.6-rc1 == 1.2.8.2 == 1.2.7.5 == 1.2.1 == 1.2.2 == 1.2.5 == 1.2.8-alpha2 == 1.2.10.1 == 1.2.6-rc6 == 1.2.10-rc1 == 1.2.8-alpha3 == 1.2.6.1 == 1.2.5-rc3 == 1.2.6-a4 == 1.2.10.3 == 1.2.11.1 == 1.2.10.4 == 1.2.10.7 == 1.2.5-rc2 == 1.2.10.2 == 1.2.8-alpha1 == 1.2.6-rc2 == 1.2.6-a2 == 1.2.6 == 1.2.6-rc7 == 1.2.8.1 == 1.2.10-alpha8 == 1.2.7-alpha3
CVE-2012-2678	Low	July 3, 2012 7/3/12	== 1.2.5-rc4 == 1.2.3 == 1.2.5-rc1 == 1.2.8-rc2 == 1.2.8-rc1 == 1.2.9.9 == 1.2.8.3 == 1.2.6-rc3 == 1.2.6-a3 <= 1.2.11.5 == 1.2.6-rc1 == 1.2.8.2 == 1.2.7.5 == 1.2.1 == 1.2.2 == 1.2.5 == 1.2.8-alpha2 == 1.2.10.1 == 1.2.6-rc6 == 1.2.10-rc1 == 1.2.8-alpha3 == 1.2.6.1 == 1.2.5-rc3 == 1.2.6-a4 == 1.2.10.3 == 1.2.11.1 == 1.2.10.4 == 1.2.10.7 == 1.2.5-rc2 == 1.2.10.2 == 1.2.8-alpha1 == 1.2.6-rc2 == 1.2.6-a2 == 1.2.6 == 1.2.6-rc7 == 1.2.8.1 == 1.2.10-alpha8 == 1.2.7-alpha3
CVE-2012-0833	Low	July 3, 2012 7/3/12	== 1.2.5-rc4 == 1.2.3 <= 1.2.10 == 1.2.5-rc1 == 1.2.8-rc2 == 1.2.8-rc1 == 1.2.9.9 == 1.2.8.3 == 1.2.6-rc3 == 1.2.6-a3 == 1.2.6-rc1 == 1.2.8.2 == 1.2.7.5 == 1.2.1 == 1.2.2 == 1.2.5 == 1.2.8-alpha2 == 1.2.6-rc6 == 1.2.8-alpha3 == 1.2.6.1 == 1.2.5-rc3 == 1.2.6-a4 == 1.2.5-rc2 == 1.2.8-alpha1 == 1.2.6-rc2 == 1.2.6-a2 == 1.2.6 == 1.2.6-rc7 == 1.2.8.1 == 1.2.10-alpha8 == 1.2.7-alpha3
CVE-2011-1067	Medium	February 23, 2011 2/23/11	== 1.2.5-rc4 == 1.2.3 == 1.2.5-rc1 == 1.2.6-rc3 == 1.2.6-a3 == 1.2.6-rc1 <= 1.2.8 == 1.2.7.5 == 1.2.1 == 1.2.2 == 1.2.5 == 1.2.6-rc6 == 1.2.6.1 == 1.2.5-rc3 == 1.2.6-a4 == 1.2.5-rc2 == 1.2.6-rc2 == 1.2.6-a2 == 1.2.6 == 1.2.6-rc7 == 1.2.7-alpha3
CVE-2010-4746	Medium	February 23, 2011 2/23/11	== 1.2.5-rc4 == 1.2.3 == 1.2.5-rc1 == 1.2.6-rc3 == 1.2.6-a3 <= 1.2.7 == 1.2.6-rc1 == 1.2.1 == 1.2.2 == 1.2.5 == 1.2.6-rc6 == 1.2.6.1 == 1.2.5-rc3 == 1.2.6-a4 == 1.2.5-rc2 == 1.2.6-rc2 == 1.2.6-a2 == 1.2.6 == 1.2.6-rc7
CVE-2011-0019	High	February 23, 2011 2/23/11	== 1.2.7.5
CVE-2011-0022	Low	February 23, 2011 2/23/11	== 1.2.1 == 1.2.2 == 1.2.3 == 1.2.5 == 1.2.5-rc1 == 1.2.5-rc2 == 1.2.5-rc3 == 1.2.5-rc4 == 1.2.6 == 1.2.6-a2 == 1.2.6-a3 == 1.2.6-a4 == 1.2.6-rc1 == 1.2.6-rc2 == 1.2.6-rc3 == 1.2.6-rc6 == 1.2.6-rc7 == 1.2.6.1 == 1.2.7-alpha3 == 1.2.7.5 == 1.2.8-alpha1 == 1.2.8-alpha2
CVE-2011-0532	Medium	February 23, 2011 2/23/11	== 1.2.1 == 1.2.2 == 1.2.3 == 1.2.5 == 1.2.5-rc1 == 1.2.5-rc2 == 1.2.5-rc3 == 1.2.5-rc4 == 1.2.6 == 1.2.6-a2 == 1.2.6-a3 == 1.2.6-a4 == 1.2.6-rc1 == 1.2.6-rc2 == 1.2.6-rc3 == 1.2.6-rc6 == 1.2.6-rc7 == 1.2.6.1 == 1.2.7-alpha3 == 1.2.7.5 == 1.2.8-alpha1 == 1.2.8-alpha2

Showing vulnerabilities for 2 products matching "389_directory_server". 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.