Security Advisories (6)
CVE-2022-48522 (2023-08-22)

In Perl 5.34.0, function S_find_uninit_var in sv.c has a stack-based crash that can lead to remote code execution or local privilege escalation.

CVE-2023-47038 (2023-10-30)

A crafted regular expression when compiled by perl 5.30.0 through 5.38.0 can cause a one attacker controlled byte buffer overflow in a heap allocated buffer

CVE-2024-56406 (2025-04-13)

A heap buffer overflow vulnerability was discovered in Perl. Release branches 5.34, 5.36, 5.38 and 5.40 are affected, including development versions from 5.33.1 through 5.41.10. When there are non-ASCII bytes in the left-hand-side of the `tr` operator, `S_do_trans_invmap` can overflow the destination pointer `d`.    $ perl -e '$_ = "\x{FF}" x 1000000; tr/\xFF/\x{100}/;'    Segmentation fault (core dumped) It is believed that this vulnerability can enable Denial of Service and possibly Code Execution attacks on platforms that lack sufficient defenses.

CVE-2025-40909 (2025-05-30)

Perl threads have a working directory race condition where file operations may target unintended paths. If a directory handle is open at thread creation, the process-wide current working directory is temporarily changed in order to clone that handle for the new thread, which is visible from any third (or more) thread already running. This may lead to unintended operations such as loading code or accessing files from unexpected locations, which a local attacker may be able to exploit. The bug was introduced in commit 11a11ecf4bea72b17d250cfb43c897be1341861e and released in Perl version 5.13.6

CVE-2023-47039 (2023-10-30)

Perl for Windows relies on the system path environment variable to find the shell (cmd.exe). When running an executable which uses Windows Perl interpreter, Perl attempts to find and execute cmd.exe within the operating system. However, due to path search order issues, Perl initially looks for cmd.exe in the current working directory. An attacker with limited privileges can exploit this behavior by placing cmd.exe in locations with weak permissions, such as C:\ProgramData. By doing so, when an administrator attempts to use this executable from these compromised locations, arbitrary code can be executed.

CVE-2023-47100

In Perl before 5.38.2, S_parse_uniprop_string in regcomp.c can write to unallocated space because a property name associated with a \p{...} regular expression construct is mishandled. The earliest affected version is 5.30.0.

NAME

if - use a Perl module if a condition holds

SYNOPSIS

use if CONDITION, "MODULE", ARGUMENTS;
no  if CONDITION, "MODULE", ARGUMENTS;

DESCRIPTION

use if

The if module is used to conditionally load another module. The construct:

use if CONDITION, "MODULE", ARGUMENTS;

... will load MODULE only if CONDITION evaluates to true; it has no effect if CONDITION evaluates to false. (The module name, assuming it contains at least one ::, must be quoted when 'use strict "subs";' is in effect.) If the CONDITION does evaluate to true, then the above line has the same effect as:

use MODULE ARGUMENTS;

For example, the Unicode::UCD module's charinfo function will use two functions from Unicode::Normalize only if a certain condition is met:

use if defined &DynaLoader::boot_DynaLoader,
    "Unicode::Normalize" => qw(getCombinClass NFD);

Suppose you wanted ARGUMENTS to be an empty list, i.e., to have the effect of:

use MODULE ();

You can't do this with the if pragma; however, you can achieve exactly this effect, at compile time, with:

BEGIN { require MODULE if CONDITION }

no if

The no if construct is mainly used to deactivate categories of warnings when those categories would produce superfluous output under specified versions of perl.

For example, the redundant category of warnings was introduced in Perl-5.22. This warning flags certain instances of superfluous arguments to printf and sprintf. But if your code was running warnings-free on earlier versions of perl and you don't care about redundant warnings in more recent versions, you can call:

use warnings;
no if $] >= 5.022, q|warnings|, qw(redundant);

my $test    = { fmt  => "%s", args => [ qw( x y ) ] };
my $result  = sprintf $test->{fmt}, @{$test->{args}};

The no if construct assumes that a module or pragma has correctly implemented an unimport() method -- but most modules and pragmata have not. That explains why the no if construct is of limited applicability.

BUGS

The current implementation does not allow specification of the required version of the module.

SEE ALSO

Module::Requires can be used to conditionally load one or modules, with constraints based on the version of the module. Unlike if though, Module::Requires is not a core module.

Module::Load::Conditional provides a number of functions you can use to query what modules are available, and then load one or more of them at runtime.

The provide module from CPAN can be used to select one of several possible modules to load based on the version of Perl that is running.

AUTHOR

Ilya Zakharevich mailto:ilyaz@cpan.org.

COPYRIGHT AND LICENCE

This software is copyright (c) 2002 by Ilya Zakharevich.

This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.