# CVE-2022-43704: Auth bypass in n/a

> Attackers can bypass authentication and control the thermostat relay by replaying UDP commands, potentially causing unsafe physical temperatures.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jan 2023
- **Updated:** 2 Apr 2025
- **Also known as:** GHSA-9rpc-xc7c-jhmw

## What is CVE-2022-43704?

CVE-2022-43704 is a medium-severity authentication bypass vulnerability in n/a, published on 20 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Sinilink XY-WFT1 WiFi Remote Thermostat, running firmware 1.3.6, allows an attacker to bypass the intended requirement to communicate using MQTT. It is possible to replay Sinilink aka SINILINK521 protocol (udp/1024) commands interfacing directly with the target device. This, in turn, allows for an attack to control the onboard relay without requiring authentication via the mobile application. This might result in an unacceptable temperature within the target device's physical environment.

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

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

It affects 1 product.


Products: Sinilink Xy-Wft1 Firmware.

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

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

## Is CVE-2022-43704 being exploited?

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

Public exploit code:

- Sinilink XY-WFTX Wifi Remote Thermostat Module Temperature Controller (github_poc): https://github.com/9lyph/CVE-2022-43704

## Fix prompt for AI coding agents

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

What it is: CVE-2022-43704 is a medium-severity authentication bypass vulnerability in n/a, published on 20 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-43704 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-2022-43704/ (Markdown: https://insights.sbomify.com/CVE-2022-43704/index.md)
```

## Sources

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

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