Security readout for executives and security teams
Plain-English summary
The affected SUSHIRO Android apps may write credential information into Android log files. If an attacker can access those logs, they may recover credentials. The business risk is account compromise and privacy exposure for users of the listed regional app versions.
Executive priority
Treat this as high priority where employees, customers, or managed devices use the affected apps. The main concern is credential disclosure, but the source bundle does not confirm active exploitation or broader platform impact.
Technical view
CVE-2023-22362 is CWE-532: insertion of sensitive information into log files. The source bundle lists specific Android app versions for Japan, Thailand, Hong Kong, Singapore, and Taiwan. CVSS 3.1 is 7.5, driven by high confidentiality impact.
Likely exposure
Exposure is limited to devices running the listed vulnerable Android app versions. The bundle does not identify affected iOS apps, backend services, or versions outside those named regional Android releases.
Exploitation context
The bundle does not show CISA KEV listing or any cited evidence of active exploitation. Practical abuse would depend on an attacker obtaining access to relevant Android log data containing credentials.
Researcher notes
Evidence is concise and does not describe the exact credential type, log location, exploit path, or fixed versions. Validate only the listed Android versions and avoid expanding scope beyond the named SUSHIRO regional apps without vendor evidence.
Mitigation direction
- Check JVN and vendor app-store guidance for fixed versions or official remediation.
- Update affected regional SUSHIRO Android apps when a fixed release is available.
- Retire or restrict use of the listed vulnerable versions on managed devices.
- Rotate credentials if log exposure or suspicious account access is suspected.
- Avoid assuming backend or iOS exposure without vendor confirmation.
Validation and detection
- Inventory managed Android devices for the listed SUSHIRO app package versions.
- Confirm whether installed versions match the affected regional releases.
- Review vendor and JVN advisories for remediation status and fixed version details.
- Assess whether mobile logging or backups could contain credential material.
- Monitor related user accounts for abnormal access if exposure is suspected.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-532: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-22362 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://play.google.com/store/apps/details?id=jp.co.akindo_sushiro.sushiroappCVE reference
- https://play.google.com/store/apps/details?id=th.co.akindo_sushiro.sushiroappCVE reference
- https://play.google.com/store/apps/details?id=hk.co.akindo_sushiro.sushiroappCVE reference
- https://play.google.com/store/apps/details?id=sg.co.akindo_sushiro.sushiroappCVE reference
- https://play.google.com/store/apps/details?id=tw.co.akindo_sushiro.sushiroappCVE reference
- https://jvn.jp/en/jp/JVN84642320/CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Insertion of Sensitive Information into Log File
Insertion of Sensitive Information into Log File represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.