Cyber Resilience

CVE-2024-29075

Published
12 November 2024
Modified
15 April 2026
CVSS Score v3.1 4.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
EPSS Score 0.0020 10th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2024-29075 is a medium-severity Active Debug Code (CWE-489) vulnerability in Jvn (inferred from references). Its CVSS base score is 4.6 (Medium).

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

OWASP Top 10 for Web (2025)

A02:2025 Security Misconfiguration

EU & UK References

Vulnerability Data

Active debug code vulnerability exists in Mesh Wi-Fi router RP562B firmware version v1.0.2 and earlier. If this vulnerability is exploited, a network-adjacent authenticated attacker may obtain or alter the settings of the device .

CWE(s)
CWE-489

Related Threats

CVEs Like This One

CVE-2026-49188Shared CWE-489
CVE-2023-32645Shared CWE-489
CVE-2025-30185Shared CWE-489
CVE-2026-9133Shared CWE-489
CVE-2024-31406Shared CWE-489
CVE-2024-7756Shared CWE-489
CVE-2024-21785Shared CWE-489
CVE-2025-46674Shared CWE-489
CVE-2025-36899Shared CWE-489
CVE-2026-54798Shared CWE-489

Affected Assets

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

Mitigating Controls

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

SC-25 Thin Nodes
addresses: CWE-489

Minimal functionality precludes inclusion of active debug code or diagnostic interfaces.

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 require removal of debug code before release, covering most of this weakness while the control addresses many other development issues.

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.29 Security testing in development and acceptance mostly match
detects

Security testing in development and acceptance catches active debug code before deployment.

A.8.9 Configuration management mostly match
prevents

Configuration management can disable or remove debug features through hardened baselines.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates removal of debug code before release.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly prohibit leaving debug code active in production.

A.8.31 Separation of development, test and production environments partial match
prevents

Separation of environments reduces risk of debug code reaching production but does not directly address its removal.

A.8.32 Change management partial match
prevents

Change management can enforce removal of debug code as part of release gates.

References