CVE-2021-25485
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 · uneditedPath traversal vulnerability in FactoryAirCommnadManger prior to SMR Oct-2021 Release 1 allows attackers to write file as system UID via BT remote socket.
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 · high confidencePath traversal vulnerability in FactoryAirCommandManager (a Samsung-related component) allows remote attackers to write files to arbitrary locations on the filesystem with system UID privileges via Bluetooth remote socket, potentially leading to complete system compromise.
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= 10.0= 11.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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/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.
-
Check Android versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADBAffected if Version is exactly 10.0 or 11.0 (not 9, 12, or later)
-
Verify FactoryAirCommandManager is installedCheck for package existence via ADB: 'pm list packages | grep aircommand' or check /system/priv-app/FactoryAirCommandManagerAffected if FactoryAirCommandManager package exists on the device
-
Check FactoryAirCommandManager versionRun 'dumpsys package com.samsung.android.aircommandmanager' via ADB and look for versionName or versionCode in the outputAffected if Version is earlier than SMR Oct-2021 Release 1 (patched version)
-
Verify Bluetooth is enabledCheck Bluetooth state via 'settings get global bluetooth_on' or through Settings UIAffected if Bluetooth is enabled (required attack vector)
Device is affected if running Android 10.0 or 11.0, has FactoryAirCommandManager installed with a version prior to SMR Oct-2021 Release 1, and has Bluetooth enabled.
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.
dbcve · scopedUpgrade FactoryAirCommandManager to SMR Oct-2021 Release 1 or later to obtain the patch for the path traversal vulnerability.
SMR Oct-2021 Release 1 or later
- Identify the Samsung device model and current SMR (Samsung Mobile Security) version installed
- Navigate to Settings > About Phone > Software Information to check the SMR version
- If the device is on Android 10.0 or 11.0 and has SMR version prior to Oct-2021 Release 1, check for available system updates
- Apply the system update to upgrade to SMR Oct-2021 Release 1 or later which contains the fix for FactoryAirCommandManager path traversal vulnerability
- Verify the SMR version after update confirms the device is running SMR Oct-2021 Release 1 or newer
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-25485 — 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-2021-25485 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