| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Achmad Zaenuri ezRADIUS 0.1. This issue affects some unknown processing of the file config.ini. Performing a manipulation results in information disclosure. This vulnerability is known as CVE-2008-1752. No exploit is available.
Details
A vulnerability, which was classified as critical, was found in Achmad Zaenuri ezRADIUS 0.1. This affects some unknown functionality of the file config.ini. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
ezRADIUS 0.1 stores sensitive information under the web root with insufficient access control, which allows remote attackers to obtain credentials via a direct request for (1) config.ini or (2) database.ini. NOTE: some of these details are obtained from third party information.
The weakness was published 04/10/2008 (Website). The advisory is shared at osvdb.org. This vulnerability is uniquely identified as CVE-2008-1752 since 04/11/2008. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
It is declared as highly functional. By approaching the search of inurl:config.ini it is possible to find vulnerable targets with Google Hacking.
The vulnerability is also documented in the databases at X-Force (41767), OSVDB (44399†) and Secunia (SA29769†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Highly functional
Google Hack: 🔍
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
04/10/2008 🔍04/11/2008 🔍
04/11/2008 🔍
04/11/2008 🔍
04/14/2008 🔍
03/16/2015 🔍
09/22/2018 🔍
Sources
Advisory: osvdb.org⛔Status: Confirmed
Confirmation: 🔍
CVE: CVE-2008-1752 (🔍)
GCVE (CVE): GCVE-0-2008-1752
GCVE (VulDB): GCVE-100-41925
X-Force: 41767 - ezRADIUS config.ini and database.ini information disclosure
Secunia: 29769 - ezRADIUS Information Disclosure Security Issue, Moderately Critical
OSVDB: 44399 - ezRADIUS config.ini / database.ini Direct Request Information Disclosure
Entry
Created: 03/16/2015 17:00Updated: 09/22/2018 09:03
Changes: 03/16/2015 17:00 (50), 09/22/2018 09:03 (7)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.