security vulnerability in requirement version dependencies needs to be updated.
Bug #1815001 reported by
Punith Kenchappa
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pypowervm |
New
|
Undecided
|
Unassigned |
Bug Description
https:/
https:/
More info -
https:/
powervm/pypowervm [3]
Known MODERATE SEVERITY security vulnerability detected in requests
<= 2.19.1 defined in requirements.txt [4].
requirements.txt [4] update suggested: requests ~> 2.20.0.
Always verify the validity and compatibility of suggestions with
your codebase.
Review vulnerable dependency [5]
To post a comment you must log in.
I would argue that this is not a security vulnerability of pypowervm. We're not requiring a vulnerable version of requests, we're just allowing for it. Anyone concerned about the requests vulnerability (and rightly so) is welcome to use a newer version of requests with pypowervm.
If we bump our requirements to include the newer version, that will force folks to move to the newer requests version when they move to the newer pypowervm version makin that change. This is great if they can do that, but could have downstream repercussions on things like PowerVC and OpenStack. Do they require the newer version of requests? Is the newer version of requests available from all the distros where pypowervm needs to work?
Also keep in mind that it's quite possible that a distro has backported the requests security fix to older versions so that they are not vulnerable.