CVE-2024-44336
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 · uneditedAn issue in AnkiDroid Android Application v2.17.6 allows attackers to retrieve internal files from the /data/data/com.ichi2.anki/ directory and save it into publicly available storage.
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 confidenceAnkiDroid v2.17.6 contains an improper file access control vulnerability that allows attackers to read internal application files from the private /data/data/com.ichi2.anki/ directory and write them to publicly accessible external storage. This exposes potentially sensitive application data that should remain confined to the app's private sandbox.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Identify installed AnkiDroid versionRun 'adb shell dumpsys package com.ichi2.anki | grep versionName' or check the app's About screen in the applicationAffected if The installed version is 2.17.6 or lower (if earlier versions share the vulnerable code path)
-
Check if app has external storage write permissionRun 'adb shell dumpsys package com.ichi2.anki' and look for WRITE_EXTERNAL_STORAGE or MANAGE_EXTERNAL_STORAGE in the permissions section, or inspect the APK's manifestAffected if The app holds WRITE_EXTERNAL_STORAGE or MANAGE_EXTERNAL_STORAGE permission enabling write access to shared external storage
-
Verify internal data directory existsRun 'adb shell ls -la /data/data/com.ichi2.anki/' to confirm the app's private sandbox directory is presentAffected if The /data/data/com.ichi2.anki/ directory exists, indicating the app is installed and has created its private sandbox
-
Check for files written to public external storageRun 'adb shell ls -la /storage/emulated/0/' and search for directories or files belonging to AnkiDroid (typically under Android/data/com.ichi2.anki/)Affected if AnkiDroid files appear in shared external storage locations outside the app's private sandbox
A user is affected if AnkiDroid version 2.17.6 is installed and the app has written internal data from /data/data/com.ichi2.anki/ to accessible external storage locations.
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 dataDeveloper should review file handling code to ensure internal app data cannot be written to external/public storage, implement proper Android storage permission checks, and use scoped storage APIs to enforce proper data isolation between internal and external storage locations.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2024-44336 — 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-2024-44336 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