IBM Support

IT26689: Channel process ends with SIGSEGV if security exit returns null MQCSP structure

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Channel process ends with SIGSEGV if security exit returns null
    MQCSP structure
    
    The function stack in the associated failure data capture (FDC)
    record indicates a failure in rriAdoptMapCallScyExit.
    

Local fix

  • Do not set the MQCSP pointer (pChannelExitParms->SecurityParms)
    to a null pointer within the security exit. Valid alternate
    approaches include:
    
    - Blank the values of the supplied MQCSP
    - Return the supplied MQCSP unchanged
    - Allocate a new MQCSP with desired values and reference its
    address from pChannelExitParms->SecurityParms
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of MQ 9.0.0.5 on all platforms who use
    a channel security exit to set the SecurityParms pointer in the
    MQCXP structure to null.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    Changes added under APAR IT25839 did not correctly handle the
    case where the security exit set the MQCSP pointer
    (pChannelExitParms->SecurityParms) to a null pointer. When a
    client application connected to a channel using the exit then
    the channel failed with a SIGSEGV error and an FFST was written.
     The connection failed with error 2538.
    

Problem conclusion

  • The MQ queue manager logic has been update to tolerate a null
    MQCSP pointer being returned by a security exit.
    
    When a client application connects to a channel using such an
    exit, the connection attempt will proceed as if no MQCSP
    structure was been supplied by the client.  The connection may
    still fail (for example because the connecting user cannot be
    authenticated) based on the defined CONNAUTH and CHLAUTH rules.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0 LTS   9.0.0.6
    v9.1 CD    9.1.2
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT26689

  • Reported component name

    IBM MQ BASE M/P

  • Reported component ID

    5724H7261

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-10-22

  • Closed date

    2018-11-26

  • Last modified date

    2018-11-26

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

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

Fix information

  • Fixed component name

    IBM MQ BASE M/P

  • Fixed component ID

    5724H7261

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
26 November 2018