CVE-2022-20605
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 SAECOMM_CopyBufferBytes of SAECOMM_Utility.c, there is a possible out of bounds read due to an incorrect bounds check. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-231722405References: N/A
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 confidenceThis is an out-of-bounds read vulnerability in the Android kernel's SAECOMM (Secure Element Communication) module. The SAECOMM_CopyBufferBytes function in SAECOMM_Utility.c contains an incorrect bounds check, allowing reading beyond the allocated buffer boundary. This enables remote information disclosure without requiring any user interaction or additional privileges.
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 dataall versionsCVSS 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.
-
Check Android Security Patch LevelGo to Settings > About Phone > Security Patch Level and verify the date. For CVE-2022-20605, the fix was released in the January 2022 Android Security Bulletin.Affected if The Security Patch Level is earlier than January 2022, or the field shows an unpatched version.
-
Verify SAECOMM module presenceOn a rooted device or via adb, check if the SAECOMM kernel module is loaded or present: ls -la /sys/module/ | grep saecomm or check /proc/modules for saecomm entries.Affected if The SAECOMM module is loaded on the device.
-
Confirm kernel source includes the fixIf you have access to the kernel source or kernel config, verify that SAECOMM_Utility.c contains the corrected bounds check in the SAECOMM_CopyBufferBytes function.Affected if The source code still shows the original vulnerable bounds check logic, or the patch is not present.
-
Check vendor-specific kernel versionRun 'uname -r' or check /proc/version to identify the kernel version, then compare against the kernel version that includes the AOSP fix for this CVE.Affected if The running kernel version predates the January 2022 Android kernel security update.
A device is affected if its Android Security Patch Level predates the January 2022 update AND the SAECOMM module is present and active on the device.
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 Android kernel security patch for CVE-2022-20605 once released by the device manufacturer or through the Android Open Source Project (AOSP) kernel updates. Users should ensure their devices receive regular security updates.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20605 — 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-20605 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