CVE-2017-1000017

phpMyAdmin SSRF in replication

phpMyAdmin 4.0, 4.4 and 4.6 are vulnerable to a weakness where a user with appropriate permissions is able to connect to an arbitrary MySQL server

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

CVE-2017-1000017 has a CVSS score of 8.8 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.6.6, 4.4.15.10, 4.0.10.19); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2017-1000017? CVE-2017-1000017 is a high-severity server-side request forgery (SSRF) vulnerability in phpmyadmin/phpmyadmin (composer), affecting versions >= 4.6, < 4.6.6. It is fixed in 4.6.6, 4.4.15.10, 4.0.10.19. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
2. How severe is CVE-2017-1000017? CVE-2017-1000017 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of phpmyadmin/phpmyadmin are affected by CVE-2017-1000017? phpmyadmin/phpmyadmin (composer) versions >= 4.6, < 4.6.6 is affected.
4. Is there a fix for CVE-2017-1000017? Yes. CVE-2017-1000017 is fixed in 4.6.6, 4.4.15.10, 4.0.10.19. Upgrade to this version or later.
5. Is CVE-2017-1000017 exploitable, and should I be worried? Whether CVE-2017-1000017 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2017-1000017 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2017-1000017?
   • Upgrade phpmyadmin/phpmyadmin to 4.6.6 or later
   • Upgrade phpmyadmin/phpmyadmin to 4.4.15.10 or later
   • Upgrade phpmyadmin/phpmyadmin to 4.0.10.19 or later

Other vulnerabilities in phpmyadmin/phpmyadmin