| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Symantec Endpoint Protection and Endpoint Protection Small Business Edition up to 14.2 RU2. It has been rated as critical. This issue affects some unknown processing. This manipulation causes out-of-bounds. The identification of this vulnerability is CVE-2020-5830. The attack can only be executed locally. There is no exploit available. Upgrading the affected component is advised.
Details
A vulnerability has been found in Symantec Endpoint Protection and Endpoint Protection Small Business Edition up to 14.2 RU2 (Anti-Malware Software) and classified as critical. Affected by this vulnerability is an unknown function. The manipulation with an unknown input leads to a out-of-bounds vulnerability. The CWE definition for the vulnerability is CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Symantec Endpoint Protection Manager (SEPM), prior to 14.2 RU2 MP1, may be susceptible to an out of bounds vulnerability, which is a type of issue that results in an existing application reading memory outside of the bounds of the memory that had been allocated to the program.
The weakness was shared 02/03/2020 as SYMSA1505 as confirmed security advisory (Website). The advisory is shared at support.symantec.com. This vulnerability is known as CVE-2020-5830 since 01/06/2020. An attack has to be approached locally. The successful exploitation requires a single authentication. Neither technical details nor an exploit are publicly available.
Upgrading to version 14.2 RU2 MP1 or 14.2.5569.2100 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The entries VDB-149979, VDB-149980, VDB-149981 and VDB-149982 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.symantec.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.0VulDB Meta Temp Score: 3.9
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Symantec): 3.3
Vendor Vector (Symantec): 🔍
NVD Base Score: 3.3
NVD Vector: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Out-of-boundsCWE: CWE-125 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
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: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: Endpoint Protection/Endpoint Protection Small Business Edition 14.2 RU2 MP1/14.2.5569.2100
Timeline
01/06/2020 🔍02/03/2020 🔍
02/03/2020 🔍
02/12/2020 🔍
02/12/2020 🔍
Sources
Vendor: symantec.comAdvisory: SYMSA1505
Status: Confirmed
CVE: CVE-2020-5830 (🔍)
GCVE (CVE): GCVE-0-2020-5830
GCVE (VulDB): GCVE-100-149989
See also: 🔍
Entry
Created: 02/12/2020 07:41Updated: 02/12/2020 07:46
Changes: 02/12/2020 07:41 (53), 02/12/2020 07:46 (19)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.