CVE-2022-44420
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 · uneditedIn modem, there is a possible missing verification of HashMME value in Security Mode Command. This could local denial of service with no additional execution privileges.
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 confidenceIn modem firmware, there is a missing verification of the HashMME value in Security Mode Command processing. This allows a local attacker to send a crafted Security Mode Command with an invalid HashMME, causing the modem to crash or hang, resulting in denial of service.
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.0= 12.0= 13.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.
-
Verify device has a cellular modemCheck if the Android device has a baseband/modem processor by examining /proc/cpuinfo for baseband info, or checking Settings > About Phone > SIM Status for baseband versionAffected if Device lacks a cellular modem (WiFi-only device), then not affected; devices with modems require further checks
-
Retrieve the baseband firmware versionRun 'getprop gsm.version.baseband' or check Settings > About Phone > Baseband version to obtain the modem firmware versionAffected if Unable to retrieve baseband version indicates non-standard or unpatched firmware that may be vulnerable
-
Identify the modem chipset and carrier-specific firmwareCheck /proc/cmdline or use 'getprop ro.baseband' to determine if the firmware is stock Android, carrier-branded, or OEM-specific (e.g., Qualcomm, MediaTek, Samsung, etc.)Affected if Carrier or OEM-specific firmware versions may have different patch timelines than stock Android
-
Confirm Security Mode Command processing is activeThis is inherent to LTE/5G modem operation - Security Mode Command is part of 3GPP connection procedures. Verify the device connects to cellular networks (check signal strength in Settings > Network or run 'service call iphonesubinfo' to confirm cellular service)Affected if Device has no cellular connectivity or is in airplane mode only, then the vulnerable processing path is not active
-
Compare installed baseband version against known vulnerable versionsSince official CVE detail lists Android 10-13 as affected ranges, compare your retrieved baseband version with vendor release notes or security bulletins for HashMME verification patchesAffected if Baseband firmware predates the HashMME verification fix or no patch information available from vendor
User is affected if the device runs Android 10-13 with a cellular modem whose baseband firmware lacks proper HashMME value validation in Security Mode Command processing, allowing crafted commands to crash the modem.
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 vendor-provided modem firmware update that includes proper HashMME value verification in Security Mode Command processing. Until patch is available, limit physical/logical access to the modem interface.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-44420 — 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-44420 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