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

Vulnerability Roundup 7 #20078

Closed
31 of 33 tasks
grahamc opened this issue Nov 2, 2016 · 25 comments
Closed
31 of 33 tasks

Vulnerability Roundup 7 #20078

grahamc opened this issue Nov 2, 2016 · 25 comments

Comments

@grahamc
Copy link
Member

grahamc commented Nov 2, 2016

Here are all the vulnerabilities from https://lwn.net/Vulnerabilities
since our last hunt.

Notes on the list

  1. The reports have been roughly grouped by the package name. This
    isn't perfect, but is intended to help identify if a whole group
    of reports is resolved already.
  2. Some issues will be duplicated, because it affects multiple packages.
    For example, there are sometimes problems that impact thunderbird,
    and firefox. LWN might report in one vulnerability "thunderbird
    firefox". These names have been split to make sure both packages get
    addressed.
  3. By each issue is a link to code search for the package name, and
    a Github search by filename. These are to help, but may not return
    results when we do in fact package the software. If a search
    doesn't turn up, please try altering the search criteria or
    looking in nixpkgs manually before asserting we don't have it.

Instructions:

  1. Triage a report: If we don't have the software or our version isn't
    vulnerable, tick the box or add a comment with the report number,
    stating it isn't vulnerable.
  2. Fix the issue: If we do have the software and it is vulnerable,
    either leave a comment on this issue saying so, even open a pull
    request with the fix. If you open a PR, make sure to tag this
    issue so we can coordinate.
  3. When an entire section is completed, move the section to the
    "Triaged and Resolved Issues" details block below.

Upon Completion ...

Without further ado...

Assorted (21 issues)

graphicsmagick (3 issues)

kernel (2 issues)

mariadb (2 issues)

mysql (2 issues)

potrace (2 issues)

@grahamc
Copy link
Member Author

grahamc commented Nov 2, 2016

cc @FRidh, @fpletz, @NeQuissimus, @vcunat who participated last time.

Also:

  • Backport 11 curl patch to 16.09: 1e1609d

PS: I'm unusually busy this morning, and won't be able to participate as much as normal. I'll have some time here and there. Feel free to conscript your friends to help finish this out ;)

@rycee
Copy link
Member

rycee commented Nov 2, 2016

The perl-Image-Info package is vulnerable. I will push an updated version shortly.

@grahamc
Copy link
Member Author

grahamc commented Nov 2, 2016

@rycee Thank you for the patches and what-not! When you push a commit to a branch, can you add a comment on this issue with the package, and the sha that you fixed it in? that'll help me do the summary at the end.

@grahamc
Copy link
Member Author

grahamc commented Nov 2, 2016

perl-Image-Info: 68f2bc8 / f33c5f7

@rycee
Copy link
Member

rycee commented Nov 2, 2016

@grahamc Sorry, I missed that. I'll make sure to include the commit hashes in the future.

@fpletz
Copy link
Member

fpletz commented Nov 2, 2016

Django (not yet on LWN): 6ad14d4, 58ad105, b806e14

https://www.djangoproject.com/weblog/2016/nov/01/security-releases/

We should remove Django 1.5 and 1.6 as they're not maintained upstream anymore. One of the users of Django 1.6 in nixpks, reviewboard, is maintaining a version with security patches, maybe switch to this: https://www.reviewboard.org/news/2016/11/01/new-django-1-6-11-5-security-releases/

I'm currently investigating and will open a PR shortly if all goes well.

@NeQuissimus
Copy link
Member

I just took a quick look at gnutar and it needs to be changed to pull from git. But something is wrong with fetchgit, it complains about an issue in cpio of all things. Not really sure what to do.

@NeQuissimus
Copy link
Member

nginx is up-to-date. I think the vulnerability is Debian-specific

@vcunat
Copy link
Member

vcunat commented Nov 2, 2016

@NeQuissimus: tar may pose problems due to being involved in bootstrapping.

@NeQuissimus
Copy link
Member

@vcunat This is how far I got:
https://gist.github.com/NeQuissimus/9a01a2215fffba1ce789ca598486fa46

  1. Changed the fetchurl to fetchgit
  2. nix-build complains about a chain of things, which lead me back to fetchurl/boot.nix
  3. Added a , ... argument to the function there "fixes" the issue
  4. C build does not work; and I have no idea about C builds :)

fpletz added a commit that referenced this issue Nov 3, 2016
fpletz added a commit that referenced this issue Nov 3, 2016
fpletz added a commit that referenced this issue Nov 3, 2016
cc #20078

(cherry picked from commit 2b2f273)
fpletz added a commit that referenced this issue Nov 3, 2016
fpletz added a commit that referenced this issue Nov 3, 2016
cc #20078

(cherry picked from commit 64902ae)
fpletz added a commit that referenced this issue Nov 3, 2016
fpletz added a commit that referenced this issue Nov 3, 2016
Fixes:

  - CVE-2016-8704
  - CVE-2016-8705
  - CVE-2016-8706

Closes #20079.

cc #20078

(cherry picked from commit a94bd88)
@grahamc
Copy link
Member Author

grahamc commented Nov 4, 2016

@vcunat can you help me out with fixing the tar issue? I'd love to understand how that process works.

@grahamc
Copy link
Member Author

grahamc commented Nov 4, 2016

BTW thank you everyone for help with this roundup. I've had an incredibly busy week, and regret not being more involved. I'll do a summary on this one shortly.

@grahamc
Copy link
Member Author

grahamc commented Nov 5, 2016

I'm closing out this issue for now, but it is important to note hydra hasn't passed in some time: https://hydra.nixos.org/build/43025591 can someone diagnose this issue and try and get a fix in?

Also, we really need to get this tar issue fixed. @vcunat If not you, who could show me the process here?

@grahamc grahamc closed this as completed Nov 5, 2016
@shlevy
Copy link
Member

shlevy commented Nov 5, 2016

@grahamc What's the issue with tar? I can help.

@shlevy
Copy link
Member

shlevy commented Nov 5, 2016

@grahamc fix for the nss issue 80cbb8a

@grahamc
Copy link
Member Author

grahamc commented Nov 5, 2016

Thank you for the nss patch, @shlevy! Regarding tar, it is mishandling .. in archives: https://lwn.net/Vulnerabilities/705216/ which @NeQuissimus was trying to patch: https://gist.github.com/NeQuissimus/9a01a2215fffba1ce789ca598486fa46

@shlevy
Copy link
Member

shlevy commented Nov 5, 2016

Testing a fix

@shlevy
Copy link
Member

shlevy commented Nov 5, 2016

ac59e2f
674ebc2

@shlevy
Copy link
Member

shlevy commented Nov 5, 2016

Will link to jobsets shortly...

@shlevy
Copy link
Member

shlevy commented Nov 5, 2016

Well, I wanted to link to evals but the loop is taking too long ( @edolstra @rbvermaa everyting good with hydra?) http://hydra.nixos.org/jobset/nixos/staging http://hydra.nixos.org/jobset/nixos/staging-16.09 I'll check back in the morning.

@vcunat
Copy link
Member

vcunat commented Nov 5, 2016

It does compilation during eval! http://hydra.nixos.org/jobset/nixos/staging#tabs-errors

@vcunat
Copy link
Member

vcunat commented Nov 5, 2016

Using git would complicate the bootstrapping process and make it longer, so it's nicer to avoid that like shlevy did.

@vcunat
Copy link
Member

vcunat commented Nov 5, 2016

I can post a few lines about (linux stdenv) bootstrapping here/somewhere, if you're still interested.

@grahamc
Copy link
Member Author

grahamc commented Nov 5, 2016

Yes please!

@shlevy
Copy link
Member

shlevy commented Nov 5, 2016

The build-during-eval is due to the cjdns test...

@grahamc grahamc mentioned this issue Nov 9, 2016
42 tasks
@grahamc grahamc mentioned this issue Nov 16, 2016
29 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants