| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in lirantal daloradius. This vulnerability affects unknown code. The manipulation leads to information expsure. This vulnerability is uniquely identified as CVE-2022-4366. The attack is possible to be carried out remotely. No exploit exists. It is recommended to apply a patch to fix this issue.
Details
A vulnerability was found in lirantal daloradius (version now known). It has been rated as problematic. This issue affects some unknown processing. The manipulation with an unknown input leads to a information expsure vulnerability. Using CWE to declare the problem leads to CWE-497. The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does. Impacted is confidentiality. The summary by CVE is:
Exposure of Sensitive System Information to an Unauthorized Control Sphere in GitHub repository lirantal/daloradius prior to master branch.
The weakness was disclosed 12/09/2022. It is possible to read the advisory at huntr.dev. The identification of this vulnerability is CVE-2022-4366 since 12/08/2022. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
Applying the patch 3d11f375a76ddb3741200296e15f81d82dfb80ce is able to eliminate this problem. The bugfix is ready for download at github.com.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Vendor
Name
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.0VulDB Meta Temp Score: 6.0
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CNA Base Score: 5.3
CNA Vector (huntr.dev): 🔍
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: Information expsureCWE: CWE-497
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
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: 3d11f375a76ddb3741200296e15f81d82dfb80ce
Timeline
12/08/2022 🔍12/09/2022 🔍
12/09/2022 🔍
01/02/2023 🔍
Sources
Product: github.comAdvisory: 3d11f375a76ddb3741200296e15f81d82dfb80ce
Status: Confirmed
CVE: CVE-2022-4366 (🔍)
GCVE (CVE): GCVE-0-2022-4366
GCVE (VulDB): GCVE-100-215207
Entry
Created: 12/09/2022 08:46Updated: 01/02/2023 09:32
Changes: 12/09/2022 08:46 (48), 01/02/2023 09:29 (1), 01/02/2023 09:32 (11)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.