Kaspersky PURE up to 3.0 RPC Server prremote.dll call_table_ref use after free

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Kaspersky PURE up to 3.0. This vulnerability affects unknown code in the library prremote.dll of the component RPC Server. This manipulation of the argument call_table_ref causes use after free. There is no exploit available. It is recommended to apply a patch to fix this issue.
Details
A vulnerability classified as very critical was found in Kaspersky PURE up to 3.0. Affected by this vulnerability is some unknown processing in the library prremote.dll of the component RPC Server. The manipulation of the argument call_table_ref with an unknown input leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was shared 05/02/2014 by ZombiE as ZDI-14-122 as confirmed advisory (Website) via Zero Day Initiative (ZDI). It is possible to read the advisory at zerodayinitiative.com. The vendor cooperated in the coordination of the public release. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/02/2019).
The vulnerability was handled as a non-public zero-day exploit for at least 326 days. During that time the estimated underground price was around $0-$5k.
Applying the patch Patch E is able to eliminate this problem. The bugfix is ready for download at support.kaspersky.com. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at Secunia (SA58490†) and SecurityTracker (ID 1030203†). Be aware that VulDB is the high quality source for vulnerability data.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.kaspersky.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 10.0VulDB Meta Temp Score: 9.5
VulDB Base Score: 10.0
VulDB Temp Score: 9.5
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: Use after freeCWE: CWE-416 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Patch: Patch E
Timeline
06/10/2013 🔍05/02/2014 🔍
05/02/2014 🔍
05/06/2014 🔍
05/07/2014 🔍
05/07/2014 🔍
04/02/2019 🔍
Sources
Vendor: kaspersky.comAdvisory: ZDI-14-122
Researcher: ZombiE
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-13159
Secunia: 58490 - Kaspersky PURE RPC Server "call_table_ref" Use-After-Free Vulnerability, Moderately Critical
SecurityTracker: 1030203
Entry
Created: 05/07/2014 11:50Updated: 04/02/2019 00:10
Changes: 05/07/2014 11:50 (52), 04/02/2019 00:10 (7)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.