Skip to content

GHSA-wpww-hx7x-xfjh CVE-2016-6609

phpMyAdmin PHP code injection

High Packagist
Severity
8.8 / 10
High · CVSS 3.0
Exploit chance (EPSS)
2.30%
Chance of exploitation in the next 30 days. Higher than 83.30% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-77 Improper Neutralization of Special Elements used in a Command ('Command Injection')
Fix
4.6.4
Upgrade phpmyadmin/phpmyadmin to this version or later

Description

An issue was discovered in phpMyAdmin. A specially crafted database name could be used to run arbitrary PHP commands through the array export feature. All 4.6.x versions (prior to 4.6.4), 4.4.x versions (prior to 4.4.15.8), and 4.0.x versions (prior to 4.0.10.17) are affected.

Affected versions

Packagist

PackageVulnerableFixed in
phpmyadmin/phpmyadmin
>= 4.6, < 4.6.4
4.6.4
phpmyadmin/phpmyadmin
>= 4.4, < 4.4.15.8
4.4.15.8
phpmyadmin/phpmyadmin
>= 4.0, < 4.0.10.17
4.0.10.17

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.6.4

composer
composer require phpmyadmin/phpmyadmin:^4.6.4

Severity breakdown

CVSS 3.0 8.8

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Weakness

CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection')

The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.

How to prevent it
  • Architecture and Design: If at all possible, use library calls rather than external processes to recreate the desired functionality.
  • Implementation: If possible, ensure that all external commands called from the program are statically created.
  • Implementation: Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
  • Operation: Run time: Run time policy enforcement may be used in an allowlist fashion to prevent use of any non-sanctioned commands.
  • System Configuration: Assign permissions that prevent the user from accessing/opening privileged files.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy 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
Is this in your code?

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