Symlink Vulnerability in GNU Libtool: Risk of Arbitrary File Overwrites

libtool Updated 02 Oct 2025

Summary

23/11/2004
N/A
Yes i
Unrated
Not published

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 ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

GNU Libtool is a widely used software utility that helps manage the creation of shared libraries and simplifies the process of linking against them. It is essential for developers who need to compile and link programs across different platforms. However, prior to version 1.5.2, Libtool was susceptible to a security flaw that allowed local users to exploit symlink attacks, leading to potential file overwrites in temporary directories.

Vulnerability Detail

The vulnerability, identified as CVE-2004-0256, arises from the way GNU Libtool handles temporary files during the compilation process. Specifically, it allows local users to create symbolic links in the /tmp directory that point to arbitrary files. When Libtool attempts to write to these temporary files, it inadvertently overwrites the target files, which could lead to data loss or corruption. This issue is particularly concerning in multi-user environments where unprivileged users can exploit this flaw to manipulate files owned by other users.

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 measure, users can avoid using the /tmp directory for Libtool operations or ensure that the permissions on the /tmp directory are set to prevent unauthorized users from creating symlinks. Additionally, users can monitor the /tmp directory for suspicious symlink creations.

Conclusion

The CVE-2004-0256 vulnerability in GNU Libtool poses a significant risk to users, particularly in multi-user environments. Upgrading to version 1.5.6 or later is essential to mitigate this risk. Users are also encouraged to implement workarounds and monitor their systems for potential exploitation.

See every vulnerability recorded for libtool →

Share this vulnerability

FAQ

CVE-2004-0256 is a vulnerability in GNU Libtool that allows local users to overwrite arbitrary files via a symlink attack on temporary directories.

You can use Vulert, which monitors open-source vulnerabilities in your software using a manifest file like package-lock.json. Visit Vulert Scanner to check if your application is affected without needing to sign up.

The primary risk is the potential for data loss or corruption, as local users can overwrite files that they should not have access to, leading to security breaches or application failures.

Yes, you can temporarily avoid using the /tmp directory for Libtool operations or adjust permissions to prevent unauthorized symlink creation.

Versions of GNU Libtool prior to 1.5.6 are affected by this vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback