Pritunl Client 1.2.2550.20 pritunl-service neutralization for logs
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Pritunl Client 1.2.2550.20. It has been rated as critical. Impacted is an unknown function of the component pritunl-service. The manipulation leads to neutralization for logs. This vulnerability is uniquely identified as CVE-2020-27519. Local access is required to approach this attack. 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 Pritunl Client 1.2.2550.20. This issue affects an unknown function of the component pritunl-service. The manipulation with an unknown input leads to a neutralization for logs vulnerability. Using CWE to declare the problem leads to CWE-117. The product does not neutralize or incorrectly neutralizes output that is written to logs. Impacted is confidentiality, integrity, and availability.
The weakness was disclosed 04/30/2021 as 87ceeae9b8ee415541d7d71de10675e699a76e5e. The advisory is shared at github.com. The identification of this vulnerability is CVE-2020-27519. Neither technical details nor an exploit are publicly available.
Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.8VulDB Meta Temp Score: 7.5
VulDB Base Score: 7.8
VulDB Temp Score: 7.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: Neutralization for logsCWE: CWE-117 / CWE-116 / CWE-74
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
10/21/2020 🔍04/30/2021 🔍
04/30/2021 🔍
05/07/2021 🔍
Sources
Advisory: 87ceeae9b8ee415541d7d71de10675e699a76e5eStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2020-27519 (🔍)
GCVE (CVE): GCVE-0-2020-27519
GCVE (VulDB): GCVE-100-174377
Entry
Created: 04/30/2021 19:24Updated: 05/07/2021 07:13
Changes: 04/30/2021 19:24 (39), 05/07/2021 07:13 (6)
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.