Summary
OpenRefine vulnerable to arbitrary file read in project import with mysql jdbc url attack
An arbitrary file read vulnerability allows any unauthenticated user to read the file on the server._
Details
Hi,Team,
i find openrefine support to import data from database,When use mysql jdbc to connect to database,It is vulnerable to jdbc url attacks,for example,unauthenticated attacker can read the file on the server.
There are some differences in utilization depending on the version of the mysql-connector dependency on the server side.
- mysql-connector-java version > 8.14
The default value ofallowLoadLocalInfileon the server side is false in this case.We need to manually set this value to true in the connection string.
Since the way to get the databaseurl incom/google/refine/extension/database/mysql/MySQLConnectionManager.javais to splice the individual configurations directly, we can set theallowLoadLocalInfileparameter after the other parameters(for example thedatabaseNameparameter ). - mysql-connector-java version <= 8.14
The default value ofallowLoadLocalInfileon the server side is true in this case.so wo don't need do anything,Just connect to our malicious server.
PoC
env:
centos 7
openrefine 3.7.4
jdk11
mysql-connector-java version 8.30.0
you can use the tool https://github.com/4ra1n/mysql-fake-server to running a malicious mysql server.
for example,to read the /etc/passwd file.
set the username to base64ZmlsZXJlYWRfL2V0Yy9wYXNzd2Q= and Database name to test?allowLoadLocalInfile=true# (for mysql-connector-java version <= 8.14,just setting the database name normally) and test to connect your malicious mysql server.
you can get the file in your fake-server-files directory.
Impact
An arbitrary file read vulnerability allows any unauthenticated user to read the file on the server._
Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.
CVE-2023-41886 has a CVSS score of 7.5 (High). The vector is network-reachable, no 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 (3.7.5); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2023-41886? CVE-2023-41886 is a high-severity SQL injection vulnerability in org.openrefine:database (maven), affecting versions <= 3.7.4. It is fixed in 3.7.5. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
- How severe is CVE-2023-41886? CVE-2023-41886 has a CVSS score of 7.5 (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.
- Which versions of org.openrefine:database are affected by CVE-2023-41886? org.openrefine:database (maven) versions <= 3.7.4 is affected.
- Is there a fix for CVE-2023-41886? Yes. CVE-2023-41886 is fixed in 3.7.5. Upgrade to this version or later.
- Is CVE-2023-41886 exploitable, and should I be worried? Whether CVE-2023-41886 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
- What actually determines whether CVE-2023-41886 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.
- How do I fix CVE-2023-41886? Upgrade
org.openrefine:databaseto 3.7.5 or later.