CVE-2009-4007 (DoS of OpenTTD < 0.7.5)

Bug #503725 reported by Remko Bijker
268
This bug affects 2 people
Affects Status Importance Assigned to Milestone
openttd (Ubuntu)
Fix Released
Low
Unassigned
Hardy
Won't Fix
Low
Unassigned
Jaunty
Won't Fix
Low
Unassigned
Karmic
Won't Fix
Low
Unassigned
Lucid
Fix Released
Low
Unassigned
Maverick
Fix Released
Low
Unassigned

Bug Description

Binary package hint: openttd

The OpenTTD versions distributed by Ubuntu are vulnerable to CVE-2009-4007.

There are two ways to fix this:
- update to 0.7.5 (or higher)
- apply the patch of 0.6.2-1+lenny1 (from Debian)

CVE References

Remko Bijker (rubidium)
visibility: private → public
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures

Changed in openttd (Ubuntu):
status: New → Confirmed
importance: Undecided → Low
Revision history for this message
Remko Bijker (rubidium) wrote :

Attached are the debdiffs for the 'stable' releases. For Lucid I recommend pulling 0.7.5 from Debian unstable/testing.

Revision history for this message
Remko Bijker (rubidium) wrote :
Revision history for this message
Remko Bijker (rubidium) wrote :
Revision history for this message
Remko Bijker (rubidium) wrote :
tags: added: patch-accepted-debian patch-accepted-upstream
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Subscribing ubuntu-security-sponsors per https://wiki.ubuntu.com/SecurityTeam/SponsorsQueue. Sorry for the delay, this got missed because it didn't follow the procedures in the aforementioned wiki page.

Changed in openttd (Ubuntu Maverick):
status: Confirmed → Fix Released
Changed in openttd (Ubuntu Lucid):
importance: Undecided → Low
Changed in openttd (Ubuntu Hardy):
importance: Undecided → Low
Changed in openttd (Ubuntu Jaunty):
importance: Undecided → Low
Changed in openttd (Ubuntu Karmic):
importance: Undecided → Low
Changed in openttd (Ubuntu Lucid):
status: New → Fix Released
Changed in openttd (Ubuntu Hardy):
status: New → Incomplete
assignee: nobody → Remko Bijker (rubidium)
Changed in openttd (Ubuntu Jaunty):
status: New → Incomplete
assignee: nobody → Remko Bijker (rubidium)
Changed in openttd (Ubuntu Karmic):
status: New → Incomplete
assignee: nobody → Remko Bijker (rubidium)
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Remko, thank you for your patches for openttd. Unfortunately I cannot process them because they do not follow the procedures detailed in https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Packaging. Specifically:

* the hardy patch uses 'dpatch' as the patch system, but your debdiff patches inline
* the distribution name is set to 'stable' for all debdiffs. This should be '<ubuntu release>-security' for each debdiff. Eg, for hardy, use 'hardy-security'
* the version is incorrect for each debdiff. Please see https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Packaging for details
* you used the Debian packager's name in the changelog. You should use your own since Matthijs Kooijman did not prepare these debdiffs, you did

As per https://wiki.ubuntu.com/SecurityTeam/SponsorsQueue I am unsubscribing ubuntu-security-sponsors, marking the bug Incomplete and assigning to you. Please resubscribe ubuntu-security-sponsors and set the status to 'NEW' when the changes are complete, and detail the testing performed.

Thanks again for your work on this!

Revision history for this message
Remko Bijker (rubidium) wrote :

I don't have an Ubuntu system so can't test it, as such I can't meet the requirements.

Changed in openttd (Ubuntu Karmic):
assignee: Remko Bijker (rubidium) → nobody
Changed in openttd (Ubuntu Jaunty):
assignee: Remko Bijker (rubidium) → nobody
Changed in openttd (Ubuntu Hardy):
assignee: Remko Bijker (rubidium) → nobody
Revision history for this message
Alex Valavanis (valavanisalex) wrote :

Jaunty reached end-of-life on 23 October 2010. The bug is marked as fixed in later versions of Ubuntu

Changed in openttd (Ubuntu Jaunty):
status: Incomplete → Won't Fix
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Thank you for reporting this bug and helping to make Ubuntu better. The package referred to in this bug is in universe or multiverse and reported against a release of Ubuntu (karmic) which no longer receives updates outside of the explicitly supported LTS packages. While the bug against karmic is being marked "Won't Fix" for now, if you are interested feel free to post a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures'

Please feel free to report any other bugs you may find.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Thank you for reporting this bug and helping to make Ubuntu better. The package referred to in this bug is in universe or multiverse and reported against a release of Ubuntu (hardy) which no longer receives updates outside of the explicitly supported LTS packages. While the bug against hardy is being marked "Won't Fix" for now, if you are interested feel free to post a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures'

Please feel free to report any other bugs you may find.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Whoops, karmic is EOL and we won't be prcessing any debdiffs for it.

Changed in openttd (Ubuntu Hardy):
status: Incomplete → Won't Fix
Changed in openttd (Ubuntu Karmic):
status: Incomplete → Won't Fix
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.