dbcve.org
Twidroyd LegacyApplication · Ubermedia

CVE-2011-4699

MEDIUM · 6.4 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 →
73/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 Ubermedia Twidroyd Legacy (com.twidroydlegacy) application 4.3.11 for Android does not properly protect data, which allows remote attackers to read or modify Twitter information 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 Ubermedia Twidroyd Legacy Android application (version 4.3.11) fails to properly protect data, enabling a malicious application on the same device to access or manipulate Twitter credentials and session information stored or processed by the app.

MitigationImplement proper data protection mechanisms including encrypted local storage, secure inter-process communication, and avoid storing sensitive Twitter credentials in plaintext or accessible locations.

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
Twidroyd LegacyApplication
Affected:= 4.3.11

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
Partial
Availability
None

AV:N/AC:L/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. Check installed Twidroyd version
    Open Android Settings > Apps > Twidroyd Legacy and view the version information under App Info, or run 'adb shell dumpsys package com.ubermedia.twidroyd' to retrieve package details
    Affected if Version displayed is exactly 4.3.11
  2. Verify app is the legacy variant
    Confirm the package name is com.ubermedia.twidroyd (not a newer or alternate version) by checking the app identifier in the Play Store or app settings
    Affected if Package name matches com.ubermedia.twidroyd and version is 4.3.11
  3. Assess data exposure risk
    Examine if the app stores Twitter credentials or session tokens in shared preferences, files, or databases under /data/data/com.ubermedia.twidroyd/ that could be accessed by other apps (requires root or a malicious app with same UID)
    Affected if Credentials or session tokens are stored in plaintext or accessible storage locations

User is affected if Twidroyd Legacy version 4.3.11 is installed and the app stores Twitter credentials or session data in an unprotected manner accessible to other applications on the device.

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

Implement proper data protection mechanisms including encrypted local storage, secure inter-process communication, and avoid storing sensitive Twitter credentials in plaintext or accessible locations.

Fix this in Twidroyd Legacy Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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