| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in NX5 NX5Linx 1.0. It has been classified as critical. Affected by this vulnerability is an unknown functionality. This manipulation causes sql injection. This vulnerability is registered as CVE-2006-4504. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in NX5 NX5Linx 1.0. It has been declared as critical. Affected by this vulnerability is an unknown code block. The manipulation with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
SQL injection vulnerability in NX5Linx 1.0 allows remote attackers to execute arbitrary SQL commands via the (1) c and (2) l parameters.
The weakness was published 08/31/2006 by Aliaksandr Hartsuyeu (Website). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2006-4504 since 08/31/2006. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
It is declared as proof-of-concept.
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 (28602), SecurityFocus (BID 20010†) and Secunia (SA21922†). Similar entries are available at VDB-32066 and VDB-32064. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.2
VulDB Base Score: 7.3
VulDB Temp Score: 6.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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
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/31/2006 🔍08/31/2006 🔍
08/31/2006 🔍
09/13/2006 🔍
09/15/2006 🔍
03/12/2015 🔍
08/03/2018 🔍
Sources
Advisory: securityfocus.com⛔Researcher: Aliaksandr Hartsuyeu
Status: Not defined
CVE: CVE-2006-4504 (🔍)
GCVE (CVE): GCVE-0-2006-4504
GCVE (VulDB): GCVE-100-32065
X-Force: 28602 - NX5Linkx user-defined scripts SQL injection
SecurityFocus: 20010 - NX5Linkx Multiple SQL Injection Vulnerabilities
Secunia: 21922 - NX5Linx Multiple Vulnerabilities, Moderately Critical
Vupen: ADV-2006-3631
See also: 🔍
Entry
Created: 03/12/2015 15:51Updated: 08/03/2018 06:19
Changes: 03/12/2015 15:51 (51), 08/03/2018 06:19 (8)
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.