CVE-2022-41986
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 · uneditedInformation disclosure vulnerability in Android App 'IIJ SmartKey' versions prior to 2.1.4 allows an attacker to obtain a one-time password issued by the product under certain conditions.
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 confidenceIIJ SmartKey Android app versions prior to 2.1.4 contain an information disclosure vulnerability that allows an attacker to obtain one-time passwords (OTPs) issued by the authentication app under certain conditions. The vulnerability exposes sensitive authentication credentials that could enable unauthorized access to protected accounts.
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< 2.1.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify IIJ SmartKey app is installedOpen Android device Settings > Apps > Apps list and search for 'IIJ SmartKey' or 'SmartKey', or check the app drawer for the SmartKey iconAffected if IIJ SmartKey app is present on the device
-
Find installed app versionIn Settings > Apps > IIJ SmartKey, scroll to the 'App info' or 'Version' field to display the installed version number (e.g., 2.1.3, 2.1.2, etc.)Affected if Version displayed is less than 2.1.4 or version info shows no number / is unknown
-
Confirm version comparisonCompare the displayed version against 2.1.4 - any version starting with 2.1.3, 2.1.2, 2.1.1, 2.1.0 or lower is affectedAffected if Installed version is a release prior to 2.1.4 (e.g., 2.1.3, 2.1.0, 1.x.x)
-
Check if OTP functionality is in useDetermine whether the app is actively generating or storing one-time passwords for authentication purposes - look for OTP codes displayed in the app or configured authentication accountsAffected if App is actively used for OTP generation and version is below 2.1.4
A user is affected if IIJ SmartKey Android app is installed with any version prior to 2.1.4 and the app is being used for OTP-based authentication.
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 · scoped2.1.4
Update IIJ SmartKey Android app to version 2.1.4 or later to remediate the vulnerability. Organizations should verify all devices have the updated version installed.
2.1.4
- Upgrade IIJ SmartKey to version 2.1.4 or later from the Google Play Store
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41986 — 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-2022-41986 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