| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in BitDefender my.bitdefender. It has been classified as critical. Impacted is an unknown function of the component Auth Token Handler. The manipulation leads to privileges management. The attack is possible to be carried out remotely. No exploit exists. It is suggested to install a patch to address this issue.
Details
A vulnerability, which was classified as critical, has been found in BitDefender my.bitdefender (unknown version). This issue affects an unknown code block of the component Auth Token Handler. The manipulation with an unknown input leads to a privileges management vulnerability. Using CWE to declare the problem leads to CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. Impacted is confidentiality, integrity, and availability.
The weakness was disclosed 01/09/2017 by Lawrence Amer as VL-ID 1683 as confirmed advisory (Website). The advisory is shared at vulnerability-lab.com. The public release has been coordinated in cooperation with BitDefender. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 310 days. During that time the estimated underground price was around $0-$5k.
Applying a patch is able to eliminate this problem. A possible mitigation has been published even before and not after the disclosure of the vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
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: Privileges managementCWE: CWE-269 / CWE-266
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: 🔍
Timeline
01/26/2016 🔍12/01/2016 🔍
01/09/2017 🔍
01/11/2017 🔍
07/19/2020 🔍
Sources
Advisory: VL-ID 1683Researcher: Lawrence Amer
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-95177
Entry
Created: 01/11/2017 15:32Updated: 07/19/2020 14:25
Changes: 01/11/2017 15:32 (44), 07/19/2020 14:25 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.