dbcve.org
Creo ViewApplication · Ptc

CVE-2015-2061

HIGH · 7.5 CVSS v2.0 Published 2015-03-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Heap-based buffer overflow in the browser plugin for PTC Creo View allows remote attackers to execute arbitrary code via vectors involving setting a large buffer to an unspecified attribute.

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 · moderate confidence

Heap-based buffer overflow in the PTC Creo View browser plugin allows remote attackers to execute arbitrary code by setting a large buffer value to an unspecified attribute, causing memory corruption on the heap.

MitigationApply vendor patch for PTC Creo View, or disable the browser plugin until patched. Restrict access to untrusted sources to reduce attack surface.

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
Creo ViewApplication
Affected:all versions

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
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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. Verify if PTC Creo View is installed
    Check for PTC Creo View installation directories (commonly in Program Files/PTC or C:\Program Files\PTC), or use system inventory tools to list installed software containing 'Creo View' in the name
    Affected if PTC Creo View software is found installed on the system
  2. Identify the browser plugin component
    Search for browser plugin files associated with PTC Creo View - look for NPAPI plugin files (typically .dll) in browser plugin directories or PTC installation folders. Check common browser plugin paths for the Creo View plugin file
    Affected if Browser plugin files for PTC Creo View are present in the system
  3. Check browser plugin registry entries (Windows)
    Examine Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\MozillaPlugins or HKEY_CURRENT_USER\SOFTWARE\MozillaPlugins for entries related to PTC Creo View, or check Chrome/Edge plugin settings at chrome://plugins
    Affected if Browser plugin registry entry or browser plugin list shows PTC Creo View plugin as registered
  4. Confirm if browser plugin is enabled
    Access browser plugin settings (about:addons in Firefox, chrome://extensions in Chrome) and verify whether the PTC Creo View plugin is currently enabled for browser use
    Affected if The PTC Creo View browser plugin is installed and set to enabled/allowed in the browser configuration
  5. Identify active browsers with the plugin
    List which web browsers have the PTC Creo View plugin loaded or permitted. Check browser security settings for plugin permissions across Internet Explorer, Chrome, Firefox, and Edge
    Affected if Any web browser has the PTC Creo View plugin enabled and permitted to run

If PTC Creo View browser plugin is installed and enabled in any web browser, the system is affected by this vulnerability since all versions contain the heap-based buffer overflow flaw.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch for PTC Creo View, or disable the browser plugin until patched. Restrict access to untrusted sources to reduce attack surface.

Fix this in Creo View Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-2061 — 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-2015-2061 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