-
-
Notifications
You must be signed in to change notification settings - Fork 533
Dependency with "vulnerable" version of py #2524
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
Comments
tox does not uses the part of the lib that has the vulnabirity so I think this is invalid for us. |
tox 4 does not uses py, 😊 and we have no plans to remove it from tox 3. tox 4 will be released eventually some time next year, hopefully. |
Right, but unfortunately tools like |
Used by tox: ``` ❯ poetry show py name : py version : 1.11.0 description : library with cross-python path, ini-parsing, io, code, log facilities required by - tox >=1.4.17 ``` But tox does not use the affected part of the library - ref: tox-dev/tox#2524 (comment)
Used by tox: ``` ❯ poetry show py name : py version : 1.11.0 description : library with cross-python path, ini-parsing, io, code, log facilities required by - tox >=1.4.17 ``` But tox does not use the affected part of the library - ref: tox-dev/tox#2524 (comment)
the py lib which has the issue is used by tox 3 but tox does not use the part of the lib which is affected tox-dev/tox#2524 pytest was updated to 7.2 prior to remove py lib
the py lib which has the issue is used by tox 3 but tox does not use the part of the lib which is affected tox-dev/tox#2524 pytest was updated to 7.2 prior to remove py lib
the py lib which has the issue is used by tox 3 but tox does not use the part of the lib which is affected tox-dev/tox#2524 pytest was updated to 7.2 prior to remove py lib
Uh oh!
There was an error while loading. Please reload this page.
Hi all,
I couldn't find this reported yet (apologies if it's duplicate), but tox has a dependency with
py
, which is currently flagged as a vulnerability: https://nvd.nist.gov/vuln/detail/CVE-2022-42969 and therefore reported by tools likesafety
andpip-audit
.There is a lot of chatter in here about whether this should be considered a vulnerability in the first place and whether the vulnerability should be taken down. It doesn't sound like the
py
maintainers are going to fix the affected code, instead they removed the dependency frompytest
altogether by vendoring the code they still needed.Is this something that could be done in
tox
as well?Thanks in advance!
The text was updated successfully, but these errors were encountered: