File::Find::Rule through 0.34 for Perl is vulnerable to Arbitrary Code Execution when `grep()` encounters a crafted filename. A file handle is opened with the 2 argument form of `open()` allowing an attacker controlled filename to provide the MODE parameter to `open()`, turning the filename into a command to be executed. Example: $ mkdir /tmp/poc; echo > "/tmp/poc/|id" $ perl -MFile::Find::Rule \ -E 'File::Find::Rule->grep("foo")->in("/tmp/poc")' uid=1000(user) gid=1000(user) groups=1000(user),100(users)

The remote Debian 12 host has a package installed that is affected by a vulnerability as referenced in the dsa-5936 advisory.

    - -------------------------------------------------------------------------     Debian Security Advisory DSA-5936-1                   security@debian.org     https://www.debian.org/security/                     Salvatore Bonaccorso     June 05, 2025                         https://www.debian.org/security/faq
    - -------------------------------------------------------------------------

    Package        : libfile-find-rule-perl     CVE ID         : CVE-2011-10007     Debian Bug     : 1107311

    It was discovered that libfile-find-rule-perl, a module to search for     files based on rules, is vulnerable to arbitrary code execution when     grep() encounters a crafted file name.

    For the stable distribution (bookworm), this problem has been fixed in     version 0.34-4~deb12u1.

    We recommend that you upgrade your libfile-find-rule-perl packages.

    For the detailed security status of libfile-find-rule-perl please refer     to its security tracker page at:
    https://security-tracker.debian.org/tracker/libfile-find-rule-perl

    Further information about Debian Security Advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://www.debian.org/security/

    Mailing list: debian-security-announce@lists.debian.org

Tenable has extracted the preceding description block directly from the Debian security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

Detections

Analytics

CVE-2011-10007

high

Tenable Plugins

high