search

opensecure / jss7

Automatically exported from code.google.com/p/jss7
0 stars 0 forks source link

SCCP XUDT bad possible length calculation #278

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
In SCCP stack when encoding XUDT message there is a bug when calculating max 
possible length of data field when callingParty / calledParty addresses filelds 
have big length.
The result is XUDT message of some length is not segmented (as it is needed) 
and the message will be encoded in a wrong way and a peer can not decode this.
A solution is: adding an extra check: 
max possible message data length must be <= 254 - (3 + calling party field 
length  + called party field length)

Original issue reported on code.google.com by serg.vet...@gmail.com on 8 May 2013 at 1:17

GoogleCodeExporter commented 9 years ago 
Hello!

This is a fix for this bug:
https://code.google.com/p/jss7/source/detail?r=53e6084451ded99de1a878f6f900a0c24
f05b74f

Original comment by serg.vet...@gmail.com on 8 May 2013 at 4:01

GoogleCodeExporter commented 9 years ago

Original comment by serg.vet...@gmail.com on 5 Jun 2013 at 10:33