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.

347,064

Total vulnerabilities in the database

Vulnerabilities for products matching "internet_explorer"

Found 1 matching product.

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

microsoft / internet_explorer

5549 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2009-2530	High	October 14, 2009 10/14/09	== 5.01-sp4 == 6-sp1 == 6 == 7 == 8
CVE-2009-2531	High	October 14, 2009 10/14/09	== 5.01-sp4 == 6-sp1 == 6 == 7 == 8
CVE-2009-3126	High	October 14, 2009 10/14/09	== 6-sp1
CVE-2009-1547	High	October 14, 2009 10/14/09	== 5.01-sp4 == 6-sp1 == 6 == 7 == 8
CVE-2009-3267	Medium	September 18, 2009 9/18/09	>= 6.0 <= 6.00.2900.2180 >= 7.0 <= 7.0.6000.16711
CVE-2009-3270	Medium	September 18, 2009 9/18/09	>= 7.0 <= 7.0.6000.16711
CVE-2009-3019	Medium	August 31, 2009 8/31/09	== 6 == 7
CVE-2009-3003	Low	August 28, 2009 8/28/09	== 8 == 7 == 6
CVE-2009-2954	Medium	August 24, 2009 8/24/09	== 5 <= 6.0.2900.2180 == 5.01-sp4 == 6 == 5.01 == 5.01-sp3 == 5.5-sp2 == 3.0.1 == 3.0.2 == 3.0 == 3.1 == 3.2 == 4.0 == 4.0.1 == 4.0.1-sp2 == 4.0.1-sp1 == 4.01 == 4.01-sp1 == 4.1 == 4.5 == 4.40.308 == 4.40.520 == 4.70.1155 == 4.70.1158 == 4.70.1215 == 4.70.1300 == 4.72.3612.1713 == 4.71.544 == 4.71.1008.3 == 4.71.1712.6 == 4.72.2106.8 == 4.72.3110.8 == 5.0 == 5.0.1 == 5.0.1-sp2 == 5.0.1-sp3 == 5.0.1-sp4 == 5.0.1-sp1 == 5.00.0518.10 == 5.00.0910.1309 == 5.00.2014.0216 == 5.00.2314.1003 == 5.00.2614.3500 == 5.00.2516.1900 == 5.00.2919.800 == 5.00.2919.3800 == 5.00.2919.6307 == 5.00.2920.0000 == 5.00.3103.1000 == 5.00.3105.0106 == 5.00.3314.2101 == 5.00.3315.1000 == 5.00.3502.1000 == 5.00.3700.1000 == 5.50.3825.1300 == 5.50.4030.2400 == 5.50.4134.0100 == 5.50.4134.0600 == 5.50.4308.2900 == 5.50.4522.1800 == 5.50.4807.2300 == 5.5 == 5.01-sp1 == 5.01-sp2 == 5.1 == 5.2.3 == 5.5-preview == 5.5-sp1 == 6.0.2600 == 6.00.2462.0000 == 6.00.2479.0006 == 6.0 == 6.0.2800 == 6.0.2800.1106 == 6.0.2900 == 6.00.2600.0000
CVE-2009-2764	Medium	August 14, 2009 8/14/09	== 8.0.7100.0
CVE-2009-2668	High	August 5, 2009 8/5/09	== 7 == 6
CVE-2009-2655	Low	August 3, 2009 8/3/09	== 7 == 8
CVE-2009-1917	High	July 29, 2009 7/29/09	== 6 == 7 == 5.01-sp4 == 6-sp1 == 8
CVE-2009-1918	High	July 29, 2009 7/29/09	== 6 == 7 == 5.01-sp4 == 6-sp1 == 8
CVE-2009-1919	High	July 29, 2009 7/29/09	== 6 == 7 == 5.01-sp4 == 6-sp1 == 8
CVE-2009-2576	Medium	July 22, 2009 7/22/09	== 5 == 6-sp1 <= 6.0.2900.2180 == 6 == 5.01 == 5.01-sp3 == 5.5-sp2 == 3.0.1 == 3.0.2 == 3.0 == 3.1 == 3.2 == 4.0 == 4.0.1 == 4.0.1-sp2 == 4.0.1-sp1 == 4.01 == 4.01-sp1 == 4.1 == 4.5 == 4.40.308 == 4.40.520 == 4.70.1155 == 4.70.1158 == 4.70.1215 == 4.70.1300 == 4.72.3612.1713 == 4.71.1008.3 == 4.71.1712.6 == 4.72.2106.8 == 4.72.3110.8 == 5.0 == 5.0.1 == 5.0.1-sp2 == 5.0.1-sp4 == 5.0.1-sp1 == 5.00.0518.10 == 5.00.0910.1309 == 5.00.2014.0216 == 5.00.2614.3500 == 5.00.2516.1900 == 5.00.2919.800 == 5.00.2919.6307 == 5.00.2920.0000 == 5.00.3103.1000 == 5.00.3105.0106 == 5.00.3314.2101 == 5.00.3315.1000 == 5.00.3502.1000 == 5.00.3700.1000 == 5.50.3825.1300 == 5.50.4030.2400 == 5.50.4134.0100 == 5.50.4134.0600 == 5.50.4308.2900 == 5.50.4522.1800 == 5.50.4807.2300 == 5.5 == 5.01-sp1 == 5.1 == 5.2.3 == 5.5-preview == 5.5-sp1 == 6.0.2600 == 6.0 == 6.0.2800 == 6.0.2800.1106 == 6.0.2900
CVE-2009-2536	Low	July 20, 2009 7/20/09	<= 8 == 5 == 7 == 6
CVE-2009-2433	Low	July 10, 2009 7/10/09	== 7 == 7.0.5730-unknown == 7.0-beta == 7.0 == 7.0.5730.11 == 7.0-beta1 == 7.0-beta2 == 7.0-beta3 == 7.00.5730.1100 == 7.00.6000.16386 == 7.00.6000.16441 == 8.0.6001-beta == 8.0.6001
CVE-2009-2350	Low	July 7, 2009 7/7/09	== 6
CVE-2009-2064	Medium	June 15, 2009 6/15/09	== 7.0.5730 == 8.0b == 8 == 5 == 6-sp1 == 6-sp2 == 5.01-sp4 == 7 == 8-beta1 == 6 <= 8
CVE-2009-2069	Medium	June 15, 2009 6/15/09	== 5 == 6-sp1 == 5.01-sp4 == 7 == 6 == 5.01 == 5.01-sp3 == 5.5-sp2 == 3.0.1 == 3.0.2 == 3.0 == 3.1 == 3.2 == 4.0 == 4.0.1 == 4.0.1-sp2 == 4.0.1-sp1 == 4.01 == 4.01-sp1 == 4.1 == 4.5 == 4.40.308 == 4.40.520 == 4.70.1155 == 4.70.1158 == 4.70.1215 == 4.70.1300 == 4.72.3612.1713 == 4.71.544 == 4.71.1008.3 == 4.71.1712.6 == 4.72.2106.8 == 4.72.3110.8 == 5.0 == 5.0.1 == 5.0.1-sp2 == 5.0.1-sp3 == 5.0.1-sp4 == 5.0.1-sp1 == 5.00.0518.10 == 5.00.0910.1309 == 5.00.2014.0216 == 5.00.2314.1003 == 5.00.2614.3500 == 5.00.2919.800 == 5.00.2919.3800 == 5.00.2919.6307 == 5.00.2920.0000 == 5.00.3103.1000 == 5.00.3105.0106 == 5.00.3314.2101 == 5.00.3315.1000 == 5.00.3502.1000 == 5.00.3700.1000 == 5.50.3825.1300 == 5.50.4030.2400 == 5.50.4134.0600 == 5.50.4308.2900 == 5.50.4522.1800 == 5.50.4807.2300 == 5.5 == 5.01-sp1 == 5.01-sp2 == 5.1 == 5.2.3 == 5.5-preview == 5.5-sp1 == 6.0.2600 == 6.00.2462.0000 == 6.00.2479.0006 == 6.0 == 6.0.2800 == 6.0.2800.1106 == 6.0.2900 == 6.00.2800.1106 == 6.0.2900.2180 == 7.0-beta == 7.0 == 7.0.5730.11 == 6.00.2900.2180 == 6.00.3663.0000 == 6.00.3790.0000 == 6.00.3790.1830 == 6.00.3790.3959 == 7.0-beta1 == 7.0-beta3 == 7.00.5730.1100 == 7.00.6000.16386 == 7.00.6000.16441
CVE-2009-2057	Medium	June 15, 2009 6/15/09	== 5 == 6-sp1 == 5.01-sp4 == 7 == 6 == 5.01 == 5.01-sp3 == 5.5-sp2 == 3.0.1 == 3.0.2 == 3.0 == 3.1 == 3.2 == 4.0 == 4.0.1 == 4.0.1-sp2 == 4.0.1-sp1 == 4.01 == 4.01-sp1 == 4.1 == 4.5 == 4.40.308 == 4.40.520 == 4.70.1155 == 4.70.1158 == 4.70.1215 == 4.70.1300 == 4.72.3612.1713 == 4.71.544 == 4.71.1008.3 == 4.71.1712.6 == 4.72.2106.8 == 4.72.3110.8 == 5.0 == 5.0.1 == 5.0.1-sp2 == 5.0.1-sp3 == 5.0.1-sp4 == 5.0.1-sp1 == 5.00.0518.10 == 5.00.0910.1309 == 5.00.2014.0216 == 5.00.2314.1003 == 5.00.2614.3500 == 5.00.2919.800 == 5.00.2919.3800 == 5.00.2919.6307 == 5.00.2920.0000 == 5.00.3103.1000 == 5.00.3105.0106 == 5.00.3314.2101 == 5.00.3315.1000 == 5.00.3502.1000 == 5.00.3700.1000 == 5.50.3825.1300 == 5.50.4030.2400 == 5.50.4134.0600 == 5.50.4308.2900 == 5.50.4522.1800 == 5.50.4807.2300 == 5.5 == 5.01-sp1 == 5.01-sp2 == 5.1 == 5.2.3 == 5.5-preview == 5.5-sp1 == 6.0.2600 == 6.00.2462.0000 == 6.00.2479.0006 == 6.0 == 6.0.2800 == 6.0.2800.1106 == 6.0.2900 == 6.00.2800.1106 == 6.0.2900.2180 == 7.0-beta == 7.0 == 7.0.5730.11 == 6.00.2900.2180 == 6.00.3663.0000 == 6.00.3790.0000 == 6.00.3790.1830 == 6.00.3790.3959 == 7.0-beta1 == 7.0-beta3 == 7.00.5730.1100 == 7.00.6000.16386 == 7.00.6000.16441
CVE-2009-1140	High	June 10, 2009 6/10/09	== 6 == 7 == 5.01-sp4 == 6-sp1
CVE-2009-1141	High	June 10, 2009 6/10/09	== 6
CVE-2009-1528	High	June 10, 2009 6/10/09	== 6 == 7
CVE-2009-1529	High	June 10, 2009 6/10/09	== 6 == 7 == 6-sp1 == 5.01 == 5.01-sp4 == 8
CVE-2009-1530	High	June 10, 2009 6/10/09	== 6 == 7 == 6-sp1 == 5.01 == 5.01-sp4 == 8
CVE-2009-1531	High	June 10, 2009 6/10/09	== 7
CVE-2009-1532	High	June 10, 2009 6/10/09	== 8
CVE-2009-1335	Low	April 17, 2009 4/17/09	== 7 == 8
CVE-2009-0550	High	April 15, 2009 4/15/09	== 5.01-sp4 == 6 == 7
CVE-2009-0551	High	April 15, 2009 4/15/09	== 6 == 7 == 6-sp1
CVE-2009-0552	High	April 15, 2009 4/15/09	== 5.0.1-sp4 == 6
CVE-2009-0553	High	April 15, 2009 4/15/09	== 6 == 7 == 6-sp1
CVE-2009-0554	High	April 15, 2009 4/15/09	== 6 == 7 == 5.01-sp4 == 6-sp1
CVE-2009-1043	High	March 23, 2009 3/23/09	== 8
CVE-2009-0075	High	February 10, 2009 2/10/09	== 7
CVE-2009-0076	High	February 10, 2009 2/10/09	== 7
CVE-2009-0369	Low	January 30, 2009 1/30/09	== 7
CVE-2009-0341	High	January 29, 2009 1/29/09	== 7
CVE-2008-5912	Low	January 20, 2009 1/20/09	*
CVE-2009-0072	Low	January 8, 2009 1/8/09	== 6-sp1 == 8-beta2 == 6-sp2 == 7 == 8-beta1 == 6
CVE-2008-5750	Medium	December 29, 2008 12/29/08	== 8-beta2
CVE-2008-5551	Low	December 12, 2008 12/12/08	== 8-beta2
CVE-2008-5552	Low	December 12, 2008 12/12/08	== 8-beta2
CVE-2008-5553	Low	December 12, 2008 12/12/08	== 8-beta2
CVE-2008-5554	Low	December 12, 2008 12/12/08	== 8-beta2
CVE-2008-5555	Low	December 12, 2008 12/12/08	== 8-beta2
CVE-2008-5556	Low	December 12, 2008 12/12/08	== 8-beta2
CVE-2008-4844	High	December 11, 2008 12/11/08	== 5.01 == 6 == 6-sp1 == 7

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.