Loop with Unreachable Exit Condition ('Infinite Loop') | |
CVE-2024-21147 | |
CVE-2024-21140 | |
Out-of-bounds Read | |
CVE-2024-21131 | |
Improper Input Validation | |
Allocation of Resources Without Limits or Throttling | |
Deserialization of Untrusted Data | |
Integer Overflow or Wraparound | |
Allocation of Resources Without Limits or Throttling | |
Improper Use of Validation Framework | |
Integer Overflow or Wraparound | |
Improper Output Neutralization for Logs | |
Out-of-bounds Write | |
Uncontrolled Memory Allocation | |
Integer Overflow or Wraparound | |
Information Exposure Through Log Files | |
Improper Input Validation | |
Improper Input Validation | |
Improper Input Validation | |
Covert Timing Channel | |
Integer Overflow or Wraparound | |
Improper Certificate Validation | |
Deserialization of Untrusted Data | |
Out-of-bounds Read | |
Directory Traversal | |
Improper Input Validation | |
Improperly Implemented Security Check for Standard | |
Improper Input Validation | |
Improper Neutralization of Null Byte or NUL Character | |
Information Exposure | |
Improper Neutralization of Null Byte or NUL Character | |
Improper Enforcement of Message Integrity During Transmission in a Communication Channel | |
Reliance on File Name or Extension of Externally-Supplied File | |
Deserialization of Untrusted Data | |
Allocation of Resources Without Limits or Throttling | |
Resource Exhaustion | |
Use of Insufficiently Random Values | |
Integer Coercion Error | |
Integer Coercion Error | |
Improper Access Control | |
Resource Leak | |
CVE-2017-10176 | |
Covert Timing Channel | |
Improper Use of Validation Framework | |
Incorrect Behavior Order: Early Validation | |
Integer Underflow | |
Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') | |
Resource Exhaustion | |
Loop with Unreachable Exit Condition ('Infinite Loop') | |
Improper Authorization | |
Allocation of Resources Without Limits or Throttling | |
Improper Use of Validation Framework | |
Uncaught Exception | |
Improper Cross-boundary Removal of Sensitive Data | |
CVE-2015-0437 | |
CVE-2014-6468 | |
CVE-2014-6562 | |
Untrusted Search Path | <1:1.8.0.191.b12-0.el6_10 |
Information Exposure | <1:1.8.0.191.b12-0.el6_10 |
Improper Access Control | <1:1.8.0.191.b12-0.el6_10 |
Improper Certificate Validation | <1:1.8.0.191.b12-0.el6_10 |
Loop with Unreachable Exit Condition ('Infinite Loop') | <1:1.8.0.191.b12-0.el6_10 |
Improper Verification of Cryptographic Signature | <1:1.8.0.191.b12-0.el6_10 |
Improper Access Control | <1:1.8.0.191.b12-0.el6_10 |
Allocation of Resources Without Limits or Throttling | <1:1.8.0.181-3.b13.el6_10 |
Sensitive Information Uncleared Before Release | |
Allocation of Resources Without Limits or Throttling | |
Allocation of Resources Without Limits or Throttling | |
CVE-2018-2814 | |
Allocation of Resources Without Limits or Throttling | |
Deserialization of Untrusted Data | |
CVE-2018-2800 | |
Allocation of Resources Without Limits or Throttling | |
Improper Verification of Cryptographic Signature | |
Allocation of Resources Without Limits or Throttling | |
Allocation of Resources Without Limits or Throttling | |
Allocation of Resources Without Limits or Throttling | |
Unsynchronized Access to Shared Data in a Multithreaded Context | |
Untrusted Search Path | |
Deserialization of Untrusted Data | |
CVE-2018-2582 | |
Improper Access Control | |
Improper Input Validation | |
Use After Free | |
Allocation of Resources Without Limits or Throttling | |
Use of a Broken or Risky Cryptographic Algorithm | |
Use of Insufficiently Random Values | |
Improper Input Validation | |
LDAP Injection | |
Use After Free | |
Allocation of Resources Without Limits or Throttling | |
Allocation of Resources Without Limits or Throttling | |
CVE-2017-10355 | |
Insufficient Verification of Data Authenticity | |
Allocation of Resources Without Limits or Throttling | |
Use of a Broken or Risky Cryptographic Algorithm | |
Allocation of Resources Without Limits or Throttling | |
Allocation of Resources Without Limits or Throttling | |
CVE-2017-10274 | |
Allocation of Resources Without Limits or Throttling | |
CVE-2017-10346 | |
CVE-2017-10285 | |
HTTP Response Splitting | |
Allocation of Resources Without Limits or Throttling | |
Allocation of Resources Without Limits or Throttling | |
CVE-2017-10096 | |
CVE-2017-10090 | |
CVE-2017-10067 | |
Allocation of Resources Without Limits or Throttling | |
CVE-2017-10110 | |
CVE-2017-10101 | |
Covert Timing Channel | |
CVE-2017-10102 | |
CVE-2017-10193 | |
CVE-2017-10107 | |
CVE-2017-10198 | |
CVE-2017-10078 | |
CVE-2017-10116 | |
Allocation of Resources Without Limits or Throttling | |
CVE-2017-10081 | |
CVE-2017-10243 | |
Allocation of Resources Without Limits or Throttling | |
Integer Overflow or Wraparound | |
Out-of-Bounds | |
CVE-2017-10087 | |
CVE-2017-10089 | |
Covert Timing Channel | |
Improper Input Validation | |
Use of a Broken or Risky Cryptographic Algorithm | |
Improper Input Validation | |
Allocation of Resources Without Limits or Throttling | |
Improper Authentication | |
Untrusted Search Path | |
Allocation of Resources Without Limits or Throttling | |
CVE-2017-3272 | |
Information Exposure | |
Integer Overflow or Wraparound | |
CVE-2017-3289 | |
Deserialization of Untrusted Data | |
Improper Input Validation | |
Improper Input Validation | |
Allocation of Resources Without Limits or Throttling | |
Covert Timing Channel | |
Improper Input Validation | |
CVE-2016-5554 | |
Access of Resource Using Incompatible Type ('Type Confusion') | |
Use of a Broken or Risky Cryptographic Algorithm | |
Cleartext Transmission of Sensitive Information | |
Improper Input Validation | |
Out-of-bounds Read | |
Allocation of Resources Without Limits or Throttling | |
CVE-2016-3587 | |
Allocation of Resources Without Limits or Throttling | |
CVE-2016-3458 | |
Integer Overflow or Wraparound | |
CVE-2016-3610 | |
CVE-2016-3606 | |
CVE-2016-3598 | |
CVE-2016-3426 | |
CVE-2016-3427 | |
CVE-2016-0687 | |
CVE-2016-3425 | |
CVE-2016-0686 | |
CVE-2016-0695 | |
Integer Overflow or Wraparound | <1:1.8.0.272.b10-0.el6_10 |
Improperly Implemented Security Check for Standard | |
Improper Certificate Validation | <1:1.8.0.272.b10-0.el6_10 |
Cleartext Transmission of Sensitive Information | <1:1.8.0.272.b10-0.el6_10 |
CVE-2020-14796 | <1:1.8.0.272.b10-0.el6_10 |
Allocation of Resources Without Limits or Throttling | <1:1.8.0.272.b10-0.el6_10 |
Improper Input Validation | <1:1.8.0.272.b10-0.el6_10 |
Improper Data Handling | |
Time-of-check Time-of-use (TOCTOU) | <1:1.8.0.272.b10-0.el6_10 |
Incorrect Conversion between Numeric Types | |
CVE-2016-0402 | |
CVE-2016-0466 | |
CVE-2016-0475 | |
Out-of-bounds Write | |
Information Exposure Through Log Files | |
Out-of-bounds Read | |
CVE-2015-4844 | |
CVE-2015-4883 | |
Information Exposure | |
CVE-2015-4882 | |
CVE-2015-4911 | |
Algorithmic Complexity | |
Information Exposure | |
Incorrect Conversion between Numeric Types | |
CVE-2015-4835 | |
CVE-2015-4868 | |
Allocation of Resources Without Limits or Throttling | |
CVE-2015-4860 | |
Improper Initialization | |
CVE-2015-4881 | |
CVE-2015-4903 | |
Improper Input Validation | |
CVE-2015-4872 | |
Uncaught Exception | <1:1.8.0.262.b10-0.el6_10 |
Uncaught Exception | <1:1.8.0.262.b10-0.el6_10 |
Out-of-Bounds | <1:1.8.0.262.b10-0.el6_10 |
Improper Input Validation | <1:1.8.0.262.b10-0.el6_10 |
CVE-2020-14577 | <1:1.8.0.262.b10-0.el6_10 |
Out-of-Bounds | <1:1.8.0.262.b10-0.el6_10 |
CVE-2020-14556 | <1:1.8.0.262.b10-0.el6_10 |
Improper Certificate Validation | |
Out-of-bounds Write | |
CVE-2015-2621 | |
Improper Check for Certificate Revocation | |
Access of Resource Using Incompatible Type ('Type Confusion') | |
CVE-2015-4733 | |
Missing Release of Resource after Effective Lifetime | |
Covert Timing Channel | |
CVE-2015-2590 | |
Integer Overflow or Wraparound | |
Unsynchronized Access to Shared Data in a Multithreaded Context | |
Insecure Temporary File | |
NULL Pointer Dereference | |
CVE-2015-4731 | |
Use of a Broken or Risky Cryptographic Algorithm | |
Use of a Broken or Risky Cryptographic Algorithm | |
CVE-2015-0470 | |
Directory Traversal | |
Uncaught Exception | |
Off-by-one Error | |
Directory Traversal | |
CVE-2015-0460 | |
CVE-2015-0477 | |
Improperly Implemented Security Check for Standard | |
CVE-2014-6549 | |
Loop with Unreachable Exit Condition ('Infinite Loop') | |
CVE-2014-6593 | |
Out-of-bounds Read | |
CVE-2015-0408 | |
CVE-2015-0407 | |
NULL Pointer Dereference | |
CVE-2015-0395 | |
CVE-2014-6601 | |
Insecure Temporary File | |
CVE-2015-0412 | |
Out-of-bounds Read | |
Not Failing Securely ('Failing Open') | |
CVE-2014-6506 | |
Insufficient Verification of Data Authenticity | |
CVE-2014-6504 | |
CVE-2014-6502 | |
CVE-2014-6511 | |
CVE-2014-6517 | |
CVE-2014-6519 | |
CVE-2014-6531 | |
CVE-2014-6457 | |
CVE-2014-6558 | |
Out-of-Bounds | <1:1.8.0.252.b09-2.el6_10 |
Uncaught Exception | <1:1.8.0.252.b09-2.el6_10 |
Improper Input Validation | <1:1.8.0.252.b09-2.el6_10 |
CVE-2020-2781 | <1:1.8.0.252.b09-2.el6_10 |
Uncaught Exception | <1:1.8.0.252.b09-2.el6_10 |
Uncaught Exception | <1:1.8.0.252.b09-2.el6_10 |
Uncaught Exception | <1:1.8.0.252.b09-2.el6_10 |
HTTP Response Splitting | <1:1.8.0.252.b09-2.el6_10 |
Uncaught Exception | <1:1.8.0.252.b09-2.el6_10 |
Incorrect Regular Expression | <1:1.8.0.252.b09-2.el6_10 |
Allocation of Resources Without Limits or Throttling | <1:1.8.0.242.b07-1.el6_10 |
Use of a Broken or Risky Cryptographic Algorithm | <1:1.8.0.242.b07-1.el6_10 |
Encoding Error | <1:1.8.0.242.b07-1.el6_10 |
Allocation of Resources Without Limits or Throttling | <1:1.8.0.242.b07-1.el6_10 |
Modification of Assumed-Immutable Data (MAID) | <1:1.8.0.242.b07-1.el6_10 |
Improper Input Validation | <1:1.8.0.242.b07-1.el6_10 |
Allocation of Resources Without Limits or Throttling | <1:1.8.0.242.b07-1.el6_10 |
Allocation of Resources Without Limits or Throttling | <1:1.8.0.232.b09-1.el6_10 |
Cross-site Scripting (XSS) | <1:1.8.0.232.b09-1.el6_10 |
Uncaught Exception | <1:1.8.0.232.b09-1.el6_10 |
CVE-2019-2945 | <1:1.8.0.232.b09-1.el6_10 |
Uncaught Exception | <1:1.8.0.232.b09-1.el6_10 |
Uncaught Exception | <1:1.8.0.232.b09-1.el6_10 |
Integer Overflow or Wraparound | <1:1.8.0.232.b09-1.el6_10 |
Uncaught Exception | <1:1.8.0.232.b09-1.el6_10 |
Uncaught Exception | <1:1.8.0.232.b09-1.el6_10 |
CVE-2019-2978 | <1:1.8.0.232.b09-1.el6_10 |
Cross-site Scripting (XSS) | <1:1.8.0.232.b09-1.el6_10 |
Insufficiently Protected Credentials | <1:1.8.0.232.b09-1.el6_10 |
NULL Pointer Dereference | <1:1.8.0.232.b09-1.el6_10 |
Improper Input Validation | <1:1.8.0.232.b09-1.el6_10 |
CVE-2019-2762 | <1:1.8.0.222.b10-0.el6_10 |
Covert Timing Channel | <1:1.8.0.222.b10-0.el6_10 |
Allocation of Resources Without Limits or Throttling | <1:1.8.0.222.b10-0.el6_10 |
Improper Input Validation | <1:1.8.0.222.b10-0.el6_10 |
CVE-2019-2786 | <1:1.8.0.222.b10-0.el6_10 |
Out-of-Bounds | <1:1.8.0.222.b10-0.el6_10 |
Information Exposure | <1:1.8.0.201.b09-1.el6_10 |
Out-of-bounds Write | <1:1.8.0.212.b04-0.el6_10 |
CVE-2019-2684 | <1:1.8.0.212.b04-0.el6_10 |
Allocation of Resources Without Limits or Throttling | <1:1.8.0.212.b04-0.el6_10 |