CVE-2022-23428
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 improper boundary check in eden_runtime hal service prior to SMR Feb-2022 Release 1 allows arbitrary memory write and code execution.
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 boundary check vulnerability in the eden_runtime hardware abstraction layer (HAL) service allows an attacker to write to arbitrary memory addresses and achieve code execution. This memory corruption flaw exists in Samsung mobile devices running software prior to the February 2022 SMR release.
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.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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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.
-
Confirm device is a Samsung Android deviceCheck the device manufacturer via 'getprop ro.product.manufacturer' or inspect Settings > About Phone > ManufacturerAffected if Manufacturer is not Samsung (this vulnerability is Samsung-specific)
-
Verify Android version is affectedRun 'getprop ro.build.version.release' or check Settings > Android VersionAffected if Version is 10.0, 11.0, or 12.0 (versions outside this range are not affected)
-
Check for the eden_runtime HAL serviceLook for '/vendor/lib64/hw/eden_runtime.default.so' or run 'ls /vendor/lib*/hw/eden_runtime*'Affected if The eden_runtime HAL library exists on the device (vulnerability only applies when this component is present)
-
Determine the SMR (Samsung Maintenance Release) version and dateRun 'getprop ro.build.version.smr' or check Settings > About Phone > Software Information > SMR version. The format is typically SMR-xx-xxxx (e.g., SMR-01-2022)Affected if The SMR version date is prior to February 2022 (e.g., SMR-01-2022 or earlier, or the property is empty/unavailable indicating older firmware)
User is affected if running a Samsung Android device on version 10.0, 11.0, or 12.0 with the eden_runtime HAL present, and the SMR firmware is older than the February 2022 release.
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 · scopedApply the Samsung SMR February-2022 Release 1 or later firmware update to patch the boundary check vulnerability in the eden_runtime HAL service.
SMR Feb-2022 Release 1 or later
- Identify your Samsung device model number (found in Settings > About Phone)
- Navigate to Settings > Software Update on your Samsung device
- Check for and install the latest Samsung security update
- Verify the installed SMR (Samsung Mobile Security) version is February 2022 Release 1 or later in Settings > Software Update > SMR version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23428 — 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-23428 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