Security Team Weekly Summary: December 21, 2017
Canonical
on 21 December 2017

The Security Team weekly reports are intended to be very short summaries of the Security Team’s weekly activities.
If you would like to reach the Security Team, you can find us at the #ubuntu-hardened channel on FreeNode. Alternatively, you can mail the Ubuntu Hardened mailing list at: ubuntu-hardened@lists.ubuntu.com
During the last week, the Ubuntu Security team:
- Triaged 301 public security vulnerability reports, retaining the 47 that applied to Ubuntu.
- Published 5 Ubuntu Security Notices which fixed 3 security issues (CVEs) across 7 supported packages.
Ubuntu Security Notices
Bug Triage
Mainline Inclusion Requests
-
libteam underway (LP: #1392012)
-
MIR backlog: https://bugs.launchpad.net/~ubuntu-security/+assignedbugs?field.searchtext=%5BMIR%5D
Development
- Disable squashfs fragments in snap
- prepared/tested/uploaded squashfs-tools fixes for 1555305 in bionic through trusty and did SRU paperwork
- PR 4387 – explicitly deny ~/.gnupg/random_seed in gpg-keys interface
- Submitted PR 4399 for rewrite snappy-app-dev in Go
- Created PR 4406 – interfaces/dbus: adjust slot policy for listen, accept and accept4 syscalls
- Reviews
- PR 4365 – wayland slot implementation
What the Security Team is Reading This Week
Weekly Meeting
More Info
Talk to us today
Interested in running Ubuntu in your organisation?
Newsletter signup
Related posts
Building an open source chain of trust: new research uncovers key blockers and ways forward
Canonical is pleased to share its latest research report, “The open source chain of trust.” Based on a survey of 500 DevOps professionals, the report...
Beyond safety and security: Why automotive open source demands dependability
In the traditional automotive world, teams often work in silos: the cybersecurity experts lock down the ports, the quality assurance teams hunt for bugs, and...
DirtyClone Linux kernel local privilege escalation vulnerability fixes available
On June 25, 2026, JFrog published their research into CVE-2026-43503, referring to the vulnerability as DirtyClone. The vulnerability had previously been...