dbcve.org
NimbuzzApplication

CVE-2011-4702

MEDIUM · 5.8 CVSS v2.0 Published 2012-01-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/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
The Nimbuzz (com.nimbuzz) application 2.0.8 and 2.0.10 for Android does not properly protect data, which allows remote attackers to read or modify a contact list 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 Nimbuzz Android application versions 2.0.8 and 2.0.10 fail to properly protect contact list data, allowing a malicious application installed on the same device to read or modify contacts due to insufficient data access controls or insecure local storage.

MitigationUpgrade to a patched version of Nimbuzz when available, and avoid installing untrusted third-party applications that could exploit this vulnerability.

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
NimbuzzApplication
Affected:= 2..0.10= 2.0.8

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
None

AV:N/AC:M/Au:N/C:P/I:P/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. Identify installed Nimbuzz version
    Go to Android Settings > Apps > Nimbuzz and view the Version information, or check the app info page for the version number
    Affected if The version listed is exactly 2.0.8 or 2.0.10
  2. Verify Nimbuzz has contacts permission
    Check Android Settings > Apps > Nimbuzz > Permissions. Confirm if the app has permission to access Contacts
    Affected if Contacts permission is granted and the vulnerable version (2.0.8 or 2.0.10) is installed
  3. Examine app data directory permissions
    Use a file manager with root access or ADB shell to navigate to /data/data/com.nimbuzz and list file permissions with 'ls -la'
    Affected if Contact-related database or XML files are world-readable (permissions show 'rwxrwxrwx' or 'rw-rw-rw--')
  4. Inspect local contact storage location
    Search within /data/data/com.nimbuzz for files containing 'contact' in the name, such as contacts.db, contacts.xml, or similar databases
    Affected if Contact data files exist in the app's private directory with insecure (world-readable) permissions

The environment is affected if Nimbuzz version 2.0.8 or 2.0.10 is installed and contact data files or the app data directory are readable by other applications.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of Nimbuzz when available, and avoid installing untrusted third-party applications that could exploit this vulnerability.

Fix this in Nimbuzz Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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