Menu

Star on GitHub · 3.2k

CVE-2009-0757

7.5 · HIGH

Multiple buffer overflows in GNU MPFR 2.4.0 allow context-dependent attackers to cause a denial of service (crash) via the (1) mpfr_snprintf and (2) mpfr_vsnprintf functions.

Published Mar 3, 2009mpfrCWE-119EPSS 1.55%

Overview

CVE-2009-0757 is a high-severity vulnerability affecting mpfr gnu_mpfr. It was published on March 3, 2009 and has a CVSS 2.0 base score of 7.5 (HIGH).

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

Multiple buffer overflows in GNU MPFR 2.4.0 allow context-dependent attackers to cause a denial of service (crash) via the (1) mpfr_snprintf and (2) mpfr_vsnprintf functions.

Remediation

Check the references section for vendor advisories and patches from mpfr. Update gnu_mpfr to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2009-0757?

CVE-2009-0757 is a high-severity vulnerability affecting mpfr gnu_mpfr. It was published on March 3, 2009 and has a CVSS 2.0 base score of 7.5 (HIGH).

How severe is CVE-2009-0757?

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2009-0757?

Check the references section for vendor advisories and patches from mpfr. Update gnu_mpfr to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2009-0757?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2009-0757 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2009

View all