# CVE-2022-47618: Merit Lilin Ent. Co., Ltd. AH55B04 & AH55B08 DVR - Hard-coded Credentials

> An unauthenticated remote attacker can use hard-coded administrator credentials to log in and manipulate the DVR system or disrupt service.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 3 Jan 2023
- **Updated:** 10 Apr 2025
- **Also known as:** GHSA-x6cv-8qm7-rqw4

## What is CVE-2022-47618?

CVE-2022-47618 is a critical vulnerability in Merit Lilin Ent. Co., Ltd. AH55B04 DVR firmware, published on 3 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Merit LILIN AH55B04 & AH55B08 DVR firm has hard-coded administrator credentials. An unauthenticated remote attacker can use these credentials to log in administrator page, to manipulate system or disrupt service.

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

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

It affects 2 products.


Products: Meritlilin Ah55b04 Firmware, Meritlilin Ah55b08 Firmware.

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

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

## Is CVE-2022-47618 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-47618 is a critical vulnerability in Merit Lilin Ent. Co., Ltd. AH55B04 DVR firmware, published on 3 Jan 2023. 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-2022-47618 in the wild and no public exploit code.

Affected product: Merit Lilin Ent. Co., Ltd. AH55B04 DVR firmware. 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-47618/ (Markdown: https://insights.sbomify.com/CVE-2022-47618/index.md)
```

## Sources

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

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