Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade version of apache-arrow for security #263

Open
bombard1004 opened this issue Aug 1, 2024 · 2 comments
Open

Upgrade version of apache-arrow for security #263

bombard1004 opened this issue Aug 1, 2024 · 2 comments

Comments

@bombard1004
Copy link

Npm package @databricks/sql depends on apache-arrow.

apache-arrow relies on command-line-usage, and a security vulnerability was discovered in one of the dependencies of command-line-usage. A patch has been released to address this issue. However, apache-arrow@^13.0.0 strictly specifies the version of command-line-usage, which prevents this security patch from being applied.

Starting from version 15, apache-arrow specifies the version of command-line-usage with a caret (^). The latest version of apache-arrow is 17.

Please consider upgrading the apache-arrow version to at least 15 or higher.

@kravets-levko
Copy link
Contributor

Hi @bombard1004! Thank you for reporting. Of course, we know about this issue, and did an investigation on the impact on this library. Considering that command-line-usage is used only for the arrow2csv CLI of apache-arrow, and also that no arbitrary JSON is passed to command-line-usage, we consider this a low severity for us.

Of course, we'll do an upgrade you suggested, but considering it's a major version upgrade - we need some time for proper testing.

If you have any considerations (especially something that may change our assessment of the issue) - feel free to share here

@bombard1004
Copy link
Author

Hi @kravets-levko! Thank you for sharing the results of your investigation. Based on your findings, it seems this security vulnerability does not pose a significant risk to our project.

We also understand that a major version upgrade requires time for thorough testing, and we appreciate your careful approach.

Please proceed with the upgrade when ready. Thank you for your support!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants