CVE-2020-5523 json
Android App 'MyPallete' and some of the Android banking applications based on 'MyPallete' do not verify X.509 certificates from servers, an…
published 2020-01-28 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-26686
- cvss
- 7.4
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 67%
- public exploits
- 0
- none known
Summary
Android App 'MyPallete' and some of the Android banking applications based on 'MyPallete' do not verify X.509 certificates from servers, and also do not properly validate certificates with host-mismatch, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate.
Exploit prediction
1.18% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:P/I:P/A:N |
Affected products
- NTT Data Corporation 'MyPallete' and some of the Android banking applications that use 'MyPallete'
Classification
- Weakness
-
- CWE-295 Improper Certificate Validation
References
-
dokodemobank.ne.jp
/info_20200128_bankingapp.html
third-party-advisory
-
ashikagabank.co.jp
/appbanking/pdf/oshirase.pdf
third-party-advisory
-
sihd-bk.jp
/common_v2/pdf/20200127.pdf
third-party-advisory
-
shikokubank.co.jp
/info/apps20200128.html
third-party-advisory
-
tohoku-bank.co.jp
/news/topics/200128_applissl.html
third-party-advisory
-
naganobank.co.jp
/soshiki/2/app-ssl.html
third-party-advisory
-
77bank.co.jp
/pdf/oshirase/20012801_appvulnerability.pdf
third-party-advisory
-
hokkaidobank.co.jp
/common/dat/2020/0120/15795047141946146699.pdf
third-party-advisory
-
hokugin.co.jp
/info/archives/personal/2020/1913.html
third-party-advisory
-
jvn.jp
/en/jp/JVN28845872/index.html
third-party-advisory
Sources
- CVE List CVE-2020-5523
- NVD CVE-2020-5523
Fencer Vulns 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.