CVE-2022-27250
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 · uneditedThe UNISOC chipset through 2022-03-15 allows attackers to obtain remote control of a mobile phone, e.g., to obtain sensitive information from text messages or the device's screen, record video of the device's physical environment, or modify data.
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 critical vulnerability in UNISOC chipsets allows remote attackers to gain unauthorized control of affected mobile devices, enabling data exfiltration (text messages, screen capture), surreptitious video recording, and data modification.
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<= 2022-03-15CVSS 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.
-
Identify Unisoc chipset in deviceCheck device hardware specifications or system information to confirm the presence of a Unisoc (also known as Spreadtrum or SC) cellular modem or SoC chipset. On Android, this may appear in 'About Phone' under 'Baseband' or 'Modem' or in kernel boot logs.Affected if The device contains a Unisoc chipset or modem
-
Determine chipset firmware versionRetrieve the baseband/modem firmware version from the device. On Android, access Settings > About Phone > Baseband version, or use terminal commands like 'AT+CGMR' (modem AT command) or check /proc/cpuinfo for chipset identifiers.Affected if Unable to determine firmware version or version is unknown
-
Check firmware date against cutoffCompare the installed baseband/modem firmware date to the cutoff date of 2022-03-15. The firmware date may be embedded in the version string or require checking with the device OEM or Unisoc documentation.Affected if Firmware build date is on or before 2022-03-15
-
Verify carrier settings versionCheck the carrier settings or operator settings version on the device, as these can include baseband configurations. On Android, this may be in Settings > About Phone > SIM status or through the service menu (*#*#4636#*#*).Affected if Carrier settings are outdated or from before March 2022
-
Inspect modem baseband logsReview baseband kernel logs (dmesg | grep -i baseband) or modem diagnostic logs for any anomalies, unexpected AT commands, or indicators of unauthorized modem configuration changes.Affected if Logs show unexplained modem reconfiguration attempts or suspicious AT command activity
The device is affected if it contains a Unisoc chipset with baseband/modem firmware dated on or before 2022-03-15, as this vulnerability resides in the chipset firmware itself.
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 chipset/firmware updates from UNISOC and device OEMs; until patches are available, minimize risk by avoiding untrusted networks and monitoring device behavior for indicators of compromise.
- Consultation24.0 h
- Implementation16.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $18,432.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27250 — 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-2022-27250 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