phpMyBackupPro up to 2.5 Request Parameter scheduled.php code injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in phpMyBackupPro up to 2.5. The impacted element is an unknown function of the file scheduled.php of the component Request Parameter Handler. This manipulation causes code injection. This vulnerability appears as CVE-2015-3640. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability was found in phpMyBackupPro up to 2.5 (Backup Software). It has been declared as critical. Affected by this vulnerability is an unknown code of the file scheduled.php of the component Request Parameter Handler. The manipulation with an unknown input leads to a code injection vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
phpMyBackupPro 2.5 and earlier does not properly escape the "." character in request parameters, which allows remote authenticated users with knowledge of a web-accessible and web-writeable directory on the target system to inject and execute arbitrary PHP scripts by injecting scripts via the path, filename, and dirs parameters to scheduled.php, and making requests to injected scripts.
The bug was discovered 05/04/2017. The weakness was presented 07/21/2017 (oss-sec). The advisory is shared at openwall.com. This vulnerability is known as CVE-2015-3640 since 05/04/2015. The attack can be launched remotely. A single authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 78 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:scheduled.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.
See VDB-111028 for similar entry. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.9VulDB Meta Temp Score: 6.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
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: 🔍
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
05/04/2015 🔍05/04/2017 🔍
07/21/2017 🔍
07/21/2017 🔍
07/21/2017 🔍
01/06/2021 🔍
Sources
Advisory: openwall.comStatus: Not defined
CVE: CVE-2015-3640 (🔍)
GCVE (CVE): GCVE-0-2015-3640
GCVE (VulDB): GCVE-100-104353
SecurityTracker: 1032250
See also: 🔍
Entry
Created: 07/21/2017 20:37Updated: 01/06/2021 08:45
Changes: 07/21/2017 20:37 (58), 10/31/2019 09:17 (1), 01/06/2021 08:45 (2)
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.