# CVE-2021-4228: Hard-coded TLS Certificate

> Attackers can perform Man-in-the-Middle attacks on HTTPS connections due to a hard-coded TLS certificate in the firmware.

- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Oct 2022
- **Updated:** 5 May 2025
- **Also known as:** GHSA-83r7-pm46-hpfw

## What is CVE-2021-4228?

CVE-2021-4228 is a medium-severity vulnerability in Lanner Inc IAC-AST2500A, published on 24 Oct 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Use of hard-coded TLS certificate by default allows an attacker to perform Man-in-the-Middle (MitM) attacks even in the presence of the HTTPS connection. This issue affects: Lanner Inc IAC-AST2500A standard firmware version 1.00.0.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-321 (Use of Hard-coded Cryptographic Key)

## Which versions are affected by CVE-2021-4228?

It affects 1 product.


Products: Lannerinc Iac-Ast2500 Firmware.

## How do I fix CVE-2021-4228?

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

## Is CVE-2021-4228 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-4228 and fix it if it is affected.

What it is: CVE-2021-4228 is a medium-severity vulnerability in Lanner Inc IAC-AST2500A, published on 24 Oct 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-4228 in the wild and no public exploit code.

Affected product: Lanner Inc IAC-AST2500A. 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-2021-4228/ (Markdown: https://insights.sbomify.com/CVE-2021-4228/index.md)
```

## Sources

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

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