Skip to content

OpenRefine Remote Code execution in project import with mysql jdbc url attack

Critical severity GitHub Reviewed Published Sep 12, 2023 in OpenRefine/OpenRefine • Updated Nov 11, 2023

Package

maven org.openrefine:database (Maven)

Affected versions

<= 3.7.4

Patched versions

3.7.5

Description

Summary

An remote Code exec vulnerability allows any unauthenticated user to exec code 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 get rce on the server through the mysql userializable If the mysql-connector-java version used on the server side is less than 8.20.
In order for the server to enable deserialization we need to set the autoDeserialize and queryInterceptors parameters in the connection string,As same with GHSA-qqh2-wvmv-h72m, since the concatenation string is a direct concatenation, it is possible to inject the required parameters after the other parameters.
image

And there is a commons-beanutils dependency library on the server side, which contains an RCE-capable deserialization exploit chain

PoC

env:
centos 7
openrefine 3.7.4
jdk11
mysql-connector-java version 8.14.0
you can use the tool https://github.com/4ra1n/mysql-fake-server to running a malicious mysql server.
for example use the CB 1.9 Gadget to exec command touch /tmp/hacked.
image
set the user to base64ZGVzZXJfQ0JfdG91Y2ggL3RtcC9oYWNrZWQ=(touch /tmp/hacked base64 encode),dataBaseName to test?autoDeserialize=true&queryInterceptors=com.mysql.cj.jdbc.interceptors.ServerStatusDiffInterceptor#.
image
image
command touch /tmp/hacked is executed.
image

Impact

An remote Code exec vulnerability allows any unauthenticated user to exec code on the server.

References

@wetneb wetneb published to OpenRefine/OpenRefine Sep 12, 2023
Published to the GitHub Advisory Database Sep 12, 2023
Reviewed Sep 12, 2023
Published by the National Vulnerability Database Sep 15, 2023
Last updated Nov 11, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.404%
(73rd percentile)

Weaknesses

CVE ID

CVE-2023-41887

GHSA ID

GHSA-p3r5-x3hr-gpg5

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.