dbcve.org
YodobashiApplication

CVE-2015-2980

MEDIUM · 6.8 CVSS v2.0 Published 2015-08-08
Fix available
A fix is available. Upgrade to after 1.2.1.0 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
The Yodobashi application 1.2.1.0 and earlier for Android allows remote attackers to execute arbitrary Java methods, and consequently obtain sensitive information or execute OS commands, via a crafted HTML document.

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 confidence

The Yodobashi Android application exposes a JavaScript interface in its WebView component that allows any HTML document to invoke arbitrary Java methods. This vulnerability allows a remote attacker who can deliver a crafted HTML document to the device to execute Java code, potentially leading to sensitive data exfiltration and OS command execution.

MitigationRemove or disable the JavaScript interface from the WebView unless strictly required, or implement proper origin validation to restrict which web content can invoke the exposed Java methods.

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
YodobashiApplication
Affected:<= 1.2.1.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Yodobashi app is installed
    On the Android device, go to Settings > Apps > Applications Manager and look for 'Yodobashi' or 'Yodobashi Yodobashi' in the installed applications list. Alternatively, use ADB command: `adb shell pm list packages | grep yodobashi`
    Affected if The Yodobashi application is found installed on the device
  2. Verify installed application version
    In Settings > Apps > Applications Manager, tap on the Yodobashi app and view the 'Version' or 'Version info' field. Alternatively, use ADB: `adb shell dumpsys package <package_name>` and look for versionName or versionCode
    Affected if The version number is 1.2.1.0 or lower
  3. Identify the application package name
    Use ADB to list package details: `adb shell pm list packages -3` to find the full package name for Yodobashi, or check the app info in Settings which typically shows the package name
    Affected if Package name is identified for further analysis
  4. Determine if WebView with JavaScript interface is in use
    This requires static analysis of the APK file. Decompile the APK using tools like apktool, then search for 'addJavascriptInterface' in the Smali or decompiled Java code, specifically within any WebView implementations
    Affected if The code contains addJavascriptInterface calls exposing Java methods to JavaScript without explicit origin restrictions
  5. Check for origin validation in WebView configuration
    In the decompiled APK, examine any WebView-related code for setJavaScriptEnabled(true) and review if setAllowFileAccess, setAllowContentAccess, or shouldOverrideUrlLoading have proper origin/scheme validation implemented. Look for whitelist implementations or lack thereof
    Affected if JavaScript is enabled and no whitelist or origin validation is found on the WebView configuration

The environment is affected if the Yodobashi Android application is installed with version 1.2.1.0 or lower and the app uses a WebView component with addJavascriptInterface exposed to web content without origin-based access controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.2.1.0
Interim mitigation

Remove or disable the JavaScript interface from the WebView unless strictly required, or implement proper origin validation to restrict which web content can invoke the exposed Java methods.

Fix this in Yodobashi Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-2980 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-2980 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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