some security issues have been identified and corrected https://www.phpmyadmin.net/news/2022/1/22/phpmyadmin-498-512-and-520-rc1-are-released/
Updated phpmyadmin package fix security vulnerabilities: A flaw was identified in how phpMyAdmin processes two factor authentication; a user could potentially manipulate their account to bypass two factor authentication in subsequent authentication sessions (PMASA-2022-1). A series of weaknesses was identified allowing a malicious user to submit malicious information to present an XSS or HTML injection attack in the graphical setup page (PMASA-2022-2). In some scenarios, potentially sensitive information such as a the database name can be part of the URL. This can now be optionally encrypted. During a failed log on attempt, the error message reveals the target database server's hostname or IP address. This can reveal some information about the network infrastructure to an attacker. Fixed some situations where a user is logged out when working with more than one server Fixed a problem with assigning privileges to a user using the multiselect list when the database name has an underscore Enable cookie parameter "SameSite" when the PHP version is 7.3 or newer. References: https://www.phpmyadmin.net/news/2022/1/22/phpmyadmin-498-512-and-520-rc1-are-released/ ======================== Updated packages in core/updates_testing: ======================== phpmyadmin-5.1.2-1.mga8.noarch.rpm SRPM: phpmyadmin-5.1.2-1.mga8.src.rpm
Assignee: mageia => qa-bugs
You should use the CVE identifiers for the security issues. Additional references: https://www.phpmyadmin.net/security/PMASA-2022-1/ https://www.phpmyadmin.net/security/PMASA-2022-2/
MGA8-64 Plasma on Lenovo B50 in Dutch No installation issues Using php 8.0.4, worked OK Deleted previous test database, inserted new table with 4 columns, a PK and one unique keyand a timestamp. Filled in a few values, all OK.
CC: (none) => herman.viaeneWhiteboard: (none) => MGA8-64-OK
Validating. Advisory in Comment 1.
CC: (none) => andrewsfarm, sysadmin-bugsKeywords: (none) => validated_update
Keywords: (none) => advisoryCC: (none) => davidwhodgins
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGASA-2022-0036.html
Status: NEW => RESOLVEDResolution: (none) => FIXED
(In reply to David Walser from comment #2) > You should use the CVE identifiers for the security issues. Additional > references: > https://www.phpmyadmin.net/security/PMASA-2022-1/ > https://www.phpmyadmin.net/security/PMASA-2022-2/ These now have CVE-2022-23807 and CVE-2022-23808.
The time it was written, no CVE was assigned.
CVE: (none) => CVE-2022-23807,CVE-2022-23808.
Yes, that's why I updated the bug now.