Skip to content

fix(ble): remediate BLE parser vulnerabilities - #707

Closed
maidang-xing wants to merge 1 commit into
tuya:masterfrom
maidang-xing:fix/ble-vulnerability-remediation
Closed

maidang-xing wants to merge 1 commit into
tuya:masterfrom
maidang-xing:fix/ble-vulnerability-remediation

Conversation

@maidang-xing

Copy link
Copy Markdown
Contributor

Summary

  • harden BLE transport and transparent-channel framing against malformed lengths, truncated varints, duplicate/out-of-order fragments, and buffer overflows
  • enforce receive-side authorization for bound/unpaired devices and destructive BLE operations
  • validate DP payloads, schema/enum values, netcfg input ownership, device-info capacity, and negotiated packet sizes
  • reject pre-activation DP requests and send DP success ACK only after application parsing succeeds

Verification

  • Host ASan/UBSan security suite: 5/5 tests passed locally (tests intentionally kept out of this PR per request)
  • ESP32-S3 BLE-enabled example: full build succeeded
  • Existing provisioning/network configuration flow manually verified successfully
  • No device flashing or radio PoC traffic was executed

The local regression tests remain untracked and are intentionally not included in this PR.

@maidang-xing
maidang-xing force-pushed the fix/ble-vulnerability-remediation branch from 01669be to 18e7aae Compare September 11, 2026 07:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant