CVE-2012-3004
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 RealFlex RealWin before 2.1.13, FlexView before 3.1.86, and RealWinDemo before 2.1.13 allow local users to gain privileges via a Trojan horse (1) realwin.dll or (2) keyhook.dll file in the current working directory.
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 · high confidenceUntrusted search path vulnerability in RealFlex RealWin, FlexView, and RealWinDemo allows local privilege escalation via DLL hijacking. The applications load realwin.dll and keyhook.dll from the current working directory without validating the path, enabling attackers to place malicious DLLs in directories from which the application is run.
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<= 2.1.12= 1.06= 2.0= 2.1<= 3.1.85<= 2.1.12CVSS 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.
-
Identify installed RealFlex productsSearch for RealWin, FlexView, or RealWinDemo executables on the system using file explorer or command: dir /s /b C:\*RealWin*.exe C:\*FlexView*.exe 2>nulAffected if Any of these executables exist on the system
-
Check installed versionRight-click the executable, select Properties, and view the Version tab. Alternatively, run: wmic product where "name like '%RealWin%' or name like '%FlexView%'" get name,versionAffected if Version is 2.1.12 or earlier for RealWin/RealWinDemo, or 3.1.85 or earlier for FlexView, or matches 1.06, 2.0, or 2.1
-
Locate vulnerable DLL filesSearch for realwin.dll and keyhook.dll on the system: dir /s /b C:\*realwin.dll C:\*keyhook.dll 2>nulAffected if These DLL files exist in application directories or working directories
-
Verify DLL loading behaviorRun the application from different directories (e.g., Downloads folder) and monitor DLL loading using Process Monitor (procmon) from Sysinternals, filtering by the executable name and DLL namesAffected if The application loads realwin.dll or keyhook.dll from the current working directory instead of a trusted system path
If RealWin version 2.1.12 or earlier, FlexView 3.1.85 or earlier, or RealWinDemo 2.1.12 or earlier is installed and the application can load DLLs from its current working directory, the system is affected by this DLL hijacking vulnerability.
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 dataUpdate to RealWin 2.1.13, FlexView 3.1.86, or RealWinDemo 2.1.13 or later. Avoid running these applications from untrusted directories (e.g., downloads folder, network shares).
- Consultation2.0 h
- Implementation6.0 h
- Testing3.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 $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3004 — 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-3004 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