CVE-2011-4363 json
ProcessTable.pm in the Proc::ProcessTable module 0.45 for Perl, when TTY information caching is enabled, allows local users to overwrite ar…
published 2012-10-07 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-4293
- cvss
- 2.6
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 23%
- public exploits
- 0
- none known
Summary
ProcessTable.pm in the Proc::ProcessTable module 0.45 for Perl, when TTY information caching is enabled, allows local users to overwrite arbitrary files via a symlink attack on /tmp/TTYDEVS.
Patch / fix
- libproc-processtable-perl Debian 14, Debian 13, Debian 12 0.45-6
debian advisories DEBIAN-CVE-2011-4363
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2011-4363 updated cvss 3.3
perl-Proc-ProcessTable: unsafe temporary file usage
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.30% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 2.6 | AV:L/AC:H/Au:N/C:N/I:P/A:P |
Classification
- Weakness
-
- CWE-59 Improper Link Resolution Before File Access
References
-
openwall.com
/lists/oss-security/2011/11/30/2
mailing-list
-
securityfocus.com
/bid/50868
vdb-entry
- bugzilla.redhat.com /show_bug.cgi?id=CVE-2011-4363
- bugs.debian.org /cgi-bin/bugreport.cgi?bug=650500
-
secunia.com
/advisories/47015
third-party-advisory
-
openwall.com
/lists/oss-security/2011/11/30/3
mailing-list
-
osvdb.org
/77428
vdb-entry
- rt.cpan.org /Public/Bug/Display.html?id=72862
Sources
- CVE List CVE-2011-4363
- NVD CVE-2011-4363
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.