| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.8 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in drachtio server 0.8.18. Affected by this issue is some unknown functionality of the file /var/log/drachtio. The manipulation leads to permission. This vulnerability is traded as CVE-2022-45473. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to install a patch to address this issue.
Details
A vulnerability was found in drachtio server 0.8.18. It has been rated as critical. This issue affects some unknown functionality of the file /var/log/drachtio. The manipulation with an unknown input leads to a permission vulnerability. Using CWE to declare the problem leads to CWE-275. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
In drachtio-server 0.8.18, /var/log/drachtio has mode 0777 and drachtio.log has mode 0666.
The weakness was shared 11/18/2022 as 241. The advisory is shared at github.com. The identification of this vulnerability is CVE-2022-45473 since 11/18/2022. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1222 for this issue.
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2022-48339). 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: 5.9VulDB Meta Temp Score: 5.8
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
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: 🔍
Exploiting
Class: PermissionCWE: CWE-275 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
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
11/18/2022 🔍11/18/2022 🔍
11/18/2022 🔍
10/02/2026 🔍
Sources
Advisory: 241Status: Confirmed
CVE: CVE-2022-45473 (🔍)
GCVE (CVE): GCVE-0-2022-45473
GCVE (VulDB): GCVE-100-213929
EUVD: 🔍
Entry
Created: 11/18/2022 20:41Updated: 10/02/2026 07:19
Changes: 11/18/2022 20:41 (39), 12/20/2022 11:04 (2), 12/20/2022 11:10 (11), 10/02/2026 07:19 (21)
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.