dbcve.org
MercariApplication

CVE-2024-23388

MEDIUM · 6.1 CVSS v3.1 Published 2024-01-26
Fix available
A fix is available. Upgrade to 5.78.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable 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
Improper authorization in handler for custom URL scheme issue in "Mercari" App for Android prior to version 5.78.0 allows a remote attacker to lead a user to access an arbitrary website via the vulnerable App. As a result, the user may become a victim of a phishing attack.

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

The Mercari Android app prior to version 5.78.0 contains an improper authorization vulnerability in its custom URL scheme handler. The app registers a custom URL scheme (e.g., mercari://) but fails to properly validate or authorize URLs before redirecting users, allowing remote attackers to craft malicious links that can redirect users to arbitrary attacker-controlled websites for phishing attacks.

MitigationUpdate the Mercari Android application to version 5.78.0 or later, which implements proper authorization checks in the custom URL scheme handler to prevent arbitrary URL redirects.

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
MercariApplication
Affected:< 5.78.0

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Verify Mercari Android app is installed
    Open device Settings > Apps > Apps list and look for 'Mercari' or check via adb with: adb shell pm list packages | grep mercari
    Affected if The Mercari app is not installed on the device (not affected)
  2. Identify installed Mercari app version
    On the device, go to Settings > Apps > Mercari > App info and note the Version number shown, or use adb: adb shell dumpsys package com.mercariapp.mercari | grep versionName
    Affected if Unable to determine the installed version
  3. Compare installed version to vulnerable range
    Check if the installed version is any version number less than 5.78.0 (for example, 5.77.0, 5.76.0, etc.)
    Affected if Installed version is < 5.78.0 (the app is affected by this vulnerability)
  4. Verify custom URL scheme handling behavior
    Attempt to trigger a mercari:// URL redirect (if you have a test device): use an intent like adb shell am start -a android.intent.action.VIEW -d "mercari://example.com" to observe if arbitrary URLs are accepted without validation
    Affected if The URL scheme handler permits redirects to arbitrary domains without user consent (the vulnerability is present)

You are affected if the Mercari Android app is installed with a version number lower than 5.78.0 and the custom URL scheme handler permits redirects to arbitrary domains.

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 5.78.0 or later
Fixed in 5.78.0
Interim mitigation

Update the Mercari Android application to version 5.78.0 or later, which implements proper authorization checks in the custom URL scheme handler to prevent arbitrary URL redirects.

Recommended fix High confidence

Mercari Android app version 5.78.0

  1. Open Google Play Store on your Android device
  2. Search for "Mercari" or locate the Mercari app in your installed apps
  3. Tap on the Mercari app and select "Update" to install version 5.78.0 or later
  4. After update completes, verify the version by checking the app's settings or about section to confirm you are running 5.78.0 or higher

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

Fix this in Mercari Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23388 — 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-2024-23388 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