How severe is CVE-2009-1674?

CVE-2009-1674 has a CVSS 2.0 base score of 9.3, rated critical severity.

Is CVE-2009-1674 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 5% (91st percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2009-1674?

CVE-2009-1674 affects Microchip Mplab Ide. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2009-1674?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2009-1674 published?

CVE-2009-1674 was published on 2009-05-18 and last updated on 2026-06-16.

CVE-2009-1674

CVE-2009-1674 is a critical-severity vulnerability in Microchip Mplab Ide with a CVSS 2.0 base score of 9.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-119.

Key facts

Severity: Critical (CVSS 2.0 base score 9.3)
EPSS exploit prediction: 5% (91st percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-119
Affected product: Microchip Mplab Ide
Published: 2009-05-18
Last modified: 2026-06-16

Description

Stack-based buffer overflow in Microchip MPLAB IDE 8.30 allows user-assisted remote attackers to execute arbitrary code via a long .cof pathname in a [TOOL_SETTINGS] section in a .mcp file, possibly a related issue to CVE-2009-1608.

Frequently asked questions

What is CVE-2009-1674?: Stack-based buffer overflow in Microchip MPLAB IDE 8.30 allows user-assisted remote attackers to execute arbitrary code via a long .cof pathname in a [TOOL_SETTINGS] section in a .mcp file, possibly a related issue to CVE-2009-1608.
How severe is CVE-2009-1674?: CVE-2009-1674 has a CVSS 2.0 base score of 9.3, rated critical severity.
Is CVE-2009-1674 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 5% (91st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2009-1674?: CVE-2009-1674 affects Microchip Mplab Ide. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2009-1674?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2009-1674 published?: CVE-2009-1674 was published on 2009-05-18 and last updated on 2026-06-16.

References

Affected products (1)

cpe:2.3:a:microchip:mplab_ide:8.30:*:*:*:*:*:*:*

More vulnerabilities in Microchip Mplab Ide

CVE-2009-1608 — Critical (CVSS 9.3): Multiple buffer overflows in Microchip MPLAB IDE 8.30 and possibly earlier versions allow user-assisted remote…

All CVEs affecting Microchip Mplab Ide →

Other CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) vulnerabilities

CVE-2026-2778 — Critical (CVSS 10.0): Sandbox escape due to incorrect boundary conditions in the DOM: Core & HTML component. This vulnerability was fixed in…
CVE-2026-2776 — Critical (CVSS 10.0): Sandbox escape due to incorrect boundary conditions in the Telemetry component in External Software. This vulnerability…
CVE-2025-1866 — Critical (CVSS 10.0): Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability in warmcat libwebsockets allows…
CVE-2022-27625 — Critical (CVSS 10.0): A vulnerability regarding improper restriction of operations within the bounds of a memory buffer is found in the…
CVE-2022-27624 — Critical (CVSS 10.0): A vulnerability regarding improper restriction of operations within the bounds of a memory buffer is found in the…
CVE-2020-11896 — Critical (CVSS 10.0): The Treck TCP/IP stack before 6.0.1.66 allows Remote Code Execution, related to IPv4 tunneling.

Browse all CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) vulnerabilities →