CVE-2022-28789
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 · uneditedUnprotected activities in Voice Note prior to version 21.3.51.11 allows attackers to record voice without user interaction. The patch adds proper permission for vulnerable activities.
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 Android application vulnerability in Voice Note where unprotected activity components allow unauthenticated voice recording without user interaction. The activities lacked proper permission checks, enabling attackers to directly invoke recording functionality. The fix involves adding proper Android permission enforcement to these vulnerable activity components.
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< 21.3.51.11CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/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 installed Voice Note versionOpen the Samsung Voice Note app, then navigate to Settings > About or Help > About Voice Note to view the current version numberAffected if The displayed version is lower than 21.3.51.11
-
Verify package version via Android settingsGo to Settings > Apps > Voice Note > App info, then view the version name or version code listedAffected if The version shown is any version before 21.3.51.11
-
Confirm app sourceEnsure the app is the official Samsung Voice Note application from Samsung's app store or pre-installed by SamsungAffected if The app is the official Samsung Voice Note and version is below 21.3.51.11
If the installed Samsung Voice Note version is anything less than 21.3.51.11, the device is vulnerable to unauthenticated voice recording via unprotected activity components.
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 · scoped21.3.51.11
Update Voice Note to version 21.3.51.11 or later, which implements proper permission checks on the previously unprotected activities to prevent unauthorized voice recording.
Voice Note version 21.3.51.11 or later
- Open the Samsung Galaxy Store or Google Play Store on your Samsung device
- Search for 'Voice Note' or navigate to your installed apps
- Locate the Voice Note application by Samsung
- Check the current version installed on your device
- If the version is lower than 21.3.51.11, tap 'Update' to install the latest version
- Verify the installed version is 21.3.51.11 or higher after the update completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28789 — 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-28789 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