-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[data grid] Snyk warning for inflight through exceljs #13187
Comments
You have created a support request under the "Priority Support" terms, which is a paid add-on to MUI X Premium ⏰. Please validate your support key using the link below: https://tools-public.mui.com/prod/pages/jyhs86t?repo=mui-x&issueId=13187 Do not share your support key in this issue! Priority Support is only provided to verified customers. Once you have verified your support key, we will remove the |
Ahh, I misunderstood and thought this was included with the MUI premium license, it looks like our support key is not valid for this |
Fwiw, this vulnerability does not apply in any way to frontend code, it can only affect nodejs HTTP requests, and the code related to it is not shipped in your bundle (I think). We're going to look into the exceljs issue, but this is not a security issue for the datagrid. |
Hi @jsyvino Are you using "overrides": {
"@mui/x-data-grid-premium": {
"exceljs": {
"archiver": "7.0.1",
"unzipper": {
".": "0.10.14",
"fstream": {
".": "1.0.12",
"rimraf": "4.4.1"
}
}
}
}
} These overrides upgrade dependencies that have no breaking changes. I tested this in https://github.com/cherniavskii/data-grid-premium-test and the Excel export works fine while the
|
@cherniavskii thanks for this, yes this is what we did for now, it just doesn't feel like a great long term solution |
@jsyvino This would be the suggested workaround for now. We are considering forking exceljs: exceljs/exceljs#2764 |
My team is also seeing the same issue. I've tried the overrides workaround, but so far haven't had any luck. Even after including the overrides in package.json, clearing node_modules, deleting our lock file, and reinstalling everything,
I'm not very familiar with overrides tho, so if I'm missing something, please let me know. |
Hi @mstrater
|
@cherniavskii, I just tried it again and I must have missed that detail. I believe it's working for me now. Sorry to bother! |
Hi everyone, If no issues are reported with this version, I plan to officially release it as |
The problem in depth
We recently upgraded our MUI pro license to MUI premium, but after making the code changes our Static Application Security Testing software (Snyk) is now surfacing a vulnerability introduced by @mui/x-data-grid-premium
It seems it is introduced through this path: @mui/x-data-grid-premium@7.4.0 › exceljs@4.4.0 › archiver@5.3.2 › archiver-utils@2.1.0 › glob@7.2.3 › inflight@1.0.6
(I know above it says @mui/x-data-grid-premium@7.4.0, but v7.5.0 also uses exceljs@4.4.0 and this was tested)
Here is the relevant link to the issue in inflight: isaacs/inflight-DEPRECATED-DO-NOT-USE#5
We are unable to use MUI Pro if it does not meet our security requirements and we are unsure how to get around this one.
I am noticing glob v9.0.0 does not have this vulnerability, archiver-utils v5.0.0 does not have this vulnerability, archiver v7.0.0 does not have this vulnerability. Any chance either of those could be pinned on your end? No clue if this is helpful, just sharing what I have found
Your environment
`npx @mui/envinfo`
Search keywords: inflight@1.0.6, security vulnerability
Duplicates
The text was updated successfully, but these errors were encountered: