Sketchbook ProApplication · Autodesk

CVE-2014-3938

HIGH · 9.3 CVSS v2.0 Published 2014-07-23
Fix available
A fix is available. Upgrade to after 6.2.5 or later.
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
Integer overflow in Autodesk SketchBook Pro before 6.2.6 allows remote attackers to execute arbitrary code via crafted layer mask data in a PSD file, which triggers a heap-based buffer overflow.

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

Integer overflow in Autodesk SketchBook Pro before version 6.2.6 when parsing PSD files causes a heap-based buffer overflow. The vulnerability is triggered by specially crafted layer mask data in a malicious PSD file, which can lead to arbitrary code execution.

MitigationUpgrade Autodesk SketchBook Pro to version 6.2.6 or later. Avoid opening PSD files from untrusted sources.

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
Sketchbook ProApplication
Affected:<= 6.2.5= 6.2.4

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 if Autodesk SketchBook Pro is installed
    Look for the application in typical installation paths such as C:\Program Files\Autodesk\SketchBook Pro or C:\Program Files (x86)\Autodesk\SketchBook Pro, or search for 'SketchBook Pro' in the system
    Affected if The application is found on the system
  2. Determine the installed SketchBook Pro version
    Right-click on the SketchBook Pro executable (SketchBookPro.exe) and select Properties, then check the Details tab for the Product Version. Alternatively, launch the application and look in Help > About SketchBook Pro
    Affected if The version listed is 6.2.5 or lower, or displays as 6.2.4
  3. Check if the system handles PSD files
    Look for .psd file associations in the system, check file type associations for SketchBook Pro, or search for any .psd files on the system that may have been opened with SketchBook Pro
    Affected if PSD files are associated with SketchBook Pro or have been opened using the application
  4. Inspect recent PSD file interactions
    Review the application's recent files list, browser history if applicable, or check Windows Jump Lists for recently opened PSD files in SketchBook Pro
    Affected if PSD files have been opened in SketchBook Pro version 6.2.5 or lower
  5. Confirm vulnerability condition
    Cross-reference the installed version against the affected range (<=6.2.5) and verify PSD file processing capability exists
    Affected if SketchBook Pro version 6.2.5 or lower is installed AND the application can open or has opened PSD files

A system is affected if Autodesk SketchBook Pro version 6.2.5 or lower is installed and PSD files can be processed or have been processed by 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
Upgrade available Upgrade to a release after 6.2.5
Interim mitigation

Upgrade Autodesk SketchBook Pro to version 6.2.6 or later. Avoid opening PSD files from untrusted sources.

Recommended fix High confidence

Autodesk SketchBook Pro 6.2.6

  1. Check current installed version of Autodesk SketchBook Pro
  2. Navigate to Autodesk website or use auto-update feature to obtain SketchBook Pro version 6.2.6 or later
  3. Download the updated version of SketchBook Pro
  4. Run the installer and follow prompts to upgrade to version 6.2.6 or newer
  5. Verify the installed version after upgrade completes

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

Fix this in Sketchbook Pro Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-3938 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-3938 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