Security 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.0057 46th percentile
Risk Priority 62 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

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 46th 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-2025-10457Same product: Zephyrproject Zephyr
CVE-2023-5055Same product: Zephyrproject Zephyr
CVE-2026-1679Same product: Zephyrproject Zephyr
CVE-2026-10685Same product: Zephyrproject Zephyr
CVE-2026-10646Same product: Zephyrproject Zephyr
CVE-2026-1677Same product: Zephyrproject Zephyr
CVE-2024-6259Same product: Zephyrproject Zephyr
CVE-2023-6881Same product: Zephyrproject Zephyr
CVE-2024-4785Same product: Zephyrproject Zephyr
CVE-2023-0359Same product: Zephyrproject Zephyr

Affected Assets

zephyrproject
zephyr
≤ 3.4.0

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.

addresses: CWE-684

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

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.

blocks

A.8.25 requires that security be designed and implemented in the SDLC (including secure coding, requirements, testing and checkpoints), but does not itself stop incorrect functionality from being exploitable once the code is written and deployed; the weakness can still be present and reachable.

blocks

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

finds

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

blocks

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

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-684, a class-level weakness, and none of its children carries one either.

References