Privilege Escalation in libtool

libtool Updated 02 Oct 2025

Summary

29/12/2009
N/A
Yes i
Unrated
Not published

DSA-1958-1: libtool - privilege escalation. Affects libtool versions < 1.5.22-4+etch1. Fixed in 1.5.22-4+etch1. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

libtool is a system-independent dlopen wrapper for GNU libtool. It provides a consistent interface for dynamically loading shared libraries in a portable manner. The library is commonly used by various applications to load modules at runtime. However, a vulnerability has been discovered in the library that allows an attacker to trick libtool into loading and executing modules from an arbitrary directory. This could lead to the execution of arbitrary code with the privileges of the user running the affected application.

Vulnerability Detail

The vulnerability in libtool arises from its ability to load and run modules from any directory. By exploiting this behavior, an attacker can place a malicious module in a specific directory and trick libtool into loading and executing it. This can result in the execution of arbitrary code with the privileges of the user running the application. The impact of this vulnerability depends on the privileges of the user and the nature of the application using libtool.

How To Fix

Minimum fixed version

1.5.22-4+etch1

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

There is no known workaround for this vulnerability. It is recommended to apply the fix by upgrading the libtool package to the fixed versions.

Conclusion

In conclusion, libtool is vulnerable to a privilege escalation issue that allows an attacker to execute arbitrary code with the privileges of the user running the affected application. To mitigate this vulnerability, it is crucial to upgrade the libtool package to the fixed versions mentioned above. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for libtool →

Share this vulnerability

FAQ

libtool is a system-independent dlopen wrapper for GNU libtool. It provides a consistent interface for dynamically loading shared libraries in a portable manner.

The vulnerability in libtool allows an attacker to trick the library into loading and executing modules from an arbitrary directory, potentially leading to the execution of arbitrary code with the privileges of the user running the affected application.

The impact of this vulnerability depends on the privileges of the user and the nature of the application using libtool. If exploited, it can result in the execution of arbitrary code with the privileges of the user running the application.

To fix this vulnerability, it is recommended to upgrade the libtool package to the fixed versions: 1.5.22-4+etch1 for the oldstable distribution (etch), 1.5.26-4+lenny1 for the stable distribution (lenny), and 2.2.6b-1 for the testing distribution (squeeze) and unstable distribution (sid).

There is no known workaround for this vulnerability. It is recommended to apply the fix by upgrading the libtool package to the fixed versions.

Related vulnerabilities

Recent vulnerabilities recorded for libtool.

How To Fix

Minimum fixed version

1.5.22-4+etch1

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