Here are all the vulnerabilities from https://lwn.net/Vulnerabilities
since our last roundup.
cc: @7c6f434c @FRidh @fpletz @vcunat.
_Note:_ The list of people CC'd on this issue participated in the last
roundup. If you participate on this roundup, I'll cc you on the next
one. If you don't participate in the next one, you won't be CC'd on
the one after that. If you would like to be CC'd on the next roundup,
add a comment to the most recent vulnerability roundup.
Permanent CC's: @joepie91, @phanimahesh, @the-kenny,
@NixOS/security-notifications
If you would like to be CC'd on _all_ roundups (or removed from the
list), open a PR editing
https://github.com/NixOS/security/blob/master/lwnvulns/src/bin/instructions.md.
details
block below.reformat
one last timeWithout further ado...
#710900
](https://lwn.net/Vulnerabilities/710900/) (search, files) kopete: encryption botch#711187
](https://lwn.net/Vulnerabilities/711187/) (search, files) nvidia304, nvidia340: denial of service#710896
](https://lwn.net/Vulnerabilities/710896/) (search, files) flac: three vulnerabilities#711047
](https://lwn.net/Vulnerabilities/711047/) (search, files) icoutils: code execution#711186
](https://lwn.net/Vulnerabilities/711186/) (search, files) libtiff: XML External Entity (XXE) attacks#710627
](https://lwn.net/Vulnerabilities/710627/) (search, files) libvncserver: two vulnerabilities#711187
](https://lwn.net/Vulnerabilities/711187/) (search, files) nvidia304, nvidia340: denial of service#711050
](https://lwn.net/Vulnerabilities/711050/) (search, files) sway: unspecified#710628
](https://lwn.net/Vulnerabilities/710628/) (search, files) borgbackup: two vulnerabilities#709985
](https://lwn.net/Vulnerabilities/709985/) (search, files) dovecot: denial of service#652799
](https://lwn.net/Vulnerabilities/652799/) (search, files) hplip: man-in-the-middle attack#711189
](https://lwn.net/Vulnerabilities/711189/) (search, files) irssi: multiple vulnerabilities#711059
](https://lwn.net/Vulnerabilities/711059/) (search, files) jasper: three vulnerabilities#710626
](https://lwn.net/Vulnerabilities/710626/) (search, files) pcsclite: privilege escalation#711049
](https://lwn.net/Vulnerabilities/711049/) (search, files) php-swiftmailer: code execution#711051
](https://lwn.net/Vulnerabilities/711051/) (search, files) php7: denial of service#710895
](https://lwn.net/Vulnerabilities/710895/) (search, files) puppet-tripleo: access restriction bypass#711055
](https://lwn.net/Vulnerabilities/711055/) (search, files) syncthing: two vulnerabilities#711055
](https://lwn.net/Vulnerabilities/711055/) (search, files) syncthing: two vulnerabilities#710898
](https://lwn.net/Vulnerabilities/710898/) (search, files) tinymce: cross-site scripting#711048
](https://lwn.net/Vulnerabilities/711048/) (search, files) tomcat: information disclosure#710899
](https://lwn.net/Vulnerabilities/710899/) (search, files) unrtf: code execution#710286
](https://lwn.net/Vulnerabilities/710286/) (search, files) openjpeg2: multiple vulnerabilitiesAlready fixed irssi in the last roundup. Borgbackup was also fixed a while ago. :smiley:
Additionally:
Those have already been backported to 16.09.
Wow, alright! Nice staying ahead of the game :D!
Also:
I've started a branch which fixes jasper
Nice work, @fpletz, you fixed the php7 issue a month ago :)
@ttuegel how can I find changelogs for something like Kopete?
When updating OTR GUI icon properly set OTR instance tag Without configured instance tag libotr library does not encrypt sent messages and moreover it even does not report any error that message was not encrypted.
This should fix a bug when OTR "encrypted" icon is shown in GUI and libotr itself does not want to encrypt messages. It happened when Kopete window with active OTR session was closed and after that again opened.
@7c6f434c can you check out libvncserver? I'm having issues with it building my update. Latest release from https://github.com/LibVNC/libvncserver/releases
backported flac from unstable to stable: https://github.com/NixOS/nixpkgs/commit/cd27f9d492a8551bd86bf461ee26394211dd35df
I will just make a regular upgrade on nixpkgs unstable for sway because there is no indication of a concrete security incidence.
Perfect, thank you! I have patches for the nvidia drivers, and I'll start working on openjpeg.
this openjpeg issue is 😬
CVEs to patch against:
@grahamc and for the maximum fun we have alleged patches submitted as a PR.
@grahamc I officially fail to understand what is the problem with 0.9.11
update of libvncserver
I was seeing syntax errors in the libvncserver's autoconf which seemed beyond my range of expertise.
Yeah. These PRs really are maximum fun ... it'd be a different story if they were merged PRs!
Obviously these were not real syntax error but undefined functions. Adding a pkgconfig
dependency fixed them nicely.
Good to know for next time, thank you :)
We're in good company with the openjpeg2 issues: https://security-tracker.debian.org/tracker/source-package/openjpeg2
libtiff
: we already have 4.0.7
icoutils
: bump done
Hot dog! Is this a record? Pretty well finished! I think we're not vulnerable to the Kopete thing, but would like ttuegel to chime in. Openjpeg2... well, I'm hoping Debian provides some patches soon or openjpeg2 decides to merge something. Great great work. I'll plan on closing it out and merging my branch this afternoon.
@grahamc I'm not the Kopete maintainer; I don't know anything about that. I do know that KDE 4 is unmaintained upstream for years, so I would guess we are almost certainly vulnerable.
There isn't a standard place to find KDE changelogs?
@grahamc our kopete is new enough: https://portal.cert.dfn.de/adv/DFN-CERT-2017-0026/
/participate
/participate
Interesting, that IRC-style and HTML-style interpretations of /participate
are both believable — and directly opposite. I know, I know IRC-style is the correct one.
I forgot to close it from last week! Thank you! :) New one: https://github.com/NixOS/nixpkgs/issues/21967
Most helpful comment
Interesting, that IRC-style and HTML-style interpretations of
/participate
are both believable — and directly opposite. I know, I know IRC-style is the correct one.