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

Fix current dependabot alerts #561

Closed
roman-khimov opened this issue May 10, 2023 · 4 comments
Closed

Fix current dependabot alerts #561

roman-khimov opened this issue May 10, 2023 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@roman-khimov
Copy link
Member

Most of them are irrelevant for the project, but they're irritating anyway: https://github.com/nspcc-dev/neofs-testcases/security/dependabot

@roman-khimov roman-khimov added the bug Something isn't working label May 10, 2023
@roman-khimov
Copy link
Member Author

This repository is the one and only source of dependabot alerts for the whole NSPCC org now. Please, fix it.

vvarg229 added a commit to vvarg229/neofs-testcases that referenced this issue May 24, 2023
vvarg229 added a commit to vvarg229/neofs-testcases that referenced this issue May 24, 2023
vvarg229 added a commit to vvarg229/neofs-testcases that referenced this issue May 25, 2023
The py library through 1.11.0 for Python allows remote attackers to conduct
a ReDoS.

The developers of the pytest package have released version 7.2.0 which removes
their dependency on py.

The pytest version has already been updated to version 7.3.1.

Signed-off-by: Oleg Kulachenko <[email protected]>
roman-khimov added a commit that referenced this issue May 25, 2023
@vvarg229
Copy link
Collaborator

@roman-khimov
One dependabot warning remains:
https://github.com/nspcc-dev/neofs-testcases/security/dependabot/8 - The latest version of the configobj is still vulnerable.

What do you think, should I close this issue now or should I wait until the configobj is fixed?

@roman-khimov
Copy link
Member Author

Well, that's a bit unexpected and special one, so a separate issue to track it wrt to DiffSK/configobj#232 is appropriate.

@vvarg229
Copy link
Collaborator

separate issue
Done:
#568

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants