| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in TeamSpeak Server. This vulnerability affects the function PacketHandler::inINITPacket_SolvePuzzle. Executing a manipulation can lead to memory corruption.
Furthermore, there is an exploit available.
Details
A vulnerability classified as problematic was found in TeamSpeak Server (version unknown). This vulnerability affects the function PacketHandler::inINITPacket_SolvePuzzle. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect availability.
The weakness was shared 08/12/2016 by Hanz Jenson as not defined mailinglist post (Full-Disclosure). The advisory is available at seclists.org. The vendor was not involved in the coordination of the public release. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details and also a private exploit are known. The advisory points out:
In PacketHandler::inINITPacket_SolvePuzzle we initialize a ParameterParser. It keeps a vector of parameters. Later, in ServerParser::inPacket, we call ParameterParser::getParam to get the parameter at index 0. However it's possible to send just the string " " which will result in the ParameterParser vector having zero entries. Then this zero-indexing will go out of bounds.
It is declared as proof-of-concept. The advisory illustrates:
This is unfortunately a DoS at best since the retrieved parameter is just compared against "clientinitiv", which isn't terribly useful.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-90866, VDB-90867, VDB-90868 and VDB-90869 are related to this item. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Private
Status: Proof-of-Concept
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
08/12/2016 🔍08/19/2016 🔍
03/30/2019 🔍
Sources
Advisory: seclists.orgResearcher: Hanz Jenson
Status: Not defined
GCVE (VulDB): GCVE-100-90874
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 08/19/2016 14:13Updated: 03/30/2019 23:30
Changes: 08/19/2016 14:13 (43), 03/30/2019 23:30 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.