What is the severity of CVE-2009-3267?

CVE-2009-3267 has a severity rating that indicates it can lead to a denial of service due to high CPU consumption.

How does CVE-2009-3267 affect Internet Explorer?

CVE-2009-3267 allows remote attackers to exploit Internet Explorer versions 6 and 7 using an automatically submitted form with a KEYGEN element.

What versions of Internet Explorer are affected by CVE-2009-3267?

CVE-2009-3267 affects Microsoft Internet Explorer versions 6.0 through 6.0.2900.2180 and 7.0.6000.16711.

How can CVE-2009-3267 be mitigated?

Mitigating CVE-2009-3267 involves updating Internet Explorer to the latest version available.

Is there a patch for CVE-2009-3267?

Microsoft has not released a specific patch for CVE-2009-3267, hence upgrading to a non-vulnerable version is the recommended action.

Vulnerability/
CVE-2009-3267

medium

CWE

400

18/9/2009

7/8/2024

CVE-2009-3267

First published: Fri Sep 18 2009(Updated: )

Microsoft Internet Explorer 6 through 6.0.2900.2180, and 7.0.6000.16711, allows remote attackers to cause a denial of service (CPU consumption) via an automatically submitted form containing a KEYGEN element, a related issue to CVE-2009-1828.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Internet Explorer	>=6.0<=6.00.2900.2180
Internet Explorer	>=7.0<=7.0.6000.16711

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2009-3267?
CVE-2009-3267 has a severity rating that indicates it can lead to a denial of service due to high CPU consumption.
How does CVE-2009-3267 affect Internet Explorer?
CVE-2009-3267 allows remote attackers to exploit Internet Explorer versions 6 and 7 using an automatically submitted form with a KEYGEN element.
What versions of Internet Explorer are affected by CVE-2009-3267?
CVE-2009-3267 affects Microsoft Internet Explorer versions 6.0 through 6.0.2900.2180 and 7.0.6000.16711.
How can CVE-2009-3267 be mitigated?
Mitigating CVE-2009-3267 involves updating Internet Explorer to the latest version available.
Is there a patch for CVE-2009-3267?
Microsoft has not released a specific patch for CVE-2009-3267, hence upgrading to a non-vulnerable version is the recommended action.

agent/softwarecombine
agent/type
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/references
agent/weakness
agent/author
agent/description
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-historical
agent/software-canonical-lookup-request
collector/nvd-index
vendor/microsoft
canonical/internet explorer
version/internet explorer/6.0
version/internet explorer/6.00.2900.2180
version/internet explorer/7.0
version/internet explorer/7.0.6000.16711

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2009-3267?
CVE-2009-3267 has a severity rating that indicates it can lead to a denial of service due to high CPU consumption.
How does CVE-2009-3267 affect Internet Explorer?
CVE-2009-3267 allows remote attackers to exploit Internet Explorer versions 6 and 7 using an automatically submitted form with a KEYGEN element.
What versions of Internet Explorer are affected by CVE-2009-3267?
CVE-2009-3267 affects Microsoft Internet Explorer versions 6.0 through 6.0.2900.2180 and 7.0.6000.16711.
How can CVE-2009-3267 be mitigated?
Mitigating CVE-2009-3267 involves updating Internet Explorer to the latest version available.
Is there a patch for CVE-2009-3267?
Microsoft has not released a specific patch for CVE-2009-3267, hence upgrading to a non-vulnerable version is the recommended action.