CVE-2020-25050
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 was discovered on Samsung mobile devices with P(9.0) and Q(10.0) software. The CMC service allows attackers to obtain sensitive information. The Samsung ID is SVE-2020-17288 (August 2020).
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 confidenceThe CMC (Call Manager Component) service on Samsung mobile devices running Android P (9.0) and Q (10.0) contains an information disclosure vulnerability (SVE-2020-17288). Attackers can obtain sensitive information through this service without authentication, indicating a network-exploitable vector with low attack complexity, as reflected by the CVSS 7.5 rating.
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= 9.0= 10.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 device manufacturer and modelCheck if the device is a Samsung mobile device through Settings > About Phone > Manufacturer or ModelAffected if Device is not a Samsung brand - the vulnerability applies specifically to Samsung mobile devices
-
Verify Android OS versionCheck Settings > About Phone > Android version - confirm if it equals 9.0 (Android P) or 10.0 (Android Q)Affected if Android version is 9.0 or 10.0 - only these specific versions are affected according to the CVE
-
Check Samsung security patch levelCheck Settings > About Phone > Security patch level - verify the date of the installed Samsung security updateAffected if Security patch level is earlier than August 2020, indicating the SVE-2020-17288 fix has not been applied
-
Assess CMC service exposureReview network listening services or ports on the device - the CMC (Call Manager Component) service should not be exposed to unauthenticated network accessAffected if CMC service is running and accessible over network without authentication credentials
Device is affected if it is a Samsung mobile device running Android 9.0 or 10.0 with a security patch level earlier than August 2020, as the vulnerability allows unauthenticated network access to the CMC service for information disclosure.
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 dataApply the August 2020 Samsung security patch (SVE-2020-17288) to all affected Samsung mobile devices running Android P (9.0) or Q (10.0). Verify patch deployment through Samsung KNOX or mobile device management solutions.
- 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-2020-25050 — 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-2020-25050 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