Symlink Attack Vulnerability in GNU Libtool: Risk of Arbitrary File Overwrite
Summary
DEBIAN-CVE-2004-0256: GNU libtool before 1.5.2, during compile time, allows local users to overwrite arbitrary files via a symlink attack on libtool directories in /tmp. Affects libtool versions < 1.5.6. Fixed in 1.5.6. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
GNU Libtool is a widely used software utility that helps manage the creation of static and dynamic libraries in software development. It simplifies the process of compiling and linking code across different platforms. However, prior to version 1.5.2, Libtool had a significant vulnerability that allowed local users to exploit symlink attacks, particularly in temporary directories, leading to potential file overwrites.
Vulnerability Detail
The vulnerability identified as DEBIAN-CVE-2004-0256 affects GNU Libtool versions before 1.5.2. During the compilation process, the software allows local users to create symbolic links in the /tmp directory, which can point to arbitrary files. This can lead to unauthorized overwriting of sensitive files, posing a serious security risk to systems using affected versions of Libtool.
How To Fix
Minimum fixed version
1.5.6
This is the first release that contains the fix.
sudo apt-get install --only-upgrade libtool
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary workaround, users can avoid using Libtool in environments where symlink attacks may be a concern. Additionally, ensuring that the /tmp directory is secured and monitored can help mitigate potential risks until the package is updated.
Conclusion
The vulnerability in GNU Libtool poses a significant risk due to the potential for arbitrary file overwrites via symlink attacks. Users are strongly advised to update to version 1.5.6 or later to mitigate this risk. Additionally, utilizing tools like Vulert can enhance security monitoring for open-source vulnerabilities.
See every vulnerability recorded for libtool →
FAQ
A symlink attack occurs when an attacker creates a symbolic link to a sensitive file, tricking the system into overwriting that file during operations that follow the symlink.
You can check your version of Libtool by running 'libtool --version' in the terminal. If it is below 1.5.6, it is vulnerable.
Not addressing this vulnerability can lead to unauthorized file access and modification, potentially compromising system integrity and security.
Yes, tools like Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
References
Related vulnerabilities
Recent vulnerabilities recorded for libtool.