dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2024-8039

CRITICAL · 9.8 CVSS v3.1 Published 2024-09-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Improper permission configurationDomain configuration vulnerability of the mobile application (com.afmobi.boomplayer) can lead to account takeover risks.

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 vulnerability involves improper permission configuration in the Android mobile application com.afmobi.boomplayer, likely allowing unauthorized access to sensitive data such as authentication credentials, session tokens, or user account information stored locally on the device. This misconfiguration could enable a malicious app or attacker with physical device access to read sensitive data and perform account takeover.

MitigationReview and restrict file system permissions, shared preferences, and local database access within the application to ensure sensitive authentication data is not world-readable or writable. Implement proper permission controls and consider encrypting stored credentials/tokens.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed version of boomplayer
    Check the app version in Android Settings > Apps > boomplayer, or use 'adb shell dumpsys package com.afmobi.boomplayer' to retrieve version info
    Affected if The installed version falls within an affected range if one is known; otherwise, the app may still be vulnerable regardless of version due to the permission misconfiguration
  2. Inspect shared preferences for sensitive data
    Access the app's private directory at /data/data/com.afmobi.boomplayer/shared_prefs/ and examine XML files for plaintext credentials, tokens, or session data
    Affected if Any sensitive authentication data such as usernames, passwords, auth tokens, or session IDs are stored in plain text in shared preferences files
  3. Check database files for unprotected credentials
    Locate SQLite databases in /data/data/com.afmobi.boomplayer/databases/ and inspect tables for authentication-related fields containing plaintext tokens or credentials
    Affected if Sensitive authentication data is found unencrypted in local database tables
  4. Verify file permissions on app storage directories
    Use 'ls -la /data/data/com.afmobi.boomplayer/' to check if directories are set to MODE_WORLD_READABLE or have overly permissive access controls
    Affected if Any app directories or files are world-readable or world-writable, allowing other apps to access stored data
  5. Examine internal file storage for sensitive artifacts
    Review files in /data/data/com.afmobi.boomplayer/files/ for configuration files, caches, or token stores that may contain authentication information
    Affected if Credentials, session tokens, or user account data are present in plain text within internal storage files

A user is affected if the app stores authentication credentials, session tokens, or sensitive account data in locations accessible to other apps or unauthorized physical access, particularly in shared preferences, databases, or files with overly permissive file system permissions.

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

Review and restrict file system permissions, shared preferences, and local database access within the application to ensure sensitive authentication data is not world-readable or writable. Implement proper permission controls and consider encrypting stored credentials/tokens.

Have this fixed 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-2024-8039 — 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-8039 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