WiKID 2FA Enterprise Server up to 4.2.0-b2047 searchDevices.jsp buildSearchWhereClause SQL Query sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in WiKID 2FA Enterprise Server up to 4.2.0-b2047 and classified as critical. Affected is the function buildSearchWhereClause of the file searchDevices.jsp. The manipulation as part of SQL Query results in sql injection.
This vulnerability was named CVE-2019-16917. The attack may be performed from remote. There is no available exploit.
Details
A vulnerability, which was classified as critical, was found in WiKID 2FA Enterprise Server up to 4.2.0-b2047 (Content Management System). Affected is the function buildSearchWhereClause of the file searchDevices.jsp. The manipulation as part of a SQL Query 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. CVE summarizes:
WiKID Enterprise 2FA (two factor authentication) Enterprise Server through 4.2.0-b2032 is vulnerable to SQL injection through the searchDevices.jsp endpoint. The uid and domain parameters are used, unsanitized, in a SQL query constructed in the buildSearchWhereClause function.
The weakness was presented 10/17/2019. This vulnerability is traded as CVE-2019-16917 since 09/26/2019. It is possible to launch the attack remotely. A authentication is needed for exploitation. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1505.
By approaching the search of inurl:searchDevices.jsp 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.
See VDB-143872, VDB-143871, VDB-143870 and VDB-143869 for similar entries. Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
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: 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
09/26/2019 🔍10/17/2019 🔍
10/18/2019 🔍
01/16/2024 🔍
Sources
Advisory: 154912Status: Not defined
CVE: CVE-2019-16917 (🔍)
GCVE (CVE): GCVE-0-2019-16917
GCVE (VulDB): GCVE-100-143868
See also: 🔍
Entry
Created: 10/18/2019 10:32Updated: 01/16/2024 13:39
Changes: 10/18/2019 10:32 (38), 10/18/2019 10:37 (18), 01/16/2024 13:33 (4), 01/16/2024 13:39 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.