dbcve.org
Power2goApplication · Cyberlink

CVE-2010-5243

MEDIUM · 6.9 CVSS v2.0 Published 2012-09-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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
Multiple untrusted search path vulnerabilities in Cyberlink Power2Go 7.0.0.0816 allow local users to gain privileges via a Trojan horse (1) dwmapi.dll or (2) MFC71LOC.DLL file in the current working directory, as demonstrated by a directory that contains a .p2g, .iso, .pdl, .pds, or .p2i file. NOTE: some of these details are obtained from third party information.

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

Cyberlink Power2Go 7.0.0.0816 contains an untrusted search path vulnerability where the application loads DLL files (dwmapi.dll or MFC71LOC.DLL) from the current working directory instead of secure system paths. When a user opens a .p2g, .iso, .pdl, .pds, or .p2i file from a directory containing a malicious DLL, the application will execute the attacker's code with the privileges of the logged-on user.

MitigationEnsure Power2Go is launched only from trusted directories and avoid opening files from untrusted locations. Apply vendor security updates or patches for Power2Go to address the unsafe DLL loading behavior.

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
Power2goApplication
Affected:= 7.0.0.0816

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
Local
Complexity
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/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 Power2Go version
    Open Power2Go and navigate to Help > About, or check the installed version in Add/Remove Programs. Alternatively, right-click the Power2Go executable in Program Files and view Properties > Details.
    Affected if The installed version is exactly 7.0.0.0816. If the version differs, this specific CVE may not apply.
  2. Identify DLLs loaded at runtime
    Use Process Monitor (ProcMon) from Sysinternals to filter by Power2Go process and monitor DLL load operations. Look for Load Image events showing dwmapi.dll or MFC71LOC.DLL being loaded.
    Affected if Either dwmapi.dll or MFC71LOC.DLL is loaded from a path other than the Windows system directory (typically C:\Windows\System32).
  3. Check DLL search path behavior
    Run Power2Go from a test directory containing a dummy dwmapi.dll or MFC71LOC.DLL file, then launch the application and use Process Monitor to see which DLL path gets loaded. Compare against the known vulnerable behavior.
    Affected if The application loads the DLL from the current working directory rather than from the system directory, indicating unsafe DLL search path usage.
  4. Verify vulnerable file type handling
    Open any of the affected file types (.p2g, .iso, .pdl, .pds, .p2i) from a directory containing a test DLL while monitoring with Process Monitor.
    Affected if The application loads dwmapi.dll or MFC71LOC.DLL from that same directory when these file types are opened, confirming the DLL hijacking vector.

If Power2Go version 7.0.0.0816 is installed AND it loads dwmapi.dll or MFC71LOC.DLL from the current working directory (not System32) when opening vulnerable file types, the environment is affected by this CVE.

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

Ensure Power2Go is launched only from trusted directories and avoid opening files from untrusted locations. Apply vendor security updates or patches for Power2Go to address the unsafe DLL loading behavior.

Fix this in Power2go Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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