CVE-2020-35454
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 Taidii Diibear Android application 2.4.0 and all its derivatives allow attackers to obtain user credentials from an Android backup because of insecure application configuration.
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 Taidii Diibear Android application 2.4.0 and all derivatives have insecure backup configuration that allows attackers to obtain user credentials through Android backup extraction (adb backup or similar tools). The application likely has android:allowBackup enabled without proper data encryption, exposing sensitive user authentication 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.4.0CVSS 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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Confirm Taidii Diibear app is installedCheck installed applications on the Android device and identify the Taidii Diibear package. Note the installed version number.Affected if Version 2.4.0 is installed and the application contains user credentials
-
Extract the application APKUse adb pull or a file explorer to obtain the APK file from /data/app/ or the installed application package.Affected if The APK is successfully retrieved for analysis
-
Inspect AndroidManifest.xml for allowBackup settingDecompile the APK using apktool or similar tool, then open AndroidManifest.xml and locate the android:allowBackup attribute in the <application> tag.Affected if android:allowBackup is set to true, set to a non-false value, or is missing (defaults to true in Android)
-
Check for sensitive data encryptionAnalyze the application code and local storage directories (/data/data/<package>/shared_prefs/, databases in /data/data/<package>/databases/) to determine if user credentials are stored without encryption.Affected if User authentication data is stored in plain text or with weak encryption without Android Keystore protection
The environment is affected if Taidii Diibear version 2.4.0 is installed and the application has android:allowBackup enabled or defaults to enabled while storing credentials without Android Keystore encryption.
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 dataSet android:allowBackup="false" in AndroidManifest.xml and ensure any remaining sensitive data is encrypted using Android Keystore or equivalent cryptographic protection to prevent credential exposure through backup files.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-35454 — 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-2020-35454 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