Your message dated Sun, 1 Jan 2012 17:37:10 -0500
with message-id 
<CANTw=mn6jpq19tcrymc7tdbevvs6vnc4wproabfttkrxrqq...@mail.gmail.com>
and subject line re: CVE-2011-3152/CVE-2011-3154
has caused the Debian Bug report #650307,
regarding CVE-2011-3152/CVE-2011-3154
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
650307: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: update-manager
Severity: grave
Tags: security

Ubuntu released the following security update for update-manager:
http://www.ubuntu.com/usn/usn-1284-1/

Details and patches:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/881548

Cheers,
        Moritz



--- End Message ---
--- Begin Message ---
Moritz Muehlenhoff wrote:
> Ubuntu released the following security update for update-manager:
> http://www.ubuntu.com/usn/usn-1284-1/
>
> Details and patches:
> https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/881548

The debian and ubuntu update-manager packages are on quite different
paths.  Although they have the same origin, they've rather diverged by
now.  It turns out that neither of these issues affect the debian
package.

For CVE-2011-3152, the debian package does not have any code that
makes use of gpgauthenticate, so it isn't affected by that race
condition.  I haven't looked into the code in detail, but I'm going to
assume that this package is using apt itself for authentication.  If
it isn't doing any authentication at all, then that's a separate
significant issue, and a new bug filed.

For CVE-2011-3154, the debian package does not use "mktemp" anywhere,
so that leak doesn't exist.

Best wishes,
Mike


--- End Message ---

Reply via email to