Skip to content
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

Ruby gems CVE-2019-13117 and CVE-2019-16892 #1019

Merged
merged 1 commit into from
Dec 5, 2019

Conversation

SDBrett
Copy link
Contributor

@SDBrett SDBrett commented Nov 27, 2019

Resolves: CVE-2019-13117 and CVE-2019-16892

Fixes: #1019

Updated gemfile.lock for security vulnerability.

Updated Gemfile to specify gem versions, providing more control over versions when using bundle update. Including the Jekyll version in the Gemfile tells Nelify which version to build with.

Signed-off-by: Brett Johnson [email protected]

Resolves: CVE-2019-13117 and CVE-2019-16892

Updated gemfile.lock for security vulnerability.

Updated Gemfile to specify gem versions, providing more control over versions when using bundle update. Including the Jekyll version in the Gemfile tells Nelify which version to build with.

Signed-off-by: Brett Johnson <[email protected]>
@codecov-io
Copy link

Codecov Report

Merging #1019 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1019   +/-   ##
=======================================
  Coverage   48.33%   48.33%           
=======================================
  Files          76       76           
  Lines        5437     5437           
=======================================
  Hits         2628     2628           
  Misses       2651     2651           
  Partials      158      158

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 44be251...e189def. Read the comment docs.

Copy link
Contributor

@johnSchnake johnSchnake left a comment

Choose a reason for hiding this comment

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

Everything seems good to me; seems like an unusually large diff for the intended change but everything still seems to work as expected and I confirmed bundle-audit showed no issues.

LGTM once @jonasrosland has a chance to peek at it. (also, fwiw even though this is "out of date" with master I should be able to merge w/o issue)

@SDBrett
Copy link
Contributor Author

SDBrett commented Dec 2, 2019

Everything seems good to me; seems like an unusually large diff for the intended change but everything still seems to work as expected and I confirmed bundle-audit showed no issues.

LGTM once @jonasrosland has a chance to peek at it. (also, fwiw even though this is "out of date" with master I should be able to merge w/o issue)

The changes to Gemfile.lock to extend beyond the scope of fixing the vulnerable packages. I felt that it was a good opportunity to update the rest of the gems and prevent dependency issues.

Copy link
Contributor

@jonasrosland jonasrosland left a comment

Choose a reason for hiding this comment

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

This looks good to me, it's much better to have proper versioning than the old "hope this works" approach :)

@SDBrett SDBrett changed the title Fixes: #1018 Ruby gems CVE-2019-13117 and CVE-2019-16892 Dec 5, 2019
@johnSchnake johnSchnake merged commit 4a88c74 into vmware-tanzu:master Dec 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants