# CVE-2024-45347: Mi Connect Service APP protocol flaws lead to unauthorized access

> Attackers can bypass authentication in the Xiaomi Mi Connect Service app to gain unauthorized access to victim devices.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **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:** 23 Jun 2025
- **Updated:** 23 Jun 2025
- **Also known as:** GHSA-g6wx-2x5f-44mv

## What is CVE-2024-45347?

CVE-2024-45347 is a critical authentication bypass vulnerability in Xiaomi Mi Connect Service, published on 23 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An unauthorized access vulnerability exists in the Xiaomi Mi Connect Service APP. The vulnerability is caused by the validation logic is flawed and can be exploited by attackers to Unauthorized access to the victim’s device.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2024-45347 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-45347 is a critical authentication bypass vulnerability in Xiaomi Mi Connect Service, published on 23 Jun 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-2024-45347 in the wild and no public exploit code.

Affected product: Xiaomi Mi Connect Service. 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-45347/ (Markdown: https://insights.sbomify.com/CVE-2024-45347/index.md)
```

## Sources

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

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