DoS-vulnerability in lighttpd

Bug #107628 reported by Fridtjof Busse
260
Affects Status Importance Assigned to Milestone
lighttpd (Ubuntu)
Fix Released
Medium
Unassigned
Dapper
Fix Released
Undecided
Kees Cook
Edgy
Fix Released
Undecided
Kees Cook
Feisty
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: lighttpd

I know it's universe, but it deserves to be fixed:
http://www.lighttpd.net/assets/2007/4/13/lighttpd_sa2007_01.txt
http://www.lighttpd.net/assets/2007/4/13/lighttpd_sa2007_02.txt
Both problems are fixed in 1.4.14, but since that version contains a regression, 1.4.15 is the best version to go with (or a backport).

Patches are here:
http://www.lighttpd.net/assets/2007/4/13/lighttpd-1.4.x_crlf_parsing_dos.patch
http://www.lighttpd.net/assets/2007/4/13/lighttpd-1.4.x_zero_mtime_crash.patch

Revision history for this message
Kees Cook (kees) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. If someone can prepare (and test) the fixes and attach debdiffs that follow the [https://wiki.ubuntu.com/SecurityUpdateProcedures], I'd be more than happy to get them uploaded.

Changed in lighttpd:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Scott Kitterman (kitterman) wrote :

I'll take a stab at it.

Changed in lighttpd:
assignee: nobody → kitterman
status: Confirmed → In Progress
Revision history for this message
Scott Kitterman (kitterman) wrote :

The relevant patches are already in the Feisty version, so no issue there.

Revision history for this message
Scott Kitterman (kitterman) wrote :

For the initial reporter, what version of Ubuntu are you running? I'll prepare a package for that one first so you can test it.

Revision history for this message
Fridtjof Busse (fbusse-deactivatedaccount-deactivatedaccount) wrote :

Running feisty as of couple of minutes ago. The changelog on packages.ubuntu.com was outdated, thus I missed the fixed package. But I can test on edgy/dapper nonetheless, I have plenty of virtual machines around.

Revision history for this message
Scott Kitterman (kitterman) wrote :

OK. I can make i386 binaries or give you a source patch.

Revision history for this message
Scott Kitterman (kitterman) wrote :

This is going to take a while because the Ubuntu repositories are totally hammered by the Feisty release.

Revision history for this message
Scott Kitterman (kitterman) wrote :

Debdiff for Edgy for testing.

Revision history for this message
Scott Kitterman (kitterman) wrote :

Dapper debdiff for testing. Note that only one of the two isses was relevant to this version.

Revision history for this message
Scott Kitterman (kitterman) wrote :

Dapper-proposed debdiff for testing. Note that only one of the two isses was relevant to this version.

Revision history for this message
Scott Kitterman (kitterman) wrote :

Here are the source changes for all the supported releases. If you need me to build binaries for you (I can do -i386), let me know. Otherwise, please test these and then let us know how it goes.

Changed in lighttpd:
assignee: kitterman → fbusse
Revision history for this message
Kees Cook (kees) wrote : Re: [Bug 107628] Re: DoS-vulnerability in lighttpd

On Thu, Apr 19, 2007 at 06:48:33PM -0000, Scott Kitterman wrote:
> Debdiff for Edgy for testing.

Hi Scott,

Thanks very much for getting the patches extracted. The lighttpd
package, however, uses the "dpatch" patch system. Instead of applying
the fixes inline, please use "dpatch-edit-patch". For more details on
patching packages with different patch mechanisms, see pitti's excellent
write up:
https://wiki.ubuntu.com/MOTU/School/PatchingSources

--
Kees Cook

Revision history for this message
Fridtjof Busse (fbusse-deactivatedaccount-deactivatedaccount) wrote :

Works and builds fine on dapper i386 (patch applied by hand).

Revision history for this message
Scott Kitterman (kitterman) wrote :

Updated patch for Edgy using the patch system. Pbuilt and verified in the pbuilder log that the patches were applied. I can probide i386 binaries for testing if requested.

Changed in lighttpd:
assignee: fbusse → kitterman
Revision history for this message
Scott Kitterman (kitterman) wrote :

Dapper fix with dpatch. Version number is due to the .1 already in dapper proposed.

Revision history for this message
Scott Kitterman (kitterman) wrote :

Dapper-proposed fix with dpatch attached.

Revision history for this message
Scott Kitterman (kitterman) wrote :

Also subscribing MOTU SRU because the fix impacts dapper-proposed.

Changed in lighttpd:
assignee: kitterman → nobody
status: In Progress → Confirmed
Revision history for this message
Kees Cook (kees) wrote :

Show state in Feisty (fixed already), Edgy, and Dapper. Also linking to CVE.

Changed in lighttpd:
status: Unconfirmed → Rejected
assignee: nobody → keescook
status: Unconfirmed → Fix Committed
assignee: nobody → keescook
status: Unconfirmed → Fix Committed
Revision history for this message
Daniel T Chen (crimsun) wrote :

+1 for new dapper-proposed.

Revision history for this message
William Grant (wgrant) wrote : Security fix uploaded to dapper-proposed

I've uploaded the security fix for 1.4.11-3ubuntu3.1 to dapper-proposed.

Revision history for this message
Martin Pitt (pitti) wrote :

Updated packages released to -security. Thank you!

Changed in lighttpd:
status: Fix Committed → Fix Released
Revision history for this message
Martin Pitt (pitti) wrote :

Package released to dapper-security. Thank you!

Changed in lighttpd:
status: Fix Committed → Fix Released
Revision history for this message
Martin Pitt (pitti) wrote :

Just for the record, I rejected the dapper-proposed upload because the fix is already in -security.

Revision history for this message
Scott Kitterman (kitterman) wrote : Re: [Bug 107628] Re: DoS-vulnerability in lighttpd

Then that leaves us with a higher version numbered package in
dapper-proposed that is unpatched. If that SRU ever gets released we'll
re-introduce the vulnerability.

Revision history for this message
Martin Pitt (pitti) wrote :

Scott, I don't understand -- If the -proposed package has the same vulnerability fix, then it doesn't matter. If it fixes something different, then it should not be treated in this bug report.

Revision history for this message
Daniel T Chen (crimsun) wrote :

Martin, Scott's debdiff for a new dapper-proposed source upload contains the fix in the dapper-security upload. The current dapper-proposed source does /not/ contain this fix.

Revision history for this message
Scott Kitterman (kitterman) wrote :

The problem is that when this was reported, there was an updated for Dapper sitting in dapper-proposed:

https://launchpad.net/ubuntu/dapper/+source/lighttpd

That update:

https://launchpad.net/ubuntu/dapper/+source/lighttpd/1.4.11-3ubuntu3.1

has been sitting in dapper-proposed since last November and lacks the fix for this issue. So the existing -proposed package has the vulnerability. The upload you rejected was meant to replace it by fixing the vulnerability.

As it stands right now, should 1.4.11-3ubuntu3.1 ever finish SRU testing and be released, it would re-introduce this vulnerability. The intent of the 1.4.11-3ubuntu3.2 upload was to ensure (in advance) that this would not happen.

Sorry I wasn't clear before (hope I am now).

Revision history for this message
Martin Pitt (pitti) wrote :

Hi Scott,

Scott Kitterman [2007-05-03 11:52 -0000]:
> That update:
>
> https://launchpad.net/ubuntu/dapper/+source/lighttpd/1.4.11-3ubuntu3.1
>
> has been sitting in dapper-proposed since last November and lacks the
> fix for this issue. So the existing -proposed package has the
> vulnerability. The upload you rejected was meant to replace it by
> fixing the vulnerability.

Ah, I'm terribly sorry. Can you please upload it again then?

Thanks,

Martin
--
Martin Pitt http://www.piware.de
Ubuntu Developer http://www.ubuntu.com
Debian Developer http://www.debian.org

Revision history for this message
Scott Kitterman (kitterman) wrote :

I've attached the dapper-proposed debdiff with the maintainer change removed to be uploaded again.

Changed in lighttpd:
status: Confirmed → Fix Released
Changed in lighttpd:
status: Fix Released → Confirmed
Revision history for this message
Scott Kitterman (kitterman) wrote :

This time with the mention of the maintainer change removed from the changelog....

Revision history for this message
Scott Kitterman (kitterman) wrote :

dapper-proposed update uploaded.

Changed in lighttpd:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.