CVE-2011-2765: pyro Package Arbitrary File Overwrite Vulnerability
Summary
CVE-2011-2765: pyro before 3.15 unsafely handles pid files in temporary directory locations and opening the pid file as root. Affects pyro across 2 version ranges.
< 3.15
< 554e095a62c4412c91f981e72fd34a936ac2bf1e
Fixed in 554e095a62c4412c91f981e72fd34a936ac2bf1e. How to fix ↓
Also tracked for
- pyro · Debian:10
The same CVE-2011-2765 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
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
The pyro package is a Python library that provides a distributed object system, allowing objects to be used across different machines. It enables remote method calls, object persistence, and automatic discovery of remote objects. The vulnerability in pyro versions before 3.15 involves unsafe handling of pid files in temporary directory locations and opening the pid file as root. This flaw can be exploited by an attacker to overwrite arbitrary files through symlinks.
Vulnerability Detail
The vulnerability in pyro versions before 3.15 arises from the insecure handling of pid files. When creating a pid file, the package does not properly validate the location of the temporary directory, which can be manipulated by an attacker. Additionally, the pid file is opened with root privileges, allowing an attacker to overwrite arbitrary files by creating a symlink to a target file. This can lead to unauthorized modification or destruction of important system files, potentially resulting in a complete system compromise.
How To Fix
Latest published version: 3.16.0 as of 23 Oct 2026
pip install --upgrade "pyro==3.16.0"Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
554e095a62c4412c91f981e72fd34a936ac2bf1e
This is the first release that contains the fix.
pip install --upgrade "pyro==554e095a62c4412c91f981e72fd34a936ac2bf1e"Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
If upgrading to the latest version is not immediately feasible, users can mitigate the risk by manually validating the location of the temporary directory used for pid files. Additionally, it is recommended to restrict the privileges of the process running pyro to minimize the potential impact of symlink attacks.
Conclusion
The pyro package versions before 3.15 are vulnerable to an arbitrary file overwrite vulnerability due to insecure handling of pid files. This can be exploited by an attacker to overwrite important system files through symlinks, potentially leading to a complete system compromise. Users should upgrade to pyro version 3.15 or later to fix this vulnerability. If immediate upgrade is not possible, manual validation of the temporary directory location and restricting process privileges can help mitigate the risk. For further support, contact DevNack.com.
See every vulnerability recorded for pyro →
FAQ
This vulnerability allows an attacker to overwrite arbitrary files on the system, potentially leading to unauthorized modification or destruction of important files and a complete system compromise.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability. The playground allows you to analyze your Pipfile.lock and provides real-time alerts for open-source vulnerabilities.
There have been reported instances of this vulnerability being exploited in the wild. It is important to promptly update to the fixed version to protect your system.
While upgrading to the fixed version is recommended, you can mitigate the risk by manually validating the location of the temporary directory used for pid files and restricting the privileges of the process running pyro.
For further support on vulnerability remediation or any other security concerns, you can contact info@devnack.com.
Related vulnerabilities
Recent vulnerabilities recorded for pyro.
