Security Information

Debian takes security very seriously. We handle all security problems brought to our attention and ensure that they are corrected within a reasonable timeframe. Many advisories are coordinated with other free software vendors and are published the same day a vulnerability is made public and we also have a Security Audit team that reviews the archive looking for new or unfixed security bugs.

Experience has shown that security through obscurity does not work. Public disclosure allows for more rapid and better solutions to security problems. In that vein, this page addresses Debian's status with respect to various known security holes, which could potentially affect Debian.

Debian also participates in security standardization efforts: the Debian Security Advisories are CVE-Compatible (review the cross references) and Debian is represented in the Board of the Open Vulnerability Assessment Language project.

Keeping your Debian system secure

In order to receive the latest Debian security advisories, subscribe to the debian-security-announce mailing list.

You can use apt to easily get the latest security updates. This requires a line such as

deb http://security.debian.org/ wheezy/updates main contrib non-free

in your /etc/apt/sources.list file. Then execute apt-get update && apt-get upgrade to download and apply the pending updates. The security archive is signed with the normal Debian archive signing keys.

For more information about security issues in Debian, please refer to the Security Team FAQ and a manual called Securing Debian.

Recent Advisories

These web pages include a condensed archive of security advisories posted to the debian-security-announce list.

[26 Feb 2015] DSA-3176 request-tracker4 - security update
[25 Feb 2015] DSA-3175 kfreebsd-9 - security update
[25 Feb 2015] DSA-3174 iceweasel - security update
[25 Feb 2015] DSA-3173 libgtk2-perl - security update
[25 Feb 2015] DSA-3172 cups - security update
[23 Feb 2015] DSA-3171 samba - security update
[23 Feb 2015] DSA-3170 linux - security update
[23 Feb 2015] DSA-3169 eglibc - security update
[22 Feb 2015] DSA-3168 ruby-redcloth - security update
[22 Feb 2015] DSA-3167 sudo - security update
[22 Feb 2015] DSA-3166 e2fsprogs - security update
[21 Feb 2015] DSA-3165 xdg-utils - security update
[21 Feb 2015] DSA-3164 typo3-src - security update
[19 Feb 2015] DSA-3163 libreoffice - security update
[18 Feb 2015] DSA-3162 bind9 - security update
[11 Feb 2015] DSA-3161 dbus - security update
[11 Feb 2015] DSA-3160 xorg-server - security update
[10 Feb 2015] DSA-3159 ruby1.8 - security update
[09 Feb 2015] DSA-3158 unrtf - security update
[09 Feb 2015] DSA-3157 ruby1.9.1 - security update
[06 Feb 2015] DSA-3155 postgresql-9.1 - security update
[05 Feb 2015] DSA-3154 ntp - security update
[03 Feb 2015] DSA-3153 krb5 - security update
[03 Feb 2015] DSA-3152 unzip - security update
[03 Feb 2015] DSA-3151 python-django - security update
[02 Feb 2015] DSA-3150 vlc - security update
[02 Feb 2015] DSA-3149 condor - security update
[31 Jan 2015] DSA-3148 chromium-browser - end of life
[30 Jan 2015] DSA-3147 openjdk-6 - security update
[30 Jan 2015] DSA-3146 requests - security update
[30 Jan 2015] DSA-3145 privoxy - security update
[29 Jan 2015] DSA-3144 openjdk-7 - security update

The latest Debian security advisories are also available in RDF format. We also offer a second file that includes the first paragraph of the corresponding advisory so you can see in it what the advisory is about.

The older security advisories are also available: 2015, 2014, 2013, 2012, 2011, 2010, 2009, 2008, 2007, 2006, 2005, 2004, 2003, 2002, 2001, 2000, 1999, 1998, 1997 and undated security advisories, included for posterity.

Debian distributions are not vulnerable to all security problems. The Debian Security Tracker collects all information about the vulnerability status of Debian packages, and can be searched by CVE name or by package.

Contact Information

Please read the Security Team FAQ before contacting us, your question may well be answered there already!

The contact information is in the FAQ as well.