John Lightsey

The issue is related to the improper handling of temporary files by the Parallel::ForkManager module for Perl.

The issue arises from improper calls to seteuid() in the src/log.c and src/masqmail.c files, leading to improper privilege dropping.

The issue improperly handles file descriptors, allowing remote attackers to bypass security using a CGI script to break out of the chroot.

The issue allows remote attackers to execute arbitrary SQL commands.

The issue is related to errors in privilege management in the Perl interpreter, specifically with the handling of the included directory array ("@INC"). This could allow a local user to gain privileges via a Trojan horse module under the current working directory by exploiting the failure to properly remove period characters from the end of the includes directory array.

The issue is related to the lack of input sanitization in the Module::Signature module of the Ubuntu operating system. This can be exploited by a remote attacker to execute arbitrary shell commands using a specially crafted SIGNATURE file. The exploitation occurs when the module generates checksums from a signed manifest and does not properly handle the crafted file.

The issue allows local users to gain privileges via a Trojan horse module under the current working directory. This can be demonstrated by a Trojan horse Text::Diff module, where an attacker could potentially exploit the untrusted search path vulnerability to elevate their privileges.

The issue allows remote attackers to bypass signature verification for files. This can be achieved by using a signature file that does not list the files.

The issue concerns the PGP signature parsing in Module::Signature, allowing remote attackers to manipulate the treatment of signed and unsigned portions of a SIGNATURE file. This is achieved via unspecified vectors.

The issue allows remote attackers to execute arbitrary code via vectors related to localization of templates. This is due to a format string vulnerability.

The issue arises from the incorrect usage of the Storable::thaw function, allowing remote attackers to execute arbitrary code through the `comment state` parameter. This enables attackers to potentially gain control over the system.

The issue arises from the improper use of the Perl Storable::thaw function, allowing remote attackers to include and execute arbitrary local Perl files, and possibly execute arbitrary code via unspecified vectors.

The issue arises from the improper use of the Storable::thaw function in the Session::Cookie component of the HTML::EP module for Perl. This allows remote attackers to execute arbitrary code via a crafted request that is not properly handled when deserialized.

The issue arises from the improper use of the Storable::thaw function in the App::Context module for Perl. This allows remote attackers to execute arbitrary code via a crafted request to API endpoints such as (1) "App::Session::Cookie" or (2) "App::Session::HTMLHidden". The problem occurs when the request is not properly handled during deserialization.

The issue arises from improper use of the Storable::thaw function in the Spoon::Cookie component of the Spoon module for Perl. This allows remote attackers to execute arbitrary code by sending a crafted request. The request is not properly handled when it is deserialized.

The issue allows local users to gain privileges via unspecified vectors, related to an RLIMIT NPROC attack, due to the setuid function's return value not being checked when the -F flag is set in the super.c file.

The issue allows context-dependent attackers to read arbitrary files via a crafted XML file, potentially affecting products such as Evergreen, Koha, and perl4lib that utilize the MARC::File::XML module for Perl.

The issue allows local users to potentially bypass intended file-read restrictions. This is due to the software retaining the supplementary group IDs of the root account during operations with a non-root effective UID, and a race condition in a file-permission check.

The issue allows local users to potentially gain privileges by exploiting cgi-bin write access during the execution of CGI scripts, as the software uses a real UID of root and a real GID of root.

The issue is related to the ` is safe` function in the File::Temp module for Perl, which does not properly handle symlinks. This can potentially allow a remote attacker to impact data integrity.