# CVE-2024-41886: Improper Input Validation

> Remote attackers can inject malformed data into URL parameters to execute code or reboot the NVR, requiring firmware updates.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Dec 2024
- **Updated:** 1 Oct 2025
- **Also known as:** GHSA-69h8-p3g9-h9gc

## What is CVE-2024-41886?

CVE-2024-41886 is a medium-severity command injection vulnerability in Hanwha Vision Co., Ltd. XRN-420S, published on 24 Dec 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Team ENVY, a Security Research TEAM has found a flaw that allows for a remote code execution on the NVR. An attacker could inject malformed data into url input parameters to reboot the NVR. The manufacturer has released patch firmware for the flaw, please refer to the manufacturer's report for details and workarounds.

Weakness: CWE-755 (Improper Handling of Exceptional Conditions)

## Which versions are affected by CVE-2024-41886?


## How do I fix CVE-2024-41886?

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

## Is CVE-2024-41886 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-41886 and fix it if it is affected.

What it is: CVE-2024-41886 is a medium-severity command injection vulnerability in Hanwha Vision Co., Ltd. XRN-420S, published on 24 Dec 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-41886 in the wild and no public exploit code.

Affected product: Hanwha Vision Co., Ltd. XRN-420S. 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-2024-41886/ (Markdown: https://insights.sbomify.com/CVE-2024-41886/index.md)
```

## Sources

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

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