dbcve.org
Kaku San Sei Million AruthurApplication · Square Enix Co Ltd

CVE-2014-7259

MEDIUM · 5.0 CVSS v2.0 Published 2014-12-05
Fix available
A fix is available. Upgrade to after 1.0.1 or later.
See remediation →
59/100
Remediation priority · Elevated
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
SQUARE ENIX Co., Ltd. Kaku-San-Sei Million Arthur before 2.25 for Android stores "product credentials" on the SD card, which allows attackers to gain privileges via a crafted application.

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 Kaku-San-Sei Million Arthur Android application before version 2.25 insecurely stores product credentials on the external SD card. Since external storage is globally readable by other applications on unpatched Android versions, a malicious application can harvest these credentials and impersonate the user or gain elevated privileges within the app.

MitigationUpdate to version 2.25 or later, which should implement secure credential storage using Android's internal storage or the Android Keystore system instead of external SD card storage.

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
Kaku San Sei Million AruthurApplication
Affected:<= 1.0.1

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
Low
Authentication
None
Confidentiality
Partial
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:P/I:N/A:N

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 Kaku San Sei Million Arthur is installed
    Use PackageManager to query for packages matching 'com.square_enix.million_arthur' or list installed applications and look for this app
    Affected if The app is present on the device
  2. Determine the installed version
    Query PackageManager for PackageInfo of the app and retrieve the versionCode or versionName
    Affected if Version is 1.0.1 or earlier (versionCode <= 1.0.1)
  3. Inspect external storage for app data
    Examine the external storage directory (typically /storage/emulated/0/ or /mnt/sdcard/) for subdirectories or files belonging to the app (commonly under Android/data/ or a folder named after the app)
    Affected if Credential files, configuration files with credentials, or authentication tokens are found in publicly accessible external storage locations

A user is affected if the Kaku San Sei Million Arthur app version 1.0.1 or earlier is installed and credential-related files exist on external storage that other apps could access.

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.0.1
Interim mitigation

Update to version 2.25 or later, which should implement secure credential storage using Android's internal storage or the Android Keystore system instead of external SD card storage.

Fix this in Kaku San Sei Million Aruthur Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-7259 — 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-2014-7259 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