GHSA-9rmm-8fp4-26hv CVE-2016-5706
phpMyAdmin Denial Of Service (DOS) attack
High
Packagist
- Severity
- 7.5 / 10
- High · CVSS 3.0
- Exploit chance (EPSS)
- 2.81%
- Chance of exploitation in the next 30 days. Higher than 86.54% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-400 Uncontrolled Resource Consumption
- Fix
4.0.10.16- Upgrade phpmyadmin/phpmyadmin to this version or later
Description
js/get_scripts.js.php in phpMyAdmin 4.0.x before 4.0.10.16, 4.4.x before 4.4.15.7, and 4.6.x before 4.6.3 allows remote attackers to cause a denial of service via a large array in the scripts parameter.
Affected versions
Packagist
| Package | Vulnerable | Fixed in |
|---|---|---|
| phpmyadmin/phpmyadmin | >= 4.0, < 4.0.10.16 |
4.0.10.16 |
| phpmyadmin/phpmyadmin | >= 4.4, < 4.4.15.7 |
4.4.15.7 |
| phpmyadmin/phpmyadmin | >= 4.6, < 4.6.3 |
4.6.3 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
phpmyadmin/phpmyadmin Packagist → 4.0.10.16
- composer
composer require phpmyadmin/phpmyadmin:^4.0.10.16
Severity breakdown
CVSS 3.0 7.5
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Weakness
CWE-400: Uncontrolled Resource Consumption
The product does not properly control the allocation and maintenance of a limited resource.
How to prevent it
- Architecture and Design: Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.
- Architecture and Design: Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed. The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question. The second solution is simply difficult to effectively institute -- and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.
- Architecture and Design: Ensure that protocols have specific limits of scale placed on them.
- Implementation: Ensure that all failures in resource allocation place the system into a safe posture.
References
Advisories
Packages
Other links
- github.com/phpmyadmin/phpmyadmin/commit/4767f24ea4c1e3822ce71a636c341e8ad8d07aa6
- github.com/phpmyadmin/phpmyadmin/commit/805225a28c1428d7809e613c731c2126960e98df
- github.com/phpmyadmin/phpmyadmin/commit/abb3685c8702de887988fee31a97ef4d80d856a1
- security.gentoo.org/glsa/201701-32
- phpmyadmin.net/security/PMASA-2016-22
- lists.opensuse.org/opensuse-updates/2016-06/msg00113.html
- lists.opensuse.org/opensuse-updates/2016-06/msg00114.html
- debian.org/security/2016/dsa-3627
- securityfocus.com/bid/91376
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-222v-cx2c-q2f5 phpMyAdmin XSS when checking tables | Medium | Also affects phpmyadmin/phpmyadmin |
| GHSA-6hr3-44gx-g6wh Cross-site Scripting vulnerability in drag-and-drop upload of phpMyAdmin | Medium | Also affects phpmyadmin/phpmyadmin |
| GHSA-prcg-mc23-hgjh phpmyadmin contains SQL Injection vulnerability | Critical | Also affects phpmyadmin/phpmyadmin |
| GHSA-4c9q-64gq-xhx4 phpMyAdmin Cross-Site Request Forgery (CSRF) | Medium | Also affects phpmyadmin/phpmyadmin |
| GHSA-7ff4-cv53-4cjq phpMyAdmin SQL injection vulnerability | Critical | Also affects phpmyadmin/phpmyadmin |
| GHSA-6349-53vr-7hcr phpMyAdmin Cross-site Scripting (XSS) | Medium | Also affects phpmyadmin/phpmyadmin |
| GHSA-h65r-8fp8-w7cx phpMyAdmin SQL Injection | High | Also affects phpmyadmin/phpmyadmin |
| GHSA-fcww-8wvc-38q9 phpMyAdmin SQL injection vulnerability | Medium | Also affects phpmyadmin/phpmyadmin |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor