lirantal daloradius unknown vulnerability

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.

A vulnerability was found in lirantal daloradius (unknown version). It has been rated as problematic. This issue affects some unknown processing. The manipulation with an unknown input leads to a exposure of sensitive system information to an unauthorized control sphere vulnerability. Using CWE to declare the problem leads to CWE-497. The application 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 application 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 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.

Applying the patch 3d11f375a76ddb3741200296e15f81d82dfb80ce is able to eliminate this problem. The bugfix is ready for download at




CPE 2.3info

CPE 2.2info


VulDB Meta Base Score: 6.0
VulDB 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 ( 🔒



VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍


Class: Exposure of sensitive system information to an unauthorized control sphere
CWE: CWE-497
ATT&CK: Unknown

Local: No
Remote: Yes

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒


Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍


Recommended: Patch
Status: 🔍

0-Day Time: 🔒

Patch: 3d11f375a76ddb3741200296e15f81d82dfb80ce


12/08/2022 CVE reserved
12/09/2022 +1 days Advisory disclosed
12/09/2022 +0 days VulDB entry created
01/02/2023 +24 days VulDB last update


Advisory: 3d11f375a76ddb3741200296e15f81d82dfb80ce
Status: Confirmed

CVE: CVE-2022-4366 (🔒)


Created: 12/09/2022 08:46 AM
Updated: 01/02/2023 09:32 AM
Changes: 12/09/2022 08:46 AM (48), 01/02/2023 09:29 AM (1), 01/02/2023 09:32 AM (11)
Complete: 🔍


No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!