CVE-2024-34608
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 · uneditedImproper access control in PaymentManagerService prior to SMR Aug-2024 Release 1 allows local attackers to bypass restrictions on starting services from the background.
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 confidenceImproper access control in Samsung's PaymentManagerService allows local attackers to bypass restrictions on starting services from the background. This could enable malicious local applications to improperly interact with payment services in ways restricted for background-originated requests.
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= 12.0= 13.0= 14.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
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.
-
Identify device manufacturerCheck the device settings or use 'getprop ro.product.brand' command to confirm the device is a Samsung deviceAffected if Device is not manufactured by Samsung, then this specific vulnerability does not apply
-
Check Android versionNavigate to Settings > About Phone > Android version, or use 'getprop ro.build.version.release' commandAffected if Android version is 12.0, 13.0, or 14.0 exactly (these are the affected versions)
-
Verify PaymentManagerService presenceCheck if the package com.sec.samsungpm is installed by running 'pm list packages | grep samsungpm' or inspect /data/data/ for the Samsung Payment Manager applicationAffected if PaymentManagerService is present on the device and Android version is one of the affected versions listed above
A Samsung Android device running version 12.0, 13.0, or 14.0 with the PaymentManagerService installed is affected by this improper access control vulnerability.
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 Samsung SMR (Security Maintenance Release) August 2024 Release 1 or later to affected Samsung devices to receive the access control fix.
Samsung SMR Aug-2024 Release 1 (Android 12.0, 13.0, 14.0)
- Go to Settings on your Samsung device
- Navigate to Software update
- Tap on Check for updates
- Ensure the device updates to the August 2024 security patch level (SMR Aug-2024 Release 1)
- Verify the update was applied by checking the Android security patch level in Settings > About phone > Software information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34608 — 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-2024-34608 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