Developers

developers@phpmyadmin.net

5 participants
7032 discussions

Re: [phpMyAdmin Developers] help accessing wordpress login

by PETAL

Hi, I hope all is well. I have a wordpress site and theme installed with MAMP. I am way out of my comfort level/knowledge. I am writing to ask if someone may be able to help me access my website? I lost track of the log in and password. Thank you. petalargie(a)gmail.com

3 years, 7 months

phpMyAdmin 5.1.0-rc2 is available

by Isaac Bennetch

Hi, I have published phpMyAdmin 5.1.0-rc2 as a quick second release candidate before 5.1.0 is officially released. Please feel free to test it out, and if you find any unreported issues you can open a new ticket at https://github.com/phpmyadmin/phpmyadmin/issues/. If this rc goes well, I expect to release 5.1.0 within a few days. Isaac and the phpMyAdmin team

3 years, 7 months

Debian translation URL missing

by Isaac Bennetch

We are getting a translation error with Weblate, apparently the Debian repository has moved. > https://salsa.debian.org/phpmyadmin-team/phpmyadmin/blob/master/debian/temp… (404 Client Error: Not Found for url: https://salsa.debian.org/phpmyadmin-team/phpmyadmin/blob/master/debian/temp… ) This has always been a very small repository but used to be part of the Debian packaging process. William (or anyone else), do you know what is happening with that repository?

3 years, 8 months

Re: [phpMyAdmin Developers] Question regarding fix of CVE 2020-26935 - SQL Injection via SearchController

by studentProject

Hi, Thank you for the quick answer. There is only one thing which confuses us, as how the vulnerability marked with CVE 2020-26935 has any danger to the system? All "dangerous" characters used for SQL injections get escaped. It is possible to send a union or a sleep command in the query but the union command is limited by the user privileges and sleep only makes everything on the attackers side slower. You can also try to send a second sql command in the where_clause but through dbi it only takes the first sql command and ignores the rest. So far as we see it, there isn't a realistic danger to the system. So why excatly did you create a cve for that, which has a relatively high score? Regards MKrebs & JHiller Students @ HAW Hof ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ Am Freitag, 18. Dezember 2020 00:01 schrieb Isaac Bennetch <bennetch(a)gmail.com>: > Hi, > > The attack vector is someone intercepting the search parameter and injecting some arbitrary SQL command there. If I recall correctly, the where_clause is not presented in the graphical interface at all and is simply present in the POST variables. It's used to build the query, but isn't going to be modified by the user, and prior to the fix we were just recalling the statement from the POST data without confirming that the user had not modified it. The fix verifies the signature of the returned portion of the query to make sure the user (or some attacker) has not injected their own statement in to the where_clause. > > If you believe the code is still vulnerable, you're welcome to write back here or send an email to security(a)phpmyadmin.net. Of course, if I have left off some detail, I'm happy to answer further questions as well as I can. > > Cheers, > Isaac from the phpMyAdmin project > > On Thu, Dec 17, 2020 at 8:45 AM studentProject via Developers <developers(a)phpmyadmin.net> wrote: > >> Hello, >> >> we are two students from the university of applied sciences Hof in Germany and for a module about IT-security we are researching the vulnerability marked with CVE 2020-26935, which describes a possible SQLi attack via SearchController. >> >> The issue has already been documented by phpmyadmin: >> https://www.phpmyadmin.net/security/PMASA-2020-6/ >> >> And the responsible fix has also been linked as a git commit in the link above: >> https://github.com/phpmyadmin/phpmyadmin/commit/d09ab9bc9d634ad08b866d42bb8… >> >> We are writing because we do not fully understand in which way the commit in question fixes any possible SQLi attacks mentioned in the CVE. As far as our research goes, we have figured out that the where_clause gets signed with an HMAC signature, which doesn't necessarily provide security against said attacks. >> >> Would you mind elaborating how the commit mentioned in the issue linked above fixes the CVE (2020-26935) in question? We are clueless considering the given commit doesn't seem to clear up the question for us. Is the commit linked in the PMASA-2020-6 note perhaps wrong? Does the fix lie in another method/class or even in the frontend instead? >> >> Regards >> MKrebs & JHiller >> Students @ HAW Hof >> _______________________________________________ >> Developers mailing list >> Developers(a)phpmyadmin.net >> https://lists.phpmyadmin.net/mailman/listinfo/developers

3 years, 8 months

phpMyAdmin 5.1.0-rc1 is released

by Isaac Bennetch

Hi, We at the phpMyAdmin project are delighted to offer a release candidate for the upcoming version 5.1.0. This release, phpMyAdmin 5.1.0-rc1, is meant as a testing release before the official release of 5.1.0, and is expected to be the only release candidate before the full release. There are many new features and bug fixes; a few highlights include: * Improve virtuality dropdown for MariaDB > 10.1 * Added an option to perform ALTER ONLINE (ALGORITHM=INPLACE) when editing a table structure * Added ip2long transformation * Improvements to linking to MySQL and MariaDB documentation * Add "Preview SQL" option on Index dialog box when creating a new table * Add a new vendor constant "CACHE_DIR" that defaults to "libraries/cache/" and store routing cache into this folder * Add $cfg['CaptchaSiteVerifyURL'] for Google ReCaptcha siteVerifyUrl * Add the password_hash PHP function as an option when inserting data * Improvements to editing and displaying columns of the JSON data type. * Added support for "SameSite=Strict" on cookies using configuration "$cfg['CookieSameSite']" * Fixed AWS RDS IAM authentication doesn't work because pma_password is truncated * Add config parameters to support third-party ReCaptcha v2 compatible APIs like hCaptcha * Add $cfg['MysqlSslWarningSafeHosts'] to set the red text black when ssl is not used on a private network * Export blobs as hex on JSON export * Fix leading space not shown in a CHAR column when browsing a table * Added a rename Button to use RENAME INDEX syntax of MySQL 5.7 (and MariaDB >= 10.5.2) * Fixed missing option to enter TABLE specific permissions when the database name contains an "_" (underscore) * Fixed a PHP notice "Trying to access array offset on value of type null" on Designer PDF export * Fix for several PHP 8 warnings or errors, giving this release full compatibility with PHP 8 There are, of course, many more fixes you can see in the ChangeLog file included with this release or online at https://demo.phpmyadmin.net/master-config/index.php?route=/changelog Downloads are available now at https://phpmyadmin.net/downloads/ Isaac for the phpMyAdmin team

3 years, 9 months

Cache warmup fails if composer is run with --no-dev

by Isaac Bennetch

I'm trying to fix the build script so I can release phpMyAdmin 5.1.0, but I've hit a strange issue with Composer and the cache warmup. I've manually defined all the "dev" packages as required, so that whether I run "composer update" or "composer update --no-dev" there are no changes to the installed packages. # composer update --no-dev # ./scripts/console cache:warmup --routing PHP Fatal error: Uncaught Error: Class 'PhpMyAdmin\Tests\Stubs\DbiDummy' not found in /var/www/pma-dev/fork/release/phpMyAdmin-5.1.0-rc1/scripts/console:41 Stack trace: #0 {main} thrown in /var/www/pma-dev/fork/release/phpMyAdmin-5.1.0-rc1/scripts/console on line 41 But # composer update # ./scripts/console cache:warmup --routing runs correctly... Any thoughts about this? I'd like to build the release without requiring all of the dev packages, but if I can't warm up the cache as part of the build, on first run phpMyAdmin throws an error message because ./cache/ isn't writable by the webserver process. Any thoughts about this?

3 years, 9 months

Question regarding fix of CVE 2020-26935 - SQL Injection via SearchController

by studentProject

Hello, we are two students from the university of applied sciences Hof in Germany and for a module about IT-security we are researching the vulnerability marked with CVE 2020-26935, which describes a possible SQLi attack via SearchController. The issue has already been documented by phpmyadmin: https://www.phpmyadmin.net/security/PMASA-2020-6/ And the responsible fix has also been linked as a git commit in the link above: https://github.com/phpmyadmin/phpmyadmin/commit/d09ab9bc9d634ad08b866d42bb8… We are writing because we do not fully understand in which way the commit in question fixes any possible SQLi attacks mentioned in the CVE. As far as our research goes, we have figured out that the where_clause gets signed with an HMAC signature, which doesn't necessarily provide security against said attacks. Would you mind elaborating how the commit mentioned in the issue linked above fixes the CVE (2020-26935) in question? We are clueless considering the given commit doesn't seem to clear up the question for us. Is the commit linked in the PMASA-2020-6 note perhaps wrong? Does the fix lie in another method/class or even in the frontend instead? Regards MKrebs & JHiller Students @ HAW Hof

3 years, 9 months

Branches and security fixes

by Isaac Bennetch

Hello team, In the past, once a release entered the LTS phase with fixes only for security issues, we would switch from the QA branch to a MAINT branch and releases would have a patch level (such as 4.0.8.1). Since we no longer do patch-level release numbers, to be more consistent with Semver and some of the tools we use, we should decide how to handle these LTS releases. It often doesn’t make sense to merge QA_4_9 in to QA_5_0 because of changed file names and different function declarations. Even though the fix is often similar, it doesn’t always merge very well (one example we’ve seen several times lately is the change in array declarations from (IIRC) [ … ] to array( … ). Would it benefit us to maintain a MAINT_4_9 branch that is meant to NOT merge to QA_5_0. In that case, a security issue would need two pull requests/commits, one for MAINT_4_9 and one for QA_5_0 (soon to be 5_1 anyway). I think that especially with the upcoming release of 5.1 this might make maintenance easier for us.

3 years, 11 months

phpMyAdmin 4.9.7 and 5.0.4 are released

by Isaac Bennetch

Welcome to the release of phpMyAdmin version 4.9.7 and 5.0.4. These are bug fix releases to address packaging problems with 4.9.6 and 5.0.3. Version 5.0.3 includes a few other minor bugs as well. Fixed in both: * Two factor authentication was broken * Incompatibilities with older PHP versions. Additional fixes in 5.0.3: * Fix for cleared search values when a Zoom search fails * Fix a PHP error when reporting a certain JavaScript error * Fixed latitude and longitude swap for geometries in edit mode * Fix CREATE TABLE not being tracked when auto tracking is enabled Sorry for the inconvenience. This is expected to be the last release of 5.0, we have scheduled 5.1.0 as the next phpMyAdmin release. This is a reminder that phpMyAdmin 4.9 is in the long-term support phase where it will only get important security fixes and critical bug fixes. Users are suggested to migrate to version 5. Downloads are available now at https://phpmyadmin.net/downloads/ For the phpMyAdmin team, Isaac

3 years, 11 months

phpMyAdmin 4.9.6 and 5.0.3 are released

by Isaac Bennetch

Hello, The phpMyAdmin team announces the release of both phpMyAdmin versions 4.9.6 and 5.0.3. Both versions contain several important security fixes: * PMASA-2020-5 XSS vulnerability with transformation feature * PMASA-2020-6 SQL injection vulnerability with the search feature In addition, 5.0.3 contains many bugfixes. Some of the highlights include: * Fix an error message about htmlspecialchars() when attempting to export XML * Support double tapping to edit on mobile * Fix the error message "Use of undefined constant MYSQLI_TYPE_JSON" when using mysqlnd * Fix fatal JS error on index creation after using Enter key to submit the form * Fix "axis-order" to swap latitude and longitude on MySQL 8.1 or newer * Fix an error when overwriting an existing query bookmark * Fix some warnings that appear with PHP 8 * Fix alter user privileges query when editing an account with MySQL 8.0.11 and newer * Fix issues regarding TIMESTAMP columns with default CURRENT_TIMESTAMP in MySQL 8.0.13 and newer * Fix a message that "Warning: error_reporting() has been disabled for security reasons" on php 7.x There are many other bugs fixes, please see the ChangeLog file included with this release for full details. Known shortcomings: Due to changes in the MySQL authentication method, PHP versions prior to 7.4 are unable to authenticate to a MySQL 8.0 or newer server (our tests show the problem actually began with MySQL 8.0.11). This relates to a PHP bug https://bugs.php.net/bug.php?id=76243. There is a workaround, that is to set your user account to use the current-style password hash method, `mysql_native_password`. This unfortunate lack of coordination has caused the incompatibility to affect all PHP applications, not just phpMyAdmin. For more details, you can see our bug tracker item at https://github.com/phpmyadmin/phpmyadmin/issues/14220. We suggest upgrading your PHP installation to take advantage of the upgraded authentication methods. Downloads are available now at https://phpmyadmin.net/downloads/

3 years, 11 months

← Newer
1
...
4
5
6
7
8
9
10
...
704
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

Developers