| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Helpbox. Affected is an unknown function of the file selectrequestlink.asp. Performing a manipulation of the argument sys_request_id results in sql injection. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability classified as critical has been found in Helpbox (affected version unknown). This affects an unknown functionality of the file selectrequestlink.asp. The manipulation of the argument sys_request_id with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability.
The bug was discovered 04/15/2004. The weakness was published 07/21/2004 by Noam Rathaus (Website). The advisory is shared at securiteam.com. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 97 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:selectrequestlink.asp 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 (16772), OSVDB (8179†) and Secunia (SA12118†). Similar entries are available at VDB-23433, VDB-82117, VDB-82118 and VDB-82119. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.3
VulDB Base Score: 6.3
VulDB Temp Score: 6.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: Sql injectionCWE: CWE-89 / 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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
04/15/2004 🔍07/21/2004 🔍
07/22/2004 🔍
04/12/2016 🔍
10/04/2018 🔍
Sources
Advisory: securiteam.com⛔Researcher: Noam Rathaus
Status: Not defined
GCVE (VulDB): GCVE-100-82125
X-Force: 16772
Secunia: 12118
OSVDB: 8179 - HelpBox selectrequestlink.asp sys_request_id Parameter SQL Injection
See also: 🔍
Entry
Created: 04/12/2016 14:11Updated: 10/04/2018 16:23
Changes: 04/12/2016 14:11 (41), 10/04/2018 16:23 (3)
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.