CVE-2014-1939
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 · uneditedjava/android/webkit/BrowserFrame.java in Android before 4.4 uses the addJavascriptInterface API in conjunction with creating an object of the SearchBoxImpl class, which allows attackers to execute arbitrary Java code by leveraging access to the searchBoxJavaBridge_ interface at certain Android API levels.
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 confidenceAndroid WebView in versions before 4.4 exposes the searchBoxJavaBridge_ interface via addJavascriptInterface API, allowing arbitrary Java code execution through JavaScript. The SearchBoxImpl class object created in BrowserFrame.java permits attackers with JavaScript access to invoke native Java methods without proper validation.
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<= 4.3.1= 4.0= 4.0.1= 4.0.2= 4.0.3= 4.0.4= 4.1= 4.1.2= 4.2= 4.2.1= 4.2.2= 4.3<= 3.5.88_wwCVSS 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
- Partial
- Availability
- Partial
AV:N/AC:L/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.
-
Identify Android OS versionCheck the device Settings > About Phone > Android version, or use 'getprop ro.build.version.release' via ADB shellAffected if Version is 4.3.1 or earlier, including any 4.0.x, 4.1.x, 4.2.x, or 4.3 build
-
Identify Lenovo ShareIt versionCheck the app version in Settings > Apps > ShareIt > Version, or check the APK versionName in the manifestAffected if Version is 3.5.88_ww or earlier
-
Determine if WebView is usedSearch the application source code for 'android.webkit.WebView' imports and usage, or inspect the APK for WebView-related classesAffected if The application uses WebView component
-
Check for addJavascriptInterface usageSearch the source code for calls to 'addJavascriptInterface' method, or inspect compiled code for this method invocationAffected if The application calls addJavascriptInterface to expose Java objects to JavaScript
-
Verify searchBoxJavaBridge exposureFor Android <= 4.3, inject JavaScript to call 'searchBoxJavaBridge_' interface methods from WebView, or perform runtime reflection during WebView initializationAffected if The searchBoxJavaBridge_ interface is accessible and responds to JavaScript calls on Android 4.3.1 or earlier
The environment is affected if running Android 4.3.1 or earlier, or using Lenovo ShareIt 3.5.88_ww or earlier, and the application uses WebView with addJavascriptInterface that exposes the searchBoxJavaBridge_ interface.
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 affected Android devices to version 4.4 or later, or for applications targeting older Android versions, programmatically remove the searchBoxJavaBridge_ interface using reflection.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1939 — 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-2014-1939 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