CVE-2022-0131 json
Jimoty App for Android versions prior to 3.7.42 uses a hard-coded API key for an external service.
published 4y ago modified 4mo ago also EUVD-2022-15344
- cvss
- 3.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 10%
- public exploits
- 0
- none known
Summary
Jimoty App for Android versions prior to 3.7.42 uses a hard-coded API key for an external service. By exploiting this vulnerability, API key for an external service may be obtained by analyzing data in the app.
Patch / fix
- jmty jimoty 3.7.42
Is CVE-2022-0131 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.20% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:P/I:N/A:N |
Affected products
- Jimoty, Inc. Jimoty App for Android
Classification
- Weakness
-
- CWE-798 Use of Hard-coded Credentials
References
-
jvn.jp
/en/jp/JVN49047921/index.html
third-party-advisory
Sources
- CVE List CVE-2022-0131
- NVD CVE-2022-0131
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.