Topic: CVE-2010-4480 (phpMyAdmin Vulnerability)
Apparently your most recent update from January has this vulnerability. When will you be releasing an update that includes the patch? It currently causes failure on PCI Compliance.
Thx.
You are not logged in. Please login or register.
Please STOP WAR NOW! | |
![]() |
For proper configuration and installation, please use the Configuration Wizard |
Versions: PHP ≤ 7.4 is EOL - PHP 8.0.28 - PHP 8.1.19 - PHP 8.1.20RC1 - PHP 8.2.6 - PHP 8.2.7RC1
More information: #remirepo IRC channel - Twitter: @RemiRepository - Discord server
Remi's RPM repository - Forum → Open discussion → CVE-2010-4480 (phpMyAdmin Vulnerability)
Apparently your most recent update from January has this vulnerability. When will you be releasing an update that includes the patch? It currently causes failure on PCI Compliance.
Thx.
As an FYI, the following page has links to the patch commits:
This issue is classified as minor.
I think phpMyAdmin team is really aware of security issues and always release a quick update when needed.
And I always publish RPM really soon after release date.
So, I don't plan, for now, to publish a fixed RPM before upstream (or fedora maintainer) release a new version.
They may classify it that way, but CERT/NIST do not. It is classified as MEDIUM and that is why everyone is getting denied PCI Compliance.
http://web.nvd.nist.gov/view/vuln/detai … -2010-4480
We've manually implemented the very small changes needed, and it would probably be a good idea if you were to do the same so everyone using your phpMyAdmin build doesn't start getting rejected on PCI Compliance scans. Scans from four days ago were not triggering the compliance failure, but scans starting yesterday have started triggering it.
From PCI Compliance scans:
---
Synopsis : The remote web server hosts a PHP script that is prone to a cross-site scripting attack.
Description : The version of phpMyAdmin fails to validate BBcode tags in user input to the 'error' parameter of the 'error.php' script before using it to generate dynamic HTML. An attacker may be able to leverage this issue to inject arbitrary HTML or script code into a user's browser to be executed within the security context of the affected site. For example, this could be used to cause a page with arbitrary text and a link to an external site to be displayed.
See also : http://www.phpmyadmin.net/home_page/sec … 2010-9.php
Solution: Upgrade to phpMyAdmin 3.4.0-beta1 or later.
Risk Factor: Medium / CVSS
Base Score : 4.3 (CVSS2#AV:N/AC:M/Au:N/C:N/I:P/A:N)
CVE : CVE-2010-4480
BID : 45633
Other references : OSVDB:69684, EDB-ID:15699
---
Well... try phpMyAdmin-3.3.9-2...
And don't forget, you can say "thanks" and use the "donate" button.
Remi.
P.S. I'm sometine tired of so must requests, so must download (~12000 RPM per day), so few thanks...
Thank you.
As I had noted, we had already manually patched all servers. We just wanted to make you aware that as of yesterday, your current phpMyAdmin build (as of the January build) no longer allowed for PCI Compliance. We simply wanted to let you know so that you could update it before you start getting inundated with others complaining of the sudden compliance failures in cases where they were using that same build. We were simply trying to get you ahead of the game per se. We weren't "telling" or "demanding" that you update it, we were simply trying to help you out.
Remi's RPM repository - Forum → Open discussion → CVE-2010-4480 (phpMyAdmin Vulnerability)
Generated in 0.005 seconds (58% PHP - 42% DB) with 11 queries
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 2 official extensions. Copyright © 2003–2009 PunBB.