LiveActive security incident?Get immediate response
CVE Record

CVE-2011-2765: Insecure temporary file handling

pyro before 3.15 unsafely handles pid files in temporary directory locations and opening the pid file as root. An attacker can use this flaw to overwrite arbitrary files via symlinks.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue affects old Pyro versions before 3.15. When Pyro handles pid files in temporary locations as root, a local attacker could abuse symlinks to overwrite files the root process can write. The business risk is mainly on legacy systems still running Pyro daemons with elevated privileges.

Executive priority

Treat this as a targeted legacy-risk cleanup, not an internet-scale emergency. Prioritize systems where old Pyro services run with root privileges, because successful exploitation could damage or replace important local files.

Technical view

CVE-2011-2765 is insecure temporary file handling around Pyro pid files. The vulnerable behavior involves temporary-directory pid file paths and opening the pid file as root, enabling arbitrary file overwrite through symlink abuse. The provided sources do not include CVSS, CWE, or detailed affected package metadata beyond Pyro before 3.15.

Likely exposure

Exposure is most likely on legacy hosts running Pyro before 3.15, especially daemonized services that create pid files under temporary directories with root privileges. Modern environments are exposed only if this old dependency or downstream distro package remains installed and used.

Exploitation context

The CVE record is not listed as KEV, and the supplied sources do not show active exploitation. The flaw appears local or same-host in nature because it depends on manipulating filesystem paths around pid file creation.

Researcher notes

Evidence is limited to the CVE description, upstream commit, Pyro change log, and Debian bug reference. No CVSS, CWE, exploit-in-the-wild evidence, or comprehensive affected CPE data is supplied. Validate exact package names and backports per environment.

Mitigation direction

  • Upgrade Pyro deployments older than 3.15 where vendor or distro guidance confirms the fix.
  • Review Debian or operating-system package advisories for backported patches.
  • Avoid running affected Pyro daemons as root where operationally possible.
  • Keep pid files out of shared temporary directories when vendor guidance allows.
  • Check vendor guidance before applying any unsupported workaround.

Validation and detection

  • Inventory hosts and applications for Pyro or Pyro3 versions before 3.15.
  • Identify services that create Pyro pid files while running as root.
  • Confirm package patch status against distro release notes or changelogs.
  • Review service configurations for pid file paths in shared temporary directories.
  • Document compensating controls if upgrade is delayed.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2011-2765 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.