| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in SWHKD 1.1.5. Affected is an unknown function of the file /tmp/swhkd.pid. Performing a manipulation results in temp file. This vulnerability is identified as CVE-2022-27815. There is not any exploit available. It is suggested to install a patch to address this issue.
Details
A vulnerability, which was classified as problematic, was found in SWHKD 1.1.5. This affects some unknown processing of the file /tmp/swhkd.pid. The manipulation with an unknown input leads to a temp file vulnerability. CWE is classifying the issue as CWE-377. Creating and using insecure temporary files can leave application and system data vulnerable to attack. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was released 03/30/2022 as e661a4940df78fbb7b52c622ac4ae6a3a7f7d8aa. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2022-27815 since 03/24/2022. Technical details are known, but no exploit is available.
Applying the patch e661a4940df78fbb7b52c622ac4ae6a3a7f7d8aa 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
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
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: Temp fileCWE: CWE-377
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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: e661a4940df78fbb7b52c622ac4ae6a3a7f7d8aa
Timeline
03/24/2022 🔍03/30/2022 🔍
03/30/2022 🔍
04/01/2022 🔍
Sources
Advisory: e661a4940df78fbb7b52c622ac4ae6a3a7f7d8aaStatus: Confirmed
CVE: CVE-2022-27815 (🔍)
GCVE (CVE): GCVE-0-2022-27815
GCVE (VulDB): GCVE-100-196041
Entry
Created: 03/30/2022 08:15Updated: 04/01/2022 09:51
Changes: 03/30/2022 08:15 (40), 04/01/2022 09:51 (1)
Complete: 🔍
Cache ID: 216:355: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.