Overview 12 matches · 0 in Waratek scope · 0 protected · 0 exploited · 0 CISA KEV · 1 public PoC · 0 EPSS ≥ 0.5
12matches
0in Waratek scope0.0%
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
1public PoC8.3%
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
0
0.0%
Not applicable
12
100.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
12
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
1
8.3%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
11
91.7%
split by
peak 2 / year
20001
Not applicable1
Low1
not blocked1
Working exploit published1
20010
20020
20030
20040
20050
20062
Not applicable2
Low2
not blocked2
No public exploit2
20070
20081
Not applicable1
Low1
not blocked1
No public exploit1
20090
20100
20110
20122
Not applicable2
Low2
not blocked2
No public exploit2
20130
20140
20150
20160
20171
Not applicable1
Low1
not blocked1
No public exploit1
20180
20190
20201
Not applicable1
Low1
not blocked1
No public exploit1
20210
20220
20231
Not applicable1
Low1
not blocked1
No public exploit1
20241
Not applicable1
Low1
not blocked1
No public exploit1
20251
Not applicable1
Low1
not blocked1
No public exploit1
20261
Not applicable1
Low1
not blocked1
No public exploit1
200220052008201120142017202020232026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-34073 | Low | 2026-03-31 | Not applicable | No public exploit | cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. Prior to version 46.0.6, DNS name constraints were only validated against SANs within child certificates, and not the "peer name" presented during each validation. Consequently, cryptography would allow a peer named bar.example.com to validate against a wildcard leaf certificate for *.example.com, even if the leaf's parent certificate (or upwards) contained an excluded subtree constraint for bar.example.com. This issue has been patched in version 46.0.6. |
| CVE-2024-41760 | Low | 2025-03-11 | Not applicable | No public exploit | IBM Common Cryptographic Architecture 7.0.0 through 7.5.51 could allow an attacker to obtain sensitive information due to a timing attack during certain RSA operations. |
| CVE-2023-33855 | Low | 2024-03-26 | Not applicable | No public exploit | Under certain conditions, RSA operations performed by IBM Common Cryptographic Architecture (CCA) 7.0.0 through 7.5.36 may exhibit non-constant-time behavior. This could allow a remote attacker to obtain sensitive information using a timing-based attack. IBM X-Force ID: 257676. |
| CVE-2023-26084 | Low | 2023-03-15 | Not applicable | No public exploit | The armv8_dec_aes_gcm_full() API of Arm AArch64cryptolib before 86065c6 fails to the verify the authentication tag of AES-GCM protected data, leading to a man-in-the-middle attack. This occurs because of an improperly initialized variable. |
| CVE-2020-8912 | Low | 2020-08-11 | Not applicable | No public exploit | A vulnerability in the in-band key negotiation exists in the AWS S3 Crypto SDK for GoLang versions prior to V2. An attacker with write access to the targeted bucket can change the encryption algorithm of an object in the bucket, which can then allow them to change AES-GCM to AES-CTR. Using this in combination with a decryption oracle can reveal the authentication key used by AES-GCM as decrypting the GMAC tag leaves the authentication key recoverable as an algebraic equation. It is recommended to update your SDK to V2 or later, and re-encrypt your files. |
| CVE-2016-8217 | Low | 2017-02-03 | Not applicable | No public exploit | EMC RSA BSAFE Crypto-J versions prior to 6.2.2 has a PKCS#12 Timing Attack Vulnerability. A possible timing attack could be carried out by modifying a PKCS#12 file that has an integrity MAC for which the password is not known. An attacker could then feed the modified PKCS#12 file to the toolkit and guess the current MAC one byte at a time. This is possible because Crypto-J uses a non-constant-time method to compare the stored MAC with the calculated MAC. This vulnerability is similar to the issue described in CVE-2015-2601. |
| CVE-2012-4454 | Low | 2012-10-10 | Not applicable | No public exploit | openCryptoki before 2.4.1, when using spinlocks, allows local users to create or set world-writable permissions on arbitrary files via a symlink attack on the (1) .pkapi_xpk or (2) .pkcs11spinloc file in /tmp. |
| CVE-2012-3504 | Low | 2012-10-10 | Not applicable | No public exploit | The nssconfigFound function in genkey.pl in crypto-utils 2.4.1-34 allows local users to overwrite arbitrary files via a symlink attack on the "list" file in the current working directory. |
| CVE-2008-3897 | Low | 2008-09-03 | Not applicable | No public exploit | DiskCryptor 0.2.6 on Windows stores pre-boot authentication passwords in the BIOS Keyboard buffer and does not clear this buffer before and after use, which allows local users to obtain sensitive information by reading the physical memory locations associated with this buffer. |
| CVE-2006-6145 | Low | 2006-11-28 | Not applicable | No public exploit | CRYPTOCard CRYPTO-Server before 6.4.56 stores LDAP credentials in plaintext in UninstallerData\installvariables.properties, which has insecure permissions and allows local users to obtain the credentials. NOTE: The provenance of this information is unknown; the details are obtained solely from third party information. |
| CVE-2006-3123 | Low | 2006-08-07 | Not applicable | No public exploit | Multiple integer overflows in the (1) dodecrypt and (2) doencrypt functions in cfs_fh.c in cfsd in Matt Blaze Cryptographic File System (CFS) 1.4.1 before Debian GNU/Linux package 1.4.1-17 allow local users to cause a denial of service (daemon crash) by appending data to a file that is larger than 2 Gb. |
| CVE-2000-0275 | Low | 2000-04-10 | Not applicable | Working exploit published | CRYPTOCard CryptoAdmin for PalmOS uses weak encryption to store a user's PIN number, which allows an attacker with access to the .PDB file to generate valid PT-1 tokens after cracking the PIN. |