ThroughTek Kalay SDK error in handling the PSK identity

published 2024-05-15 2 y ago modified 2026-06-17 4 mo ago also EUVD-2023-58566

cvss: 8.1; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.7%; EPSS 0.7% chance of exploitation in 30 days, percentile 53%
public exploits: 0; none known

ThroughTek Kalay SDK uses a predictable PSK value in the DTLS session when encountering an unexpected PSK identity

Patch / fix

fixed in 2

owletcare cam_firmware 4.2.11
owletcare cam_2_firmware 4.2.10

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: 2 y ago (2024-05-15)

Exploit prediction

0.71% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

bitdefender.com https://bitdefender.com/blog/labs/notes-on-throughtek-kalay-vulnerabilities-and-their-impact/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.1	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
NVD	3.1	8.8	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

ThroughTek Kalay SDK
throughtek kalay_sdk

Classification

Weakness

CWE-457 Use of Uninitialized Variable
CWE-908 Use of Uninitialized Resource

References

bitdefender.com /blog/labs/notes-on-throughtek-kalay-vulnerabilities-and-their-impact/
exploit, third-party-advisory

Sources

CVE List CVE-2023-6324
NVD CVE-2023-6324

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary