Re: [nv-l] 512 byte limit on trap variables

2004-08-05 09:34:36
Subject: Re: [nv-l] 512 byte limit on trap variables
From: James Shanks <jshanks AT us.ibm DOT com>
To: nv-l AT lists.us.ibm DOT com
Date: Thu, 5 Aug 2004 09:24:29 -0400

It's 512-bytes per varbind and it is enforced as a result of a CERT advisory which indicated that people might seek to gain control of your system by sending cunningly-designed traps which would allow them to crash the trap receiver (trapd) and take over your box with his (root) authority.

If you get a trap with a varbind which exceeds 512 bytes, you will see an invalid trap message in trapd.log instead of that trap, though a trapd.trace with hex dump should show the problem more clearly.

If you have such a problem, please call IBM Support so that someone may look at it.

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group

"Qureshi, Fawad" <Fawad.Qureshi AT ssa DOT gov>
Sent by: owner-nv-l AT lists.us.ibm DOT com

08/04/2004 04:10 PM
Please respond to

"'nv-l AT lists.us.ibm DOT com'" <nv-l AT lists.us.ibm DOT com>
[nv-l] 512 byte limit on trap variables

Is the 512 byte limit for trap variables still enforced? If yes, would this mean any individual varbind cannot be more then 512 bytes or the total of all varbinds can not be more then 512 bytes in length? Thanks.
Fawad Qureshi
<Prev in Thread] Current Thread [Next in Thread>