# CVE-2018-5723: Hardcoded credentials in n/a

> Attackers can gain root access to MASTER IPCAMERA01 devices using a hardcoded password, leading to full device compromise.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jan 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xw63-m43m-c93h

## What is CVE-2018-5723?

CVE-2018-5723 is a critical vulnerability in n/a, published on 16 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MASTER IPCAMERA01 3.3.4.2103 devices have a hardcoded password of cat1029 for the root account.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2018-5723?

It affects 1 product.


Products: Barni Master Ip Camera01 Firmware.

## How do I fix CVE-2018-5723?

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

## Is CVE-2018-5723 being exploited?

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

Public exploit code:

- Master IP CAM 01 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2019-8387](https://insights.sbomify.com/CVE-2019-8387/): Command injection in n/a (critical 9.8)
- [CVE-2018-5724](https://insights.sbomify.com/CVE-2018-5724/): File upload in n/a (critical 9.8)
- [CVE-2018-5726](https://insights.sbomify.com/CVE-2018-5726/): Information disclosure in n/a (critical 9.8)
- [CVE-2018-5725](https://insights.sbomify.com/CVE-2018-5725/): Missing authorization in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-5723 and fix it if it is affected.

What it is: CVE-2018-5723 is a critical vulnerability in n/a, published on 16 Jan 2018. 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-2018-5723 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-2018-5723/ (Markdown: https://insights.sbomify.com/CVE-2018-5723/index.md)
```

## Sources

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

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