WebSphere MQ Namelist resources are not protected in accordance with security requirements.

Associated with: CCI-000213

SV-7549r2_rule WebSphere MQ Namelist resources are not protected in accordance with security requirements.

Vulnerability discussion

WebSphere MQ resources allow for the control of administrator functions, connections, commands, queues, processes, and namelists. Some resources provide the ability to disable or bypass security checking. Failure to properly protect WebSphere MQ resources may result in unauthorized access. This exposure could compromise the availability, integrity, and confidentiality of system services, applications, and customer data.

Check content

a) Refer to the following report produced by the TSS Data Collection: - SENSITVE.RPT(WHOHMNLI) b) For all namelist resources (i.e., ssid.namelist) defined to MQNLIST resource class, ensure access authorization restricts access to users requiring the ability to make namelist inquiries. This is difficult to determine. However, an item for concern may be a profile with * READ specified in the access list. NOTE: ssid is the queue manager name (a.k.a., subsystem identifier). c) If (b) is true, there is NO FINDING. d) If (b) is untrue, this is a FINDING.

Fix text

For all namelist resources (i.e., ssid.namelist) defined to MQNLIST resource class, ensure access authorization restricts access to users requiring the ability to make namelist inquiries. This is difficult to determine. However, an item for concern may be a profile with * READ specified in the access list. NOTE: ssid is the queue manager name (a.k.a., subsystem identifier). The following is a sample of the commands required to allow a user (USER1) to inquire on namelist TST1 on queue manager (QM1): TSS ADD(USER1) FAC(QM1MSTR) TSS PER(USER1) MQNLIST(QM1.TST1.) ACC(READ) ACTION(AUDIT)

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.