CVE-2012-4011
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 Cybozu KUNAI application before 2.0.6 for Android allows 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 confidenceCybozu KUNAI Android app before version 2.0.6 contains a vulnerability allowing remote attackers to execute arbitrary Java methods, obtain sensitive information, and execute arbitrary commands via a crafted website. The attack likely exploits an insecure WebView or JavaScript bridge implementation that exposes native app functionality to web content.
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.0.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
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/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.
-
Check installed Cybozu KUNAI versionOpen Android Settings > Apps > Cybozu KUNAI, or run 'adb shell dumpsys package com.cybozu.kunai' to view the package versionAffected if The displayed version is 2.0.5 or lower
-
Verify WebView component exists in appInspect the app APK or use a decompiler to check for WebView usage in the app's code, specifically looking for WebView.addJavascriptInterface() callsAffected if The app contains a WebView with JavaScript interface binding exposed to web content
-
Confirm JavaScript bridge exposureReview the app's source code (if available) or network traffic to determine if native Java methods are callable from JavaScript through the WebViewAffected if The WebView implementation allows arbitrary Java methods to be invoked from loaded web pages
-
Test for exposed native methodsIf the app can load arbitrary URLs, attempt to access a controlled webpage that tries to invoke Java methods through the JavaScript bridge (for example: 'javascript:window.Android.methodName()')Affected if Java methods from the app are accessible and executable from web content loaded in the WebView
You are affected if Cybozu KUNAI version 2.0.5 or earlier is installed and the app contains a WebView with exposed JavaScript interfaces that allow remote web content to invoke native methods.
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.
dbcve · scopedUpdate Cybozu KUNAI to version 2.0.6 or later. Until updated, users should avoid visiting untrusted websites and disable any web browsing features within the application.
Kunai 2.0.6
- 1. Open the Google Play Store app on your Android device
- 2. Search for "Cybozu KUNAI" or "KUNAI"
- 3. If the app is installed, check the current version in app settings
- 4. Update the application to version 2.0.6 or later
- 5. Alternatively, uninstall the current version and reinstall version 2.0.6 from a trusted source
- 6. Verify the installed version is 2.0.6 or higher after update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-4011 — 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-4011 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