# CVE-2024-41883: Null Pointer Dereference

> A remote attacker can cause a denial of service by triggering a null pointer dereference via a specific URL parameter, requiring a firmware patch.

- **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:** 24 Dec 2024
- **Also known as:** GHSA-hch6-hfvx-h3mw

## What is CVE-2024-41883?

CVE-2024-41883 is a medium-severity 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 enters a special value for a specific URL parameter, resulting in a NULL pointer reference and a reboot of the NVR. The manufacturer has released patch firmware for the flaw, please refer to the manufacturer's report for details and workarounds.

Weakness: CWE-476 (NULL Pointer Dereference)

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


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

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

## Is CVE-2024-41883 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-41883 is a medium-severity 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-41883 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-41883/ (Markdown: https://insights.sbomify.com/CVE-2024-41883/index.md)
```

## Sources

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

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