WaratekVRT Sign in
Reset
More filters (2)
Columns
Including CVEs outside Waratek scope✕Product caddy✕Has a public PoC✕
Overview 3 matches · 1 in Waratek scope · 0 protected · 2 exploited · 1 CISA KEV · 1 EPSS ≥ 0.5
3matches 1in Waratek scope33.3% 0protected0.0% 2exploited66.7% 1CISA KEV33.3% 1EPSS ≥ 0.533.3%
Protected by Waratek 0 0.0% Rule in development 0 0.0% Mitigation candidate 1 33.3% No exploit published 0 0.0% Outside Waratek scope 0 0.0% Not applicable 2 66.7% Withdrawn CVE 0 0.0%
Critical 0 0.0% High 1 33.3% Medium 2 66.7% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 0 0.0% partly blocked 0 0.0% not blocked 3 100.0% not established 0 0.0% unrecorded 0 0.0%
Exploited 2 66.7% Working exploit published 1 33.3% Proof of concept only 0 0.0% Forecast only 0 0.0% No public exploit 0 0.0%
split by peak 2 / year
Not applicable: 2Mitigation candidate: 1 Medium: 2High: 1 not blocked: 3 Working exploit published: 1Exploited: 2
20171 Not applicable1 Medium1 not blocked1 Exploited1 20180 20190 20200 20210 20220 20232 Mitigation candidate1 Not applicable1 High1 Medium1 not blocked2 Exploited1 Working exploit published1
2017201820192020202120222023
3 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed.
CVE Severity Published▾ Status Exploitation Description
CVE-2023-44487 High 2023-10-10 Mitigation candidate Exploited The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.
CVE-2022-28923 Medium 2023-02-06 Not applicable Working exploit published Caddy v2.4.6 was discovered to contain an open redirection vulnerability which allows attackers to redirect users to phishing websites via crafted URLs.
CVE-2017-5963 Medium 2017-02-12 Not applicable Exploited An issue was discovered in caddy (for TYPO3) before 7.2.10. The vulnerability exists due to insufficient filtration of user-supplied data in the "paymillToken" HTTP POST parameter passed to the "caddy/Resources/Public/JavaScript/e-payment/paymill/api/php/payment.php" URL. An attacker could execute arbitrary HTML and script code in a browser in the context of the vulnerable website.