| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in VegaDNS 0.8.1/0.9.8. Impacted is an unknown function of the file index.php. This manipulation of the argument Message causes cross site scripting. This vulnerability appears as CVE-2005-2610. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability was found in VegaDNS 0.8.1/0.9.8. It has been declared as problematic. Affected by this vulnerability is some unknown processing of the file index.php. The manipulation of the argument message 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 summary by CVE is:
Cross-site scripting (XSS) vulnerability in index.php in VegaDNS 0.8.1, 0.9.8, and possibly other versions, allows remote attackers to inject arbitrary web script or HTML via the message parameter.
The weakness was presented 08/17/2005 (Packetstorm). The advisory is shared at packetstormsecurity.org. This vulnerability is known as CVE-2005-2610 since 08/17/2005. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
By approaching the search of inurl:index.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 SecurityFocus (BID 14538†) and Secunia (SA16370†). See VDB-26052, VDB-40399, VDB-48982 and VDB-50309 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: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Cross site scriptingCWE: CWE-80 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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
08/10/2005 🔍08/10/2005 🔍
08/17/2005 🔍
08/17/2005 🔍
08/17/2005 🔍
03/11/2015 🔍
07/10/2018 🔍
Sources
Advisory: packetstormsecurity.orgStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2005-2610 (🔍)
GCVE (CVE): GCVE-0-2005-2610
GCVE (VulDB): GCVE-100-26053
SecurityFocus: 14538 - VegaDNS Index.PHP Cross Site Scripting Vulnerability
Secunia: 16370 - VegaDNS "message" Cross-Site Scripting Vulnerability, Less Critical
See also: 🔍
Entry
Created: 03/11/2015 23:39Updated: 07/10/2018 09:08
Changes: 03/11/2015 23:39 (49), 07/10/2018 09:08 (7)
Complete: 🔍
Cache ID: 216:4E5: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.