On Wed, 3 Jul 2002, David Hedley wrote:
>
>
> I have been extensively testing the Speedtouch USB modem under
> FreeBSD (currently 4.4, will be testing 4.6 soon) with the latest
> (161.5R) alcaudsl.sys from Alcatel and the 1.1 drivers from this
> site.
>
> I have noticed the following problems:
>
<snip>
>
> 2) pppoa2 freezes under heavy load.
>
> I use the excellent userland ppp which uses pppoa2. Under heavy load,
> the pppoa2 process which reads from the USB hangs in
> pusb_endpoint_read in pusb-bsd.c. This will normally be observed as
> an LQR timeout in the upper PPP layer (assuming you enable LQR). I'm
> not sure why this is happening. The only way I've found to unwedge it
> is to send the pppoa2 process a signal. To this end, the following
> patch uses a watchdog timer to ensure the process doesn't get wedged:
>
I get this with pppoa3 on linux.
Same place in the code. I will try your fix.
(The thing that trips it reliably for me is downloading a 64K or so file
consisting entirely of 0xFF via FTP.)
> (You can ignore the first part to this patch - I just don't like rude
> words being written to the logs!)
>
> 3) Heavy usages causes large amounts of bad data to be read from the
> USB. In the logs this looks like:
>
> Jul 3 13:58:35 exoserver pppoa2[6631]: Cell had wrong VPI(4068)/VCI(31234) (OAM?)
>PTI=0x06
> Jul 3 13:58:41 exoserver pppoa2[6631]: Cell had wrong VPI(3240)/VCI(48850) (OAM?)
>PTI=0x04
> Jul 3 13:58:48 exoserver pppoa2[6631]: Cell had wrong VPI(981)/VCI(44053) (OAM?)
>PTI=0x05
> Jul 3 13:58:49 exoserver pppoa2[6631]: Cell had wrong VPI(1447)/VCI(31788) (OAM?)
>PTI=0x00
> Jul 3 13:59:05 exoserver pppoa2[6631]: Cell had wrong VPI(2948)/VCI(3831) (OAM?)
>PTI=0x03
> Jul 3 13:59:05 exoserver pppoa2[6631]: CRC error in an AAL5 frame
> Jul 3 13:59:26 exoserver pppoa2[6631]: Cell had wrong VPI(1251)/VCI(55468) (OAM?)
>PTI=0x06
> Jul 3 13:59:31 exoserver pppoa2[6631]: Cell had wrong VPI(671)/VCI(4876) (OAM?)
>PTI=0x07
>
> Not sure why this is happening - it doesn't seem to affect throughput that much but
>is quite noisy. It seems to result from a read from pusb_endpoint_read which returns
>a non-integer number of ATM cells. This looks to me like a synchronisation/locking
>issue between the read syscall in pppoa2 and the USB subsystem.
>
There is definitely a bug in the bit of code that rebuilds the ppp
packet from the atm frame where it calculates the length.
in aal5_frame_dec if the CRC check passes we rely on the length being
correct in the packet. This _might_ be exploitable but won't be a
standard "stack smashing" attack if so. However, AFAICT, only someone
with the ability to craft corrupt ATM frames and get them delivered to
pppoa[23] could exploit it which I think limits it to people with
access to the ATM equipment at the exchange.
(I don't think it can be exploited to give remote access/run remote
commands but it could possibly be used to sniff network traffic
remotely by sending a corrupted echo_request packet which would then
reply with the data that was previously read from the frog. Of course,
if someone has access to the equipment at the exchange then this seems
like a somewhat tortuous route to sniff the traffic :-)
Regards,
Tim.
p.s. any chance you can configure your mail client to limit its lines
to circa 72 characters please.
--
God said, "div D = rho, div B = 0, curl E = - @B/@t, curl H = J + @D/@t,"
and there was light.
http://tjw.hn.org/ http://www.locofungus.btinternet.co.uk/
Liste de diffusion modem ALCATEL SpeedTouch USB
Pour se d�sinscrire : mailto:[EMAIL PROTECTED]?subject=unsubscribe