# CVE-2019-10711: Auth bypass in n/a

> Attackers can view RTSP streams on Hisilicon-based IP cameras by using hidden default credentials that are not exposed in the management application.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-4g2r-w797-wfcq

## What is CVE-2019-10711?

CVE-2019-10711 is a high-severity authentication bypass vulnerability in n/a, published on 23 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Incorrect access control in the RTSP stream and web portal on all IP cameras based on Hisilicon Hi3510 firmware (until Webware version V1.0.1) allows attackers to view an RTSP stream by connecting to the stream with hidden credentials (guest or user) that are neither displayed nor configurable in the camera's CamHi or keye mobile management application. This affects certain devices labeled as HI3510, HI3518, LOOSAFE, LEVCOECAM, Sywstoda, BESDER, WUSONGLUSAN, GADINAN, Unitoptek, ESCAM, etc.

## Which versions are affected by CVE-2019-10711?

It affects 1 product.


Products: Hisilicon Hi3510 Firmware.

## How do I fix CVE-2019-10711?

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

## Is CVE-2019-10711 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-10710](https://insights.sbomify.com/CVE-2019-10710/): Information disclosure in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10711 and fix it if it is affected.

What it is: CVE-2019-10711 is a high-severity authentication bypass vulnerability in n/a, published on 23 Apr 2019. 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-2019-10711 in the wild and no public exploit code.

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-2019-10711/ (Markdown: https://insights.sbomify.com/CVE-2019-10711/index.md)
```

## Sources

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

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