Overview 7 matches · 0 in Waratek scope · 0 protected · 1 exploited · 0 CISA KEV · 2 public PoC · 1 EPSS ≥ 0.5
7matches
0in Waratek scope0.0%
0protected0.0%
1exploited14.3%
0CISA KEV0.0%
2public PoC28.6%
1EPSS ≥ 0.514.3%
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
0
0.0%
Not applicable
7
100.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
7
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
1
14.3%
Working exploit published
1
14.3%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
5
71.4%
split by
peak 2 / year
20022
Not applicable2
Critical2
not blocked2
Working exploit published1
No public exploit1
20030
20040
20050
20060
20070
20080
20090
20101
Not applicable1
Critical1
not blocked1
No public exploit1
20110
20120
20130
20140
20150
20160
20171
Not applicable1
Critical1
not blocked1
No public exploit1
20180
20190
20200
20210
20220
20232
Not applicable2
Critical2
not blocked2
Exploited1
No public exploit1
20240
20250
20261
Not applicable1
Critical1
not blocked1
No public exploit1
2002200420062008201020122014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-60002 | Critical | 2026-07-08 | Not applicable | No public exploit | ssh in OpenSSH before 10.4 can have a use-after-free when a server changes its host key during a key re-exchange. (This outcome occurs only on the client side.) |
| CVE-2023-38408 | Critical | 2023-07-20 | Not applicable | Exploited | The PKCS#11 feature in ssh-agent in OpenSSH before 9.3p2 has an insufficiently trustworthy search path, leading to remote code execution if an agent is forwarded to an attacker-controlled system. (Code in /usr/lib is not necessarily safe for loading into ssh-agent.) NOTE: this issue exists because of an incomplete fix for CVE-2016-10009. |
| CVE-2023-28531 | Critical | 2023-03-17 | Not applicable | No public exploit | ssh-add in OpenSSH before 9.3 adds smartcard keys to ssh-agent without the intended per-hop destination constraints. The earliest affected version is 8.9. |
| CVE-2016-1908 | Critical | 2017-04-11 | Not applicable | No public exploit | The client in OpenSSH before 7.2 mishandles failed cookie generation for untrusted X11 forwarding and relies on the local X11 server for access-control decisions, which allows remote X11 clients to trigger a fallback and obtain trusted X11 forwarding privileges by leveraging configuration issues on this X11 server, as demonstrated by lack of the SECURITY extension on this X11 server. |
| CVE-2010-4478 | Critical | 2010-12-06 | Not applicable | No public exploit | OpenSSH 5.6 and earlier, when J-PAKE is enabled, does not properly validate the public parameters in the J-PAKE protocol, which allows remote attackers to bypass the need for knowledge of the shared secret, and successfully authenticate, by sending crafted values in each round of the protocol, a related issue to CVE-2010-4252. |
| CVE-2002-0639 | Critical | 2002-07-03 | Not applicable | No public exploit | Integer overflow in sshd in OpenSSH 2.9.9 through 3.3 allows remote attackers to execute arbitrary code during challenge response authentication (ChallengeResponseAuthentication) when OpenSSH is using SKEY or BSD_AUTH authentication. |
| CVE-2002-0083 | Critical | 2002-03-15 | Not applicable | Working exploit published | Off-by-one error in the channel code of OpenSSH 2.0 through 3.0.2 allows local users or remote malicious servers to gain privileges. |