-
Notifications
You must be signed in to change notification settings - Fork 304
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
Multiple high-severity vulnerabilities in Docker image #2361
Comments
Hi @WillStephen, Unfortunately, the library is no longer maintained, so there is no public solution. We're part of a startup called Seal Security that mitigates software vulnerabilities in older open source versions by backporting/creating standalone security patches - enabling more straightforward remediation in cases like this. We created an ip 1.1.5-sp1 that's vulnerability-free. As with all of our patches, it's open-source and available for free. If relevant, check out our GitHub repo if you wish to learn more, or start using our app. Please feel free to reach us at [email protected] if you have any requests/questions. |
Would you please help to look at the dependency issue? |
* Upgrade docker base image to node:20-alpine3.19 * Upgrade tedious to 16.7.1 that supports node 20 * Moved npm prepare script to prepack & prepublishOnly as prepare incorrectly runs during npm install --production see npm/cli#4027
* Upgrade docker base image to node:20-alpine3.19 * Upgrade tedious to 16.7.1 that supports node 20 * Moved npm prepare script to prepack, prepublishOnly & postinstallas & added `--ignore-scripts` as prepare does not respect `--ignore-scripts` see npm/cli#3707
* Upgrade docker base image to node:20-alpine3.19 * Upgrade tedious to 16.7.1 that supports node 20 * Moved npm prepare script to prepack, prepublishOnly & postinstallas & added `--ignore-scripts` as prepare does not respect `--ignore-scripts` see npm/cli#3707
The latest Docker image fails Trivy scans with five high-severity CVEs. There are two in the base image and three in Azurite itself.
We'd love to use Azurite but this is a bit of a problem for us - is there anyone working on updating the dependencies to fix these?
The text was updated successfully, but these errors were encountered: