| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.8 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Airport Köln-Bonn and classified as critical. The impacted element is an unknown function of the file main.php. Performing a manipulation of the argument langID/id results in sql injection. Remote exploitation of the attack is possible. No exploit is available. To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability classified as critical has been found in Airport Köln-Bonn (the affected version unknown). This affects an unknown part of the file main.php. The manipulation of the argument langID/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 weakness was published 01/20/2012 as VL-ID 174 as not defined advisory (Website). It is possible to read the advisory at vulnerability-lab.com. It is possible to initiate the attack remotely. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.
The vulnerability was handled as a non-public zero-day exploit for at least 307 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:main.php it is possible to find vulnerable targets with Google Hacking.
Applying a patch is able to eliminate this problem. A possible mitigation has been published even before and not after the disclosure of the vulnerability.
Similar entry is available at VDB-91394. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 5.8
VulDB Base Score: 6.3
VulDB Temp Score: 5.8
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: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Timeline
03/02/2011 🔍01/03/2012 🔍
01/20/2012 🔍
09/09/2016 🔍
04/12/2019 🔍
Sources
Advisory: VL-ID 174Status: Not defined
GCVE (VulDB): GCVE-100-91395
See also: 🔍
Entry
Created: 09/09/2016 10:56Updated: 04/12/2019 11:03
Changes: 09/09/2016 10:56 (42), 04/12/2019 11:03 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.