| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in Piwigo up to 2.9.0. This issue affects some unknown processing of the file user_list_backend.php. The manipulation results in sql injection. This vulnerability is identified as CVE-2017-9463. The attack can be executed remotely. There is not any exploit available. VulDB is the best source for vulnerability data and more expert information about this specific topic.
Details
A vulnerability classified as critical has been found in Piwigo up to 2.9.0 (Photo Gallery Software). Affected is an unknown part of the file user_list_backend.php. The manipulation 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. CVE summarizes:
The application Piwigo is affected by a SQL injection vulnerability in version 2.9.0 and possibly prior. This vulnerability allows remote authenticated attackers to obtain information in the context of the user used by the application to retrieve data from the database. The user_list_backend.php component is affected: values of the iDisplayStart & iDisplayLength parameters are not sanitized; these are used to construct a SQL query and retrieve a list of registered users into the application.
The bug was discovered 06/13/2017. The weakness was released 06/14/2017 (GitHub Repository). The advisory is available at github.com. This vulnerability is traded as CVE-2017-9463 since 06/06/2017. The exploitability is told to be easy. It is possible to launch the attack remotely. A authentication is necessary for exploitation. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1505 by the MITRE ATT&CK project.
The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:user_list_backend.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.
Entry connected to this vulnerability is available at VDB-102547. VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Name
Version
License
Website
- Product: https://github.com/Piwigo/Piwigo/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.1
VulDB Base Score: 6.3
VulDB Temp Score: 5.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.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: 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 |
OpenVAS ID: 100689
OpenVAS Name: Piwigo Multiple Vulnerabilities
OpenVAS File: 🔍
OpenVAS Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
06/06/2017 🔍06/13/2017 🔍
06/14/2017 🔍
06/14/2017 🔍
06/15/2017 🔍
12/08/2022 🔍
Sources
Product: github.comAdvisory: 42920897ce927c236728d387f61bf03d117109a2
Status: Not defined
CVE: CVE-2017-9463 (🔍)
GCVE (CVE): GCVE-0-2017-9463
GCVE (VulDB): GCVE-100-102546
See also: 🔍
Entry
Created: 06/15/2017 10:21 AMUpdated: 12/08/2022 02:15 PM
Changes: 06/15/2017 10:21 AM (61), 12/29/2019 03:56 PM (1), 12/08/2022 02:15 PM (5)
Complete: 🔍
Cache ID: 244:5D6:40
No comments yet. Languages: en.
Please log in to comment.