Menu

Star on GitHub · 3.2k

CVE-2014-1758

9.3 · HIGH

Stack-based buffer overflow in Microsoft Word 2003 SP3 allows remote attackers to execute arbitrary code via a crafted document, aka "Microsoft Word Stack Overflow Vulnerability."

Published Apr 8, 2014microsoftCWE-119EPSS 16.70%

Overview

CVE-2014-1758 is a high-severity vulnerability affecting microsoft word. It was published on April 8, 2014 and has a CVSS 2.0 base score of 9.3 (HIGH).

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

Technical description

Stack-based buffer overflow in Microsoft Word 2003 SP3 allows remote attackers to execute arbitrary code via a crafted document, aka "Microsoft Word Stack Overflow Vulnerability."

Remediation

Check the references section for vendor advisories and patches from microsoft. Update word 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-2014-1758?

CVE-2014-1758 is a high-severity vulnerability affecting microsoft word. It was published on April 8, 2014 and has a CVSS 2.0 base score of 9.3 (HIGH).

How severe is CVE-2014-1758?

This vulnerability has a CVSS 2.0 base score of 9.3, 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-2014-1758?

Check the references section for vendor advisories and patches from microsoft. Update word 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-2014-1758?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2014-1758 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 2014

View all