dbcve.org
LabelprintApplication · Cyberlink

CVE-2012-4756

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 LabelPrint 2.5.3602 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 .lpp 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 · moderate confidence

CyberLink LabelPrint 2.5.3602 contains an untrusted search path (DLL hijacking) vulnerability. The application loads DLL files (mfc71loc.dll or mfc71enu.dll) from the current working directory without validating the path, allowing a local attacker to place a malicious DLL in a directory containing a .lpp file. When a user opens the .lpp file, the application loads the attacker's DLL with elevated privileges, achieving local privilege escalation.

MitigationRemove write permissions for standard users in directories from which .lpp files may be opened; implement secure DLL loading by using full absolute paths or safe library loading functions; consider applying any available vendor patch if the product is still supported.

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
LabelprintApplication
Affected:= 2.5.3602

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. Identify installed CyberLink LabelPrint version
    Open Windows Control Panel, go to Programs and Features, locate CyberLink LabelPrint in the list, and note the version column. Alternatively, right-click the LabelPrint executable (typically in C:\Program Files\CyberLink\LabelPrint or C:\Program Files (x86)\CyberLink\LabelPrint), select Properties, and check the Details tab for Product Version.
    Affected if The installed version is exactly 2.5.3602
  2. Verify .lpp file association exists
    Check if .lpp files are associated with CyberLink LabelPrint by opening Command Prompt and running 'assoc .lpp' to see the file type, or check the default program settings in Windows. Also look for any .lpp files on the system to confirm the association is used.
    Affected if The system has .lpp files associated with CyberLink LabelPrint and these files are present on the system
  3. Test DLL loading from current working directory
    Create a test directory, place a test .lpp file inside it, then run CyberLink LabelPrint from that directory while monitoring DLL loads using Process Monitor (procmon) from Sysinternals. Filter procmon for the process LabelPrint.exe and look for attempts to load mfc71loc.dll or mfc71enu.dll from the current directory path.
    Affected if The application attempts to load mfc71loc.dll or mfc71enu.dll from the current working directory instead of only from the application installation folder
  4. Check directory permissions for .lpp file locations
    Identify common locations where .lpp files are stored (user Documents folders, Downloads, shared network drives). Right-click each directory, go to Properties, then the Security tab, and verify which users or groups have Write permission. Use 'icacls <directory>' from Command Prompt to list permissions explicitly.
    Affected if Standard users have Write permission to directories that contain .lpp files and from which those files might be opened

A system is affected if CyberLink LabelPrint version 2.5.3602 is installed, .lpp files are associated with it, and users can write to directories from which .lpp files may be opened, allowing DLL hijacking.

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

Remove write permissions for standard users in directories from which .lpp files may be opened; implement secure DLL loading by using full absolute paths or safe library loading functions; consider applying any available vendor patch if the product is still supported.

Fix this in Labelprint 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-2012-4756 — 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-4756 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