Overview 33 matches · 0 in Waratek scope · 0 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
33matches
0in Waratek scope0.0%
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
0public PoC0.0%
0EPSS ≥ 0.50.0%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
2
6.1%
Not applicable
31
93.9%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
33
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
1
3.0%
Forecast only
0
0.0%
No public exploit
32
97.0%
split by
peak 6 / year
20071
Not applicable1
Medium1
not blocked1
No public exploit1
20080
20090
20100
20111
Not applicable1
Medium1
not blocked1
No public exploit1
20120
20130
20143
Not applicable3
Medium3
not blocked3
No public exploit3
20150
20161
Not applicable1
High1
not blocked1
No public exploit1
20171
Not applicable1
Medium1
not blocked1
No public exploit1
20182
Outside Waratek scope1
Not applicable1
High2
not blocked2
No public exploit2
20195
Not applicable5
Critical3
Medium2
not blocked5
No public exploit5
20202
Not applicable2
High1
Medium1
not blocked2
No public exploit2
20215
Outside Waratek scope1
Not applicable4
High4
Medium1
not blocked5
No public exploit5
20221
Not applicable1
High1
not blocked1
Proof of concept only1
20232
Not applicable2
High1
Medium1
not blocked2
No public exploit2
20242
Not applicable2
Critical1
High1
not blocked2
No public exploit2
20251
Not applicable1
Critical1
not blocked1
No public exploit1
20266
Not applicable6
Critical3
High3
not blocked6
No public exploit6
2008201020122014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-9487 | Critical | 2026-08-03 | Not applicable | No public exploit | XML::Sig versions before 0.71 for Perl allow signature wrapping via duplicate ID. _get_signed_xml() in lib/XML/Sig.pm, called from verify(), resolves the SignedInfo Reference/@URI to a node with the XPath expression "//*[@ID='$id']" and returns the first node of the resulting node set. A document in which two elements share that ID value is accepted: the digest and signature are checked against whichever element comes first in document order, and the duplicate is not detected. Such a document verifies successfully while an application that resolves the same ID independently can read the second, attacker supplied element; in a SAML2 context this places the contents of an Assertion under attacker control. |
| CVE-2026-9390 | Critical | 2026-08-03 | Not applicable | No public exploit | XML::Sig versions before 0.71 for Perl allow XPath injection in ID lookup. verify() and _get_signed_xml() in lib/XML/Sig.pm build XPath expressions by concatenating the SignedInfo/Reference/@URI value read from the document being verified. The value is neither escaped nor checked against the NCName grammar that XML requires of an ID, so a URI containing a single quote closes the string literal in the generated expression and appends arbitrary XPath operators. A crafted URI can make the lookup match elements the reference does not name, or every element in the document, so which node is selected for digest verification is decided by the injected expression rather than by the reference. |
| CVE-2026-18568 | High | 2026-08-03 | Not applicable | No public exploit | XML::Sig versions from 0.29 before 0.72 for Perl allow signature verification bypass because verify returns true when every signature was skipped before any cryptographic check. verify in lib/XML/Sig.pm counts the `//dsig:Signature` elements into `$numsigs` and iterates over them, but two paths reach `next` before any digest or key check runs: a `SignedInfo/Reference/@URI` that resolves to no element while `$numsigs` is greater than 1, and, when `id_attr` is set, a reference that does not match the requested ID. The loop records nothing about what it checked, so when every signature takes one of those paths control reaches the unconditional `return 1` that ends verify. Two `Signature` elements whose Reference URI names an ID that no element carries is enough, as is one such element combined with `id_attr`. Any caller that passes untrusted XML to verify can receive a true return for a document in which no digest and no signature value was checked; a `cert` or `cert_text` trust anchor does not change this, because no key check runs. Versions up to 0.28 use an XML::XPath based verify that has no such skip and are not affected. |
| CVE-2026-9538 | High | 2026-05-26 | Not applicable | No public exploit | Archive::Tar versions before 3.10 for Perl allow memory exhaustion via attacker controlled entry size field in tar header. _read_tar() reads each entry's payload with $handle->read($$data, $block), where $block is derived from the entry's 12-byte size field in the tar header with no upper bound on that value. A crafted header declaring a multi-gigabyte size causes Perl to allocate a scalar of that size. |
| CVE-2026-42497 | High | 2026-05-26 | Not applicable | No public exploit | Archive::Tar versions before 3.08 for Perl extract hardlinks to attacker controlled paths outside the extraction directory. _make_special_file() passes the tar header's linkname to link() without validating it against absolute paths or .. segments, creating a hardlink that shares the victim file's inode. A subsequent write through the extracted name modifies the victim file, and the post-extraction chmod, chown, and utime block in _extract_file() (guarded only against symlinks via -l) applies the tar header's mode, owner, and timestamps to the shared inode during extraction alone. |
| CVE-2026-42496 | Critical | 2026-05-26 | Not applicable | No public exploit | Archive::Tar versions before 3.08 for Perl extract symlinks with attacker controlled targets outside the extraction directory. _make_special_file() passes the tar header's linkname to symlink() without validating it against absolute paths or .. segments. The secure-extract mode check that guards regular file extraction does not cover the symlink target. A subsequent open through the extracted name reads or writes the attacker chosen path. |
| CVE-2025-40934 | Critical | 2025-11-26 | Not applicable | No public exploit | XML-Sig versions 0.27 through 0.67 for Perl incorrectly validates XML files if signatures are omitted. An attacker can remove the signature from the XML document to make it pass the verification check. XML-Sig is a Perl module to validate signatures on XML files. An unsigned XML file should return an error message. The affected versions return true when attempting to validate an XML file that contains no signatures. |
| CVE-2024-45321 | Critical | 2024-08-27 | Not applicable | No public exploit | The App::cpanminus package through 1.7047 for Perl downloads code via insecure HTTP, enabling code execution for network attackers. |
| CVE-2023-52431 | High | 2024-02-13 | Not applicable | No public exploit | The Plack::Middleware::XSRFBlock package before 0.0.19 for Perl allows attackers to bypass a CSRF protection mechanism via an empty form value and an empty cookie (if signed cookies are disabled). |
| CVE-2023-31486 | High | 2023-04-29 | Not applicable | No public exploit | HTTP::Tiny before 0.083, a Perl core module since 5.13.9 and available standalone on CPAN, has an insecure default TLS configuration where users must opt in to verify certificates. |
| CVE-2023-31485 | Medium | 2023-04-29 | Not applicable | No public exploit | GitLab::API::v4 through 0.26 does not verify TLS certificates when connecting to a GitLab server, enabling machine-in-the-middle attacks. |
| CVE-2022-31081 | High | 2022-06-27 | Not applicable | Proof of concept only | HTTP::Daemon is a simple http server class written in perl. Versions prior to 6.15 are subject to a vulnerability which could potentially be exploited to gain privileged access to APIs or poison intermediate caches. It is uncertain how large the risks are, most Perl based applications are served on top of Nginx or Apache, not on the `HTTP::Daemon`. This library is commonly used for local development and tests. Users are advised to update to resolve this issue. Users unable to upgrade may add additional request handling logic as a mitigation. After calling `my $rqst = $conn->get_request()` one could inspect the returned `HTTP::Request` object. Querying the 'Content-Length' (`my $cl = $rqst->header('Content-Length')`) will show any abnormalities that should be dealt with by a `400` response. Expected strings of 'Content-Length' SHOULD consist of either a single non-negative integer, or, a comma separated repetition of that number. (that is `42` or `42, 42, 42`). Anything else MUST be rejected. |
| CVE-2020-16155 | Medium | 2021-12-13 | Not applicable | No public exploit | The CPAN::Checksums package 2.12 for Perl does not uniquely define signed data. |
| CVE-2020-16154 | High | 2021-12-13 | Not applicable | No public exploit | The App::cpanminus package 1.7044 for Perl allows Signature Verification Bypass. |
| CVE-2012-1102 | High | 2021-07-09 | Not applicable | No public exploit | It was discovered that the XML::Atom Perl module before version 0.39 did not disable external entities when parsing XML from potentially untrusted sources. This may allow attackers to gain read access to otherwise protected resources, depending on how the library is used. |
| CVE-2021-29424 | High | 2021-04-06 | Not applicable | No public exploit | The Net::Netmask module before 2.0000 for Perl does not properly consider extraneous zero characters at the beginning of an IP address string, which (in some situations) allows attackers to bypass access control that is based on IP addresses. |
| CVE-2021-29662 | High | 2021-03-31 | Outside Waratek scope | No public exploit | The Data::Validate::IP module through 0.29 for Perl does not properly consider extraneous zero characters at the beginning of an IP address string, which (in some situations) allows attackers to bypass access control that is based on IP addresses. |
| CVE-2013-7488 | High | 2020-04-07 | Not applicable | No public exploit | perl-Convert-ASN1 (aka the Convert::ASN1 module for Perl) through 0.27 allows remote attackers to cause an infinite loop via unexpected input. |
| CVE-2014-3230 | Medium | 2020-01-28 | Not applicable | No public exploit | The libwww-perl LWP::Protocol::https module 6.04 through 6.06 for Perl, when using IO::Socket::SSL as the SSL socket class, allows attackers to disable server certificate validation via the (1) HTTPS_CA_DIR or (2) HTTPS_CA_FILE environment variable. |
| CVE-2014-7257 | Critical | 2019-12-11 | Not applicable | No public exploit | SQL injection vulnerability in DBD::PgPP 0.05 and earlier |
| CVE-2013-4184 | Medium | 2019-12-10 | Not applicable | No public exploit | Perl module Data::UUID from CPAN version 1.219 vulnerable to symlink attacks |
| CVE-2011-1933 | Critical | 2019-11-26 | Not applicable | No public exploit | SQL injection vulnerability in Jifty::DBI before 0.68. |
| CVE-2019-1010263 | Critical | 2019-07-17 | Not applicable | No public exploit | Perl Crypt::JWT prior to 0.023 is affected by: Incorrect Access Control. The impact is: allow attackers to bypass authentication by providing a token by crafting with hmac(). The component is: JWT.pm, line 614. The attack vector is: network connectivity. The fixed version is: after commit b98a59b42ded9f9e51b2560410106207c2152d6c. |
| CVE-2019-1010084 | Medium | 2019-07-17 | Not applicable | No public exploit | Dancer::Plugin::SimpleCRUD 1.14 and earlier is affected by: Incorrect Access Control. The impact is: Potential for unathorised access to data. The component is: Incorrect calls to _ensure_auth() wrapper result in authentication-checking not being applied to al routes. |
| CVE-2018-12558 | High | 2018-06-20 | Not applicable | No public exploit | The parse() method in the Email::Address module through 1.909 for Perl is vulnerable to Algorithmic complexity on specially prepared input, leading to Denial of Service. Prepared special input that caused this problem contained 30 form-field characters ("\f"). |
| CVE-2018-12015 | High | 2018-06-07 | Outside Waratek scope | No public exploit | In Perl through 5.26.2, the Archive::Tar module allows remote attackers to bypass a directory-traversal protection mechanism, and overwrite arbitrary files, via an archive file containing a symlink and a regular file with the same name. |
| CVE-2017-6512 | Medium | 2017-06-01 | Not applicable | No public exploit | Race condition in the rmtree and remove_tree functions in the File-Path module before 2.13 for Perl allows attackers to set the mode on arbitrary files via vectors involving directory-permission loosening logic. |
| CVE-2015-8978 | High | 2016-11-22 | Not applicable | No public exploit | In Soap Lite (aka the SOAP::Lite extension for Perl) 1.14 and earlier, an example attack consists of defining 10 or more XML entities, each defined as consisting of 10 of the previous entity, with the document consisting of a single instance of the largest entity, which expands to one billion copies of the first entity. The amount of computer memory used for handling an external SOAP call would likely exceed that available to the process parsing the XML. |
| CVE-2014-1474 | Medium | 2014-07-15 | Not applicable | No public exploit | Algorithmic complexity vulnerability in Email::Address::List before 0.02, as used in RT 4.2.0 through 4.2.2, allows remote attackers to cause a denial of service (CPU consumption) via a string without an address. |
| CVE-2014-4720 | Medium | 2014-07-06 | Not applicable | No public exploit | Email::Address module before 1.904 for Perl uses an inefficient regular expression, which allows remote attackers to cause a denial of service (CPU consumption) via vectors related to "backtracking into the phrase," a different vulnerability than CVE-2014-0477. |
| CVE-2014-0477 | Medium | 2014-07-03 | Not applicable | No public exploit | The parse function in Email::Address module before 1.905 for Perl uses an inefficient regular expression, which allows remote attackers to cause a denial of service (CPU consumption) via an empty quoted string in an RFC 2822 address. |
| CVE-2011-3758 | Medium | 2011-09-23 | Not applicable | No public exploit | ::mound:: 2.1.6 allows remote attackers to obtain sensitive information via a direct request to a .php file, which reveals the installation path in an error message, as demonstrated by lib/smarty/libs/sysplugins/smarty_internal_template.php and certain other files. |
| CVE-2007-4829 | Medium | 2007-11-02 | Not applicable | No public exploit | Directory traversal vulnerability in the Archive::Tar Perl module 1.36 and earlier allows user-assisted remote attackers to overwrite arbitrary files via a TAR archive that contains a file whose name is an absolute path or has ".." sequences. |