PM08892: SIP logging does not support hiding specific header fields

Fixes are available

7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
6.1.0.33: WebSphere Application Server V6.1 Fix Pack 33 for AIX
6.1.0.33: WebSphere Application Server V6.1 Fix Pack 33 for HP-UX
6.1.0.31: WebSphere Application Server V6.1 Fix Pack 31 for AIX
6.1.0.31: WebSphere Application Server V6.1 Fix Pack 31 for HP-UX
6.1.0.31: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
6.1.0.35: WebSphere Application Server V6.1 Fix Pack 35 for AIX
6.1.0.35: WebSphere Application Server V6.1 Fix Pack 35 for HP-UX
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
6.1.0.37: WebSphere Application Server V6.1 Fix Pack 37
6.1.0.39: WebSphere Application Server V6.1 Fix Pack 39
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: WebSphere Application Server V6.1 Fix Pack 41
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: WebSphere Application Server V6.1 Fix Pack 43
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: WebSphere Application Server V6.1 Fix Pack 45
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When enabling SIP trace; sensitive information may be printed
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  SIP (Session Initiation Protocol) users of  *
    *                  IBM WebSphere Application Server using      *
    *                  Basic authentication                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: The server writes all fields of a SIP   *
    *                      message to the log when SIP tracing     *
    *                      is enabled using Basic authentication   *
    *                      (not digest)                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The problem occurs when the server receives a SIP message from
    the network, or sends a SIP message out to the network, and
    full SIP trace logging is enabled. The entire SIP message is
    written in the trace file, along with all header fields and
    the message body, including information that may be
    considered sensitive.
    
    For example, if you set the trace level in the application
    server to com.ibm.ws.sip.*=all, and the server receives a SIP
    "instant message", the message body is written to the trace
    log file:
    
    MESSAGE sips:user2@domain.com SIP/2.0
    Via: SIP/2.0/TLS user1pc.domain.com;branch=z9hG4bK776sgdkse
    Max-Forwards: 70
    From: sips:user1@domain.com;tag=49583
    To: sips:user2@domain.com
    Call-ID: asd88asd77a@1.2.3.4
    CSeq: 1 MESSAGE
    Content-Type: text/plain
    Content-Length: 33
    
    Hey buddy, can you keep a secret?
    
    
    This SIP message was sent securely over the network to the
    server, but having full SIP tracing enabled, it is written in
    cleartext form to the server's trace log.
    

Problem conclusion

  • The problem is fixed by introducing 3 new custom properties in
    the SIP container that control the message fields that are
    hidden in the trace log:
    
    o javax.sip.hide.message.body - A flag (true/false)
    specifying whether or not to hide the SIP message content.
    o javax.sip.hide.message.headers - A comma-separated list of
    header field names that will be hidden.
    o javax.sip.hide.request.uri - A flag specifying whether or
    not to hide the request URI.
    
    For example, consider these settings:
    javax.sip.hide.message.body=true
    javax.sip.hide.message.headers=From,To
    javax.sip.hide.request.uri=true
    
    With this configuration, the same message from the example above
    would be printed to the trace log exactly like this:
    
    MESSAGE <hidden request URI> SIP/2.0
    Via: SIP/2.0/TLS user1pc.domain.com;branch=z9hG4bK776sgdkse
    Max-Forwards: 70
    From: <hidden value>
    To: <hidden value>
    Call-ID: asd88asd77a@1.2.3.4
    CSeq: 1 MESSAGE
    Content-Type: text/plain
    Content-Length: 33
    
    <hidden body>
    
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.11.  Please refer to the Recommended Updates
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM08892

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    61I

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-03-02

  • Closed date

    2010-03-23

  • Last modified date

    2010-06-03

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

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

    PM10744 PM15862

Fix information

  • Fixed component name

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R700 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Application Server
General

Software version:

6.1

Reference #:

PM08892

Modified date:

2010-06-03

Translate my page

Machine Translation

Content navigation