CVE-2012-2649
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 Sleipnir Mobile application 2.2.0 and earlier and Sleipnir Mobile Black Edition application 2.2.0 and earlier for Android allow remote attackers to execute arbitrary Java methods, and obtain sensitive information or execute arbitrary commands, via a crafted web site.
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 Sleipnir Mobile Android applications (2.2.0 and earlier) expose Java methods to JavaScript in a WebView without proper validation, allowing a malicious website to invoke arbitrary Java methods, access sensitive data, and execute commands on the device. This is a classic WebView JavaScript interface exposure vulnerability common in older Android applications.
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.2.0= 1.0.0= 1.1.0= 1.2.0= 1.3.0= 1.4.0= 1.5.0= 1.5.1= 1.6.0= 1.7.0= 1.7.1= 2.0.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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 Sleipnir Mobile is installedCheck the Android device for the presence of the Sleipnir Mobile application in the app drawer or via package manager (adb shell pm list packages | grep -i sleipnir)Affected if The application is installed on the device
-
Determine installed versionOpen Google Play Store app page for Sleipnir Mobile, or check app info in Settings > Apps > Sleipnir Mobile > Version. Alternatively, use: adb shell dumpsys package com.fenrir.sleipnir | grep versionNameAffected if Version is 2.2.0 or earlier, or specifically matches 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.5.1, 1.6.0, 1.7.0, 1.7.1, or 2.0.0
-
Confirm WebView usageThe vulnerability exists within the WebView component that the browser uses to render web pages. This is core browser functionality and cannot be disabled separately.Affected if The app is used to browse the web, as the exposed JavaScript interface is present in the WebView implementation regardless of user configuration
The environment is affected if Sleipnir Mobile version 2.2.0 or earlier (including the specific listed versions) is installed and used for web browsing, because the app exposes Java methods to JavaScript in its WebView without validation.
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 dataUsers should update to a patched version if available. If no update exists, consider migrating to an alternative browser application. For developers, remove or properly secure JavaScript interfaces in WebViews, implement URL allow-listing, and validate all communication between web content and native code.
- 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-2649 — 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-2649 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