dbcve.org
Command InjectionWeakness · CWE-77

CVE-2024-33469

HIGH · 7.9 CVSS v3.1 Published 2025-02-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
An issue in Team Amaze Amaze File Manager v.3.8.5 and fixed in v.3.10 allows a local attacker to execute arbitrary code via the onCreate method of DatabaseViewerActivity.java.

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

A local privilege escalation exists in Amaze File Manager v3.8.5 and earlier where the onCreate method of DatabaseViewerActivity.java does not properly validate input, allowing a local attacker to execute arbitrary code with the application's privileges.

MitigationUpgrade Amaze File Manager to v3.10 or later to obtain the security patch.

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
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:H/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 Amaze File Manager version
    Open Android Settings > Apps > Amaze File Manager, or use ADB command: `adb shell pm list packages -3 | grep amaze` then `adb shell dumpsys package <packagename> | grep versionName`
    Affected if Version is 3.8.5 or earlier, or version name cannot be determined (indicating outdated release)
  2. Verify DatabaseViewerActivity component exists
    Use ADB to check if the vulnerable activity is exported: `adb shell pm dump com.amaze.filemanager | grep -A 20 DatabaseViewerActivity`
    Affected if The DatabaseViewerActivity component is present and accessible (check for 'exported=true' or if the activity can be launched)

User is affected if Amaze File Manager version is 3.8.5 or earlier AND the DatabaseViewerActivity feature is accessible 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Amaze File Manager to v3.10 or later to obtain the security patch.

Recommended fix High confidence

Amaze File Manager v3.10

  1. Upgrade Amaze File Manager from v3.8.5 to v3.10 or later
  2. Verify the upgrade by checking the app version in Settings > Apps > Amaze File Manager > Version
  3. Ensure the device is running a compatible Android version (Android 5.0+ recommended)
  4. After upgrade, test the Database Viewer functionality to confirm normal operation

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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 locally
dbcve dependency scanner

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