# CVE-2023-45797: DreamSecurity MagicLine Buffer Overflow Vulnerability

> A buffer overflow in DreamSecurity MagicLine4NX allows remote attackers to execute arbitrary code, requiring immediate patching.

- **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:** 30 Oct 2023
- **Updated:** 6 Sep 2024
- **Also known as:** GHSA-q55p-r853-6qcm

## What is CVE-2023-45797?

CVE-2023-45797 is a critical memory corruption vulnerability in Dream Security MagicLine4NX, published on 30 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Buffer overflow vulnerability in DreamSecurity MagicLine4NX versions 1.0.0.1 to 1.0.0.26 allows an attacker to remotely execute code.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2023-45797?

It affects 1 product.


Products: Dreamsecurity Magicline 4.0.

## How do I fix CVE-2023-45797?

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

## Is CVE-2023-45797 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-45797 and fix it if it is affected.

What it is: CVE-2023-45797 is a critical memory corruption vulnerability in Dream Security MagicLine4NX, published on 30 Oct 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-2023-45797 in the wild and no public exploit code.

Affected product: Dream Security MagicLine4NX. 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-2023-45797/ (Markdown: https://insights.sbomify.com/CVE-2023-45797/index.md)
```

## Sources

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

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