# CVE-2024-36557: Auth bypass in n/a

> Attackers can hijack Forever KidsWatch devices by spoofing the IMEI, allowing unauthorized control via the mobile app.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Feb 2025
- **Updated:** 10 Feb 2025
- **Also known as:** GHSA-2r8x-g2v5-x892

## What is CVE-2024-36557?

CVE-2024-36557 is a medium-severity authentication bypass vulnerability in n/a, published on 6 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The device ID is based on IMEI in Forever KidsWatch Call Me KW50 R36_YDR_A3PW_GM7S_V1.0_2019_07_15_16.19.24_cob_h and Forever KidsWatch Call Me 2 KW60 R36CW_YDE_S4_A29_2_V1.0_2023.05.24_22.49.44_cob_b. If a malicious user changes the IMEI to the IMEI of a unit they registered in the mobile app, it is possible to hijack the device and control it from the app.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

## Which versions are affected by CVE-2024-36557?


## How do I fix CVE-2024-36557?

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

## Is CVE-2024-36557 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-36557 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-36557 and fix it if it is affected.

What it is: CVE-2024-36557 is a medium-severity authentication bypass vulnerability in n/a, published on 6 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-36557 exists.

Affected product: n/a. 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-2024-36557/ (Markdown: https://insights.sbomify.com/CVE-2024-36557/index.md)
```

## Sources

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

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