CVE-2013-3646
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 Live application before 2.0.1 for Android allows remote attackers to execute arbitrary Java methods, and obtain sensitive information or execute arbitrary commands, via a crafted web site. NOTE: this vulnerability exists because of a CVE-2012-4008 regression.
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 confidenceThe Cybozu Live Android application before version 2.0.1 contains a vulnerability allowing remote attackers to execute arbitrary Java methods via a crafted website. This occurs due to improper validation or exposure of Java interfaces in the Android WebView component, enabling attackers to invoke native methods, access sensitive device data, or execute arbitrary commands on the device.
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.0= 1.0.4CVSS 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 Cybozu Live is installedOn the Android device, go to Settings > Apps > Apps list and search for 'Cybozu Live', or use ADB: adb shell pm list packages | grep -i cybozuAffected if The Cybozu Live application is present on the device
-
Determine installed Cybozu Live versionIn Settings > Apps > Cybozu Live, view the Version information under App details, or use ADB: adb shell dumpsys package <package_name> | grep versionNameAffected if The displayed version is 2.0.0 or earlier, specifically <= 2.0.0 or exactly 1.0.4
-
Check if WebView JavaScript bridge is exposedThis requires reverse-engineering the APK to inspect the addJavascriptInterface calls in WebView implementations. Use tools like jadx to decompile and search for 'addJavascriptInterface' in the source code.Affected if The app code contains addJavascriptInterface calls exposing Java methods to JavaScript without proper restrictions
-
Assess sensitivity of device data accessible to the appReview the permissions granted to Cybozu Live in Settings > Apps > Cybozu Live > Permissions. Common high-risk permissions include Camera, Contacts, Storage, Location, and Phone.Affected if The app has been granted permissions to sensitive device data (contacts, storage, camera, location) and runs a vulnerable version
A user is affected if Cybozu Live version 2.0.0 or earlier (including 1.0.4) is installed and the app has access to sensitive device data through its granted permissions.
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 Cybozu Live to version 2.0.1 or later. Developers must remove or properly restrict JavaScript-to-Java bridges in WebView components and implement proper URL validation for incoming intents.
- 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-2013-3646 — 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-2013-3646 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