CVE-2024-41885

Published

24 December 2024

Modified

15 April 2026

CVSS Score v4 5.6

Click a component to see what it means

Raw vector

CVSS:4.0/AV:L/AC:H/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/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

EPSS Score 0.0018 8th percentile

Risk Priority 23 floored blend · peak EPSS

Summary

CVE-2024-41885 is a medium-severity Use of Hard-coded, Security-relevant Constants (CWE-547) vulnerability in Hanwhavision (inferred from references). Its CVSS base score is 5.6 (Medium).

Operationally, ranked at the 8th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to CM-6 (Configuration Settings) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

🇪🇺 ENISA EUVD: EUVD-2024-38911

Vulnerability Data

Team ENVY, a Security Research TEAM has found a flaw that allows for a remote code execution on the NVR. The seed string for the encrypt key was hardcoding. The manufacturer has released patch firmware for the flaw, please refer…

to the manufacturer's report for details and workarounds.

CWE(s): CWE-547

Related Threats

CVEs Like This One

CVE-2025-49151Shared CWE-547

CVE-2025-2079Shared CWE-547

CVE-2024-32021Shared CWE-547

CVE-2026-28256Shared CWE-547

CVE-2025-2081Shared CWE-547

CVE-2025-23253Shared CWE-547

CVE-2024-39888Shared CWE-547

CVE-2023-1712Shared CWE-547

CVE-2025-30206Shared CWE-547

Affected Assets

Hanwhavision

—

inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

CM-6 Configuration Settings partial match

Documented configuration settings externalize security-critical values so they are not hard-coded in source.

SA-15 Development Process, Standards, and Tools partial match

Requiring a documented development process and standards can mandate use of symbolic names for constants.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match

prevents

Secure SDLC practices directly enforce use of named constants and configurable values for security parameters.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.25 Secure development life cycle partial match

prevents

Secure SDLC processes can catch hard-coded constants during reviews and testing.

A.8.28 Secure coding partial match

prevents

Secure coding standards explicitly prohibit hard-coded security constants.

A.8.32 Change management none match

none

Change management may detect constant changes but does not prevent their initial hard-coding.

A.8.9 Configuration management none match

none

Configuration management can externalize constants but does not directly address coding practice.