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

> Remote attackers can defeat cryptographic protections on Amcrest devices by using a shared hardcoded SSL private key found in other installations.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/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:** 5 Sep 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-c5gc-77wf-jm29

## What is CVE-2018-16546?

CVE-2018-16546 is a medium-severity vulnerability in n/a, published on 5 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Amcrest networked devices use the same hardcoded SSL private key across different customers' installations, which allows remote attackers to defeat cryptographic protection mechanisms by leveraging knowledge of this key from another installation, as demonstrated by Amcrest_IPC-HX1X3X-LEXUS_Eng_N_AMCREST_V2.420.AC01.3.R.20180206.

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

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

It affects 1 product.


Products: Amcrest Amcrest Ipc-Hx1x3x-Lexus Eng N Amcrest.

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

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

## Is CVE-2018-16546 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-16546 is a medium-severity vulnerability in n/a, published on 5 Sep 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-16546 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-16546/ (Markdown: https://insights.sbomify.com/CVE-2018-16546/index.md)
```

## Sources

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

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