# CVE-2023-6096: using a inappropriate encryption logic

> Inappropriate encryption logic in Hanwha Vision DVR firmware allows attackers to decrypt data, compromising confidentiality.

- **Severity:** High 7.4 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-q4p9-39fv-h479

## What is CVE-2023-6096?

CVE-2023-6096 is a high-severity vulnerability in Hanwha Vision Co., Ltd. HRX-1620, published on 26 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Vladimir Kononovich, a Security Researcher has found a flaw that using a inappropriate encryption logic on the DVR. firmware encryption is broken and allows to decrypt. The manufacturer has released patch firmware for the flaw, please refer to the manufacturer's report for details and workarounds.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

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


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

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

## Is CVE-2023-6096 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-6096 is a high-severity vulnerability in Hanwha Vision Co., Ltd. HRX-1620, published on 26 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-6096 in the wild and no public exploit code.

Affected product: Hanwha Vision Co., Ltd. HRX-1620. 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-6096/ (Markdown: https://insights.sbomify.com/CVE-2023-6096/index.md)
```

## Sources

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

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