IV34106: STACK CORRUPTION RESULTS IN SEGMENTATION FAULT

IBM Tivoli Monitoring 6.2.3 Fix Pack 5 (6.2.3-TIV-ITM-FP0005)
IBM Tivoli Monitoring 6.2.3 Fix Pack 4 (6.2.3-TIV-ITM-FP0004)

APAR status

• Closed as program error.

Error description

• APAR Type:         Field
  Approver Initials: HT
  Severity:          2
  Reported Release:  623
  Compid:            5724C04MS Tivoli Enterprise Management Server
  ABSTRACT:          Stack corruption results in segmentation
  fault.
  
  PROBLEM DESCRIPTION:
  Local automation operations message KFAST003 can cause stack
  corruption by kglmsww.c's SendUniversalMessage() function.  Two
  local character arrays in this function, univMsg[] and tmpMsg[]
  can be overrun causing stack corruption, leading to a
  segmentation fault.
  
  RECREATE INSTRUCTIONS:
  The following were the steps performed when level 2 reproduced
  the failure reported here:
  
  Setup LogFile Agent with LFA_Oracle.fmt and LFA_Oracle_HPDB.conf
  and imported a situation HP_LOG_Oracle_C.xml. I made LFA to read
  alert_oracle.log, then kdsmain will crash.
  
  The following is the xml for the HP_LOG_Oracle_C mentioned
  above:
  
  <TABLE><ROW><SITNAME>HP_LOG_Oracle_C</SITNAME><FULLNAME></FULLNA
  ME><ADVISE>*NONE</ADVISE><AFFINITIES>%IBM.KLO0000000000#########
  </AFFINITIES><ALERTLIST/><AUTOSOPT>YNY</AUTOSOPT><AUTOSTART>*YES
  </AUTOSTART><CMD>set -f;/tmp/mail.sh HP_LOG_Oracle_C
  &{KLO_LOGFILEEVENTS.Node} "&{KLO_LOGFILEEVENTS.Logname}"
  "&{KLO_LOGFILEEVENTS.msg}"</CMD><DESTNODE/><HUB/><LOCFLAG/><LSTC
  CSID>ja_JP</LSTCCSID><LSTDATE>1121113090916000</LSTDATE><LSTRELE
  ASE>V100</LSTRELEASE><LSTUSRPRF>SYSADMIN</LSTUSRPRF><NOTIFYARGS/
  ><NOTIFYOPTS/><OBJECTLOCK/><PDT>*IF *VALUE
  KLO_LOGFILEEVENTS.Class *EQ '*' *UNTIL ( *TTL 1:00:00:00
  )</PDT><PRNAMES/><QIBSCOPE>E</QIBSCOPE><REEV_DAYS>0</REEV_DAYS><
  REEV_TIME>000000</REEV_TIME><REFLEXOK/><SENDMSGQ>*NONE</SENDMSGQ
  ><SITINFO>ATOM=KLOLOGEVTS.LOGNAME;TFWD=Y;TDST=0;~;</SITINFO><SOU
  RCE/><TEXT></TEXT><DISTRIBUTION>Oracle:TIVTEST:LO</DISTRIBUTION>
  </ROW></TABLE>
  

Local fix

• The segmentation fault reported here can be prevented by
  specifying the following environment variable:
  
    KGL_MSG2_UNIVERSAL=NO
  
  
  Note:
  Setting the above environment variable will disable
  operations/MSG2 messages from being written to the Universal
  Messge table.  Situations authored to query the universal
  message table will no longer function correctly.  Additionally,
  the TEP Universal Message Console interface will no longer
  display any data.
  

Problem summary

• Situations that define an Action to emit a message to the
  Universal Message Console may crash the monitoring server due to
  a memory overwrite condition. This occurs when a translated
  message is more than 254 bytes.
  

Problem conclusion

• Logic was corrected to guard against the memory overwrite, thus
  preventing a crash of the monitoring server.  This allows the
  truncated message with a trailing ellipsis to be sent to
  Universal Message Console.
  
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
    | fix pack | 6.2.3-TIV-ITM-FP0004
    | fix pack | 6.3.0-TIV-ITM-FP0002
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  IV47956 OA43271 OA43303

Fix information

• Fixed component name

  TEMS

• Fixed component ID

  5724C04MS

Applicable component levels

• R623 PSY

     UP