ServersCheck Monitoring 8.8.10 devicescan1.html linenumber cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.2 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in ServersCheck Monitoring 8.8.10. This vulnerability affects unknown code of the file devicescan1.html. The manipulation of the argument linenumber leads to cross site scripting. The attack may be initiated remotely. There is no available exploit. It is suggested to upgrade the affected component.
Details
A vulnerability was found in ServersCheck Monitoring 8.8.10 and classified as problematic. This issue affects an unknown code of the file devicescan1.html. The manipulation of the argument linenumber with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to 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. Impacted is integrity.
The weakness was presented 09/26/2011 by Benjamin Kunz Mejri as VL-ID 93 as not defined advisory (Website). The advisory is shared at vulnerability-lab.com. The exploitation is known to be easy. The attack may be initiated remotely. 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:devicescan1.html it is possible to find vulnerable targets with Google Hacking.
Upgrading eliminates this vulnerability. A possible mitigation has been published 1 days after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at OSVDB (76042†). See VDB-91186, VDB-91187, VDB-91188 and VDB-91189 for similar entries. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.2
VulDB Base Score: 3.5
VulDB Temp Score: 3.2
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: Not defined
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: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
09/26/2011 🔍09/26/2011 🔍
09/27/2011 🔍
09/27/2011 🔍
09/06/2016 🔍
04/10/2019 🔍
Sources
Advisory: VL-ID 93Researcher: Benjamin Kunz Mejri
Status: Not defined
GCVE (VulDB): GCVE-100-91193
OSVDB: 76042
See also: 🔍
Entry
Created: 09/06/2016 12:55Updated: 04/10/2019 06:45
Changes: 09/06/2016 12:55 (47), 04/10/2019 06:45 (1)
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.