Summary
This update for perl-MIME-tools fixes the following issues:
Changes in perl-MIME-tools:
- updated to 5.522.0 (5.522)
* 5.522
* VERSION 5.522 RELEASED
* Many security issues were addressed (see the following ten CVEs)
Issues were brought to my attention, and patches supplied, by the
CPANSec security group.
* parse_params: flag a parameter list that could not be parsed
Detect additional ambiguous parse situations when parameter
names contain illegal characters. Fixes:
CVE-2026-116264 invalid parameter hides boundary/filename. bsc#1288723
* parse_params: check the boundary after RFC 2231 reassembly
Another ambiguous-parse case was missed (trailing space after
boundary was not detected for RFC-2231-encoded boundaries.) Fixes:
CVE-2026-116265 RFC 2231 boundary skips ambiguity checks. bsc#1288722
* parse_params: Stricter checking for encoded boundaries; earlier
versions would miss some cases. Fixes:
CVE-2026-116266 boundary changed by decoding not flagged. bsc#1288721
* Cap the indentation levels in the Results: structure. Otherwise,
specially-crafted messages could consume large amounts of memory.
Fixes: CVE-2026-116267 indent stored per message per level bsc#1288720
* parse_params: stop a comment match at the next parenthesis.
Otherwise, specially-crafted messages could cause the regex
back-tracker to consume large amounts of CPU time. Note that
MIME::Parser does not correctly parse ((nested comments)) and
has never done so. Fixes:
CVE-2026-116268 unclosed "(" comments backtrack CPU exhaustion. bsc#1288719
* parse_params: re-encode filename* values without charset tricks
Specially-crafted messages could trick recommended_filename()
into returning an empty string instead of a plausible filename.
Fixes: CVE-2026-116269 RFC 2231 language tag empties filename. bsc#1288718
* decode_mimewords: do not copy the input into each error. Otherwise,
specially-crafted messages could consume large amounts of memory.
Fixes: CVE-2026-116270 each bad "=?" copies the input into $@. bsc#1288717
* FileUnder: do not reuse an existing generated directory. Otherwise,
attackers might be able to use symbolic links to get files created
in unexpected locations. Fixes:
CVE-2026-116271 FileUnder reuses a pre-created directory. bsc#1288716
* parse_params: flag comments other readers do not skip
Specially-crafted messages could create ambiguous messages without
setting the ambiguous_parse flag. Fixes:
CVE-2026-116272 comment hides a duplicate boundary. bsc#1288715
* Call whine() rather than error() if max_parts or max_depth is
exceeded during a parse. This lets us return undef rather than
throwing an exception if ignore_errors() is set to 0.
* Change to defaults: max_parts is now set to 1000 and max_depth
to 64 rather than being unlimited. This should not affect most
real-world uses of MIME::tools, but you may need to increase
these values or set them to -1 (unlimited) if you run into trouble.
***** NOTE INCOMPATIBILITY *****
Fixes: CVE-2026-116273 max_parts and max_depth unlimited. bsc#1288714
* Do not signal an ambiguous parse if we have filename="" or
name=""
* Update author names in META.yml
* Add git repo to META.yml
* 5.520
* VERSION 5.520 RELEASED
* MIME::Parser used O(N^2) CPU time and memory parsing a MIME
message nested N levels deep. A smallish specially-crafted
message could DOS the computer by making it consume enormous
amounts of memory and CPU time. The parser was modified to use
O(N) time and memory in this case. Additionally, a new
MIME::Parser::max_depth() function was added to limit the nesting
depth before declaring a parse failure. Problem was reported to
me by Zhaoyang Li and Xiang Li from AOSP Lab at Nankai University.
* MIME::Parser would ignore multiple blank lines in a message
preamble when parsing it; this could break DKIM. Problem pointed
out and fix suggested by Tim Henderson.
* If a MIME boundary includes trailing whitespace, we mark the
parse as ambiguous. Problem noted and patch submitted by
Christian Herdtweck
* 5.519
* VERSION 5.519 RELEASED
* Some (buggy) software creates base64-encoded parts as a
concatenation of multiple base64-encoded streams, and some client
software decodes each stream separately and concatenates the
results. Duplicate this behavior in MIME::tools to prevent it
from being used as a mechanism to sneak dangerous content past a
security scanner. Patch courtesy of Giorgio Premi
<giosh94mhz@gmail.com>.
- updated to 5.518.0 (5.518)
* 5.518
* VERSION 5.518 RELEASED
* Add tests for encoded "boundary=XXX" parameters and set
the ambiguous-parse flag if any are found. Patch courtesy
of Dominik Csapak <d.csapak@proxmox.com>
MIME::tools chooses to decode encoded boundary parameters.
MUA behaviors differ; Claws-Mail decodes them while Thunderbird
does not.
* Don't ignore invalid whitespace after "boundary=XXX" parameter.
Patch courtesy of Dominik Csapak <d.csapak@proxmox.com>
* Ignore comments between tokens. A header parameter can be
written foo(comment)=bar and it's the same as foo=bar.
Patch courtesy of Dominik Csapak <d.csapak@proxmox.com>
- updated to 5.517.0 (5.517)
* 5.517
* VERSION 5.517 RELEASED
* Add a missing test message file that was causing tests to fail.
* 5.516
* VERSION 5.516 RELEASED
* Handle MIME parameters of the form param= better (ie,
a parameter with no value at all.) It's treated the
same as param="" rather than aborting the parse.
* Diagnose additional types of malformed MIME as ambiguous.
Specifically, an empty boundary parameters like boundary= or
boundary="" is treated as ambiguous. Thanks to Stoiko Ivanov
<s.ivanov@proxmox.com> for pointing out this missing case.
Fixed packages 1
| Release | Package | Fixed in |
|---|---|---|
| openSUSE · Leap 16.0 | perl-MIME-tools | 5.522.0-bp160.1.1 |
Vulnerabilities 10
-
High 7.5
MIME::Parser versions before 5.521 for Perl allow memory exhaustion via indented error messages from a truncated, deeply nested message
MIME::Parser versions before 5.521 for Perl allow memory exhaustion via indented error messages from a truncated, deeply nested message. Each stored parser diagnostic is indented by three spaces per nesting level. When a message nested N levels deep ends with…
-
High 7.5
MIME::Field::ParamVal versions before 5.521 for Perl allow CPU exhaustion via unclosed comments in header parameters
MIME::Field::ParamVal versions before 5.521 for Perl allow CPU exhaustion via unclosed comments in header parameters. The comment pattern used to parse Content-Type and Content-Disposition parameters scans from each "(" to the next ")". In a field with no ")"…
-
High 7.5
MIME::Words versions before 5.521 for Perl allow memory exhaustion via repeated "=?" sequences in decode_mimewords
MIME::Words versions before 5.521 for Perl allow memory exhaustion via repeated "=?" sequences in decode_mimewords. For each "=?" that does not start a complete encoded word, decode_mimewords appends an error message containing the whole input string to $@. A…
-
High 7.5
MIME::Parser versions before 5.521 for Perl set no limit on the number of message parts by default, allowing memory exhaustion
MIME::Parser versions before 5.521 for Perl set no limit on the number of message parts by default, allowing memory exhaustion. The max_parts option defaulted to -1, which disables the limit, so a parser created with default settings builds an entity for ever…
-
High 7.0
MIME::Parser::FileUnder versions before 5.521 for Perl reuse a pre-created output directory and follow symlinks in it, letting local users redirect attachment writes
MIME::Parser::FileUnder versions before 5.521 for Perl reuse a pre-created output directory and follow symlinks in it, letting local users redirect attachment writes. Each message is written to a directory named msg-<time>-<pid>-<n> under the output base, and…
-
Medium 5.3
MIME::Field::ParamVal versions before 5.521 for Perl allow one invalid Content-Type parameter to hide the parameters after it, including the multipart boundary
MIME::Field::ParamVal versions before 5.521 for Perl allow one invalid Content-Type parameter to hide the parameters after it, including the multipart boundary. Parameter parsing stops at the first parameter whose name it cannot read, such as x:y=1 or a name …
-
Medium 5.3
MIME::Field::ParamVal versions before 5.521 for Perl do not flag an ambiguous multipart boundary written as RFC 2231 continuations
MIME::Field::ParamVal versions before 5.521 for Perl do not flag an ambiguous multipart boundary written as RFC 2231 continuations. The boundary ambiguity checks look only at a plain boundary= parameter, and a boundary split into RFC 2231 sections (boundary*0…
-
Medium 5.3
MIME::Head versions from 5.518 before 5.521 for Perl decode a partly encoded multipart boundary without flagging the parse as ambiguous
MIME::Head versions from 5.518 before 5.521 for Perl decode a partly encoded multipart boundary without flagging the parse as ambiguous. The multipart_boundary() method decodes RFC 2047 encoded words anywhere in the boundary, but the ambiguity check only fire…
-
Medium 5.3
MIME::Field::ParamVal versions before 5.521 for Perl turn an RFC 2231 filename with a hyphenated language tag into an empty recommended filename
MIME::Field::ParamVal versions before 5.521 for Perl turn an RFC 2231 filename with a hyphenated language tag into an empty recommended filename. A parameter such as filename*=utf-8'en-US'payload.exe is converted to an encoded word with the language tag appen…
-
Medium 5.3
MIME::Field::ParamVal versions before 5.521 for Perl do not flag a duplicate boundary parameter whose name contains a nested comment
MIME::Field::ParamVal versions before 5.521 for Perl do not flag a duplicate boundary parameter whose name contains a nested comment. A parameter written boundary((c))="A" or boundary(\))="A" is stored under that literal name rather than as boundary. A second…
References
-
report
https://bugzilla.suse.com/1288714
-
report
https://bugzilla.suse.com/1288715
-
report
https://bugzilla.suse.com/1288716
-
report
https://bugzilla.suse.com/1288717
-
report
https://bugzilla.suse.com/1288718
-
report
https://bugzilla.suse.com/1288719
-
report
https://bugzilla.suse.com/1288720
-
report
https://bugzilla.suse.com/1288721
-
report
https://bugzilla.suse.com/1288722
-
report
https://bugzilla.suse.com/1288723
-
web
https://www.suse.com/security/cve/CVE-2026-116264
-
web
https://www.suse.com/security/cve/CVE-2026-116265
-
web
https://www.suse.com/security/cve/CVE-2026-116266
-
web
https://www.suse.com/security/cve/CVE-2026-116267
-
web
https://www.suse.com/security/cve/CVE-2026-116268
-
web
https://www.suse.com/security/cve/CVE-2026-116269
-
web
https://www.suse.com/security/cve/CVE-2026-116270
-
web
https://www.suse.com/security/cve/CVE-2026-116271
-
web
https://www.suse.com/security/cve/CVE-2026-116272
-
web
https://www.suse.com/security/cve/CVE-2026-116273