dbcve.org
Hong Kong SushiroApplication · Akindo Sushiro

CVE-2023-22362

HIGH · 7.5 CVSS v3.1 Published 2023-02-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
SUSHIRO App for Android outputs sensitive information to the log file, which may result in an attacker obtaining a credential information from the log file. Affected products/versions are as follows: SUSHIRO Ver.4.0.31, Thailand SUSHIRO Ver.1.0.0, Hong Kong SUSHIRO Ver.3.0.2, Singapore SUSHIRO Ver.2.0.0, and Taiwan SUSHIRO Ver.2.0.1

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 · high confidence

The SUSHIRO Android application writes sensitive credential information to log files, which can be accessed by attackers with local device access or through other applications with log reading permissions. This exposes authentication credentials through the Android system log.

MitigationUpdate the SUSHIRO application to a patched version that removes credential logging, or disable debug logging in production builds to prevent sensitive data from being written to log files.

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
Hong Kong SushiroApplication
Affected:= 3.0.3
Singapore SushiroApplication
Affected:= 2.0.3
SushiroApplication
Affected:= 4.0.31
Taiwan SushiroApplication
Affected:= 2.0.3
Thailand SushiroApplication
Affected:= 2.0.3

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. Identify installed SUSHIRO application
    Use 'adb shell pm list packages | grep sushiro' to find installed SUSHIRO app package names. Common package patterns include com.akindo.sushiro.hk, com.akindo.sushiro.sg, com.akindo.sushiro.tw, com.akindo.sushiro.th, or similar
    Affected if Any SUSHIRO app from the affected product list is installed
  2. Check installed application version
    Use 'adb shell dumpsys package <package_name>' and look for versionName in the Package [ ] section, or view the app version in device Settings > Apps > SUSHIRO > Version
    Affected if The installed version exactly matches 3.0.3 (Hong Kong), 2.0.3 (Singapore/Taiwan/Thailand), or 4.0.31 (main Sushiro)
  3. Examine log files for credential exposure
    Run 'adb logcat -d | grep -i -E "(password|token|auth|credential|secret)"' to search Android logs for sensitive strings, or use 'adb logcat -v time' to view recent log entries for any plaintext credentials
    Affected if Log output contains readable authentication credentials, tokens, passwords, or session identifiers written by the SUSHIRO application

A defender is affected if they have installed any of the specific SUSHIRO app variants at versions 3.0.3, 2.0.3, or 4.0.31 and those apps have written credentials to accessible log files.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the SUSHIRO application to a patched version that removes credential logging, or disable debug logging in production builds to prevent sensitive data from being written to log files.

Recommended fix Moderate confidence

Latest available version from Google Play Store (version higher than affected: Sushiro 4.0.31+, Thailand 1.0.0+, Hong Kong 3.0.2+, Singapore 2.0.0+, Taiwan 2.0.1+)

  1. 1. Open Google Play Store on the Android device
  2. 2. Search for "Sushiro" or the specific regional Sushiro app (Hong Kong, Singapore, Taiwan, or Thailand)
  3. 3. If an update is available, tap the "Update" button to install the latest version
  4. 4. Alternatively, navigate to the app's page in Google Play Store and check for any available updates under the "What's new" section
  5. 5. After updating, verify the app launches successfully and functions normally

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

Fix this in Hong Kong Sushiro Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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