CVE-2012-4757
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 · uneditedMultiple untrusted search path vulnerabilities in CyberLink StreamAuthor 4.0 build 3308 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 .sta or .stp 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 confidenceCyberLink StreamAuthor 4.0 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 local attackers to place malicious DLLs in directories containing .sta or .stp files. When the application opens these files, it executes the attacker's DLL with elevated privileges.
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= 4.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm CyberLink StreamAuthor 4.0 installationCheck the Windows registry under HKLM\SOFTWARE\CyberLink\StreamAuthor or look for the application in Program Files (typically C:\Program Files\CyberLink\StreamAuthor). Verify the installed version by examining the executable's properties.Affected if StreamAuthor version 4.0 is installed on the system
-
Identify .sta and .stp file associationsCheck Windows registry for file associations under HKCR\.sta and HKCR\.stp to see if they are linked to StreamAuthor. Run 'assoc .sta' and 'assoc .stp' from command prompt.Affected if The system has .sta or .stp files associated with StreamAuthor 4.0
-
Check for vulnerable DLL files in application directoryNavigate to the StreamAuthor installation directory and verify the presence of mfc71loc.dll and mfc71enu.dll files in that folder.Affected if These DLLs exist in the StreamAuthor installation folder and the application may load them at runtime
-
Assess directory write permissions for .sta/.stp filesIdentify directories where .sta or .stp files are commonly stored (user documents, shared folders). Use 'icacls' command to check if untrusted users have Write permission to these directories.Affected if Users other than administrators can write to directories containing .sta or .stp files that would be opened by StreamAuthor
A user is affected if CyberLink StreamAuthor 4.0 is installed and .sta or .stp files can be opened from directories where untrusted users have write access, allowing DLL hijacking via mfc71loc.dll or mfc71enu.dll.
Generated from the published advisory. Verify against your own configuration.
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 dataAvoid opening .sta or .stp files from directories where untrusted users can write files. If a patched version is available from CyberLink, upgrade immediately. Otherwise, implement application controls to prevent loading DLLs from the current directory.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-4757 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-4757 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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