CVE-2010-3927
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 · uneditedUntrusted search path vulnerability in Lunascape before 6.4.0 allows local users to gain privileges via a Trojan horse DLL 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 Lunascape before version 6.4.0 allows local privilege escalation through DLL preloading. The application loads dynamic link libraries from the current working directory without validating the full path, enabling an attacker to place a malicious DLL with a legitimate-sounding name that gets loaded with the application's 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<= 6.3.4= 4.1= 4.1.1= 4.1.2= 4.1.3= 5.0= 5.1= 5.1.0= 5.1.2= 5.1.3= 5.1.4= 5.1.5CVSS 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.
-
Locate installed Lunascape versionCheck the Windows registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Lunascape (or HKCU for per-user installs) for the DisplayVersion value, or inspect the executable properties of lunascape.exe in the installation folder.Affected if The version displayed is 6.3.4 or lower, or matches any of these: 4.1, 4.1.1, 4.1.2, 4.1.3, 5.0, 5.1, 5.1.0, 5.1.2, 5.1.3, 5.1.4, 5.1.5.
-
Confirm Lunascape is installedLook for lunascape.exe in typical installation paths such as C:\Program Files\Lunascape\Lunascape6\ or C:\Program Files (x86)\Lunascape\.Affected if Lunascape is present on the system.
-
Determine execution contextIdentify whether the application is launched from or could be launched from user-writable directories such as Downloads, Desktop, or temporary folders. Check shortcuts and startup entries for the working directory configuration.Affected if The current working directory when launching Lunascape can be controlled by an untrusted user or is a world-writable location.
-
Check for vulnerable DLL loading behaviorObserve Lunascape startup using a process monitor tool (such as Sysinternals Process Monitor) and filter for DLL load events. Look for DLLs loaded from paths other than the application directory.Affected if DLLs are being loaded from the current working directory (CWD) rather than always using full paths from the application directory.
You are affected if Lunascape version is 6.3.4 or lower (or matches one of the specific affected versions) AND the application can be run from or inherits a current working directory controlled by an untrusted user.
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 dataUpgrade to Lunascape 6.4.0 or later which implements safe DLL loading. As a workaround, avoid running the application from user-writable directories such as Downloads or Desktop, and ensure the current working directory cannot be controlled by untrusted users.
- Consultation2.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-3927 — 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-2010-3927 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