Cyber Resilience

CVE-2023-4258

Zephyrproject Zephyr ≤ 3.4.0

Published
25 September 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 8.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
EPSS Score 0.0047 38th percentile
Risk Priority 62 floored blend · peak EPSS

Summary

CVE-2023-4258 is a high-severity Incorrect Provision of Specified Functionality (CWE-684) vulnerability in Zephyrproject Zephyr. Its CVSS base score is 8.6 (High).

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

EU & UK References

Vulnerability Data

In Bluetooth mesh implementation If provisionee has a public key that is sent OOB then during provisioning it can be sent back and will be accepted by provisionee.

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-10849Same product: Zephyrproject Zephyr
CVE-2026-10668Same product: Zephyrproject Zephyr
CVE-2023-0359Same product: Zephyrproject Zephyr
CVE-2023-4424Same product: Zephyrproject Zephyr
CVE-2023-7060Same product: Zephyrproject Zephyr
CVE-2025-1674Same product: Zephyrproject Zephyr
CVE-2026-10653Same product: Zephyrproject Zephyr
CVE-2026-10656Same product: Zephyrproject Zephyr
CVE-2026-5071Same product: Zephyrproject Zephyr
CVE-2026-10678Same product: Zephyrproject Zephyr

Affected Assets

zephyrproject
zephyr
≤ 3.4.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 1 hardening rule · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)

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.

addresses: CWE-684

Periodic checks confirm that specified security and privacy functions are actually provided and operating.

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 spec-compliant functionality and testing, while eliminating this weakness fulfills only part of the control's broader monitoring intent.

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.

finds

Security testing in development and acceptance validates that implemented functionality conforms to specifications before release.

prevents

Secure development life cycle includes requirements and verification activities that directly reduce the risk of delivering functionality that deviates from published specifications.

prevents

Explicit application security requirements and acceptance criteria help ensure the delivered software matches its intended specifications.

prevents

Change management processes reduce the chance of unintended functional deviations during updates, though they do not directly address initial specification conformance.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

RHEL 9 (1 rule)
  • V-258078 RHEL 9 must use a Linux Security Module configured to enforce limits on system services. prevents CWE-684

References