TestLink up to 1.9.16 Installation install/installNewDB.php code injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in TestLink up to 1.9.16. Affected by this vulnerability is an unknown functionality of the file install/installNewDB.php of the component Installation. Performing a manipulation results in code injection. This vulnerability is reported as CVE-2018-7466. The attack is possible to be carried out remotely. Moreover, an exploit is present.
Details
A vulnerability, which was classified as critical, was found in TestLink up to 1.9.16. This affects an unknown code of the file install/installNewDB.php of the component Installation. The manipulation with an unknown input leads to a code injection vulnerability. CWE is classifying the issue as CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
install/installNewDB.php in TestLink through 1.9.16 allows remote attackers to conduct injection attacks by leveraging control over DB LOGIN NAMES data during installation to provide a long, crafted value.
The bug was discovered 02/25/2018. The weakness was disclosed 02/25/2018 (Website). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2018-7466 since 02/25/2018. It is possible to initiate the attack remotely. A authentication is needed for exploitation. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1059 for this issue.
The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:install/installNewDB.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 vulnerability database at Exploit-DB (44226). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.2VulDB Meta Temp Score: 6.0
VulDB Base Score: 5.0
VulDB Temp Score: 4.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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: Code injectionCWE: CWE-94 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
02/25/2018 🔍02/25/2018 🔍
02/25/2018 🔍
02/25/2018 🔍
02/26/2018 🔍
03/20/2025 🔍
Sources
Advisory: 9696012eecbafb0aa21cc346234512c29b474679Status: Confirmed
CVE: CVE-2018-7466 (🔍)
GCVE (CVE): GCVE-0-2018-7466
GCVE (VulDB): GCVE-100-113817
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 02/26/2018 15:06Updated: 03/20/2025 20:11
Changes: 02/26/2018 15:06 (56), 01/08/2020 15:26 (4), 02/10/2023 10:35 (5), 03/20/2025 20:11 (20)
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.