Skip to content

GHSA-8m97-xc46-rw9w CVE-2016-2041

phpMyAdmin Unsafe comparison of XSRF/CSRF token

High Packagist
Severity
7.5 / 10
High · CVSS 3.0
Exploit chance (EPSS)
2.58%
Chance of exploitation in the next 30 days. Higher than 85.20% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-203 Observable Discrepancy
Fix
4.0.10.13
Upgrade phpmyadmin/phpmyadmin to this version or later

Description

libraries/common.inc.php in phpMyAdmin 4.0.x before 4.0.10.13, 4.4.x before 4.4.15.3, and 4.5.x before 4.5.4 does not use a constant-time algorithm for comparing CSRF tokens, which makes it easier for remote attackers to bypass intended access restrictions by measuring time differences.

Affected versions

Packagist

PackageVulnerableFixed in
phpmyadmin/phpmyadmin
>= 4.0, < 4.0.10.13
4.0.10.13
phpmyadmin/phpmyadmin
>= 4.4, < 4.4.15.3
4.4.15.3
phpmyadmin/phpmyadmin
>= 4.5, < 4.5.4
4.5.4

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

composer
composer require phpmyadmin/phpmyadmin:^4.0.10.13

Severity breakdown

CVSS 3.0 7.5

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

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

Weakness

CWE-203: Observable Discrepancy

The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor.

How to prevent it
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
  • Implementation: Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success. If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files. Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.

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