TADDM security improvement deployed started from TADDM 126.96.36.199 and in TADDM 7.2.2 that restrict access to TADDM files on UNIX-like servers.
Default TADDM file permission on UNIX-like servers, by default are 755 (rwx r-x r-x), that allow all machines users have access to TADDM configuration files and logs (that can contain sensitive information)
CVSS Base Score: 2.1
CVSS Temporal Score: https://exchange.xforce.ibmcloud.com/vulnerabilities/86176
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:L/AC:L/Au:N/C:P/I:N/A:N)
Affected Products and Versions
TADDM 7.1.2, and 188.8.131.52 through 184.108.40.206 (fix included in TADDM 220.127.116.11 and TADDM 18.104.22.168)
Upgrade to TADDM 22.214.171.124 or TADDM 126.96.36.199
If you are unable to upgrade apply workaround, or please contact IBM Support.
Workarounds and Mitigations
1. Stop TADDM
2. On TADDM server login to taddmuser (user defined during TADDM installation), and change recursively files/directories privileges:
# chmod -R o-rwx $COLLATION_HOME/..
3. Add to ~/.profile line: umask 027 , to ensure that log file create also will have the same privileges.
# cat ~/.profile
4. After relogin to taddmuser check if umask is changed to new value:
5. Restart TADDM
Get Notified about Future Security Bulletins
7 May 2014: Original Copy Published
*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.
According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES ""AS IS"" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.
17 June 2018