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-2006-3354	Medium	July 6, 2006 7/6/06	== 6-sp1 == 6.0.2600 == 6.0 == 6.0.2800 == 6.0.2800.1106 == 6.0.2900.2180
CVE-2006-3280	High	June 28, 2006 6/28/06	== 6.0
CVE-2006-3281	Medium	June 28, 2006 6/28/06	== 6.0
CVE-2006-3227	Low	June 26, 2006 6/26/06	== 6.0.2900
CVE-2006-3200	Medium	June 23, 2006 6/23/06	== 6.0.2900
CVE-2006-1303	High	June 13, 2006 6/13/06	== 5.0.1 == 5.0.1-sp2 == 5.0.1-sp3 == 5.0.1-sp4 == 5.0.1-sp1 == 6.0
CVE-2006-2378	Medium	June 13, 2006 6/13/06	== 5.0.1 == 5.0.1-sp2 == 5.0.1-sp3 == 5.0.1-sp4 == 5.0.1-sp1 == 6.0
CVE-2006-2382	High	June 13, 2006 6/13/06	== 6-sp1 == 5.01-sp4
CVE-2006-2383	High	June 13, 2006 6/13/06	== 6-sp1 == 5.01-sp4
CVE-2006-2384	Low	June 13, 2006 6/13/06	== 5.01-sp4 <= 6.0
CVE-2006-2385	High	June 13, 2006 6/13/06	== 5.01-sp4
CVE-2006-2766	Low	June 2, 2006 6/2/06	== 6.0 == 7.0-beta1 == 7.0-beta2
CVE-2006-2218	High	May 5, 2006 5/5/06	== 6.0
CVE-2006-2094	Medium	April 29, 2006 4/29/06	== 5.5-sp2 == 5.0 == 5.0.1 == 5.0.1-sp2 == 5.0.1-sp3 == 5.0.1-sp4 == 5.0.1-sp1 == 5.5 == 5.5-preview == 5.5-sp1 == 6.0 == 7.0-beta1 == 7.0-beta2
CVE-2006-2056	Medium	April 26, 2006 4/26/06	== 6.0
CVE-2006-1992	Low	April 25, 2006 4/25/06	== 6.0.2900
CVE-2006-1185	High	April 11, 2006 4/11/06	== 6-sp1
CVE-2006-1186	High	April 11, 2006 4/11/06	== 5.01-sp4 == 5.01 == 5.01-sp3 == 5.5-sp2 == 5.0.1 == 5.0.1-sp2 == 5.0.1-sp3 == 5.0.1-sp4 == 5.0.1-sp1 == 5.5 == 5.01-sp1 == 5.01-sp2 == 5.1 == 5.5-preview == 5.5-sp1
CVE-2006-1188	High	April 11, 2006 4/11/06	== 6-sp1 == 5.5-sp2 == 5.5 == 5.1 == 5.5-preview == 5.5-sp1 == 6.0.2600 == 6.0 == 6.0.2800 == 6.0.2800.1106 == 6.0.2900.2180
CVE-2006-1189	High	April 11, 2006 4/11/06	== 5.01 == 5.5 == 5.1 == 6.0
CVE-2006-1190	High	April 11, 2006 4/11/06	== 5.01 == 5.5 == 5.1 == 6.0
CVE-2006-1191	Low	April 11, 2006 4/11/06	== 5.01 == 5.5 == 5.1 == 6.0
CVE-2006-1192	Low	April 11, 2006 4/11/06	== 6-sp1
CVE-2006-1626	Low	April 5, 2006 4/5/06	== 6.0
CVE-2006-1388	High	March 24, 2006 3/24/06	== 6.0
CVE-2006-1359	High	March 23, 2006 3/23/06	== 6.0
CVE-2006-1016	High	March 7, 2006 3/7/06	== 6.0
CVE-2006-0830	High	February 21, 2006 2/21/06	== 6.0.2900
CVE-2006-0799	Low	February 19, 2006 2/19/06	== 6.0.2900
CVE-2006-0585	Medium	February 8, 2006 2/8/06	== 5.01-sp4 == 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 <= 6 == 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
CVE-2006-0057	High	January 27, 2006 1/27/06	== 6-sp1 == 5.01-sp4 == 5.5-sp2
CVE-2005-3240	Medium	December 31, 2005 12/31/05	== 5.01-sp4 == 5.01 == 5.01-sp3 == 5.5-sp2 == 5.5 == 5.01-sp1 == 5.01-sp2 == 5.5-sp1 == 6.0
CVE-2005-4717	Medium	December 31, 2005 12/31/05	== 6.0
CVE-2005-4810	Medium	December 31, 2005 12/31/05	== 7.0-beta3
CVE-2005-4827	High	December 31, 2005 12/31/05	== 6-sp1 == 6.0.2600 == 6.0 == 6.0.2800 == 6.0.2800.1106 == 6.0.2900.2180
CVE-2005-4841	High	December 31, 2005 12/31/05	== 7.0
CVE-2005-4842	High	December 31, 2005 12/31/05	== 7.0
CVE-2005-4843	High	December 31, 2005 12/31/05	== 7.0
CVE-2005-4844	High	December 31, 2005 12/31/05	<= 7.0
CVE-2005-2829	Medium	December 14, 2005 12/14/05	== 5.5-sp2 == 5.0.1-sp4 == 6.0
CVE-2005-2830	Medium	December 14, 2005 12/14/05	== 5.5-sp2 == 5.0.1-sp4 == 6.0
CVE-2005-2831	High	December 14, 2005 12/14/05	== 5.5-sp2 == 5.0.1 == 5.0.1-sp2 == 5.0.1-sp3 == 5.0.1-sp4 == 5.0.1-sp1 == 5.5 == 5.5-sp1 == 6.0
CVE-2005-4089	High	December 8, 2005 12/8/05	== 6.0
CVE-2005-3312	Low	October 26, 2005 10/26/05	== 6.0
CVE-2005-1988	Medium	August 10, 2005 8/10/05	== 5.01 == 5.5
CVE-2005-1989	High	August 10, 2005 8/10/05	== 5.01 == 5.5
CVE-2005-1990	Medium	August 10, 2005 8/10/05	== 5.01 == 5.5
CVE-2005-2304	Medium	July 19, 2005 7/19/05	== 6.0
CVE-2005-2274	Low	July 13, 2005 7/13/05	== 6.0
CVE-2005-2087	Medium	July 5, 2005 7/5/05	== 5.01-sp4 == 5.5-sp2 == 5.5 == 5.1 == 5.5-preview == 5.5-sp1 == 6.0 == 6.0.2900.2180

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.