Skip to content
This repository has been archived by the owner on May 17, 2019. It is now read-only.

Address CVE-2018-18074 #30

Merged
merged 1 commit into from
Jan 21, 2019
Merged

Address CVE-2018-18074 #30

merged 1 commit into from
Jan 21, 2019

Conversation

jwoudenberg
Copy link
Contributor

@jwoudenberg jwoudenberg commented Jan 18, 2019

What is this?

Fixes CVE-2018-18074.

Review asks

I followed instructions in the requirements.txt file for upgrading (see commit message). Please let me know if I should have done something else (entirely possible, I have little python experience!).

We were dependent on the requests library version 2.12.0, which is
vulnerable to CVE-2018-18074. This upgrades us to a version with a fix.

I regenerated the `requirements.txt` file by running the `pip-compile`
command it mentioned. This did not result in any changes, so I removed
the file, then reran the command. This time multiple changes were made,
including an upgrade of the `requests` package to a safe version.
@jwoudenberg jwoudenberg requested a review from ento January 18, 2019 13:00
@jwoudenberg jwoudenberg changed the title Upgrade requests to fix security issue Address CVE-2018-18074 Jan 18, 2019
Copy link
Contributor

@ento ento left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Thanks for updating!

@@ -4,4 +4,8 @@
#
# pip-compile --output-file requirements.txt requirements.in
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To update, run:

I think this is actually saying "To update this file after making a change to requirements.in, run:"

There's a separate command for upgrading the version of a specific package: https://github.com/jazzband/pip-tools#updating-requirements

@ento ento merged commit 9b26886 into master Jan 21, 2019
@ento ento deleted the address-CVE-2018-18074 branch January 21, 2019 19:25
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants