dbcve.org
Proc\Application · Detlef Pilzecker

CVE-2013-7135

HIGH · 7.2 CVSS v2.0 Published 2014-01-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Proc::Daemon module 0.14 for Perl uses world-writable permissions for a file that stores a process ID, which allows local users to have an unspecified impact by modifying this file.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Proc::Daemon Perl module version 0.14 creates a PID file with world-writable permissions (mode 0666), allowing any local user to read, modify, or overwrite the file. This could enable local users to kill arbitrary processes by replacing the PID, cause denial of service, or manipulate daemon behavior.

MitigationUpgrade Proc::Daemon to a patched version, or manually correct PID file permissions after daemon startup using chmod to remove world-writable bits (e.g., chmod 644).

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Proc\Application
Affected:= \

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/AC:L/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Proc::Daemon Perl module is installed
    Run: perl -MProc::Daemon -e 'print $Proc::Daemon::VERSION' 2>/dev/null
    Affected if The command returns a version number, meaning the module is installed
  2. Verify the installed version of Proc::Daemon
    Compare the version number from step 1 against the affected version 0.14. If the version is exactly 0.14, it is affected. Earlier versions may also have this issue.
    Affected if Version is 0.14 or earlier (the specific affected version per the CVE)
  3. Identify PID files created by daemons using Proc::Daemon
    Locate PID files in common locations such as /var/run/, /tmp/, or application-specific directories. Look for files with .pid extension.
    Affected if PID files exist in directories writable by the application user
  4. Check the permissions of any PID files
    Run: ls -la /path/to/pidfile (replace with actual PID file path). Check if permissions show -rw-rw-rw- (mode 0666)
    Affected if Permissions are 0666 (rw-rw-rw-), indicating world-writable access

A user is affected if Proc::Daemon version 0.14 (or earlier) is installed AND any PID files it creates have world-writable (0666) permissions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Proc::Daemon to a patched version, or manually correct PID file permissions after daemon startup using chmod to remove world-writable bits (e.g., chmod 644).

Fix this in Proc\ Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-7135 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-7135 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data