Overview 295 matches · 12 in Waratek scope · 1 protected · 4 exploited · 0 CISA KEV · 13 public PoC · 1 EPSS ≥ 0.5
295matches
12in Waratek scope4.1%
1protected0.3%
4exploited1.4%
0CISA KEV0.0%
13public PoC4.4%
1EPSS ≥ 0.50.3%
Protected by Waratek
1
0.3%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
11
3.7%
Outside Waratek scope
7
2.4%
Not applicable
276
93.6%
Withdrawn CVE
0
0.0%
blocked by ARMR today
1
0.3%
partly blocked
0
0.0%
not blocked
294
99.7%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 57 / year
20001
Not applicable1
Low1
not blocked1
Working exploit published1
20010
20020
20034
Not applicable4
High3
Medium1
not blocked4
No public exploit4
20043
Not applicable3
High1
Medium2
not blocked3
No public exploit3
20050
20064
Not applicable4
Medium2
Low2
not blocked4
Working exploit published1
No public exploit3
20073
Not applicable3
High1
Medium2
not blocked3
Working exploit published2
No public exploit1
20082
Not applicable2
Medium1
Low1
not blocked2
No public exploit2
20092
No exploit published1
Not applicable1
High1
Medium1
not blocked2
No public exploit2
20100
20111
Not applicable1
High1
not blocked1
No public exploit1
20126
Not applicable6
Medium4
Low2
not blocked6
No public exploit6
20133
No exploit published1
Not applicable2
Medium3
not blocked3
No public exploit3
20141
Not applicable1
High1
not blocked1
No public exploit1
20153
Outside Waratek scope1
Not applicable2
Critical1
Medium2
not blocked3
No public exploit3
20164
Not applicable4
Medium4
not blocked4
No public exploit4
201710
Outside Waratek scope1
Not applicable9
Critical1
High7
Medium1
Low1
not blocked10
No public exploit10
201819
No exploit published1
Outside Waratek scope1
Not applicable17
Critical2
High13
Medium4
not blocked19
No public exploit19
201930
No exploit published2
Outside Waratek scope1
Not applicable27
Critical6
High10
Medium14
not blocked30
Working exploit published2
No public exploit28
202010
Protected by Waratek1
Not applicable9
Critical2
High2
Medium5
Low1
blocked by ARMR today1
not blocked9
Exploited1
No public exploit9
202113
No exploit published1
Outside Waratek scope2
Not applicable10
Critical2
High2
Medium9
not blocked13
No public exploit13
202221
No exploit published4
Not applicable17
Critical12
High4
Medium5
not blocked21
Working exploit published1
No public exploit20
202344
Outside Waratek scope1
Not applicable43
Critical10
High19
Medium14
Low1
not blocked44
Exploited3
Working exploit published2
Proof of concept only10
No public exploit29
202432
Not applicable32
Critical8
High12
Medium11
Low1
not blocked32
Working exploit published1
Proof of concept only7
No public exploit24
202522
No exploit published1
Not applicable21
Critical4
High11
Medium6
Low1
not blocked22
Proof of concept only13
No public exploit9
202657
Not applicable57
Critical10
High27
Medium19
Low1
not blocked57
Proof of concept only17
No public exploit40
200220052008201120142017202020232026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2013-4108 | Critical | 2019-11-14 | Not applicable | No public exploit | Multiple unspecified vulnerabilities in Cryptocat Project Cryptocat 2.0.18 have unknown impact and attack vectors. |
| CVE-2013-4106 | Medium | 2019-11-14 | Not applicable | No public exploit | A Cross-site scripting (XSS) vulnerability exists in Conversation Overview Nickname in Cryptocat before 2.0.22. |
| CVE-2013-4110 | Medium | 2019-11-05 | Not applicable | No public exploit | Cryptocat has an Unspecified Chat Participant User List Disclosure |
| CVE-2013-4107 | Medium | 2019-11-05 | Not applicable | No public exploit | Cryptocat before 2.0.22: cryptocat.js handlePresence() has cross site scripting |
| CVE-2013-4105 | High | 2019-11-04 | Not applicable | No public exploit | Cryptocat before 2.0.22 has Multiparty Encryption Scheme Information Disclosure |
| CVE-2013-4104 | High | 2019-11-04 | Not applicable | No public exploit | Cryptocat before 2.0.22 has weak encryption in the Socialist Millionnaire Protocol |
| CVE-2013-4103 | Critical | 2019-11-04 | Not applicable | Working exploit published | Cryptocat before 2.0.22 has Remote Script Injection due to improperly sanitizing user input |
| CVE-2013-4102 | Critical | 2019-11-04 | Not applicable | No public exploit | Cryptocat before 2.0.22 strophe.js Math.random() Random Number Generator Weakness |
| CVE-2013-4101 | Medium | 2019-11-04 | Not applicable | No public exploit | Cryptocat before 2.0.22 Link Markup Decorator HTML Handling Weakness |
| CVE-2013-4100 | High | 2019-11-04 | Not applicable | No public exploit | Cryptocat before 2.0.22 has Remote Denial of Service via username |
| CVE-2013-2262 | High | 2019-11-04 | Not applicable | No public exploit | Cryptocat strophe.js before 2.0.22 has information disclosure |
| CVE-2013-2261 | High | 2019-11-04 | Not applicable | Working exploit published | Cryptocat before 2.0.22 Chrome Extension 'img/keygen.gif' has Information Disclosure |
| CVE-2013-2260 | Critical | 2019-11-04 | Not applicable | No public exploit | Cryptocat before 2.0.22: Cryptocat.random() Function Array Key has Entropy Weakness |
| CVE-2013-2259 | Critical | 2019-11-04 | Not applicable | No public exploit | Cryptocat before 2.0.22 has Arbitrary Code Execution on Firefox Conversation Overview |
| CVE-2013-2258 | Medium | 2019-11-04 | Not applicable | No public exploit | Cryptocat before 2.0.22 has Nickname User Impersonation |
| CVE-2013-2257 | High | 2019-11-04 | Not applicable | No public exploit | Cryptocat before 2.0.42 has Group Chat ECC Private Key Generation Brute Force Weakness |
| CVE-2019-14823 | High | 2019-10-14 | Not applicable | No public exploit | A flaw was found in the "Leaf and Chain" OCSP policy implementation in JSS' CryptoManager versions after 4.4.6, 4.5.3, 4.6.0, where it implicitly trusted the root certificate of a certificate chain. Applications using this policy may not properly verify the chain and could be vulnerable to attacks such as Man in the Middle. |
| CVE-2019-3733 | Medium | 2019-09-30 | Not applicable | No public exploit | RSA BSAFE Crypto-C Micro Edition, all versions prior to 4.1.4, is vulnerable to three (3) different Improper Clearing of Heap Memory Before Release vulnerability, also known as 'Heap Inspection vulnerability'. A malicious remote user could potentially exploit this vulnerability to extract information leaving data at risk of exposure. |
| CVE-2019-3732 | High | 2019-09-30 | Not applicable | No public exploit | RSA BSAFE Crypto-C Micro Edition, versions prior to 4.0.5.3 (in 4.0.x) and versions prior to 4.1.3.3 (in 4.1.x), and RSA Micro Edition Suite, versions prior to 4.0.11 (in 4.0.x) versions prior to 4.1.6.1 (in 4.1.x) and versions prior to 4.3.3 (4.2.x and 4.3.x) are vulnerable to an Information Exposure Through Timing Discrepancy. A malicious remote user could potentially exploit this vulnerability to extract information leaving data at risk of exposure. |
| CVE-2019-3731 | High | 2019-09-30 | Not applicable | No public exploit | RSA BSAFE Crypto-C Micro Edition versions prior to 4.1.4 and RSA Micro Edition Suite versions prior to 4.4 are vulnerable to an Information Exposure Through Timing Discrepancy. A malicious remote user could potentially exploit this vulnerability to extract information leaving data at risk of exposure. |
| CVE-2019-3728 | High | 2019-09-30 | Not applicable | No public exploit | RSA BSAFE Crypto-C Micro Edition versions from 4.0.0.0 before 4.0.5.4 and from 4.1.0 before 4.1.4, RSA BSAFE Micro Edition Suite versions from 4.0.0 before 4.0.13 and from 4.1.0 before 4.4 and RSA Crypto-C versions from 6.0.0 through 6.4.* are vulnerable to an out-of-bounds read vulnerability when processing DSA signature. A malicious remote user could potentially exploit this vulnerability to cause a crash in the library of the affected system. |
| CVE-2019-16910 | Medium | 2019-09-26 | Not applicable | No public exploit | Arm Mbed TLS before 2.19.0 and Arm Mbed Crypto before 2.0.0, when deterministic ECDSA is enabled, use an RNG with insufficient entropy for blinding, which might allow an attacker to recover a private key via side-channel attacks if a victim signs the same message many times. (For Mbed TLS, the fix is also available in versions 2.7.12 and 2.16.3.) |
| CVE-2019-3740 | Medium | 2019-09-18 | Outside Waratek scope | No public exploit | RSA BSAFE Crypto-J versions prior to 6.2.5 are vulnerable to an Information Exposure Through Timing Discrepancy vulnerabilities during DSA key generation. A malicious remote attacker could potentially exploit those vulnerabilities to recover DSA keys. |
| CVE-2019-3739 | Medium | 2019-09-18 | No exploit published | No public exploit | RSA BSAFE Crypto-J versions prior to 6.2.5 are vulnerable to Information Exposure Through Timing Discrepancy vulnerabilities during ECDSA key generation. A malicious remote attacker could potentially exploit those vulnerabilities to recover ECDSA keys. |
| CVE-2019-3738 | Medium | 2019-09-18 | No exploit published | No public exploit | RSA BSAFE Crypto-J versions prior to 6.2.5 are vulnerable to a Missing Required Cryptographic Step vulnerability. A malicious remote attacker could potentially exploit this vulnerability to coerce two parties into computing the same predictable shared key. |
| CVE-2019-14318 | Medium | 2019-07-30 | Not applicable | No public exploit | Crypto++ 8.3.0 and earlier contains a timing side channel in ECDSA signature generation. This allows a local or remote attacker, able to measure the duration of hundreds to thousands of signing operations, to compute the private key used. The issue occurs because scalar multiplication in ecp.cpp (prime field curves, small leakage) and algebra.cpp (binary field curves, large leakage) is not constant time and leaks the bit length of the scalar among other information. |
| CVE-2019-11841 | Medium | 2019-05-22 | Not applicable | No public exploit | A message-forgery issue was discovered in crypto/openpgp/clearsign/clearsign.go in supplementary Go cryptography libraries 2019-03-25. According to the OpenPGP Message Format specification in RFC 4880 chapter 7, a cleartext signed message can contain one or more optional "Hash" Armor Headers. The "Hash" Armor Header specifies the message digest algorithm(s) used for the signature. However, the Go clearsign package ignores the value of this header, which allows an attacker to spoof it. Consequently, an attacker can lead a victim to believe the signature was generated using a different message digest algorithm than what was actually used. Moreover, since the library skips Armor Header parsing in general, an attacker can not only embed arbitrary Armor Headers, but also prepend arbitrary text to cleartext messages without invalidating the signatures. |
| CVE-2019-11840 | Medium | 2019-05-09 | Not applicable | No public exploit | An issue was discovered in the supplementary Go cryptography library, golang.org/x/crypto, before v0.0.0-20190320223903-b7391e95e576. A flaw was found in the amd64 implementation of the golang.org/x/crypto/salsa20 and golang.org/x/crypto/salsa20/salsa packages. If more than 256 GiB of keystream is generated, or if the counter otherwise grows greater than 32 bits, the amd64 implementation will first generate incorrect output, and then cycle back to previously generated keystream. Repeated keystream bytes can lead to loss of confidentiality in encryption applications, or to predictability in CSPRNG applications. |
| CVE-2019-9115 | Critical | 2019-02-25 | Not applicable | No public exploit | In irisnet-crypto before 1.1.7 for IRISnet, the util/utils.js file allows code execution because of unsafe eval usage. |
| CVE-2018-12975 | High | 2018-09-24 | Not applicable | No public exploit | The random() function of the smart contract implementation for CryptoSaga, an Ethereum game, generates a random value with publicly readable variables such as timestamp, the current block's blockhash, and a private variable (which can be read with a getStorageAt call). Therefore, attackers can precompute the random number and manipulate the game (e.g., get powerful characters or get critical damages). |
| CVE-2018-11058 | Critical | 2018-09-14 | Outside Waratek scope | No public exploit | RSA BSAFE Micro Edition Suite, versions prior to 4.0.11 (in 4.0.x) and prior to 4.1.6 (in 4.1.x), and RSA BSAFE Crypto-C Micro Edition, version prior to 4.0.5.3 (in 4.0.x) contain a Buffer Over-Read vulnerability when parsing ASN.1 data. A remote attacker could use maliciously constructed ASN.1 data that would result in such issue. |
| CVE-2018-11070 | Medium | 2018-09-11 | Not applicable | No public exploit | RSA BSAFE Crypto-J versions prior to 6.2.4 and RSA BSAFE SSL-J versions prior to 6.2.4 contain a Covert Timing Channel vulnerability during PKCS #1 unpadding operations, also known as a Bleichenbacher attack. A remote attacker may be able to recover a RSA key. |
| CVE-2018-11056 | Medium | 2018-08-31 | No exploit published | No public exploit | RSA BSAFE Micro Edition Suite, prior to 4.1.6.1 (in 4.1.x), and RSA BSAFE Crypto-C Micro Edition versions prior to 4.0.5.3 (in 4.0.x) contain an Uncontrolled Resource Consumption ('Resource Exhaustion') vulnerability when parsing ASN.1 data. A remote attacker could use maliciously constructed ASN.1 data that would exhaust the stack, potentially causing a Denial Of Service. |
| CVE-2018-15560 | High | 2018-08-20 | Not applicable | No public exploit | PyCryptodome before 3.6.6 has an integer overflow in the data_len variable in AESNI.c, related to the AESNI_encrypt and AESNI_decrypt functions, leading to the mishandling of messages shorter than 16 bytes. |
| CVE-2018-12885 | Medium | 2018-08-07 | Not applicable | No public exploit | The randMod() function of the smart contract implementation for MyCryptoChamp, an Ethereum game, generates a random value with publicly readable variables such as the current block information and a private variable, (which can be read with a getStorageAt call). Therefore, attackers can get powerful champs/items and get rewards. |
| CVE-2018-13877 | High | 2018-08-06 | Not applicable | No public exploit | The doPayouts() function of the smart contract implementation for MegaCryptoPolis, an Ethereum game, has a Denial of Service vulnerability. If a smart contract that has a fallback function always causing exceptions buys a land, users cannot buy lands near that contract's land, because those purchase attempts will not be completed unless the doPayouts() function successfully sends Ether to certain neighbors. |
| CVE-2018-14715 | High | 2018-08-03 | Not applicable | No public exploit | The endCoinFlip function and throwSlammer function of the smart contract implementations for Cryptogs, an Ethereum game, generate random numbers with an old block's hash. Therefore, attackers can predict the random number and always win the game. |
| CVE-2018-10903 | High | 2018-07-30 | Not applicable | No public exploit | A flaw was found in python-cryptography versions between >=1.9.0 and <2.3. The finalize_with_tag API did not enforce a minimum tag length. If a user did not validate the input length prior to passing it to finalize_with_tag an attacker could craft an invalid payload with a shortened tag (e.g. 1 byte) such that they would have a 1 in 256 chance of passing the MAC check. GCM tag forgeries can cause key leakage. |
| CVE-2018-8319 | Critical | 2018-07-11 | Not applicable | No public exploit | A Security Feature Bypass vulnerability exists in MSR JavaScript Cryptography Library that is caused by incorrect arithmetic computations, aka "MSR JavaScript Cryptography Library Security Feature Bypass Vulnerability." This affects Microsoft Research JavaScript Cryptography Library. |
| CVE-2018-13754 | High | 2018-07-09 | Not applicable | No public exploit | The mintToken function of a smart contract implementation for CryptosisToken, an Ethereum token, has an integer overflow that allows the owner of the contract to set the balance of an arbitrary user to any value. |
| CVE-2018-13541 | High | 2018-07-09 | Not applicable | No public exploit | The mintToken function of a smart contract implementation for CryptoLeu, an Ethereum token, has an integer overflow that allows the owner of the contract to set the balance of an arbitrary user to any value. |
| CVE-2018-13488 | High | 2018-07-09 | Not applicable | No public exploit | The mintToken function of a smart contract implementation for Crypto Alley Shares (CAST), an Ethereum token, has an integer overflow that allows the owner of the contract to set the balance of an arbitrary user to any value. |
| CVE-2018-13210 | High | 2018-07-05 | Not applicable | No public exploit | The sell function of a smart contract implementation for Providence Crypto Casino (PVE) (Contract Name: ProvidenceCasinoToken), an Ethereum token, has an integer overflow in which "amount * sellPrice" can be zero, consequently reducing a seller's assets. |
| CVE-2018-13174 | High | 2018-07-05 | Not applicable | No public exploit | The mintToken function of a smart contract implementation for CryptoABS (ABS), an Ethereum token, has an integer overflow that allows the owner of the contract to set the balance of an arbitrary user to any value. |
| CVE-2018-13157 | High | 2018-07-05 | Not applicable | No public exploit | The mintToken function of a smart contract implementation for CryptonitexCoin, an Ethereum token, has an integer overflow that allows the owner of the contract to set the balance of an arbitrary user to any value. |
| CVE-2018-3691 | Medium | 2018-06-05 | Not applicable | No public exploit | Some implementations in Intel Integrated Performance Primitives Cryptography Library before version 2018 U3.1 do not properly ensure constant execution time. |
| CVE-2018-1000093 | High | 2018-03-13 | Not applicable | No public exploit | CryptoNote version version 0.8.9 and possibly later contain a local RPC server which does not require authentication, as a result the walletd and the simplewallet RPC daemons will process any commands sent to them, resulting in remote command execution and a takeover of the cryptocurrency wallet if an attacker can trick an application such as a web browser into connecting and sending a command for example. This attack appears to be exploitable via a victim visiting a webpage hosting malicious content that trigger such behavior. |
| CVE-2018-6594 | High | 2018-02-03 | Not applicable | No public exploit | lib/Crypto/PublicKey/ElGamal.py in PyCrypto through 2.6.1 generates weak ElGamal key parameters, which allows attackers to obtain sensitive information by reading ciphertext data (i.e., it does not have semantic security in face of a ciphertext-only attack). The Decisional Diffie-Hellman (DDH) assumption does not hold for PyCrypto's ElGamal implementation. |
| CVE-2017-9434 | Medium | 2017-06-05 | Not applicable | No public exploit | Crypto++ (aka cryptopp) through 5.6.5 contains an out-of-bounds read vulnerability in zinflate.cpp in the Inflator filter. |
| CVE-2017-3204 | High | 2017-04-04 | Not applicable | No public exploit | The Go SSH library (x/crypto/ssh) by default does not verify host keys, facilitating man-in-the-middle attacks. Default behavior changed in commit e4e2799 to require explicitly registering a hostkey verification mechanism. |
| CVE-2016-9243 | High | 2017-03-27 | Not applicable | No public exploit | HKDF in cryptography before 1.5.2 returns an empty byte-string if used with a length less than algorithm.digest_size. |
| CVE-2017-5682 | High | 2017-02-28 | Outside Waratek scope | No public exploit | Intel PSET Application Install wrapper of Intel Parallel Studio XE, Intel System Studio, Intel VTune Amplifier, Intel Inspector, Intel Advisor, Intel MPI Library, Intel Trace Analyzer and Collector, Intel Integrated Performance Primitives, Cryptography for Intel Integrated Performance Primitives, Intel Math Kernel Library, Intel Data Analytics Acceleration Library, and Intel Threading Building Blocks before 2017 Update 2 allows an attacker to launch a process with escalated privileges. |
| CVE-2013-7459 | Critical | 2017-02-15 | Not applicable | No public exploit | Heap-based buffer overflow in the ALGnew function in block_templace.c in Python Cryptography Toolkit (aka pycrypto) allows remote attackers to execute arbitrary code as demonstrated by a crafted iv parameter to cryptmsg.py. |
| CVE-2016-3995 | High | 2017-02-13 | Not applicable | No public exploit | The timing attack protection in Rijndael::Enc::ProcessAndXorBlock and Rijndael::Dec::ProcessAndXorBlock in Crypto++ (aka cryptopp) before 5.6.4 may be optimized out by the compiler, which allows attackers to conduct timing attacks. |
| 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-2016-8212 | High | 2017-02-03 | Not applicable | No public exploit | An issue was discovered in EMC RSA BSAFE Crypto-J versions prior to 6.2.2. There is an Improper OCSP Validation Vulnerability. OCSP responses have two time values: thisUpdate and nextUpdate. These specify a validity period; however, both values are optional. Crypto-J treats the lack of a nextUpdate as indicating that the OCSP response is valid indefinitely instead of restricting its validity for a brief period surrounding the thisUpdate time. This vulnerability is similar to the issue described in CVE-2015-4748. |
| CVE-2016-9939 | High | 2017-01-30 | Not applicable | No public exploit | Crypto++ (aka cryptopp and libcrypto++) 5.6.4 contained a bug in its ASN.1 BER decoding routine. The library will allocate a memory block based on the length field of the ASN.1 object. If there is not enough content octets in the ASN.1 object, then the function will fail and the memory block will be zeroed even if its unused. There is a noticeable delay during the wipe for a large allocation. |
| CVE-2016-7544 | High | 2017-01-30 | Not applicable | No public exploit | Crypto++ 5.6.4 incorrectly uses Microsoft's stack-based _malloca and _freea functions. The library will request a block of memory to align a table in memory. If the table is later reallocated, then the wrong pointer could be freed. |
| CVE-2016-4407 | Medium | 2016-10-13 | Not applicable | No public exploit | The DSA algorithm implementation in SAP SAPCRYPTOLIB 5.555.38 does not properly check signatures, which allows remote authenticated users to impersonate arbitrary users via unspecified vectors, aka SAP Security Note 2223008. |
| CVE-2016-7420 | Medium | 2016-09-16 | Not applicable | No public exploit | Crypto++ (aka cryptopp) through 5.6.4 does not document the requirement for a compile-time NDEBUG definition disabling the many assert calls that are unintended in production use, which might allow context-dependent attackers to obtain sensitive information by leveraging access to process memory after an assertion failure, as demonstrated by reading a core dump. |
| CVE-2016-6298 | Medium | 2016-09-01 | Not applicable | No public exploit | The _Rsa15 class in the RSA 1.5 algorithm implementation in jwa.py in jwcrypto before 0.3.2 lacks the Random Filling protection mechanism, which makes it easier for remote attackers to obtain cleartext data via a Million Message Attack (MMA). |
| CVE-2016-0887 | Medium | 2016-04-12 | Not applicable | No public exploit | EMC RSA BSAFE Micro Edition Suite (MES) 4.0.x and 4.1.x before 4.1.5, RSA BSAFE Crypto-C Micro Edition (CCME) 4.0.x and 4.1.x before 4.1.3, RSA BSAFE Crypto-J before 6.2.1, RSA BSAFE SSL-J before 6.2.1, and RSA BSAFE SSL-C before 2.8.9 allow remote attackers to discover a private-key prime by conducting a Lenstra side-channel attack that leverages an application's failure to detect an RSA signature failure during a TLS session. |
| CVE-2015-7940 | Medium | 2015-11-09 | Outside Waratek scope | No public exploit | The Bouncy Castle Java library before 1.51 does not validate a point is withing the elliptic curve, which makes it easier for remote attackers to obtain private keys via a series of crafted elliptic curve Diffie Hellman (ECDH) key exchanges, aka an "invalid curve attack." |
| CVE-2015-0537 | Critical | 2015-08-20 | Not applicable | No public exploit | Integer underflow in the base64-decoding implementation in EMC RSA BSAFE Micro Edition Suite (MES) 4.0.x before 4.0.8 and 4.1.x before 4.1.3, RSA BSAFE Crypto-C Micro Edition (Crypto-C ME) before 4.0.4 and 4.1, and RSA BSAFE SSL-C 2.8.9 and earlier allows remote attackers to cause a denial of service (memory corruption or segmentation fault) or possibly have unspecified other impact via crafted base64 data, a similar issue to CVE-2015-0292. |
| CVE-2015-2141 | Medium | 2015-07-01 | Not applicable | No public exploit | The InvertibleRWFunction::CalculateInverse function in rw.cpp in libcrypt++ 5.6.2 does not properly blind private key operations for the Rabin-Williams digital signature algorithm, which allows remote attackers to obtain private keys via a timing attack. |
| CVE-2014-8587 | High | 2014-11-04 | Not applicable | No public exploit | SAPCRYPTOLIB before 5.555.38, SAPSECULIB, and CommonCryptoLib before 8.4.30, as used in SAP NetWeaver AS for ABAP and SAP HANA, allows remote attackers to spoof Digital Signature Algorithm (DSA) signatures via unspecified vectors. |
| CVE-2013-1445 | Medium | 2013-10-26 | Not applicable | No public exploit | The Crypto.Random.atfork function in PyCrypto before 2.6.1 does not properly reseed the pseudo-random number generator (PRNG) before allowing a child process to access it, which makes it easier for context-dependent attackers to obtain sensitive information by leveraging a race condition in which a child process is created and accesses the PRNG within the same rate-limit period as another process. |
| CVE-2007-6755 | Medium | 2013-10-11 | Not applicable | No public exploit | The NIST SP 800-90A default statement of the Dual Elliptic Curve Deterministic Random Bit Generation (Dual_EC_DRBG) algorithm contains point Q constants with a possible relationship to certain "skeleton key" values, which might allow context-dependent attackers to defeat cryptographic protection mechanisms by leveraging knowledge of those values. NOTE: this is a preliminary CVE for Dual_EC_DRBG; future research may provide additional details about point Q and associated attacks, and could potentially lead to a RECAST or REJECT of this CVE. |
| CVE-2013-1624 | Medium | 2013-02-08 | No exploit published | No public exploit | The TLS implementation in the Bouncy Castle Java library before 1.48 and C# library before 1.8 does not properly consider timing side-channel attacks on a noncompliant MAC check operation during the processing of malformed CBC padding, which allows remote attackers to conduct distinguishing attacks and plaintext-recovery attacks via statistical analysis of timing data for crafted packets, a related issue to CVE-2013-0169. |
| CVE-2012-4455 | Medium | 2012-10-10 | Not applicable | No public exploit | openCryptoki 2.4.1 allows local users to create or set world-writable permissions on arbitrary files via a symlink attack on the (1) LCK..opencryptoki or (2) LCK..opencryptoki_stdll file in /var/lock/. |
| 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-2010-5249 | Medium | 2012-09-07 | Not applicable | No public exploit | Untrusted search path vulnerability in Sophos Free Encryption 2.40.1.1 and Sophos SafeGuard PrivateCrypto 2.40.1.2 allows local users to gain privileges via a Trojan horse pcrypt0406.dll file in the current working directory, as demonstrated by a directory that contains a .uti file. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information. |
| CVE-2012-2417 | Medium | 2012-06-17 | Not applicable | No public exploit | PyCrypto before 2.6 does not produce appropriate prime numbers when using an ElGamal scheme to generate a key, which reduces the signature space or public key space and makes it easier for attackers to conduct brute force attacks to obtain the private key. |
| CVE-2012-2943 | Medium | 2012-05-27 | Not applicable | No public exploit | CRLF injection vulnerability in cryptographp.inc.php in Cryptographp allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via the cfg parameter. |
| CVE-2011-0766 | High | 2011-05-31 | Not applicable | No public exploit | The random number generator in the Crypto application before 2.0.2.2, and SSH before 2.0.5, as used in the Erlang/OTP ssh library before R14B03, uses predictable seeds based on the current time, which makes it easier for remote attackers to guess DSA host and SSH session keys. |
| CVE-2007-6721 | High | 2009-03-30 | No exploit published | No public exploit | The Legion of the Bouncy Castle Java Cryptography API before release 1.38, as used in Crypto Provider Package before 1.36, has unknown impact and remote attack vectors related to "a Bleichenbacher vulnerability in simple RSA CMS signatures without signed attributes." |
| CVE-2009-0127 | Medium | 2009-01-15 | Not applicable | No public exploit | M2Crypto does not properly check the return value from the OpenSSL EVP_VerifyFinal, DSA_verify, ECDSA_verify, DSA_do_verify, and ECDSA_do_verify functions, which might allow remote attackers to bypass validation of the certificate chain via a malformed SSL/TLS signature, a similar vulnerability to CVE-2008-5077. NOTE: a Linux vendor disputes the relevance of this report to the M2Crypto product because "these functions are not used anywhere in m2crypto. |
| 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-2008-0203 | Medium | 2008-01-10 | Not applicable | No public exploit | Multiple cross-site scripting (XSS) vulnerabilities in cryptographp/admin.php in the Cryptographp 1.2 and earlier plugin for WordPress allow remote attackers to inject arbitrary web script or HTML via the (1) cryptwidth, (2) cryptheight, (3) bgimg, (4) charR, (5) charG, (6) charB, (7) charclear, (8) tfont, (9) charel, (10) charelc, (11) charelv, (12) charnbmin, (13) charnbmax, (14) charspace, (15) charsizemin, (16) charsizemax, (17) charanglemax, (18) noisepxmin, (19) noisepxmax, (20) noiselinemin, (21) noiselinemax, (22) nbcirclemin, (23) nbcirclemax, or (24) brushsize parameter to wp-admin/options-general.php. |
| CVE-2007-4903 | High | 2007-09-17 | Not applicable | Working exploit published | Multiple buffer overflows in a certain ActiveX control in CryptoX.dll 2.0 and earlier in the Ultra Crypto Component allow remote attackers to execute arbitrary code via (1) a long string in the first argument to the AcquireContext method or (2) an unspecified vector to the DeleteContext method. |
| CVE-2007-4902 | Medium | 2007-09-17 | Not applicable | Working exploit published | Absolute path traversal vulnerability in a certain ActiveX control in CryptoX.dll 2.0 and earlier in the Ultra Crypto Component allows remote attackers to write to arbitrary files via a full pathname in the argument to the SaveToFile method. |
| CVE-2006-3894 | Medium | 2007-05-22 | Not applicable | No public exploit | The RSA Crypto-C before 6.3.1 and Cert-C before 2.8 libraries, as used by RSA BSAFE, multiple Cisco products, and other products, allows remote attackers to cause a denial of service via malformed ASN.1 objects. |
| CVE-2006-3896 | Medium | 2006-12-19 | Not applicable | No public exploit | The NeoScale Systems CryptoStor 700 series appliance before 2.6 relies on client-side ActiveX code for smartcard authentication, which allows remote attackers to bypass smartcard authentication, and gain access if able to present a valid username and password, by disabling ActiveX. |
| 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-2006-1172 | Medium | 2006-05-09 | Not applicable | Working exploit published | Stack-based buffer overflow in the createPKCS10 function in Cryptomathic Cenroll ActiveX Control 1.1.0.0 allows remote attackers to execute arbitrary code via vectors related to the TDC Digital signature. |
| CVE-2004-0112 | Medium | 2004-11-23 | Not applicable | No public exploit | The SSL/TLS handshaking code in OpenSSL 0.9.7a, 0.9.7b, and 0.9.7c, when using Kerberos ciphersuites, does not properly check the length of Kerberos tickets during a handshake, which allows remote attackers to cause a denial of service (crash) via a crafted SSL/TLS handshake that causes an out-of-bounds read. |
| CVE-2004-0081 | Medium | 2004-11-23 | Not applicable | No public exploit | OpenSSL 0.9.6 before 0.9.6d does not properly handle unknown message types, which allows remote attackers to cause a denial of service (infinite loop), as demonstrated using the Codenomicon TLS Test Tool. |
| CVE-2004-0079 | High | 2004-11-23 | Not applicable | No public exploit | The do_change_cipher_spec function in OpenSSL 0.9.6c to 0.9.6k, and 0.9.7a to 0.9.7c, allows remote attackers to cause a denial of service (crash) via a crafted SSL/TLS handshake that triggers a null dereference. |
| CVE-2003-1392 | Medium | 2003-12-31 | Not applicable | No public exploit | CryptoBuddy 1.0 and 1.2 does not use the user-supplied passphrase to encrypt data, which could allow local users to use their own passphrase to decrypt the data. |
| CVE-2003-1391 | High | 2003-12-31 | Not applicable | No public exploit | RTS CryptoBuddy 1.0 and 1.2 uses a weak encryption algorithm for the passphrase and generates predictable keys, which makes it easier for attackers to guess the passphrase. |
| CVE-2003-1390 | High | 2003-12-31 | Not applicable | No public exploit | RTS CryptoBuddy 1.2 and earlier stores bytes 53 through 55 of a 55-byte passphrase in plaintext, which makes it easier for local users to guess the passphrase. |
| CVE-2003-1389 | High | 2003-12-31 | Not applicable | No public exploit | RTS CryptoBuddy 1.2 and earlier truncates long passphrases without warning the user, which may make it easier to conduct certain brute force guessing attacks. |
| 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. |