# CVE-2022-29525: Hardcoded credentials in Rakuten Casa

> Remote attackers can use hard-coded credentials to gain root access and execute arbitrary operations on Rakuten Casa devices.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-p4rr-qwvg-x2jf

## What is CVE-2022-29525?

CVE-2022-29525 is a critical vulnerability in Rakuten Casa, published on 13 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Rakuten Casa version AP_F_V1_4_1 or AP_F_V2_0_0 uses a hard-coded credential which may allow a remote unauthenticated attacker to log in with the root privilege and perform an arbitrary operation.

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

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

It affects 1 product.


Products: Rakuten Casa.

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

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

## Is CVE-2022-29525 being exploited?

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

## Other vulnerabilities in Rakuten Casa

- [CVE-2022-26834](https://insights.sbomify.com/CVE-2022-26834/): Misconfiguration in Rakuten Casa (high 7.5)
- [CVE-2022-28704](https://insights.sbomify.com/CVE-2022-28704/): Hardcoded credentials in Rakuten Casa (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-29525 is a critical vulnerability in Rakuten Casa, published on 13 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-29525 in the wild and no public exploit code.

Affected product: Rakuten Casa. 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-29525/ (Markdown: https://insights.sbomify.com/CVE-2022-29525/index.md)
```

## Sources

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

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