What is the severity of CVE-2009-2575?

CVE-2009-2575 is classified as a high severity vulnerability due to its potential to cause a denial of service.

How does CVE-2009-2575 affect the BlackBerry 8800?

CVE-2009-2575 allows remote attackers to crash the BlackBerry 8800 browser and consume its memory.

What versions of the BlackBerry are affected by CVE-2009-2575?

CVE-2009-2575 specifically affects the Research In Motion BlackBerry 8800.

How can I mitigate the risks associated with CVE-2009-2575?

To mitigate risks from CVE-2009-2575, users should consider disabling incompatible browser features or applying security patches if available.

Is there a workaround for CVE-2009-2575?

A workaround for CVE-2009-2575 may involve limiting the use of the affected browser features that can be exploited.

Vulnerability/
CVE-2009-2575

high

7.1

CWE

399

22/7/2009

3/10/2022

7/8/2024

CVE-2009-2575

First published: Wed Jul 22 2009(Updated: )

The Research In Motion (RIM) BlackBerry 8800 allows remote attackers to cause a denial of service (memory consumption and browser crash) via a large integer value for the length property of a Select object, a related issue to CVE-2009-1692.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Rim Blackberry 8800

Never miss a vulnerability like this again

Reference Links

http://lists.grok.org.uk/pipermail/full-disclosure/2009-July/069772.html

Frequently Asked Questions

What is the severity of CVE-2009-2575?
CVE-2009-2575 is classified as a high severity vulnerability due to its potential to cause a denial of service.
How does CVE-2009-2575 affect the BlackBerry 8800?
CVE-2009-2575 allows remote attackers to crash the BlackBerry 8800 browser and consume its memory.
What versions of the BlackBerry are affected by CVE-2009-2575?
CVE-2009-2575 specifically affects the Research In Motion BlackBerry 8800.
How can I mitigate the risks associated with CVE-2009-2575?
To mitigate risks from CVE-2009-2575, users should consider disabling incompatible browser features or applying security patches if available.
Is there a workaround for CVE-2009-2575?
A workaround for CVE-2009-2575 may involve limiting the use of the affected browser features that can be exploited.

collector/nvd-historical
collector/nvd-index
agent/type
agent/softwarecombine
agent/first-publish-date
collector/mitre-cve
source/MITRE
agent/references
agent/author
agent/weakness
agent/last-modified-date
agent/severity
agent/tags
agent/description
agent/event
agent/source
vendor/rim
canonical/rim blackberry 8800

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-2575?
CVE-2009-2575 is classified as a high severity vulnerability due to its potential to cause a denial of service.
How does CVE-2009-2575 affect the BlackBerry 8800?
CVE-2009-2575 allows remote attackers to crash the BlackBerry 8800 browser and consume its memory.
What versions of the BlackBerry are affected by CVE-2009-2575?
CVE-2009-2575 specifically affects the Research In Motion BlackBerry 8800.
How can I mitigate the risks associated with CVE-2009-2575?
To mitigate risks from CVE-2009-2575, users should consider disabling incompatible browser features or applying security patches if available.
Is there a workaround for CVE-2009-2575?
A workaround for CVE-2009-2575 may involve limiting the use of the affected browser features that can be exploited.