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 47 (master) #47121

Closed
16 of 17 tasks
ckauhaus opened this issue Sep 21, 2018 · 9 comments
Closed
16 of 17 tasks

Vulnerability roundup 47 (master) #47121

ckauhaus opened this issue Sep 21, 2018 · 9 comments
Labels
1.severity: security Issues which raise a security issue, or PRs that fix one

Comments

@ckauhaus
Copy link
Contributor

ckauhaus commented Sep 21, 2018

Scanned nixos/release-combined.nix @ 5664e64. Filtered out previously reported CVEs. May contain false positives.

binutils-2.30 (search, files)

exempi-2.4.5 (search, files)

ffmpeg-3.4.4 (search, files)

libsndfile-1.0.28 (search, files)

libtiff-4.0.9 (search, files)

openjpeg-2.3.0 (search, files)

procps-3.3.15 (search, files)

sddm-0.17.0 (search, files)

zip-3.0 (search, files)

Cc: @joepie91, @phanimahesh, @the-kenny, @7c6f434c, @k0001, @peterhoeg, @nh2, @LnL7, @grahamc, @adisbladis, @fpletz, @vcunat

Contact @ckauhaus for any questions.

@ckauhaus
Copy link
Contributor Author

An attempt to incorporate some 2.30 patches got stuck at #41042

@andrew-d
Copy link
Contributor

andrew-d commented Sep 22, 2018

Some initial investigations:

CVE-2018-12900 (libtiff) is marked as "no upstream fix yet" in Ubuntu's tracker.

CVE-2018-14423 (openjpeg) was reported on July 16th but appears to not have a fix yet (unmerged PR is here).

CVE-2018-1121 (procps) - "As of 2018-09-12 no upstream fix is available" from here.

CVE-2018-14345 (sddm) - #43978

CVE-2018-13410 (zip) - This appears to be disputed:

NOTE: it is unclear whether there are realistic scenarios in which an untrusted party controls the -TT value, given that the entire purpose of -TT is execution of arbitrary commands.

@andrew-d
Copy link
Contributor

Looks like CVE-2018-13419 doesn't yet have a proof-of-concept, and nobody except the reporter has been able to reproduce (see here).

@andrew-d
Copy link
Contributor

For CVE-2018-14394 and CVE-2018-14395 in ffmpeg, it looks like these fixes are included in the ffmpeg 3.4.4 release? I'm possibly reading this wrong, but:

You can confirm that both of those fixes are present in the given release tag here.

@ckauhaus
Copy link
Contributor Author

CVE-2018-14394 and CVE-2018-14395 seem to be in. vulnix reports false positives in some cases.

@vcunat vcunat added the 1.severity: security Issues which raise a security issue, or PRs that fix one label Sep 23, 2018
@xeji
Copy link
Contributor

xeji commented Sep 23, 2018

exempi: fix proposed in hfiguiere/exempi#7 , not yet merged.

@Ma27
Copy link
Member

Ma27 commented Oct 26, 2018

excempi (CVE-2018-12648) has been fixed on master in #47496.

@vcunat
Copy link
Member

vcunat commented Mar 10, 2019

@Ekleog
Copy link
Member

Ekleog commented Jul 1, 2019

Most unchecked vulns had already been fixed in the mean time, I just backported the openjpeg fix to master.

CVE-2018-13410, the last non-fixed one, is disputed with what looks like a real argument: it's an off-by-one that can be triggered only when using an option that allows arbitrary code execution. As this is the last one of this report, I'm going to close this issue. Thank you all! :)

@Ekleog Ekleog closed this as completed Jul 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.severity: security Issues which raise a security issue, or PRs that fix one
Projects
None yet
Development

No branches or pull requests

6 participants