Bug 200545 - (CVE-2006-3913) CVE-2006-3913, freeciv: server buffer overflow issues
CVE-2006-3913, freeciv: server buffer overflow issues
Product: Fedora
Classification: Fedora
Component: freeciv (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Brian Pepple
Fedora Extras Quality Assurance
: Reopened, Security
Depends On:
  Show dependency treegraph
Reported: 2006-07-28 11:42 EDT by Ville Skyttä
Modified: 2007-11-30 17:11 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-08-07 15:13:24 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ville Skyttä 2006-07-28 11:42:00 EDT
CVE-2006-3913, http://nvd.nist.gov/nvd.cfm?cvename=CVE-2006-3913 :

Buffer overflow in Freeciv 2.1.0-beta1 and earlier, and SVN 15 Jul 2006 and
earlier, allows remote attackers to cause a denial of service (crash) and
possibly execute arbitrary code via a (1) negative chunk_length or a (2) large
chunk->offset value in a PACKET_PLAYER_ATTRIBUTE_CHUNK packet in the
generic_handle_player_attribute_chunk function in common/packets.c, and (3) a
large packet->length value in the handle_unit_orders function in server/unithand.c.

All FE-[345] and devel are probably affected.
Comment 1 Brian Pepple 2006-08-01 12:58:06 EDT
Thanks for the bug report.  Packages should be available after the next
Comment 2 Ville Skyttä 2006-08-02 13:56:29 EDT
The CVE description of the vulnerability mentions three bugs, but the patch
applied in latest freeciv package revisions appears to address only two of them.

Maybe this is the missing piece?
Comment 3 Brian Pepple 2006-08-02 18:36:46 EDT
Yeah, that should be added to my patch.  The report stated this was corrected on
July 16th, but the changes you referenced weren't applied to svn until July 24th.
Comment 4 Ville Skyttä 2006-08-07 15:13:24 EDT
Seems to be fixed now, thanks.

Note You need to log in before you can comment on or make changes to this bug.