Bug 23275 - libsoup new security issue CVE-2018-12910
Summary: libsoup new security issue CVE-2018-12910
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Security (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: QA Team
QA Contact: Sec team
URL:
Whiteboard: MGA6-64-OK
Keywords: advisory, has_procedure, validated_update
Depends on:
Blocks:
 
Reported: 2018-07-03 23:19 CEST by David Walser
Modified: 2018-08-10 16:39 CEST (History)
7 users (show)

See Also:
Source RPM: libsoup-2.63.2-1.mga7.src.rpm
CVE:
Status comment:


Attachments

Description David Walser 2018-07-03 23:19:36 CEST
Ubuntu has issued an advisory today (July 3):
https://usn.ubuntu.com/3701-1/

Mageia 5 and Mageia 6 are also affected.
Comment 1 David Walser 2018-07-03 23:22:29 CEST
Fedora has also issued an advisory for this today:
https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/thread/SBREWZ3EEDYWG6PCLWL2EJ24ME5ZFAX6/
David Walser 2018-07-03 23:22:55 CEST

Whiteboard: (none) => MGA6TOO

Comment 2 Marja Van Waes 2018-07-04 12:41:59 CEST
Assigning to all packagers collectively, since there is no registered maintainer for this package.

CC'ing ovitters, who pushed this package most often, and neoclust, who fixed CVE-2017-2885 in this package for Mga6

CC: (none) => mageia, marja11, olav
Assignee: bugsquad => pkg-bugs

Comment 3 Mike Rambo 2018-07-23 18:20:24 CEST
Patched packages uploaded for cauldron and Mageia 6.

Advisory:
========================

Updated libsoup package fixes security vulnerability:

It was discovered that libsoup versions 2.63.2 and prior incorrectly handled certain cookie requests. An attacker could possibly use this to cause a denial of service (CVE-2018-12910).

References:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12910
https://security-tracker.debian.org/tracker/CVE-2018-12910
https://usn.ubuntu.com/3701-1/
========================

Updated packages in core/updates_testing:
========================
libsoup-i18n-2.58.2-1.1.mga6.noarch.rpm
lib64soup2.4_1-2.58.2-1.1.mga6
lib64soup-devel-2.58.2-1.1.mga6
lib64soup-gir2.4-2.58.2-1.1.mga6

from libsoup-2.58.2-1.1.mga6.src.rpm


Test procedure: https://bugs.mageia.org/show_bug.cgi?id=21487#c10

Keywords: (none) => has_procedure
CC: (none) => mrambo
Version: Cauldron => 6
Whiteboard: MGA6TOO => (none)
Assignee: pkg-bugs => qa-bugs

Comment 4 Len Lawrence 2018-07-24 00:51:46 CEST
Mageia 6, x86_64

Referred to the tests on bug 21487.

Tried out banshee, darktable and shotwell successfully and confirmed that libsoup was involved in running shotwell.

$ strace shotwell 2> trace
$ grep soup trace
open("/lib64/libsoup-2.4.so.1", O_RDONLY|O_CLOEXEC) = 14
stat("/usr/lib64/gstreamer-1.0/libgstsouphttpsrc.so", {st_mode=S_IFREG|0755, st_size=71104, ...}) = 0
write(13, "soup\0", 5)                  = 5
write(13, "libsoup HTTP client src/sink\0", 29) = 29
write(13, "souphttpsrc\0", 12)          = 12
write(13, "souphttpclientsink\0", 19)   = 19

Updated the four packages and ran those applications again.
Imported local music tracks and played them in banshee.  Youtube music videos played fine also.  Used darktable in lighttable mode to select images and manipulated them in the darkroom section, rotations, changing contrast, brightness and colour ranges, changed shape of tone curve, field of view...
No obvious problems.  No regressions in shotwell.  pix worked fine as well - was able to add a comment to one image and see it displayed on refreshing the browser view.  Loaded midori and was able to browse the web and search.

This looks OK for 64-bits.

Whiteboard: (none) => MGA6-64-OK
CC: (none) => tarazed25

Len Lawrence 2018-08-09 21:42:16 CEST

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

Thomas Backlund 2018-08-10 15:17:27 CEST

Keywords: (none) => advisory
CC: (none) => tmb

Comment 5 Mageia Robot 2018-08-10 16:39:31 CEST
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGASA-2018-0328.html

Resolution: (none) => FIXED
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.