A jdbc attack vulnerability exists in OpenRefine(version<=3.7.7)
Start by constructing a malicious MySQL Server (using the open source project MySQLFakeServer here). Then go to the Jdbc connection trigger vulnerability
This vulnerability is the bypass of CVE-2023-41887
vulnerability repair, the main vulnerability principle is actually the use of official syntax features, as shown in the following figure, when the connection we can perform parameter configuration in the Host part
In com.google.refine.extension.database.mysql.MySQLConnectionManager#getConnection
method in the final JdbcUrl structure
That is, in the toURI
method call here, you can see that the Host part is directly concatenated for any verification, which can be bypassed using the address feature of mysql
That is, in the toURI method call here, you can see that the Host part is directly concatenated for any verification, which can be bypassed using the address feature of mysql
Complete instructions, including specific configuration details, to reproduce the vulnerability.
Type: MySQL
Host: 127.0.0.1:3306,(host=127.0.0.1,port=3306,autoDeserialize=true,allowLoadLocalInfile=true,allowUrlInLocalInfile=true,allowLoadLocalInfileInPath=true),127.0.0.1
Port: 3306
User: win_hosts
Database: test
Due to the newer MySQL driver library in the latest version of OpenRefine (8.0.30), there is no associated deserialization utilization point, so original code execution cannot be achieved, but attackers can use this vulnerability to read sensitive files on the target server.
{ "nvd_published_at": "2024-02-12T21:15:08Z", "cwe_ids": [ "CWE-22", "CWE-863" ], "severity": "HIGH", "github_reviewed": true, "github_reviewed_at": "2024-02-12T15:08:48Z" }