IBM Support

IJ16954: THE REST API FOR 'USERS' INCORRECTLY CHECKS USER NAMES FOR VALIDATION WHEN UPDATING FIELDS

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

  • It has been identified that the REST API for 'users' in QRadar
    incorrectly checks user names for validation when updating
    fields.
    API response messages similar to the following can be observed
    when usernames with invalid characters (created using LDAP)
    exist:
    {"http_response":{"code":500,"message":"Unexpected internal
    server
    error"},"code":12,"description":"","details":{},"message" :
    "Endpoint invocation returned an unexpected error"}
    Messages similar to the following might be visible in
    /var/log/qradar.log when this issue is occurring also:
    [tomcat.tomcat] [admin@127.0.0.1 (942)
    /console/restapi/api/staged_config/access/users/3]
    com.q1labs.restapi.servlet.apidelegate.APIDelegate: [ERROR]
    [NOT:0000003000][127.0.0.1/- -] [-/- -]Request Exception
    [tomcat.tomcat] [admin@127.0.0.1 (942)
    /console/restapi/api/staged_config/access/users/3]
    com.q1labs.restapi_annotations.content.exceptions.APIMappedExcep
    tion: Endpoint invocation returned an unexpected error
    [tomcat.tomcat] [admin@127.0.0.1 (942)
    /console/restapi/api/staged_config/access/users/3]    at
    com.q1labs.restapi.exceptionmapper.ExceptionMapper.mapException(
    ExceptionMapper.java:154)
    [tomcat.tomcat] [admin@127.0.0.1 (942)
    /console/restapi/api/staged_config/access/users/3]    at
    com.q1labs.restapi.servlet.utilities.APIRequestHandler.processEn
    dpointException(APIRequestHandler.java:1410)
    [tomcat.tomcat] [admin@127.0.0.1 (942)
    /console/restapi/api/staged_config/access/users/3]    at
    com.q1labs.restapi.servlet.utilities.APIRequestHandler.redirectR
    equest(APIRequestHandler.java:408)
    [tomcat.tomcat] [admin@127.0.0.1 (942)
    /console/restapi/api/staged_config/access/users/3]    at
    com.q1labs.restapi.servlet.utilities.APIRequestHandler.handleReq
    uest(APIRequestHandler.java:239)
    .....
    [tomcat.tomcat] [admin@127.0.0.1 (942)
    /console/restapi/api/staged_config/access/users/3] Caused by:
    [tomcat.tomcat] [admin@127.0.0.1 (942)
    /console/restapi/api/staged_config/access/users/3]
    com.q1labs.core.dao.permissions.light.validator.exception.users.
    UserNameInvalidCharactersValidationException: Usernames must
    not contain slashes or quotes.
    [tomcat.tomcat] [admin@127.0.0.1 (942)
    /console/restapi/api/staged_config/access/users/3]    at
    com.q1labs.core.dao.permissions.light.validator.UserValidator.va
    lidateUsernameCharacters(UserValidator.java:384)
    [tomcat.tomcat] [admin@127.0.0.1 (942)
    /console/restapi/api/staged_config/access/users/3]    at
    com.q1labs.core.dao.permissions.light.validator.UserValidator.va
    lidateUsername(UserValidator.java:336)
    [tomcat.tomcat] [admin@127.0.0.1 (942)
    /console/restapi/api/staged_config/access/users/3]    at
    com.q1labs.core.dao.permissions.light.validator.UserValidator.va
    lidate(UserValidator.java:311)
    [tomcat.tomcat] [admin@127.0.0.1 (942)
    /console/restapi/api/staged_config/access/users/3]    at
    com.q1labs.core.api.v11_0.user.UserAPI.updateStagedUser(UserAPI.
    java:893)
    [tomcat.tomcat] [admin@127.0.0.1 (942)
    /console/restapi/api/staged_config/access/users/3]    at
    sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [tomcat.tomcat] [admin@127.0.0.1 (942)
    /console/restapi/api/staged_config/access/users/3]    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
    Impl.java:90)
    [tomcat.tomcat] [admin@127.0.0.1 (942)
    /console/restapi/api/staged_config/access/users/3]    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
    AccessorImpl.java:55)
    [tomcat.tomcat] [admin@127.0.0.1 (942)
    /console/restapi/api/staged_config/access/users/3]    at
    java.lang.reflect.Method.invoke(Method.java:508)
    [tomcat.tomcat] [admin@127.0.0.1 (942)
    /console/restapi/api/staged_config/access/users/3]    at
    com.q1labs.restapi.servlet.utilities.APIRequestHandler.invokeMet
    hod(APIRequestHandler.java:1031)
    [tomcat.tomcat] [admin@127.0.0.1 (942)
    /console/restapi/api/staged_config/access/users/3]    at
    com.q1labs.restapi.servlet.utilities.APIRequestHandler.redirectR
    equest(APIRequestHandler.java:399)
    

Local fix

  • No workaround available.
    

Problem summary

  • This issue was fixed in QRadar QRM QVM release of 7.3.3 GA.
    

Problem conclusion

  • This issue was fixed in QRadar QRM QVM release of 7.3.3 GA.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ16954

  • Reported component name

    QRADAR SOFTWARE

  • Reported component ID

    5725QRDSW

  • Reported release

    732

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-06-17

  • Closed date

    2019-12-06

  • Last modified date

    2019-12-06

  • 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

    QRADAR SOFTWARE

  • Fixed component ID

    5725QRDSW

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"}, "Product":{"code":"SSBQAC","label":"IBM Security QRadar SIEM"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"732","Edition":""}]

Document Information

Modified date:
06 December 2019