Resolved Bugs
965126 – License metadata do not reflect cpansign license
1209911 – perl-Module-Signature: unsigned files interpreted as signed in some circumstances
1209915 – perl-Module-Signature: arbitrary code execution during test phase
1209917 – perl-Module-Signature: arbitrary code execution when verifying module signatures
1209918 – perl-Module-Signature: arbitrary modules loading in some circumstances
1209922 – perl-Module-Signature: various flaws [epel-all]<br
This update addresses various security issues in perl-Module-Signature as described below. The default behavior is also changed so as to ignore any MANIFEST.SKIP files unless a “skip” parameter is specified. An updated version of perl-Test-Signature that accounts for the changed default behavior is included in this update.
Security issues:
* Module::Signature before version 0.75 could be tricked into interpreting the unsigned portion of a SIGNATURE file as the signed portion due to faulty parsing of the PGP signature boundaries.
* When verifying the contents of a CPAN module, Module::Signature before version 0.75 ignored some files in the extracted tarball that were not listed in the signature file. This included some files in the t/ directory that would execute
automatically during “make test”.
* Module::Signature before version 0.75 used two argument open() calls to read the files when generating checksums from the signed manifest. This allowed embedding arbitrary shell commands into the SIGNATURE file that would execute during the signature verification process.
* Module::Signature before version 0.75 has been loading several modules at runtime inside the extracted module directory. Modules like Text::Diff are not guaranteed to be available on all platforms and could be added to a malicious
module so that they would load from the ‘.’ path in @INC.