dbcve.org
Stack-based Buffer OverflowWeakness · CWE-121

CVE-2024-41882

MEDIUM · 6.9 CVSS v4.0 Published 2024-12-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
75/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Team ENVY, a Security Research TEAM has found a flaw that allows for a remote code execution on the NVR. An attacker can cause a stack overflow by entering large data into URL parameters, which will result in a system reboot. The manufacturer has released patch firmware for the flaw, please refer to the manufacturer's report for details and workarounds.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A stack overflow vulnerability in NVR (Network Video Recorder) firmware allows remote attackers to inject large data into URL parameters, triggering the overflow which can lead to remote code execution and system reboot.

MitigationApply the manufacturer-released patch firmware to affected NVR devices. If patching is not immediately possible, consider network segmentation to limit exposure to untrusted networks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device is an NVR (Network Video Recorder)
    Identify the device type through manufacturer documentation, device labeling, or by accessing the device's web interface which typically presents NVR management screens (camera channels, recording settings, playback). Check the device's model number against the manufacturer's product line.
    Affected if The device is a Network Video Recorder from any manufacturer that has not released patched firmware for this vulnerability.
  2. Determine the installed firmware version
    Access the NVR administration interface (usually via web browser on port 80/443 or through a dedicated client). Navigate to System Settings, About, or Maintenance section to view the firmware version. Alternatively, some NVRs display version info on the boot screen or in the device status page.
    Affected if The installed firmware version is older than the manufacturer-provided patch for CVE-2024-41882, or the version cannot be confirmed as patched.
  3. Check if the NVR web interface is network-accessible
    Determine if the NVR's HTTP/HTTPS service is exposed to network segments beyond the local management network. Review firewall rules, port forwards, and NAT configurations. Attempt to access the NVR web login page from an untrusted network segment if you have authorization to test.
    Affected if The NVR web service (HTTP/HTTPS on ports typically 80, 443, 8080, 8443) is reachable from untrusted networks or the internet without proper access controls.
  4. Review system logs for unexpected reboots or crashes
    Access NVR system logs through the administration interface (look for System Log, Event Log, or Diagnostic sections). Check for timestamps and patterns indicating unexpected system reboots, service restarts, or crashes that coincide with network activity.
    Affected if Logs show unexplained system reboots or service interruptions that could indicate exploitation attempts against the stack overflow vulnerability.

If the device is an NVR with a firmware version that has not been confirmed as patched for CVE-2024-41882 and its web interface is network-accessible, the environment may be affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the manufacturer-released patch firmware to affected NVR devices. If patching is not immediately possible, consider network segmentation to limit exposure to untrusted networks.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-41882 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-41882 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data