Stack-based buffer overflow in dsmtca in the client in IBM Tivoli Storage Manager (TSM) 5.4 through 5.4.3.6, 5.5 through 5.5.4.3, 6.1 through 6.1.5.6, 6.2 before 6.2.5.4, and 6.3 before 6.3.2.3 on UNIX, Linux, and OS X allows local users to gain privileges via unspecified vectors.
Credit: psirt@us.ibm.com
Affected Software
Affected Version
How to fix
IBM Tivoli Storage Manager
>=5.4.0<=5.4.3.6
IBM Tivoli Storage Manager
>=5.5.0<=5.5.4.3
IBM Tivoli Storage Manager
>=6.1.0<=6.1.5.6
IBM Tivoli Storage Manager
>=6.2.0<=6.2.5.3
IBM Tivoli Storage Manager
>=6.3.0<=6.3.2.2
macOS
Linux Kernel
OpenGroup Unix
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2014-6184 is considered a high severity vulnerability due to the potential for local users to gain elevated privileges.
How do I fix CVE-2014-6184?
To fix CVE-2014-6184, upgrade to IBM Tivoli Storage Manager version 5.4.3.7 or newer, 5.5.4.4 or newer, 6.1.5.7 or newer, 6.2.5.4 or newer, or 6.3.2.3 or newer.
What impact does CVE-2014-6184 have on affected systems?
CVE-2014-6184 allows local users to exploit a stack-based buffer overflow, potentially leading to unauthorized system access and privilege escalation.
Which versions of IBM Tivoli Storage Manager are affected by CVE-2014-6184?
The affected versions of IBM Tivoli Storage Manager are 5.4 through 5.4.3.6, 5.5 through 5.5.4.3, 6.1 through 6.1.5.6, 6.2 before 6.2.5.4, and 6.3 before 6.3.2.3.
Is there a workaround for CVE-2014-6184?
There are no specific workarounds for CVE-2014-6184, and the recommended action is to apply the necessary software updates.
SecAlerts Pty Ltd. 132 Wickham Terrace Fortitude Valley, QLD 4006, Australia info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.