HiveMail up to 3.1 Installation search.results.php information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in HiveMail up to 3.1 and classified as problematic. This impacts an unknown function of the file search.results.php of the component Installation. Performing a manipulation results in information disclosure. This vulnerability was named CVE-2006-3566. There is no available exploit.
Details
A vulnerability classified as problematic has been found in HiveMail up to 3.1. This affects an unknown part of the file search.results.php of the component Installation. 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. The summary by CVE is:
search.results.php in HiveMail 3.1 and earlier allows remote attackers to obtain the installation path via certain manipulations related to the (1) searchdate and (2) folderids parameters.
The weakness was presented 07/11/2006 by r0t (Website). The advisory is shared at osvdb.org. This vulnerability is uniquely identified as CVE-2006-3566 since 07/12/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 known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
By approaching the search of inurl:search.results.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at X-Force (27696), OSVDB (27104†), Secunia (SA20993†) and SecurityTracker (ID 1016531†). See VDB-31292, VDB-31291, VDB-84245 and VDB-84246 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.7
VulDB Base Score: 5.3
VulDB Temp Score: 4.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: Unproven
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
07/11/2006 🔍07/12/2006 🔍
07/12/2006 🔍
07/12/2006 🔍
07/12/2006 🔍
07/18/2006 🔍
03/12/2015 🔍
07/31/2018 🔍
Sources
Advisory: osvdb.org⛔Researcher: r0t
Status: Not defined
CVE: CVE-2006-3566 (🔍)
GCVE (CVE): GCVE-0-2006-3566
GCVE (VulDB): GCVE-100-31293
X-Force: 27696 - HiveMail search.results.php path disclosure
Secunia: 20993 - HiveMail Cross-Site Scripting and SQL Injection Vulnerabilities, Less Critical
OSVDB: 27104 - HiveMail search.results.php Multiple Variable Path Disclosure
SecurityTracker: 1016531
See also: 🔍
Entry
Created: 03/12/2015 14:25Updated: 07/31/2018 05:50
Changes: 03/12/2015 14:25 (52), 07/31/2018 05:50 (9)
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.