CVE-2014-7222

Public exploit available. Not confirmed exploited in the wild yet. No fix published yet.

CVSS 3.06.5Medium EPSS percentile96th11% chance in 30 days CISA KEVNot listedNo confirmed exploitation
Public exploit: 1 source FixNone yetNo fix or workaround published

Published 2018-01-08Updated 2024-11-21Sources: CVE.org, NVD

NVD CVE.org

What to do

No fixed build or workaround is published yet. Limit exposure and watch for a patch.

Teamspeak3Affected: ≤ 3.0.14Upgrade to: after 3.0.14Stated by: NVD

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record

Check whether your business uses TeamSpeak Client 3.0.14 or earlier.
Ask your IT provider to identify which users can join channels and send chat messages.
Obtain and install a vendor-supported version newer than 3.0.14; no confirmed fixed version is available in the findings.
Until updated, restrict TeamSpeak access to trusted users and remove unneeded accounts.

May need vendor or contractor work

Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

Buffer overflow in TeamSpeak Client 3.0.14 and earlier allows remote authenticated users to cause a denial of service (application crash) by connecting to a channel with a different client instance, and placing crafted data in the Chat/Server tab with two \\ (backslash) characters, a digit, a \ (backslash) character, and "z" in a series of nested img BBCODE tags.

In plain language

Written by AI from the record

TeamSpeak Client 3.0.14 and earlier can be crashed by a logged-in user, so small businesses using these versions should have their IT provider assess and limit access.

Authenticated remote denial of service in TeamSpeak Client 3.0.14 and earlier: crafted chat content with nested image tags and backslash patterns triggers a buffer overflow and application crash.

If you're affected

Voice chat disruption
Meeting interruption
Support downtime
Repeated client crashes

What is it

This is a flaw in the TeamSpeak desktop client that lets a user send a specially constructed chat message that closes the application. It is like someone using a malformed form to make a receptionist’s computer repeatedly freeze: it interrupts service but does not give them access to the business.

Who is affected

This matters to you if staff or community members use TeamSpeak Client for voice-chat channels. It is only a risk if an attacker already has a valid account and can connect to the relevant channel.

How urgent is it

A public exploit is available, meaning someone with an account may be able to deliberately crash affected clients. Treat this as an amber priority: review access and plan an upgrade promptly, especially where external users can join your TeamSpeak channels.

What to do — in detail

Confirm whether endpoints run TeamSpeak Client 3.0.14 or earlier, then review account permissions and channel membership to identify users who can connect and post chat content. The findings do not identify a confirmed fixed release or supported branch target; obtain the current supported upgrade guidance directly from TeamSpeak before deploying.

If an upgrade must wait, restrict access to trusted accounts, disable or remove unnecessary accounts, and limit untrusted users’ ability to join channels. Monitor for unexpected TeamSpeak client crashes and repeated suspicious chat content involving nested image tags or unusual backslash sequences. This CVE is not listed in CISA KEV, so no CISA remediation due date applies.

Technical context

CVE-2014-7222 is rated CVSS 6.5 (Medium) with network access, low privileges required, no user interaction, and high availability impact. The issue is CWE-20 input validation leading to a buffer overflow and authenticated application crash; the attack requires channel access and crafted Chat/Server-tab content. One public exploit is known. EPSS is 11.0% (96th percentile) with a flat trend. It is not listed in CISA KEV; there is no finding confirming exploitation in the wild.

This is a general assessment based on public vulnerability data. It does not account for your specific infrastructure — when in doubt, consult a security specialist.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS96th

Public exploit

CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

1 source with a proof of concept or module.

Exploit links, PoCs and Metasploit modules after sign-in

EPSS

11% chance of exploitation activity in the next 30 days, which ranks it in the 96th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

22 events over 3179 days, from the signal feeds we watch.

2026-09-22EPSS band changelow → moderateepss band change
2026-09-21EPSS band changemoderate → lowepss band change
2026-09-06EPSS band changelow → moderateepss band change
2026-09-05EPSS band changemoderate → lowepss band change
2026-08-31EPSS band change0 → moderateepss band change
2026-08-29EPSS band changemoderate → low

Affected products

teamspeakcommercialaka teamspeak3
- teamspeak3On-premCommunications / voip-telephony

And 1 more affected product. See all after sign-in

Technical detail

CVSS 3.0 vector

Open in the CVSS calculator

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Scored 6.5 by NVD.

How it is reached

Attack Vector NetworkExploitable remotely over the network without any special conditions
Attack Complexity LowNo special conditions — the attack can be reliably reproduced
Privileges Required LowRequires basic user-level privileges
User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

Confidentiality NoneNo confidentiality impact
Integrity NoneNo integrity impact
Availability HighTotal denial of service — the component is completely unavailable