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

CVE-2022-24434 #882

Closed
chkp-idoma opened this issue May 26, 2022 · 8 comments
Closed

CVE-2022-24434 #882

chkp-idoma opened this issue May 26, 2022 · 8 comments

Comments

@chkp-idoma
Copy link

Hi,
Please fix CVE-2022-24434
need to make sure to update dicer to be <= 0.3.1
(by updating multer when possible - please follow expressjs/multer#1095)

npm ls output:

-- routing-controllers@0.9.0 -- multer@1.4.4
-- busboy@0.2.14 -- dicer@0.2.5

@zSakuraEvilz
Copy link

zSakuraEvilz commented Jun 3, 2022

Hi
Is there no released version to fix this problem?.
This repo is dead, right?
It's been over a year and there no one new releases.

@gokuldeep-kk
Copy link

Facing a similar issue on performing a Snyk scan - https://security.snyk.io/vuln/SNYK-JS-DICER-2311764
The package version remains to be the same as mentioned above

@eladni101
Copy link

any update?

@look4regev
Copy link

It seems we have no choice but to replace to a better maintained alternative such as https://github.com/tsedio/tsed to resolve this high severity CVE. Any other ideas?

@roi972
Copy link

roi972 commented Jun 13, 2022

@look4regev @chkp-idoma - as fas as I understand the vulnerability occurs only if you expose a route with file upload.
Also, because this project isn't maintained, you can fork this project and update the related dependency. I tried this and the project tests pass (after making a small correction), but I didn't do any other tests (degradation)

@attilaorosz
Copy link
Member

Should be fixed

@look4regev
Copy link

look4regev commented Dec 13, 2022

Thanks! The new release (v0.10.0) looks packed with goodies. Much appreciated.

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

7 participants