Re: [leafnode-list] Leafnode 2.0b8: XPAT causes segfault

[Stefan Wiens <s.wi@xxxxxxx>]

Joerg Dietrich <joerg@xxxxxxxxxxxx> writes:

>> Message-ID: <9rfqg9.bkr.ln@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
> Exactly.
>> Looks like a buffer overflow or something. 
>
> I currently blame the hundreds of strchr() in doxover that never
> check for a NULL argument.

That's probably the same bug as reported in:

From: Raymond Scholz <rscholz@xxxxxx>
To: leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Message-ID: <3A72CC9A.BeroList-2.5.9@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Date: 27 Jan 2001 14:04:56 +0100
Subject: [leafnode-list] fetchnews segfaults



The segfault occurs if the upstream server sends a truncated line
(containing too few '\t' characters) in its XOVER response.

IIRC I've sent Cornelius my patches which do also close various memory
leaks, so I hope this will be fixed soon.

Stefan


-- 
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list