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

[QUESTION] Possible to fix vulnerability issue related to dot-prop? #1560

Closed
ziale opened this issue Jul 24, 2020 · 3 comments
Closed

[QUESTION] Possible to fix vulnerability issue related to dot-prop? #1560

ziale opened this issue Jul 24, 2020 · 3 comments
Labels
Awaiting Information further information is requested Release 6.x work is associated with a specific npm 6 release

Comments

@ziale
Copy link

ziale commented Jul 24, 2020

What / Why

Anchore is reporting a vulnerability issue that is related to an old(<5.1.1) version of the dot-prop package.

I tried to trace the versions:
update-notifier depends on configstore which depends on dot-prop.

update-notifier@4.1.0 uses configstore@5.0.1 which uses dot-prop@5.2.0 where the issue has been fixed.

Is it possible to fix this?

@ljharb
Copy link
Contributor

ljharb commented Jul 24, 2020

You'd have to file that on configstore's repo, and then on update-notifier's repo.

@ziale
Copy link
Author

ziale commented Jul 27, 2020

You'd have to file that on configstore's repo, and then on update-notifier's repo.

This repo is using update-notifier 2.5.0, and 4.1.0 would fix the issues. The other repos mentioned already using the fixed versions.

@darcyclarke darcyclarke added Awaiting Information further information is requested Release 6.x work is associated with a specific npm 6 release labels Oct 30, 2020
@darcyclarke
Copy link
Contributor

npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.

If your bug is preproducible on v7, please re-file this issue using our new issue template.

If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo

Closing: This is an automated message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Information further information is requested Release 6.x work is associated with a specific npm 6 release
Projects
None yet
Development

No branches or pull requests

3 participants