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.

383,211

Total vulnerabilities in the database

Vulnerabilities for products matching "informix_dynamic_server"

Found 1 matching product.

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

ibm / informix_dynamic_server

53 vulnerabilities found

Title	Severity	Date	Affected versions
CVE-2026-13367	High	August 12, 2026 8/12/26	`= 14.10` `= 15.0`
CVE-2026-13476	High	August 12, 2026 8/12/26	`>= 15.0, < 15.0.1.13` `= 12.10` `= 14.10`
CVE-2026-13361	High	August 12, 2026 8/12/26	`>= 15.0, < 15.0.1.14` `= 12.10` `= 14.10`
CVE-2024-45675	High	December 2, 2025 12/2/25	`< 14.10`
CVE-2024-49343	Medium	July 28, 2025 7/28/25	`= 12.10` `= 14.10`
CVE-2024-49342	High	July 28, 2025 7/28/25	`= 12.10` `= 14.10`
CVE-2025-1991	High	June 28, 2025 6/28/25	`= 12.10` `= 14.10` `= 15.0`
CVE-2023-28527	Medium	December 9, 2023 12/9/23	`= 12.10` `= 14.10`
CVE-2023-28526	Medium	December 9, 2023 12/9/23	`= 12.10` `= 14.10`
CVE-2023-28523	High	December 9, 2023 12/9/23	`= 12.10` `= 14.10`
CVE-2021-20515	Medium	April 30, 2021 4/30/21	`= 14.10`
CVE-2020-4799	High	October 8, 2020 10/8/20	`= 14.10`
CVE-2019-4253	High	August 20, 2019 8/20/19	`= 12.10-fc1` `= 12.10-fc10` `= 12.10-fc11` `= 12.10-fc12` `= 12.10-fc2` `= 12.10-fc3` `= 12.10-fc4` `= 12.10-fc5` `= 12.10-fc6` `= 12.10-fc7` `= 12.10-fc8` `= 12.10-fc9`
CVE-2018-1632	High	August 20, 2019 8/20/19	`= 12.10-fc1` `= 12.10-fc10` `= 12.10-fc11` `= 12.10-fc12` `= 12.10-fc2` `= 12.10-fc3` `= 12.10-fc4` `= 12.10-fc5` `= 12.10-fc6` `= 12.10-fc7` `= 12.10-fc8` `= 12.10-fc9`
CVE-2018-1633	High	August 20, 2019 8/20/19	`= 12.10-fc1` `= 12.10-fc10` `= 12.10-fc11` `= 12.10-fc12` `= 12.10-fc2` `= 12.10-fc3` `= 12.10-fc4` `= 12.10-fc5` `= 12.10-fc6` `= 12.10-fc7` `= 12.10-fc8` `= 12.10-fc9`
CVE-2018-1634	High	August 20, 2019 8/20/19	`= 12.10-fc1` `= 12.10-fc10` `= 12.10-fc11` `= 12.10-fc12` `= 12.10-fc2` `= 12.10-fc3` `= 12.10-fc4` `= 12.10-fc5` `= 12.10-fc6` `= 12.10-fc7` `= 12.10-fc8` `= 12.10-fc9`
CVE-2018-1635	High	August 20, 2019 8/20/19	`= 12.10-fc1` `= 12.10-fc10` `= 12.10-fc11` `= 12.10-fc12` `= 12.10-fc2` `= 12.10-fc3` `= 12.10-fc4` `= 12.10-fc5` `= 12.10-fc6` `= 12.10-fc7` `= 12.10-fc8` `= 12.10-fc9`
CVE-2018-1636	High	August 20, 2019 8/20/19	`= 12.10-fc1` `= 12.10-fc10` `= 12.10-fc11` `= 12.10-fc12` `= 12.10-fc2` `= 12.10-fc3` `= 12.10-fc4` `= 12.10-fc5` `= 12.10-fc6` `= 12.10-fc7` `= 12.10-fc8` `= 12.10-fc9`
CVE-2018-1796	High	August 20, 2019 8/20/19	`= 12.10-fc1` `= 12.10-fc10` `= 12.10-fc11` `= 12.10-fc12` `= 12.10-fc2` `= 12.10-fc3` `= 12.10-fc4` `= 12.10-fc5` `= 12.10-fc6` `= 12.10-fc7` `= 12.10-fc8` `= 12.10-fc9`
CVE-2018-1630	High	August 20, 2019 8/20/19	`= 12.1`
CVE-2018-1631	High	August 20, 2019 8/20/19	`= 12.1`
CVE-2017-1508	Medium	September 13, 2017 9/13/17	`= 12.10`
CVE-2017-1310	Medium	June 29, 2017 6/29/17	`= 12.10`
CVE-2016-0226	Medium	March 28, 2016 3/28/16	`= 11.70.xcn`
CVE-2012-4857	High	December 8, 2012 12/8/12	`= 11.50` `= 11.50.xc1` `= 11.50.xc2` `= 11.50.xc3` `= 11.50.xc3w1` `= 11.50.xc4` `= 11.50.xc4w1` `= 11.50.xc5` `= 11.50.xc5w2` `= 11.50.xc5w3` `= 11.50.xc5w4` `= 11.50.xc6` `= 11.50.xc6w1` `= 11.50.xc6w2` `= 11.50.xc6w3` `= 11.50.xc6w4` `= 11.50.xc7` `= 11.50.xc7w1` `= 11.50.xc7w2` `= 11.50.xc7w3` `= 11.50.xc7w4` `= 11.50.xc8` `= 11.50.xc8w1` `= 11.50.xc8w2` `= 11.50.xc8w3` `= 11.50.xc8w4` `= 11.50.xc9` `= 11.70.xc1` `= 11.70.xc2` `= 11.70.xc3`
CVE-2012-3334	High	September 25, 2012 9/25/12	`= 11.50` `= 11.50.xc1` `= 11.50.xc2` `= 11.50.xc3` `= 11.50.xc3w1` `= 11.50.xc4` `= 11.50.xc4w1` `= 11.50.xc5` `= 11.50.xc5w2` `= 11.50.xc5w3` `= 11.50.xc5w4` `= 11.50.xc6` `= 11.50.xc6w1` `= 11.50.xc6w2` `= 11.50.xc6w3` `= 11.50.xc6w4` `= 11.50.xc7` `= 11.50.xc7w1` `= 11.50.xc7w2` `= 11.50.xc7w3` `= 11.50.xc7w4` `= 11.50.xc8` `= 11.50.xc8w1` `= 11.50.xc8w2` `= 11.50.xc8w3` `= 11.50.xc8w4` `= 11.50.xc9` `= 11.50.xc9w1` `= 11.70.xc1` `= 11.70.xc2` `= 11.70.xc3` `= 11.70.xc4`
CVE-2011-1033	High	February 15, 2011 2/15/11	`= 11.50`
CVE-2010-4069	High	October 25, 2010 10/25/10	`= 7.31` `= 9.40.tc5` `= 9.40.uc1` `= 9.40.uc2` `= 9.40.uc3` `= 9.40.uc5` `= 9.40.xc5` `= 9.40.xc7` `= 10.00` `= 10.00.tc3tl` `= 10.00.xc1` `= 10.00.xc2` `= 10.00.xc3` `= 10.00.xc4` `= 10.00.xc5` `= 10.00.xc6` `= 10.00.xc7w1` `= 10.00.xc8` `= 10.00.xc9` `= 10.00.xc10` `= 11.10` `= 11.10.tb4tl` `= 11.10.xc1` `= 11.10.xc1de` `= 11.10.xc2` `= 11.10.xc2e` `= 11.50` `= 11.50.xc1` `= 11.50.xc2`
CVE-2010-4070	High	October 25, 2010 10/25/10	`= 7.31` `= 9.40.tc5` `= 9.40.uc1` `= 9.40.uc2` `= 9.40.uc3` `= 9.40.uc5` `= 9.40.xc5` `= 9.40.xc7` `= 10.00` `= 10.00.tc3tl` `= 10.00.xc1` `= 10.00.xc2` `= 10.00.xc3` `= 10.00.xc4` `= 10.00.xc5` `= 10.00.xc6` `= 10.00.xc7w1` `= 10.00.xc8` `= 10.00.xc9` `= 10.00.xc10` `= 11.10` `= 11.10.tb4tl` `= 11.10.xc1` `= 11.10.xc1de` `= 11.50`
CVE-2010-4053	High	October 23, 2010 10/23/10	`= 11.10` `= 11.50`
CVE-2009-2753	High	March 5, 2010 3/5/10	`= 10.0` `= 10.0.tc1` `= 10.0.xc1` `= 10.0.xc2e` `= 10.0.xc3` `= 10.0.xc3e` `= 10.0.xc4` `= 10.0.xc4e` `= 10.0.xc5` `= 10.0.xc5e` `= 10.0.xc6` `= 10.0.xc6e` `= 10.0.xc7` `= 10.0.xc7e` `= 10.0.xc8` `= 10.0.xc8e` `= 10.0.xc9` `= 10.0.xc9e` `= 10.0.xc10` `= 10.0.xc10e` `= 11.1` `= 11.10` `= 11.10.xc1` `= 11.10.xc1de` `= 11.10.xc2` `= 11.10.xc2e` `= 11.10.xc3` `= 11.10.xc3e`
CVE-2009-2754	High	March 5, 2010 3/5/10	`= 10.0` `= 10.0.tc1` `= 10.0.xc1` `= 10.0.xc2e` `= 10.0.xc3` `= 10.0.xc3e` `= 10.0.xc4` `= 10.0.xc4e` `= 10.0.xc5` `= 10.0.xc5e` `= 10.0.xc6` `= 10.0.xc6e` `= 10.0.xc7` `= 10.0.xc7e` `= 10.0.xc8` `= 10.0.xc8e` `= 10.0.xc9` `= 10.0.xc9e` `= 10.0.xc10` `= 10.0.xc10e` `= 11.1` `= 11.10` `= 11.10.xc1` `= 11.10.xc1de` `= 11.10.xc2` `= 11.10.xc2e` `= 11.10.xc3` `= 11.10.xc3e`
CVE-2009-3470	Medium	September 29, 2009 9/29/09	`= 10.0` `= 10.00.xc1` `= 10.00.xc2` `= 10.00.xc3` `= 10.00.xc4` `= 10.00.xc5` `= 10.00.xc6` `= 10.00.xc8` `= 10.00.xc9` `= 10.00.xc10` `= 11.10` `= 11.10.xc1` `= 11.10.xc2` `= 11.10.xc3` `= 11.50` `= 11.50.xc1` `= 11.50.xc2` `= 11.50.xc3` `= 11.50.xc4`
CVE-2008-0727	High	March 18, 2008 3/18/08	`= 7.3` `= 7.31.xd8` `= 7.31.xd9` `= 9.3` `= 9.4` `= 9.40.tc5` `= 9.40.uc1` `= 9.40.uc2` `= 9.40.uc3` `= 9.40.uc5` `= 9.40.xd8` `= 9.40_xc7` `= 10.0` `= 10.0.xc3` `= 10.0.xc4` `= 10.00.xc7w1` `= 11.10.xc2`
CVE-2008-0949	High	March 18, 2008 3/18/08	`= 7.3` `= 7.31.xd8` `= 7.31.xd9` `= 9.3` `= 9.4` `= 9.40.tc5` `= 9.40.uc1` `= 9.40.uc2` `= 9.40.uc3` `= 9.40.uc5` `= 9.40.xd8` `= 9.40_xc7` `= 10.0` `= 10.0.xc3` `= 10.0.xc4` `= 10.00.xc7w1` `= 11.10.xc2`
CVE-2008-0768	High	February 13, 2008 2/13/08	`>= 10.0, <= 10.00.xc8` `>= 11.10, <= 11.10.xc2`
CVE-2008-0368	High	January 19, 2008 1/19/08	`= 10.0`
CVE-2008-0369	Medium	January 19, 2008 1/19/08	`= 10.00`
CVE-2007-5956	High	November 14, 2007 11/14/07	`<= 10.00`
CVE-2007-5957	Medium	November 14, 2007 11/14/07	`= 10.00.tc3tl` `= 11.10.tb4tl`
CVE-2006-5663	Medium	November 3, 2006 11/3/06	`= 10.00`
CVE-2006-5664	Medium	November 3, 2006 11/3/06	`= 10.00`
CVE-2006-5163	Low	October 5, 2006 10/5/06	`= 10.uc_rc1`
CVE-2006-3853	Medium	August 8, 2006 8/8/06	`= 9.4` `= 9.40.tc5` `= 9.40.uc1` `= 9.40.uc2` `= 9.40.uc3` `= 9.40.uc5` `= 9.40.xc7` `= 10.0` `= 10.0.xc3`
CVE-2006-3855	Medium	August 8, 2006 8/8/06	`= 9.4` `= 9.40.tc5` `= 9.40.uc1` `= 9.40.uc2` `= 9.40.uc3` `= 9.40.uc5` `= 10.0` `= 10.0.xc3`
CVE-2006-3856	Low	August 8, 2006 8/8/06	`= 9.4` `= 9.40.tc5` `= 9.40.uc1` `= 9.40.uc2` `= 9.40.uc3` `= 9.40.uc5` `= 9.40.xc5` `= 10.0` `= 10.0.xc1`
CVE-2006-3858	Low	August 8, 2006 8/8/06	`= 9.4` `= 9.40.tc5` `= 9.40.uc1` `= 9.40.uc2` `= 9.40.uc3` `= 9.40.uc5` `= 9.40.xc5` `= 9.40.xc7` `= 10.0` `= 10.0.xc1` `= 10.0.xc3`
CVE-2006-3861	Medium	August 8, 2006 8/8/06	`= 7.31` `= 9.4` `= 9.40.tc5` `= 9.40.uc1` `= 9.40.uc2` `= 9.40.uc3` `= 9.40.uc5` `= 9.40.xc5` `= 10.0` `= 10.0.xc1`
CVE-2006-3862	High	August 8, 2006 8/8/06	`= 9.40.tc5` `= 9.40.uc5` `= 9.40.xc5` `= 10.0.tc1` `= 10.0.xc1`
CVE-2004-2319	Low	December 31, 2004 12/31/04	`= 9.40.uc1` `= 9.40.uc2`

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.