Golioth Pouch version 0.1.0, prior to commit 1b2219a1, contains a heap-based buffer overflow in BLE GATT server certificate handling. server_cert_write() allocates a heap buffer of size CONFIG_POUCH_SERVER_CERT_MAX_LEN when receiving the first fragment, then appends subsequent fragments using memcpy() without verifying that sufficient capacity remains. An adjacent BLE client can send unauthenticated fragments whose combined size exceeds the allocated buffer, causing a heap overflow and crash; integrity impact is also possible due to memory corruption.
Attack Parameters
Attack Vector
Adjacent
Requires local network access
Attack Complexity
Low
Easy to exploit
Attack Requirements
None
No additional conditions
Privileges Required
None
No privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
None
No data leak
Integrity
High
Complete data modification
Availability
High
Complete denial of service
CVSS Vector v4.0
Weakness Type (CWE)
References 4
https://blog.secmate.dev/posts/golioth-vulnerabilities-disclosure/
disclosure@vulncheck.com
https://github.com/golioth/pouch/commit/1b2219a1
disclosure@vulncheck.com
https://secmate.dev/disclosures/SECMATE-2025-0018
disclosure@vulncheck.com
https://www.vulncheck.com/advisories/golioth-pouch-ble-gatt-heap-based-buffer-o…
disclosure@vulncheck.com