Ubuntu Wiki

Security updates

Announcements

• Official Ubuntu Security Notices (USNs)

• Ubuntu security update notifications additional information

Media coverage

In order to stay secure, Ubuntu users should simply apply all Ubuntu security updates to their systems when they become available.

For some vulnerabilities that are highlighted by the media, we've provided additional information as part of our KnowledgeBase:

• GHOST (CVE-2015-0235)

• VENOM (CVE-2015-3456)

• LogJam (CVE-2015-4000)

• Stagefright (CVE-2015-1538, CVE-2015-1539, CVE-2015-3824, CVE-2015-3826, CVE-2015-3827, CVE-2015-3828, CVE-2015-3829)

• OpenSSH Client Roaming (CVE-2016-0777, CVE-2016-0778)

• httpoxy CGI application vulnerability

• BlueBorne bluetooth vulnerabilities (CVE-2017-1000250, CVE-2017-1000251)

Vulnerability Resources

• Ubuntu CVE tracker

• Ubuntu CVE Tracker (web view)

• Common Vulnerabilities and Exposures (CVEs)

• National Vulnerabilities Database

• Open Source Software Security

Update processes

• Security update procedures

• StableReleaseUpdates/MicroReleaseExceptions

• StableReleaseUpdates (SRU)

• Backport Requests

Update techniques

• How to prepare an updated package

• How to handle backporting security updates

  • schroot/sbuild setup

  • virtual machine setup

• How to test the update

  • QA Regression Testing

  • Proof of Concept (PoC)
  • Build test suites (eg, 'make check')
• ABI compatibility (eg, check-symbols, nm)
• Checklists

• Media coverage

Policies

• Ubuntu Security Policies

• Creating enforcing AppArmor profiles policy

Features

• Feature Matrix (for all releases since Dapper, see the Historical Feature Matrix.)

• Security Hardening Compiler Flags

• AppArmor Profiles

• Applications Built with PIE

• AppArmor docs

• SELinux docs

Process

• Bug Triage

• Release Cycle Actions

Problems

• DebuggingSecurity for bug reports

• DebuggingApparmor for bug reports dealing with AppArmor profiles

CategorySecurityTeam