Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 521257 - (CVE-2008-7159) CVE-2008-7159 libsilc: stack corruption during ASN1 encoding of OID
CVE-2008-7159 libsilc: stack corruption during ASN1 encoding of OID
Status: CLOSED CURRENTRELEASE
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
source=osssecurity,reported=20090831,...
: Security
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-09-04 10:53 EDT by Tomas Hoger
Modified: 2010-08-18 05:35 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-09-04 10:54:11 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Tomas Hoger 2009-09-04 10:53:04 EDT
SILC Toolkit 1.1.8 fixed following issue:

  http://silcnet.org/docs/changelog/SILC%20Toolkit%201.1.8

    ASN1: Fix stack variable overwrite when encoding OID.
    
    The call to sscanf specifies a format string of "%lu", a long unsigned
    int.  The pointer argument was cast to unsigned long *, but this is
    wrong for 64 bit systems.  On 64 bit systems, unsigned long is 64 bits,
    but the oid value is a SilcUInt32 on all systems.  As a result, sscanf
    will overwrite a neighboring variable on the stack.  Fix this by
    changing the format string to "%u" and removing the cast.

Upstream fix:
http://git.silcnet.org/gitweb/?p=silc.git;a=commitdiff;h=ebfe5dc8641467efea3506a4797a2b1260b2da55

This problem is already fixed in Fedora libsilc packages, which are based on fixed 1.1.8 version.

Version of libsilc shipped in Red Hat Enterprise Linux 4 and 5 do not contain affected code and hence are not affected by this problem.

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