Skip to content
Fencer Intel
high 7.5

CVE-2017-1000018 json

phpMyAdmin DoS Vulnerability

published 9y ago modified 4mo ago also GHSA-47qr-f86f-3wm4 , EUVD-2022-2329

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.8%
EPSS 1.8% chance of exploitation in 30 days, percentile 78%
public exploits
0
none known

Summary

phpMyAdmin 4.0, 4.4., and 4.6 are vulnerable to a DOS attack in the replication status by using a specially crafted table name

Patch / fix

  • packagist phpmyadmin/phpmyadmin 4.0.10.19, 4.4.15.10, 4.6.6
  • phpmyadmin phpmyadmin 4.0.10.19, 4.4.15.10, 4.6.6
  • phpmyadmin Debian 14, Debian 13, Debian 12 4:4.6.6-1

debian advisories DEBIAN-CVE-2017-1000018

  • phpMyAdmin openSUSE Tumbleweed 5.1.1-1.2

opensuse advisories openSUSE-SU-2024:11171-1

Is CVE-2017-1000018 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-1000018 updated cvss 5.3

phpMyAdmin: DOS in replication status

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.83% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P
GitHub 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
packagist phpmyadmin/phpmyadmin
>=4.6, <4.6.6
>=4.4, <4.4.15.10
>=4.0, <4.0.10.19
4.6.6
4.4.15.10
4.0.10.19

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.