CVE-2008-3547: Network exploitable buffer overrun in openttd < 0.6.2

Bug #261373 reported by Chris Halse Rogers
2
Affects Status Importance Assigned to Milestone
openttd (Debian)
Fix Released
Unknown
openttd (Ubuntu)
Fix Released
Undecided
Unassigned
Hardy
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: openttd

From the Debian bug:

OpenTTD servers of version 0.6.1 and below are susceptible to a remotely
exploitable buffer overflow when the server is filled with companies and
clients with names that are (near) the maximum allowed length for names.
In the worst case OpenTTD will write the following (mostly remotely
changable bytes) into 1460 bytes of malloc-ed memory:
up to 11 times (amount of players) 118 bytes
up to 8 times (amount of companies) 124 bytes
and 7 "header" bytes
Resulting in up to 2297 bytes being written in 1460 bytes of malloc-ed
memory. This makes it possible to remotely crash the game or change the
gamestate into an unrecoverable state.

There are three ways of fixing this:
- upgrading to 0.6.2.
- backporting the bugfixes to 0.6.1 and make a network-incompatible version
 of OpenTTD which makes it impossible to participate in multiplayer games
 with both Debian and non-Debian users.
- increase the allocation size, which will make it even network incompatible
 with itself.

I'm not sure what, if anything, we want to do about this.

Revision history for this message
Chris Halse Rogers (raof) wrote :

Intrepid has 0.6.2

Changed in openttd:
status: New → Fix Released
Changed in openttd:
status: Unknown → Fix Released
Revision history for this message
Daniel T Chen (crimsun) wrote :

Really, the only sane method here is to place 0.6.2 in hardy-security. Backporting the fixes introduces a fairly major regression, and anything other than an upstream-vetted change to allocation is begging for disaster.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as "Won't Fix".

Changed in openttd (Ubuntu Hardy):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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