CVE-2023-22367
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 · uneditedIchiran App for iOS versions prior to 3.1.0 and Ichiran App for Android versions prior to 3.1.0 improperly verify server certificates, which may allow a remote unauthenticated attacker to eavesdrop on an encrypted communication via a man-in-the-middle 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 · high confidenceThe Ichiran mobile applications for iOS and Android fail to properly validate SSL/TLS server certificates during HTTPS connections. This improper certificate verification allows a remote attacker positioned between the client and server to intercept encrypted communications by presenting a fraudulent certificate, enabling eavesdropping on sensitive data in transit.
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.1.0CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Ichiran app version on iOSOpen the App Store app, tap your profile icon, scroll to 'Purchased' and search for 'Ichiran', or go to Settings > General > iPhone Storage to find the Ichiran app and view its version numberAffected if The displayed version number is lower than 3.1.0
-
Check installed Ichiran app version on AndroidOpen the Google Play Store app, search for 'Ichiran', tap on the app, and view the version under 'Additional information', or go to Settings > Apps > Ichiran to see the versionAffected if The displayed version number is lower than 3.1.0
-
Verify app sourceConfirm the app is 'Ichiranusa Ichiran' specifically, as other Ichiran-related apps may exist with different version numberingAffected if The app is the Ichiranusa version and its version is below 3.1.0
If the installed version of the Ichiranusa Ichiran mobile app is any version below 3.1.0 on either iOS or Android, the device is vulnerable to certificate validation bypass attacks.
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.
dbcve · scoped3.1.0
Update both the iOS and Android Ichiran App installations to version 3.1.0 or later, which implements proper server certificate verification.
Ichiran App for iOS and Android version 3.1.0
- Open the app store on your iOS or Android device
- Search for the Ichiran App
- Locate the Ichiran App and verify the current installed version
- If the version is earlier than 3.1.0, update the app to the latest version available
- For iOS: Open App Store > Tap your profile icon > Tap 'Purchased' > Find Ichiran and update
- For Android: Open Google Play Store > Tap menu > Tap 'My apps & games' > Find Ichiran and update
- After updating, verify the app is now at version 3.1.0 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22367 — 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-22367 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