CVE-2025-6172
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 · uneditedPermission vulnerability in the mobile application (com.afmobi.boomplayer) may lead to the risk of unauthorized operation.
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 confidenceA permission vulnerability exists in the mobile application com.afmobi.boomplayer that allows improper access to protected functionality, potentially enabling an attacker to perform unauthorized operations on the device or user data.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm the application is installedCheck if com.afmobi.boomplayer exists on the device by reviewing installed applications via device settings, MDM inventory, or using ADB command: adb shell pm list packages | grep boomplayerAffected if The package com.afmobi.boomplayer is present on the device
-
Retrieve the installed application versionUse ADB: adb shell dumpsys package com.afmobi.boomplayer | grep versionName, or check via Google Play Store/alternative app store if installed from thereAffected if Unable to obtain a version or version is unknown/older than current release
-
Review granted permissionsExecute: adb shell dumpsys package com.afmobi.boomplayer | grep -E "(android.permission|runtime)" to list all permissions the app has been granted, or manually inspect in Settings > Apps > Boom Player > PermissionsAffected if The app has been granted permissions beyond what is necessary for core audio playback functionality, especially sensitive permissions like READ_CONTACTS, WRITE_EXTERNAL_STORAGE, or INTERNET if not required
-
Check for exported componentsUse ADB: aapt dump badging /path/to/apk.apk | grep exported, or analyze the AndroidManifest.xml for activity, service, or receiver elements with android:exported="true" that lack proper permission checksAffected if The application exposes components (activities, services, broadcast receivers) that are exported without requiring proper permissions for access
-
Verify permission enforcement on sensitive operationsReview application behavior by attempting to access protected features through intent-based calls from another app, or analyze the app's code/library if available for missing permission checks on sensitive functionsAffected if Protected functionality can be accessed by other apps without the Boom Player holding the required permissions or without user consent
A user is affected if the com.afmobi.boomplayer application is installed and possesses permissions or exported components that allow other applications or unauthorized users to access protected device functionality or user data without proper authorization checks.
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 dataUpdate the application to the latest version which should contain proper permission controls; review and restrict permission grants to only what is strictly necessary for the application's core functionality.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6172 — 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-2025-6172 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