| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in MySQL Eventum. The affected element is an unknown function of the file get_jsrs_data.php. This manipulation of the argument F causes cross site scripting. Remote exploitation of the attack is possible. Furthermore, an exploit is available.
Details
A vulnerability was found in MySQL Eventum (Database Software) (affected version unknown). It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the file get_jsrs_data.php. The manipulation of the argument F with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is CWE-80. The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages. As an impact it is known to affect integrity.
The weakness was published 07/31/2005 by James Bercegay with Gulftech (Website). The advisory is shared at gulftech.org. The exploitation appears to be easy. The attack can be launched remotely. It demands that the victim is doing some kind of user interaction. Technical details and also a exploit are known. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
After even before and not, there has been an exploit disclosed. It is declared as proof-of-concept. By approaching the search of inurl:get_jsrs_data.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 (21638), SecurityFocus (BID 14436†), OSVDB (18402†) and Secunia (SA16304†). Similar entries are available at VDB-1674, VDB-1673, VDB-1676 and VDB-1675. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.3
VulDB Base Score: 3.5
VulDB Temp Score: 3.3
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: 🔍
Exploiting
Class: Cross site scriptingCWE: CWE-80 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
Google Hack: 🔍
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/31/2005 🔍07/31/2005 🔍
08/01/2005 🔍
08/01/2005 🔍
04/25/2016 🔍
10/24/2018 🔍
Sources
Advisory: gulftech.orgResearcher: James Bercegay
Organization: Gulftech
Status: Not defined
GCVE (VulDB): GCVE-100-82825
X-Force: 21638
SecurityFocus: 14436 - MySQL Eventum Multiple Cross-Site Scripting Vulnerabilities
Secunia: 16304
OSVDB: 18402 - MySQL Eventum get_jsrs_data.php F Parameter XSS
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 04/25/2016 17:11Updated: 10/24/2018 10:12
Changes: 04/25/2016 17:11 (44), 10/24/2018 10:12 (7)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.