CVE-2012-1249
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 · uneditedThe iLunascape application 1.0.4.0 and earlier for Android does not properly implement the WebView class, which allows remote attackers to obtain sensitive stored information via a crafted application.
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 confidenceThe iLunascape Android application versions 1.0.4.0 and earlier contain a vulnerability in how the WebView class is implemented. The improper implementation allows a malicious application installed on the same device to access sensitive information stored locally on the device through the WebView component.
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<= 1.0.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
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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.
-
Verify iLunascape Android app is installedCheck device or app inventory for 'Lunascape' or 'iLunascape' Android application. Use 'adb shell pm list packages' or check device Settings > AppsAffected if The app is installed and its version is 1.0.4.0 or earlier
-
Confirm installed app versionCheck the app version in Play Store info, app settings, or use 'adb shell dumpsys package <package_name>' to retrieve versionCode and versionNameAffected if Version name is 1.0.4.0 or lower, or versionCode corresponds to 1.0.4.0 or earlier
-
Identify if WebView component is usedAnalyze the app APK for usage of android.webkit.WebView class. Use 'adb shell pm dump <package_name>' and look for WEBVIEW component, or decompile APK and search for 'Landroid/webkit/WebView;'Affected if The app implements and uses the WebView class in its code
-
Inspect WebView JavaScript configurationDecompile the APK and inspect source code for addJavascriptInterface() calls and setJavaScriptEnabled(true). Search for 'addJavascriptInterface' and 'setJavaScriptEnabled' in Smali or Java sourcesAffected if WebView has JavaScript enabled AND exposes a Java object via addJavascriptInterface, creating a bridge from JavaScript to local Java methods
-
Check WebView file access settingsSearch the decompiled source for setAllowFileAccess(true) or setAllowContentAccess(true) calls on the WebView objectAffected if WebView has file access enabled from JavaScript (setAllowFileAccess is true), allowing a malicious page to read local device files
The environment is affected if iLunascape Android version 1.0.4.0 or earlier is installed AND the app's WebView implementation exposes JavaScript interfaces or enables file access from JavaScript.
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 dataThe WebView implementation should be reviewed and secured—typically by removing unnecessary JavaScript interface exposure, disabling file URL access from JavaScript, and ensuring the WebView does not expose sensitive local data or device resources to untrusted content.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-1249 — 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-1249 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