CVE-2013-0720
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 COBIME application before 0.9.4 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 COBIME Android application before version 0.9.4 uses overly permissive file permissions on certain files stored on the device's local filesystem. This allows any malicious application installed on the same device to read these files by exploiting the world-readable or group-readable permissions, potentially exposing sensitive user 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<= 0.9.3= 0.9.2CVSS 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.
-
Check if COBIME app is installedUse a package manager query or app list to search for an app named COBIME or Cobime installed on the device. On Android, you can use 'pm list packages' or check through device settings under Apps.Affected if The COBIME application is found installed on the device
-
Determine installed COBIME versionObtain the version number of the installed COBIME app. On Android, this can be done via 'pm dump <package_name> | grep version' or through the device Settings > Apps > COBIME page.Affected if The installed version is 0.9.3, 0.9.2, or any version lower than 0.9.4
-
Inspect file permissions on app data filesAccess the application's private data directory (typically under /data/data/<package_name>/files/ or /data/data/<package_name>/shared_prefs/) and list file permissions using 'ls -la'. Look for files with permissions showing 'r--r--r--' (644) or 'rwxrwxrwx' (777) which indicate world-readable access.Affected if Any sensitive files within the app's private directories show world-readable (others read bit set) or group-readable permissions
You are affected if COBIME version 0.9.3 or lower is installed AND sensitive files in its private data directory have world-readable or group-readable 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 dataUpdate COBIME to version 0.9.4 or later, which should contain corrected file permission settings. If update is not available, review and restrict file permissions in the application to use private mode (MODE_PRIVATE) for all sensitive files.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0720 — 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-0720 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