# CVE-2022-38117: Juiker app - Hard-coded Credentials

> A physical attacker with root access can use a hard-coded AES key to decrypt and tamper with user data in the Juiker mobile application.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:P/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Oct 2022
- **Updated:** 7 May 2025
- **Also known as:** GHSA-2wjq-7fcc-4p8f

## What is CVE-2022-38117?

CVE-2022-38117 is a medium-severity vulnerability in Juiker app, published on 24 Oct 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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 with it.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2022-38117?

It affects 1 product.


Products: Juiker Juiker.

## How do I fix CVE-2022-38117?

No fix has been published for CVE-2022-38117 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-38117 being exploited?

There is no known exploitation of CVE-2022-38117 in the wild and no public exploit code.

## Other vulnerabilities in Juiker app

- [CVE-2014-6693](https://insights.sbomify.com/CVE-2014-6693/): Weak cryptography in n/a (medium 5.4)
- [CVE-2022-39043](https://insights.sbomify.com/CVE-2022-39043/): Juiker app - Information Leakage (low 2.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-38117 and fix it if it is affected.

What it is: CVE-2022-38117 is a medium-severity vulnerability in Juiker app, published on 24 Oct 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-38117 in the wild and no public exploit code.

Affected product: Juiker app. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-38117/ (Markdown: https://insights.sbomify.com/CVE-2022-38117/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-38117
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-38117
- OSV: https://osv.dev/vulnerability/CVE-2022-38117

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-38117/
Summaries are generated and may contain mistakes; the official description above is the record.