CVE-2007-5348
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 · uneditedInteger overflow in GDI+ in Microsoft Internet Explorer 6 SP1, Windows XP SP2 and SP3, Server 2003 SP1 and SP2, Vista Gold and SP1, Server 2008, Office XP SP3, Office 2003 SP2 and SP3, 2007 Microsoft Office System Gold and SP1, Visio 2002 SP2, PowerPoint Viewer 2003, Works 8, Digital Image Suite 2006, SQL Server 2000 Reporting Services SP2, SQL Server 2005 SP2, Report Viewer 2005 SP1 and 2008, and Forefront Client Security 1.0 allows remote attackers to execute arbitrary code via an image file with crafted gradient sizes in gradient fill input, which triggers a heap-based buffer overflow related to GdiPlus.dll and VGX.DLL, aka "GDI+ VML Buffer Overrun 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 confidenceInteger overflow in GDI+ (GdiPlus.dll and VGX.DLL) allows remote code execution via specially crafted image files with manipulated gradient sizes, triggering a heap-based buffer overflow during gradient fill processing.
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= 2006= 1.0= 6= 2003= xp= 2003= 2005= 2008= 2008= 2005CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate GDI+ DLL files on the systemSearch for GdiPlus.dll and VGX.DLL files on the system. Common locations include C:\Windows\System32\ and C:\Windows\SysWOW64\ on 64-bit systems.Affected if If either GdiPlus.dll or VGX.DLL exists on the system, the component is present and could be vulnerable.
-
Identify installed Microsoft productsReview installed programs in Control Panel or use 'wmic product get name,version' command to enumerate installed Microsoft software.Affected if If any of these products are installed: Digital Image Suite 2006, Forefront Client Security 1.0, Internet Explorer 6, Office 2003, Office XP, Office PowerPoint Viewer 2003, Report Viewer 2005/2008, Server 2008, or SQL Server 2005, the system may be affected.
-
Check GDI+ DLL versionRight-click on GdiPlus.dll or VGX.DLL, select Properties, and view the File Version tab. Compare against known vulnerable versions.Affected if If the DLL version matches the affected product versions or is unpatched, the system is vulnerable.
-
Determine image processing usageIdentify applications that utilize GDI+ for image rendering. Check if users or services process untrusted image files (JPEG, PNG, BMP, TIFF, WMF, EMF).Affected if If the system processes untrusted image files through GDI+-using applications, exploitation is possible.
The system is affected if GDI+ DLLs are present AND an affected Microsoft product is installed AND the system processes image files, particularly untrusted ones.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply Microsoft security updates for GDI+ across all affected products (Internet Explorer, Windows, Office, Visio, SQL Server, Forefront Client Security). Restrict handling of untrusted image files and enable DEP/ASLR where available.
Migrate to supported versions of Windows (Windows 10/11) and Microsoft Office (Office 365 or current supported Office versions)
- Check if the system is still running any of the affected products (IE 6, Office XP/2003, Windows XP/2003, Vista, Server 2008) - these are all End of Life and no longer receive security updates
- If the system is still running any affected product, migrate to a supported version of the operating system and applications
- For organizations that cannot migrate immediately, apply Microsoft Security Bulletin MS07-046 which addressed this vulnerability (Cumulative Security Update for GDI+)
- Verify the patch is installed by checking for MS07-046 or later GDI+ security updates in Windows Update or Add/Remove Programs
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-5348 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-5348 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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