dbcve.org
ZephyrOperating system · Zephyrproject

CVE-2024-6444

MEDIUM · 6.5 CVSS v3.1 Published 2024-10-04
Fix available
A fix is available. Upgrade to after 3.6.0 or later.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
No proper validation of the length of user input in olcp_ind_handler in zephyr/subsys/bluetooth/services/ots/ots_client.c.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The olcp_ind_handler function in Zephyr's Bluetooth Object Transfer Service (OTS) client lacks proper validation of user input length. This could allow an attacker to provide excessively long data that may cause buffer overflows or unexpected behavior when processed without adequate bounds checking.

MitigationUpdate to a Zephyr version containing the fix for proper input length validation in the OTS client code. If unable to update, review and add explicit length checks before processing incoming OLSP indication data.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ZephyrOperating system
Affected:<= 3.6.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Zephyr version
    Check the Zephyr version in your project by examining version.h, zephyr_version.txt in the build directory, or the VERSION file in the Zephyr source tree. Run 'git log --oneline -1' in the Zephyr directory if using git.
    Affected if The Zephyr version is 3.6.0 or earlier.
  2. Confirm OTS client is enabled
    Search your build configuration (defconfig, prj.conf, or .config) for 'CONFIG_BT_OTS_CLIENT=y' or 'CONFIG_BT_OTS_CLIENT=1'. This Kconfig option enables the Bluetooth Object Transfer Service client.
    Affected if CONFIG_BT_OTS_CLIENT is set to y or 1.
  3. Verify OTS client code is compiled
    Check your build output or filesystem for the presence of 'ots_client.c' or 'libots_client.a' in the Zephyr build artifacts. Also verify that 'bt_ots_client_register' or similar OTS client API functions appear in your compiled binary.
    Affected if The OTS client source code is compiled into your firmware or application.
  4. Check for OLSP indication handling
    Inspect the application source code for usage of Bluetooth OTS client APIs, particularly functions that handle OLSP (Object List Service Profile) indications or the Object List Control Point. Look for calls to bt_ots_client_register or OTS client callbacks.
    Affected if Your application registers OTS client callbacks or processes OTS data from a remote BLE device.

You are affected if your Zephyr version is 3.6.0 or earlier, the BT_OTS_CLIENT Kconfig option is enabled, and your application uses the OTS client to exchange object list data with remote BLE devices.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 3.6.0
Interim mitigation

Update to a Zephyr version containing the fix for proper input length validation in the OTS client code. If unable to update, review and add explicit length checks before processing incoming OLSP indication data.

Recommended fix Moderate confidence

Zephyr RTOS 3.7.0 or later

  1. 1. Identify the current Zephyr RTOS version in your project by checking the manifest file (west.yml or west.yml) or the version.h header
  2. 2. Upgrade Zephyr to version 3.7.0 or later, as this vulnerability affects versions <= 3.6.0
  3. 3. Update the west.yml manifest to point to the fixed version tag (e.g., zephyr-v3.7.0) or the latest stable release
  4. 4. Run 'west update' to fetch the updated codebase
  5. 5. Rebuild and flash your firmware with the updated Zephyr version
  6. 6. Verify the build completes without errors and test functionality
Caveat Minor API changes may exist between 3.6.0 and 3.7.0; review the Zephyr release notes for any Bluetooth-related changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zephyr Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6444 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-6444 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data