Juiker's vulnerability profile centers on its core communication and collaboration platform, with a durable signal focused on information-handling and credential-management weaknesses, including exposure of sensitive data to unauthorized actors, insecure storage practices, accidental logging of secrets, and reliance on hard-coded credentials. Treat this as a compact vendor profile; live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Juiker over time
Signals from CVEs in this vendor scope (3 CVEs).
3 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2022-38117MEDIUM Juiker app hard-coded its AES key in the source code. A physical attacker, after getting the Android root privilege, can use the AES key to decrypt users’ ciphertext and tamper wit | Oct 24, 2022 | 6.1 | 21 | NO | NO |
CVE-2014-6693MEDIUM The Juiker (aka org.itri) application 3.2.0829.1 for Android does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obta | Sep 24, 2014 | 5.4 | 20 | NO | NO |
Juiker app stores debug logs which contains sensitive information to mobile external storage. An unauthenticated physical attacker can access these files to acquire partial user in | Mar 27, 2023 | 2.4 | 15 | NO | NO |
Signals from CVEs in this vendor scope (3 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Juiker.
Media articles that mention a CVE ID that affects a product developed by Juiker — matched by CVE ID, not by vendor name.