dbcve.org
PowerproducerApplication · Cyberlink

CVE-2012-4758

MEDIUM · 6.9 CVSS v2.0 Published 2012-09-06
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 PowerProducer 5.5.3.2325 allow local users to gain privileges via a Trojan horse (1) mfc71loc.dll or (2) mfc71enu.dll file in the current working directory, as demonstrated by a directory that contains a .ppp or .rdf file. NOTE: the provenance of this information is unknown; the details are obtained solely 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 · low confidence

CyberLink PowerProducer 5.5.3.2325 is vulnerable to DLL hijacking (untrusted search path). The application loads mfc71loc.dll or mfc71enu.dll from the current working directory without validation. An attacker can place a malicious DLL in a directory containing .ppp or .rdf files; when a user opens a media file with PowerProducer from that directory, the Trojan DLL executes with the application's privileges.

MitigationAvoid opening CyberLink project files from untrusted or shared directories. Ensure the application directory is not writable by untrusted users. Consider upgrading to a patched version if available.

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
PowerproducerApplication
Affected:= 5.5.3.2325

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. Verify CyberLink PowerProducer installation and version
    Check the installed version of CyberLink PowerProducer on the system. Look in Add/Remove Programs (Windows), or check the program's executable properties (right-click PowerProducer.exe > Properties > Details), or examine the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\PowerProducer or HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\PowerProducer.
    Affected if The installed version is exactly 5.5.3.2325 (no other versions are listed as affected in this CVE).
  2. Confirm .ppp or .rdf file associations
    Check if .ppp (PowerProducer Project) or .rdf (likely a related media file) file extensions are associated with PowerProducer. Look in the Windows registry under HKEY_CLASSES_ROOT\.ppp or HKEY_CLASSES_ROOT\.rdf, or simply right-click any .ppp or .rdf file and check the 'Opens with' program.
    Affected if The system has .ppp or .rdf files associated with CyberLink PowerProducer, indicating the application can be invoked when these files are opened.
  3. Assess current working directory behavior
    Test opening a .ppp or .rdf file from a directory that also contains mfc71loc.dll or mfc71enu.dll. Observe whether PowerProducer attempts to load these DLLs from the file's directory rather than its own installation folder.
    Affected if The application loads DLLs from the same directory as the opened media file rather than exclusively from its secure installation path.

A user is affected if CyberLink PowerProducer version 5.5.3.2325 is installed and the system has .ppp or .rdf files associated with this application, allowing potential DLL hijacking from untrusted directories.

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

Avoid opening CyberLink project files from untrusted or shared directories. Ensure the application directory is not writable by untrusted users. Consider upgrading to a patched version if available.

Fix this in Powerproducer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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