Skip to content
Fencer Vulns
medium 4.6

CVE-2008-2827 json

The rmtree function in lib/File/Path.pm in Perl 5.10 does not properly check permissions before performing a chmod, which allows local user…

published 2008-06-23 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-2820

cvss
4.6
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 58%
public exploits
1
Exploit-DB

Summary

The rmtree function in lib/File/Path.pm in Perl 5.10 does not properly check permissions before performing a chmod, which allows local users to modify the permissions of arbitrary files via a symlink attack, a different vulnerability than CVE-2005-0448 and CVE-2004-0452.

Patch / fix

  • perl Debian 14, Debian 13, Debian 12 5.10.0-11

debian advisories DEBIAN-CVE-2008-2827

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-2008-2827 updated

perl: insecure use of chmod in rmtree

  • Red Hat All currently supported Red Hat products
    not 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

Timeline

  1. First public exploit (EDB-31959)
  2. Published

Exploit prediction

0.84% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-31959 Perl - 'rmtree()' Function Local Insecure Permissions local, 2008-06-23
  • rt.cpan.org http://rt.cpan.org/Public/Bug/Display.html?id=36982 referenced PoC, tagged "exploit" by a source, unverified
  • bugs.debian.org http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=487319 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 4.6 AV:L/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls

References

Sources

Fencer Vulns 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.