-----BEGIN PGP SIGNED MESSAGE-----
AUSCERT External Security Bulletin Redistribution
Security Bulletin: Tivoli Federated Identity Manager -
Passwords exposed in trace files (CVE-2012-3310)
9 January 2013
AusCERT Security Bulletin Summary
Product: IBM Tivoli Federated Identity Manager
Operating System: AIX
Impact/Access: Access Confidential Data -- Existing Account
CVE Names: CVE-2012-3310
- --------------------------BEGIN INCLUDED TEXT--------------------
Security Bulletin: Tivoli Federated Identity Manager - Passwords exposed in
trace files (CVE-2012-3310)
Tivoli Federated Identity Manager
6.1.1, 6.2, 6.2.1
AIX, HP-UX, Linux, Solaris, Windows, z/OS
It is possible to configure Tivoli Federated Identity Manager (TFIM) in such a
way that the logging of certain activities could result in the trace files
produced by TFIM containing passwords that are either in clear text or
obfuscated in a manner that the password can be derived.
CVE ID: CVE-2012-3310
The four logging configurations described below result in the TFIM trace files
containing passwords that are either in clear text or obfuscated in a manner
that the password can be derived. In all cases, accessing the configuration of
the system in order to enable the logging, as well as accessing the resulting
trace files, requires elevated privileges.
1) ALIAS SERVICE SETTINGS
Enabling the "all" TFIM log trace setting results in the Alias Service Settings
LDAP "Bind Password" to appear in clear text in the resulting log files upon
execution of SAML 2.0 Single Sign On flow.
2) VIEWING KEYSTORES
Enabling the "all" TFIM log trace setting results in obfuscated keystore
passwords being logged upon "View Keys" execution in TFIM configuration.
3) ARTIFACT FEDERATION SINGLE SIGN ON WITH BASIC AUTHENTICATION
Enabling the "all" TFIM log trace setting results in the client Basic
Authentication password being logged in clear text upon execution of SAML 2.0
Federation SSO flow using HTTP-Artifact.
4) STS MODULE USERNAMETOKEN
Enabling the "all" TFIM log trace setting results in the end-user supplied
password being logged in clear text when issuing the UsernameToken.
An attack does not require local network access, but it does it require
authentication and specialized knowledge and techniques. An exploit will not
impact accessibility of system resources or the integrity of information, but
the confidentiality of some of the data managed by TFIM could be compromised.
CVSS Base Score: 3.5
CVSS Vector: (AV:N/AC:M/Au:S/C:P/I:N/A:N)
All versions of TFIM before 6.2.2 are affected, including those no longer
TFIM versions 6.1.1, 6.2.0, 6.2.1
Vendor Fixes: Patches and installation instructions are provided at the URLs
Fix Build APAR Download URL
6.2.1-TIV-TFIM-FP0004 188.8.131.52 IV26822 http://www-01.ibm.com/support/docview.wss?uid=swg24032885
6.2.0-TIV-TFIM-IF0012 184.108.40.206 IV26823 http://www-01.ibm.com/support/docview.wss?uid=swg24033345
6.1.1-TIV-TFIM-IF0014 220.127.116.11 IV26824 http://www-01.ibm.com/support/docview.wss?uid=swg24033343
For versions of TFIM that are no longer supported, IBM recommends that
customers upgrade to a supported, fixed version of the product.
* Ensure that only qualified users have administrative rights to the TFIM
* Ensure that only qualified users can access the file system of the TFIM
* Complete CVSS Guide
* IBM Secure Engineering Web Portal
* IBM Product Security Incident Response Blog
*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 Flash.
Note: 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.
- --------------------------END INCLUDED TEXT--------------------
You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to firstname.lastname@example.org
and we will forward your request to the appropriate person.
NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members. As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.
NOTE: This is only the original release of the security bulletin. It may
not be updated when updates to the original are made. If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.
Contact information for the authors of the original document is included
in the Security Bulletin above. If you have any questions or need further
information, please contact them directly.
Previous advisories and external security bulletins can be retrieved from:
Australian Computer Emergency Response Team
The University of Queensland
Internet Email: email@example.com
Facsimile: (07) 3365 7031
Telephone: (07) 3365 4417 (International: +61 7 3365 4417)
AusCERT personnel answer during Queensland business hours
which are GMT+10:00 (AEST).
On call after hours for member emergencies only.
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----