-
-
Notifications
You must be signed in to change notification settings - Fork 137
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
False positive with loofah CVE #210
Comments
I posted this on the wrong repository. Hurrah! Sorry about that! |
No worries! I expect it's the same problem reported at #209? If so, thanks for your patience. |
Yeah it was (thanks for linking!), and I was searching around between
brakeman and loofah to establish a chronology and after all that I realised
I hadn’t updated brakeman which already fixed this. :)
…On Mon, 28 Jun 2021 at 16:33, Mike Dalessio ***@***.***> wrote:
No worries! I expect it's the same problem reported at #209
<#209>? If so, thanks for
your patience.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#210 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAATJHV3DZOJSWNJKV5XBP3TVDMDBANCNFSM47OUQ7NA>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There appears to be a false positive with identifying a loofah version vulnerable to a CVE.
This message started appearing after upgrading from
2.9.1
to2.10.0
. The nature of the error and the correlation with the version bump leads me to think there's a string vs numeric version comparison issue.Brakeman version 5.0.0
The text was updated successfully, but these errors were encountered: