# CVE-2024-4062: Hualai Xiaofang iSC5 certificate validation

> Remote attackers can bypass certificate validation in Hualai Xiaofang iSC5, potentially enabling man-in-the-middle attacks.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/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:** 23 Apr 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-wm4r-wfxq-54cf

## What is CVE-2024-4062?

CVE-2024-4062 is a low-severity vulnerability in Hualai Xiaofang iSC5, published on 23 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in Hualai Xiaofang iSC5 3.2.2_112 and classified as problematic. Affected by this issue is some unknown functionality. The manipulation leads to improper certificate validation. The attack may be launched remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The identifier of this vulnerability is VDB-261788. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-295 (Improper Certificate Validation)

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


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

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

## Is CVE-2024-4062 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-4062 is a low-severity vulnerability in Hualai Xiaofang iSC5, published on 23 Apr 2024. 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-2024-4062 in the wild and no public exploit code.

Affected product: Hualai Xiaofang iSC5. 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-4062/ (Markdown: https://insights.sbomify.com/CVE-2024-4062/index.md)
```

## Sources

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

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