-
Notifications
You must be signed in to change notification settings - Fork 910
Security Vulnerability Identified in software.amazon:flow:1.7 Dependency #1227
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
The flow library is a copy of aws-eventstream-java repo and is included along with the SDK before the other repo was open sourced. We have plans to remove flow from our repo and add a dependency on the other library. Can you run the check on eventstream library and cut a ticket there if vulnerability still exists? |
Thanks for the info. I confirmed that My team would like to put off migrating to v2 until this vulnerability is resolved - could we use this ticket (or a new one) to track the switch from |
Sure, we will use this for tracking. |
After discussing with the team, I am not sure if we are actually effected. The CVE says |
I was confused by that too - it seems like a strange thing to have hanging out in the flow dependency. I don't have much visibility into the library, though, so I don't have a reliable way to tell if it's a false positive or not. If your team agrees that its a false positive, that would be great news for us. I wanted to raise the issue in the first place because I don't have a good idea of what's actually going on in the potentially vulnerable dependency. |
We think its a false positive as the |
Closing this as it was a false positive. The move to the |
Running DependencyCheck on a project mid-migration to
software.amazon.awssdk:sns:2.5.29
revealed a possible vulnerability:The dependency
software.amazon:flow:1.7
contains CVE-2018-13525I don't have a good idea of how to tell if it's a false positive or not, since I don't have a clear idea of how it's being used behind-the-scenes.
Please let me know if there's any further investigation I can do to help dig up more information on this issue.
The text was updated successfully, but these errors were encountered: