dbcve.org
Office ProjectApplication · Microsoft

CVE-2009-0102

HIGH · 9.3 CVSS v2.0 Published 2009-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Microsoft Project 2000 SR1 and 2002 SP1, and Office Project 2003 SP3, does not properly handle memory allocation for Project files, which allows remote attackers to execute arbitrary code via a malformed file, aka "Project Memory Validation Vulnerability."

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A memory validation vulnerability in Microsoft Project versions 2000 SR1, 2002 SP1, and 2003 SP3 allows remote code execution via malformed Project files. The application does not properly handle memory allocation when parsing specially crafted .mpp files, enabling attackers to inject and execute arbitrary code.

MitigationApply Microsoft security updates for this vulnerability (MS09-005 or subsequent relevant patches); restrict opening of untrusted Project files from unknown sources; consider upgrading to supported Project versions if running these legacy releases.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Office ProjectApplication
Affected:= 2007
Project Portfolio ServerApplication
Affected:= 2007
Project ServerApplication
Affected:= 2003= 2007

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Microsoft Project version
    Open Microsoft Project, go to Help > About Microsoft Project to display the exact version and service pack level. Alternatively, check Add/Remove Programs or the program's properties in the installation directory for version information.
    Affected if Version is 2000 SR1, 2002 SP1, 2003 SP3, or 2007 (any sub-version)
  2. Check Microsoft Project Server version
    Open Project Server Administration site or check the installed version via Add/Remove Programs. Access the Server Settings in Project Web Access or check the server's program files for version information.
    Affected if Project Server version is 2003 or 2007 (any service pack)
  3. Check Microsoft Project Portfolio Server version
    Access the installed programs list via Control Panel > Programs and Features, or check the application's About dialog accessible from the program menu.
    Affected if Project Portfolio Server version is 2007 (any service pack)
  4. Verify .mpp file handling is enabled
    Confirm that the system can open .mpp files by default. Check file association settings in Windows (Right-click any .mpp file > Properties > Opens with) to verify Microsoft Project is configured as the handler for Project files.
    Affected if Microsoft Project is set as the default handler for .mpp files and users can open project files
  5. Confirm memory validation behavior in file parsing
    Attempt to open or examine a malformed .mpp file in a controlled, isolated test environment using the installed Project version. Monitor for unexpected application behavior, crashes, or memory errors during file parsing.
    Affected if The application parses .mpp files without crashing or throwing memory-related errors (meaning it processes them and could be vulnerable to malformed input)

A system is affected if it runs any of the listed Project versions (2000 SR1, 2002 SP1, 2003 SP3, 2007), Project Server 2003/2007, or Project Portfolio Server 2007, and users can open .mpp files with the application.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Microsoft security updates for this vulnerability (MS09-005 or subsequent relevant patches); restrict opening of untrusted Project files from unknown sources; consider upgrading to supported Project versions if running these legacy releases.

Recommended fix High confidence

Microsoft Project 2010 or later (e.g., Project 2013, Project 2016, Project 2019, or Project 365)

  1. 1. Identify the exact version of Microsoft Project or Office Project installed (2000 SR1, 2002 SP1, 2003 SP3, or 2007)
  2. 2. Backup all existing Project files before making any changes
  3. 3. Uninstall the affected Microsoft Project version
  4. 4. Download Microsoft Project 2010 or later from the official Microsoft Volume Licensing Service Center or your existing license portal
  5. 5. Install the newer version of Microsoft Project
  6. 6. Test critical Project files for compatibility with the new version
  7. 7. Re-apply any custom templates or add-ins compatible with the new version
Caveat Older Project file formats (.mpp) from Project 2000/2002 may require migration/upgrade; verify macro and add-in compatibility with newer versions before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Office Project Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2009-0102 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2009-0102 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data