Cyber Resilience

CVE-2023-29243

Intel Realsense 450 Fa Firmware ≤ 0.25.0

Published
11 August 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 4.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0016 6th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2023-29243 is a medium-severity Unchecked Return Value (CWE-252) vulnerability in Intel Realsense 450 Fa Firmware. Its CVSS base score is 4.4 (Medium).

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

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Unchecked return value in some Intel(R) RealSense(TM) ID software for Intel(R) RealSense(TM) 450 FA in version 0.25.0 may allow a priviledged user to potentially enable denial of service via local access.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-32656Same product: Intel Realsense 450 Fa
CVE-2023-30760Same product: Intel Realsense 450 Fa
CVE-2023-33867Same product: Intel Realsense 450 Fa
CVE-2023-34427Same product: Intel Realsense 450 Fa
CVE-2023-33877Same product: Intel Realsense 450 Fa
CVE-2023-26591Same vendor: Intel
CVE-2023-22330Same vendor: Intel
CVE-2023-22848Same vendor: Intel
CVE-2024-32666Same vendor: Intel
CVE-2023-27386Same vendor: Intel

Affected Assets

intel
realsense 450 fa firmware
≤ 0.25.0

Mitigating Controls

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 checking and handling all function return values to detect error conditions.

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.

detects

Security testing in development and acceptance can detect missing return-value checks.

prevents

Secure development life cycle mandates verification of return values to prevent undetected failures.

prevents

Application security requirements include input/output validation and error handling that covers return-value checks.

degrades

Secure system architecture and engineering principles require robust error handling and defensive coding practices.

prevents

Secure coding explicitly requires checking return values to avoid CWE-252.

References