# CVE-2025-24852: Information disclosure in CHOCO TEI WATCHER mini (IB-MCT001)

> An attacker with physical access to the microSD card can retrieve the login password, potentially leading to unauthorized access to the IoT camera.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Mar 2025
- **Updated:** 31 Mar 2025
- **Also known as:** GHSA-rj8r-3hfq-pwj3

## What is CVE-2025-24852?

CVE-2025-24852 is a medium-severity vulnerability in Inaba Denki Sangyo Co., Ltd. CHOCO TEI WATCHER mini (IB-MCT001), published on 31 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Storing passwords in a recoverable format issue exists in CHOCO TEI WATCHER mini (IB-MCT001) all versions. If this issue is exploited, an attacker who can access the microSD card used on the product may obtain the product login password.

Weakness: CWE-257 (Storing Passwords in a Recoverable Format)

## Which versions are affected by CVE-2025-24852?


## How do I fix CVE-2025-24852?

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

## Is CVE-2025-24852 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24852 and fix it if it is affected.

What it is: CVE-2025-24852 is a medium-severity vulnerability in Inaba Denki Sangyo Co., Ltd. CHOCO TEI WATCHER mini (IB-MCT001), published on 31 Mar 2025. 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-2025-24852 in the wild and no public exploit code.

Affected product: Inaba Denki Sangyo Co., Ltd. CHOCO TEI WATCHER mini (IB-MCT001). 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-2025-24852/ (Markdown: https://insights.sbomify.com/CVE-2025-24852/index.md)
```

## Sources

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

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