| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in myEvent 1.6. It has been rated as problematic. This affects an unknown function of the file login.php of the component Error Message Handler. Performing a manipulation results in information disclosure. This vulnerability was named CVE-2007-0690. There is no available exploit.
Details
A vulnerability was found in myEvent 1.6. It has been classified as problematic. This affects an unknown function of the file login.php of the component Error Message Handler. 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:
myEvent 1.6 allows remote attackers to obtain sensitive information via (1) a Log In action without a password to login.php, or an invalid (2) view[] or (3) monthno[] parameter to myevent.php, which reveals the path in various error messages.
The weakness was presented 05/30/2007 as not defined posting (Bugtraq). It is possible to read the advisory at securityfocus.com. This vulnerability is uniquely identified as CVE-2007-0690 since 02/03/2007. 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 of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
After even before and not, there has been an exploit disclosed. It is declared as highly functional. By approaching the search of inurl:login.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 (34542) and OSVDB (34272†). See VDB-86022 for similar entry. Be aware that VulDB is the high quality source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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
02/03/2007 🔍05/07/2007 🔍
05/28/2007 🔍
05/30/2007 🔍
05/30/2007 🔍
03/15/2015 🔍
09/03/2018 🔍
Sources
Advisory: securityfocus.com⛔Status: Not defined
CVE: CVE-2007-0690 (🔍)
GCVE (CVE): GCVE-0-2007-0690
GCVE (VulDB): GCVE-100-37023
X-Force: 34542 - myEvent myevent.php and login.php path disclosure
OSVDB: 34272 - myEvent login.php Log In Action Path Disclosure
See also: 🔍
Entry
Created: 03/15/2015 15:58Updated: 09/03/2018 08:09
Changes: 03/15/2015 15:58 (53), 09/03/2018 08:09 (2)
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.