| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Dayfox Designs Dayfox Blog up to 2.0. It has been classified as problematic. This affects an unknown function. Performing a manipulation results in information disclosure. This vulnerability is reported as CVE-2006-2522. Moreover, an exploit is present. It is recommended to add additional authentication.
Details
A vulnerability classified as critical has been found in Dayfox Designs Dayfox Blog up to 2.0 (Blog Software). This affects an unknown code block. 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:
Dayfox Blog 2.0 and earlier stores user credentials in edit/slog_users.txt under the web document root with insufficient access control, which allows remote attackers to gain privileges.
The weakness was disclosed 03/14/2006 by omnipresent (Website). The advisory is shared at vupen.com. This vulnerability is uniquely identified as CVE-2006-2522 since 05/22/2006. 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 unknown but an exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
After before and not just, there has been an exploit disclosed. It is declared as proof-of-concept.
It is possible to mitigate the problem by adding an authentication mechanism.
The vulnerability is also documented in the databases at X-Force (26623), OSVDB (25689†), Secunia (SA20216†) and SecurityTracker (ID 1016163†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.7
VulDB Base Score: 7.3
VulDB Temp Score: 6.7
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: Proof-of-Concept
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: AuthenticationStatus: 🔍
0-Day Time: 🔍
Timeline
03/14/2006 🔍03/14/2006 🔍
05/22/2006 🔍
05/22/2006 🔍
05/22/2006 🔍
05/22/2006 🔍
05/26/2006 🔍
03/12/2015 🔍
08/06/2017 🔍
Sources
Advisory: vupen.com⛔Researcher: omnipresent
Status: Confirmed
CVE: CVE-2006-2522 (🔍)
GCVE (CVE): GCVE-0-2006-2522
GCVE (VulDB): GCVE-100-30357
X-Force: 26623 - Dayfox Blog slog_users.txt information disclosure
Secunia: 20216 - Dayfox Blog "slog_users.txt" Exposure of User Credentials, Moderately Critical
OSVDB: 25689 - Dayfox Blog slog_users.txt User Credential Disclosure
SecurityTracker: 1016163 - Dayfox Blog Discloses Hashed Passwords to Remote Users
Vupen: ADV-2006-1904
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/12/2015 12:19Updated: 08/06/2017 14:44
Changes: 03/12/2015 12:19 (57), 08/06/2017 14:44 (8)
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.