dbcve.org
Solipay MobileApplication · Utarit

CVE-2023-6255

HIGH · 7.5 CVSS v3.1 Published 2024-02-15
Fix available
A fix is available. Upgrade to 5.0.8 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Use of Hard-coded Credentials vulnerability in Utarit Information Technologies SoliPay Mobile App allows Read Sensitive Strings Within an Executable. This issue affects SoliPay Mobile App: before 5.0.8.

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 SoliPay Mobile App version before 5.0.8 contains hard-coded credentials embedded within the application executable. Attackers can extract these sensitive strings from the app binary, potentially gaining unauthorized access to backend services or sensitive functionality.

MitigationUpdate to SoliPay Mobile App version 5.0.8 or later, which should remove the hardcoded credentials. If update is not available, implement proper credential management using secure authentication mechanisms (e.g., OAuth, token-based auth) and rotate any credentials that may have been exposed.

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
Solipay MobileApplication
Affected:< 5.0.8

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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

  1. Check installed SoliPay Mobile app version
    On Android: Go to Settings > Apps > SoliPay > Version, or run 'adb shell dumpsys package com.solipay.mobile' | grep versionName. On iOS: Go to Settings > General > iPhone Storage > SoliPay, or check in App Store if installed.
    Affected if Version is below 5.0.8 (e.g., 5.0.7, 5.0.6, etc.)
  2. Locate the app binary file
    On Android, pull the APK using 'adb shell pm path com.solipay.mobile' then 'adb pull <path>/base.apk'. On iOS, if you have the IPA, extract it. The binary is typically in the lib/ folder (lib/armeabi-v7a/libnative.so) or as raw resources.
    Affected if You have access to the unpacked app binary and version is below 5.0.8
  3. Search for hardcoded credential patterns in binary
    Use strings tool on the binary: 'strings <binary_file> | grep -iE "(password|passwd|pwd|secret|key|token|api_key|auth)"'. Also search for base64-like patterns or long alphanumeric strings that resemble API keys or tokens.
    Affected if Binary contains readable strings matching credential patterns, especially in native libraries or embedded resources
  4. Inspect string resources for sensitive data
    If the APK is extracted, open res/values/strings.xml and search for any string values that appear to be credentials, API endpoints with auth parameters, or secrets. Also check any .so native libraries with 'strings' command.
    Affected if String resources or native libraries contain hardcoded sensitive-looking values that should not be present in the app binary
  5. Verify if app communicates with known backend services
    Use a network proxy (e.g., Burp Suite, mitmproxy) to intercept app traffic. Observe if authentication works without proper user login flow, or if the app sends hardcoded credentials in requests.
    Affected if App sends hardcoded credentials in API requests or authenticates using embedded secrets rather than dynamic authentication

If SoliPay Mobile version is below 5.0.8 and the app binary contains hardcoded credential strings or makes authenticated requests using embedded secrets, the environment is affected by CVE-2023-6255.

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.0.8 or later
Fixed in 5.0.8
Interim mitigation

Update to SoliPay Mobile App version 5.0.8 or later, which should remove the hardcoded credentials. If update is not available, implement proper credential management using secure authentication mechanisms (e.g., OAuth, token-based auth) and rotate any credentials that may have been exposed.

Recommended fix Moderate confidence

5.0.8

  1. Upgrade SoliPay Mobile to version 5.0.8 or later

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

Fix this in Solipay Mobile Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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