-
Notifications
You must be signed in to change notification settings - Fork 182
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
Any plan to fix CVE-2022-30284 [Critical] - python-libnmap 0.7.2 ? #131
Comments
It looks like there is no active maintenance on this module at the moment, as no valid commits have been made for about a year, and obvious issues (black issue) on the last commits have not been addressed. Judging by the response noted on the CVE page, a fix is not forthcoming.
Seeing that the author feels no need to mitigate against this very easily exploited issue should send shockwaves to any user of this lib. |
Just a note here, I don't exactly know where this dispute quote comes from but these are not my words. When the bug hunter found the issue, I've accepted it as a security issue but could not provide a fix short/mid-term. Since he was waiting for publication of the issue I said the following: Bug hunter: "Ok, I'm waiting for the new release." Which translates to: since this lib (or helper if you prefer to call it like that) would most likely be interfaced, filtering should be straight forward for the developers using it. Hope it clarifies. |
@underdarknl interesting proposal! Now the world is waiting for your PR and/or your refactoring of the lib/helper. Keep me posted on your progresses. regards, |
Would like to know if there is any plan on fixing CVE-2022-30284 in python-libnmap pack 0.7.2 for Python ? This library is part of scheduled network scan in my org so require action on this
The text was updated successfully, but these errors were encountered: