CVE-2012-0009

CVE-2012-0009 is a critical-severity vulnerability in Microsoft Windows Server 2003 with a CVSS 2.0 base score of 9.3. Its EPSS exploit-prediction score of 21% places it in the 97th percentile, indicating an elevated likelihood of exploitation.

Key facts

Description

Untrusted search path vulnerability in the Windows Object Packager configuration in Microsoft Windows XP SP2 and SP3 and Server 2003 SP2 allows local users to gain privileges via a Trojan horse executable file in the current working directory, as demonstrated by a directory that contains a file with an embedded packaged object, aka "Object Packager Insecure Executable Launching Vulnerability."

Frequently asked questions

What is CVE-2012-0009?
Untrusted search path vulnerability in the Windows Object Packager configuration in Microsoft Windows XP SP2 and SP3 and Server 2003 SP2 allows local users to gain privileges via a Trojan horse executable file in the current working directory, as demonstrated by a directory that contains a file with an embedded packaged object, aka "Object Packager Insecure Executable Launching Vulnerability."
How severe is CVE-2012-0009?
CVE-2012-0009 has a CVSS 2.0 base score of 9.3, rated critical severity.
Is CVE-2012-0009 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 21% (97th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2012-0009?
CVE-2012-0009 primarily affects Microsoft Windows Server 2003. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2012-0009?
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-2012-0009 published?
CVE-2012-0009 was published on 2012-01-10 and last updated on 2026-06-16.

References

Affected products (3)

More vulnerabilities in Microsoft Windows Server 2003

All CVEs affecting Microsoft Windows Server 2003 →