CVE-2013-2300
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 FlickWnn (aka OpenWnn/Flick support) application 2.02 and earlier for Android uses weak permissions for unspecified files, which allows attackers to obtain sensitive information via an application that accesses the local filesystem.
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 confidenceThe FlickWnn Android input method application versions 2.02 and earlier stores certain files with overly permissive access controls, making them world-readable. This allows any other application installed on the same device to read these files without permissions, potentially exposing sensitive user data such as dictionary entries, user preferences, or cached input data.
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.02CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify FlickWnn is installedCheck if the FlickWnn input method app is present on the Android device. Use adb shell to list installed packages with 'pm list packages' and search for 'flickwnn' or 'FlickWnn', or manually check the device's installed applications.Affected if FlickWnn (Pm9 Flickwnn) is found installed on the device.
-
Check installed FlickWnn versionRetrieve the version of the installed FlickWnn application. Use 'adb shell dumpsys package <package_name>' to get version info, or view the app version in the device's Application Manager under FlickWnn settings.Affected if The installed version is 2.02 or any version lower than 2.02.
-
Inspect FlickWnn data directory permissionsUsing adb shell, navigate to the app's private data directory (typically under /data/data/) and list file permissions with 'ls -la'. Check if files or directories within the app's storage have world-readable permissions (r--r--r-- or similar).Affected if Files in the app's data directory show world-readable (others have read permission) access controls.
-
Identify sensitive files in app storageList all files within the FlickWnn app data directory. Look for files that may contain dictionary data, user preferences, or cached input (commonly named like dictionary.txt, userdict.db, prefs.xml, or cache files).Affected if Sensitive files such as dictionaries, preference files, or cached input data exist and are world-readable.
A user is affected if FlickWnn version 2.02 or earlier is installed and its data files have world-readable permissions, allowing other apps to access sensitive user data.
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 dataUpdate to a patched version of FlickWnn. If no update is available, verify that any sensitive data files created by the application use Android's private file storage (MODE_PRIVATE) rather than world-readable modes, and consider removing the application until a fix is available.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2300 — 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-2300 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