/ 
perl-5.27.11
⭐ Starred 2013
/ Encode::JP
Security Advisories (7)
CVE-2020-12723 (2020-06-05)

regcomp.c in Perl before 5.30.3 allows a buffer overflow via a crafted regular expression because of recursive S_study_chunk calls.

CVE-2020-10878 (2020-06-05)

Perl before 5.30.3 has an integer overflow related to mishandling of a "PL_regkind[OP(n)] == NOTHING" situation. A crafted regular expression could lead to malformed bytecode with a possibility of instruction injection.

CVE-2020-10543 (2020-06-05)

Perl before 5.30.3 on 32-bit platforms allows a heap-based buffer overflow because nested regular expression quantifiers have an integer overflow.

CVE-2018-6798 (2018-04-17)

An issue was discovered in Perl 5.22 through 5.26. Matching a crafted locale dependent regular expression can cause a heap-based buffer over-read and potentially information disclosure.

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.

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-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

NAME

Encode::JP - Japanese Encodings

SYNOPSIS

use Encode qw/encode decode/; 
$euc_jp = encode("euc-jp", $utf8);   # loads Encode::JP implicitly
$utf8   = decode("euc-jp", $euc_jp); # ditto

ABSTRACT

This module implements Japanese charset encodings. Encodings supported are as follows.

Canonical   Alias		Description
--------------------------------------------------------------------
euc-jp      /\beuc.*jp$/i	EUC (Extended Unix Character)
            /\bjp.*euc/i   
        /\bujis$/i
shiftjis    /\bshift.*jis$/i	Shift JIS (aka MS Kanji)
        /\bsjis$/i
7bit-jis    /\bjis$/i		7bit JIS
iso-2022-jp			ISO-2022-JP                  [RFC1468]
              = 7bit JIS with all Halfwidth Kana 
                converted to Fullwidth
iso-2022-jp-1			ISO-2022-JP-1                [RFC2237]
                              = ISO-2022-JP with JIS X 0212-1990
                support.  See below
MacJapanese	                Shift JIS + Apple vendor mappings
cp932       /\bwindows-31j$/i Code Page 932
                              = Shift JIS + MS/IBM vendor mappings
jis0201-raw                   JIS0201, raw format
jis0208-raw                   JIS0201, raw format
jis0212-raw                   JIS0201, raw format
--------------------------------------------------------------------

DESCRIPTION

To find out how to use this module in detail, see Encode.

Note on ISO-2022-JP(-1)?

ISO-2022-JP-1 (RFC2237) is a superset of ISO-2022-JP (RFC1468) which adds support for JIS X 0212-1990. That means you can use the same code to decode to utf8 but not vice versa.

$utf8 = decode('iso-2022-jp-1', $stream);

and

$utf8 = decode('iso-2022-jp',   $stream);

yield the same result but

$with_0212 = encode('iso-2022-jp-1', $utf8);

is now different from

$without_0212 = encode('iso-2022-jp', $utf8 );

In the latter case, characters that map to 0212 are first converted to U+3013 (0xA2AE in EUC-JP; a white square also known as 'Tofu' or 'geta mark') then fed to the decoding engine. U+FFFD is not used, in order to preserve text layout as much as possible.

BUGS

The ASCII region (0x00-0x7f) is preserved for all encodings, even though this conflicts with mappings by the Unicode Consortium.

SEE ALSO

Encode