CVE-2024-49760

OpenRefine is a free, open source tool for working with messy data. The load-language command expects a lang parameter from which it constructs the path of the localization file to load, of the form translations-$LANG.json. But when doing so in versions prior to 3.8.3, it does not check that the resulting path is in the expected directory, which means that this command could be exploited to read other JSON files on the file system. Version 3.8.3 addresses this issue.

OpenRefine is a free, open source tool for working with messy data. The load-language command expects a lang parameter from which it constructs the path of the localization file to load, of the form translations-$LANG.json. But when doing so in versions prior to 3.8.3, it does not check that the resulting path is in the expected directory, which means that this command could be exploited to read other JSON files on the file system. Version 3.8.3 addresses this issue.

The load-language command expects a lang parameter from which it constructs the path of the localization file to load, of the form translations-$LANG.json. When doing so, it does not check that the resulting path is in the expected directory, which means that this command could be exploited to read other JSON files on the file system.

The command should be patched by checking that the normalized path is in the expected directory.

OpenRefine is a free, open source tool for working with messy data. The load-language command expects a lang parameter from which it constructs the path of the localization file to load, of the form translations-$LANG.json. But when doing so in versions prior to 3.8.3, it does not check that the resulting path is in the expected directory, which means that this command could be exploited to read other JSON files on the file system. Version 3.8.3 addresses this issue.

OpenRefine is a free, open source tool for working with messy data. The load-language command expects a lang parameter from which it constructs the path of the localization file to load, of the form translations-$LANG.json. But when doing so in versions prior to 3.8.3, it does not check that the resulting path is in the expected directory, which means that this command could be exploited to read other JSON files on the file system. Version 3.8.3 addresses this issue.

OpenRefine is a free, open source tool for working with messy data. The load-language command expects a lang parameter from which it constructs the path of the localization file to load, of the form translations-$LANG.json. But when doing so in versions prior to 3.8.3, it does not check that the resulting path is in the expected directory, which means that this command could be exploited to read other JSON files on the file system. Version 3.8.3 addresses this issue.

The load-language command expects a lang parameter from which it constructs the path of the localization file to load, of the form translations-$LANG.json. When doing so, it does not check that the resulting path is in the expected directory, which means that this command could be exploited to read other JSON files on the file system.

The command should be patched by checking that the normalized path is in the expected directory.

OpenRefine is a free, open source tool for working with messy data. The load-language command expects a lang parameter from which it constructs the path of the localization file to load, of the form translations-$LANG.json. But when doing so in versions prior to 3.8.3, it does not check that the resulting path is in the expected directory, which means that this command could be exploited to read other JSON files on the file system. Version 3.8.3 addresses this issue.

It was discovered that OpenRefine did not properly handle opening tar files. If a user or application were tricked into opening a crafted tar file, an attacker could possibly use this issue to execute arbitrary code. This issue only affected Ubuntu 22.04 LTS. (CVE-2023-37476)

It was discovered that OpenRefine incorrectly handled file permissions and user authentication. An unauthenticated attacker could possibly use this issue to leak sensitive information or execute arbitrary code. This issue only affected Ubuntu 22.04 LTS. (CVE-2023-41886, CVE-2023-41887)

It was discovered that OpenRefine did not properly disallow database settings to be modified when queried. An attacker could possibly use this issue to leak sensitive information. This issue only affected Ubuntu 22.04 LTS and Ubuntu 24.04 LTS. (CVE-2024-23833)

It was discovered that OpenRefine did not properly sanitize the GET parameter for authorized commands, leading to a cross site scripting vulnerability. An attacker could possibly use this issue to execute arbitrary code. (CVE-2024-47878)

It was discovered that OpenRefine did not properly prevent cross-site request forgery when running the preview-expression command. If a user or application were tricked into opening a specially crafted webpage, an attacker could possibly use this issue to execute arbitrary code. (CVE-2024-47879)

It was discovered that OpenRefine did not properly handle HTTP headers. An attacker could possibly use this issue to execute arbitrary code. (CVE-2024-47880)

It was discovered that OpenRefine incorrectly handled database extensions. An attacker could possibly use this issue to execute arbitrary code. (CVE-2024-47881)

It was discovered that OpenRefine did not properly escape HTML tags in exception messages, which could enable code injection. If a user or application were tricked into opening a malicious file, an attacker could use this issue to execute arbitrary code. (CVE-2024-47882)

It was discovered that OpenRefine did not correctly handle paths when executing the load-language command. An attacker could possibly use this issue to leak sensitive information. (CVE-2024-49760)