dbcve.org
Account Web Software Development KitApplication · Samsung

CVE-2023-42572

MEDIUM · 5.5 CVSS v3.1 Published 2023-12-05
Fix available
A fix is available. Upgrade to 1.5.24 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 · unedited
Implicit intent hijacking vulnerability in Samsung Account Web SDK prior to version 1.5.24 allows attacker to get sensitive information.

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 confidence

Implicit intent hijacking vulnerability in Samsung Account Web SDK allows a malicious application to intercept implicit intents sent by the SDK, potentially exposing sensitive user information such as authentication tokens or credentials. This is an Android-specific issue where the SDK does not properly restrict intent destinations.

MitigationUpgrade Samsung Account Web SDK to version 1.5.24 or later to obtain the patched version that properly validates intent handling.

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
Account Web Software Development KitApplication
Affected:< 1.5.24

CVSS 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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate Samsung Account Web SDK in project dependencies
    Search your Android project for the Samsung Account Web SDK in build.gradle (Module: app) under dependencies, or in pom.xml if using Maven. Look for artifacts named 'samsung-account-web-sdk', 'samsung-account', or similar Samsung Account libraries.
    Affected if The SDK is present in dependencies with version < 1.5.24 or if version is unspecified/unknown
  2. Identify the exact SDK version number
    Examine the version declared in your dependency configuration. If using Gradle, run './gradlew app:dependencies' or check the resolved version in the build cache. If using a direct AAR import, check the manifest or SDK documentation bundled with the library.
    Affected if Version is less than 1.5.24 or cannot be determined
  3. Confirm the app uses Samsung Account authentication
    Review your application code for imports from com.samsung.account or similar Samsung Account Web SDK packages. Look for usage of authentication-related classes, login flows, or token retrieval methods that would invoke the SDK.
    Affected if The app directly uses Samsung Account Web SDK for authentication or user login flows
  4. Check if implicit intents are used in authentication flow
    Inspect the Samsung Account Web SDK code (if decompileable) or review API documentation for the specific methods being called. Look for intent creation in authentication workflows that may use implicit intents rather than explicit component references.
    Affected if The SDK version < 1.5.24 is in use and the app performs Samsung Account authentication

If Samsung Account Web SDK version < 1.5.24 is present and your app uses Samsung Account authentication flows, the implicit intent hijacking vulnerability applies to your environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.5.24 or later
Fixed in 1.5.24
Interim mitigation

Upgrade Samsung Account Web SDK to version 1.5.24 or later to obtain the patched version that properly validates intent handling.

Recommended fix Moderate confidence

1.5.24

  1. Update the Samsung Account Web SDK dependency in your project to version 1.5.24 or later
  2. Verify the update was applied correctly by checking the installed SDK version
  3. Rebuild and test your application to ensure the SDK upgrade does not cause any runtime issues

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Account Web Software Development Kit Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-42572 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-42572 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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