CVE-2023-6542
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 · uneditedDue to lack of proper authorization checks in Emarsys SDK for Android, an attacker can call a particular activity and can forward himself web pages and/or deep links without any validation directly from the host application. On successful attack, an attacker could navigate to arbitrary URL including application deep links on the device.
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 confidenceThe Emarsys SDK for Android lacks proper authorization checks on a specific activity that can be invoked externally. An attacker can directly call this activity to navigate to arbitrary URLs or deep links without any validation from the host application, potentially redirecting users to malicious URLs or triggering unauthorized deep link actions within the app.
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= 3.6.2CVSS 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
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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 if the Emarsys SDK is present in the Android applicationInspect the application's manifest file (AndroidManifest.xml) for activities belonging to the com.emarsys package. Look for activity declarations that contain 'emarsys' in the package name.Affected if The application includes any com.emarsys.* activity components in its manifest.
-
Determine the installed Emarsys SDK versionCheck the build configuration files (build.gradle, build.gradle.kts, or libs.versions.toml) for the Emarsys SDK dependency version, or inspect the resolved dependency tree using './gradlew app:dependencies' and search for 'emarsys' or 'com.emarsys' entries.Affected if The Emarsys SDK version is exactly 3.6.2.
-
Locate the vulnerable activity in the manifestSearch the AndroidManifest.xml for activity declarations with intent filters that handle VIEW actions or deep link schemes, particularly those within the com.emarsys package that handle URL navigation.Affected if An exported Emarsys activity with intent filters capable of handling external URL or deep link navigation is present in the manifest.
-
Verify if the activity is exportedIn the AndroidManifest.xml, examine the 'android:exported' attribute on any Emarsys activity that handles URL or deep link navigation. Check both the activity tag and any <intent-filter> child elements for the exported status.Affected if The vulnerable activity has android:exported='true' or has an intent-filter without an explicit android:exported='false' set, allowing external apps to invoke it.
A user is affected if their Android application bundles the Emarsys SDK at version 3.6.2 AND contains an exported activity (or intent-filter) within the com.emarsys package that handles external URL or deep link navigation without authorization validation.
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 dataOrganizations using the Emarsys SDK should update to the patched version provided by Emarsys that includes proper authorization validation on the vulnerable activity. Until the patch is available, consider implementing additional validation at the application layer or restricting exported activity components.
- Consultation4.0 h
- Implementation2.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,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6542 — 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-2023-6542 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