CVE-2011-0452
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 the script function in Lunascape before 6.4.3 allows local users to gain privileges via a Trojan horse executable 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 Lunascape's script function allows local privilege escalation. The application executes Trojan horse executables from the current working directory instead of using fully qualified paths, enabling attackers to place malicious executables that run 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<= 6.4.2= 3.0.0= 3.0.1= 3.1.0= 3.5.0= 3.5.1= 3.5.2= 3.5.3= 3.5.4= 3.6.0= 3.6.1= 3.6.2CVSS 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
- High
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:H/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 Lunascape installation and versionCheck the program's installation directory (commonly C:\Program Files\Lunascape\ or C:\Program Files (x86)\Lunascape\) and look for a version file or check file properties of the main executable (lunascape.exe). Alternatively, check Add/Remove Programs or the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Lunascape for the installed version.Affected if The installed version matches <= 6.4.2, or equals 3.0.0, 3.0.1, 3.1.0, 3.5.0, 3.5.1, 3.5.2, 3.5.3, 3.5.4, 3.6.0, 3.6.1, or 3.6.2.
-
Identify if the script function is usedDetermine whether the Lunascape script function feature is enabled or has been invoked. This may be visible in user scripts, add-ons, or automated tasks that call Lunascape's scripting interface. Check for any .lua or custom script files that interact with Lunascape.Affected if The script function feature is actively used or enabled in the environment.
-
Verify working directory at runtimeObserve the current working directory (CWD) when Lunascape is launched. If launched from a command prompt, note the directory from which the command is executed. Check if the application is launched from directories writable by other users (such as shared folders, downloads, or user-controlled paths).Affected if Lunascape is executed from a directory writable by untrusted users, or if the CWD contains executable files with common names that could be replaced by an attacker.
-
Check for vulnerable DLL/executable plantingAudit the common launch directories for unexpected executables that match typical system tool names (e.g., cmd.exe, net.exe, tasklist.exe) that could be exploited via the untrusted search path. Use file system auditing to detect new executables in directories where Lunascape is run.Affected if Suspicious executables exist in directories from which Lunascape is typically launched, indicating potential exploitation attempt.
A user is affected if Lunascape version is 6.4.2 or lower (or matches one of the specific affected versions 3.x) and the script function feature is used while the application is run from or executes in directories writable by untrusted users.
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 version 6.4.3 or later, which implements fully qualified path resolution. As a compensating control, avoid running Lunascape from directories writeable by untrusted users.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-0452 — 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-2011-0452 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