| CVE-2025-53066 | |
| Inappropriate Encoding for Output Context | |
| Information Exposure | |
| Heap-based Buffer Overflow | |
| Missing Required Cryptographic Step | |
| Heap-based Buffer Overflow | |
| CVE-2025-30761 | |
| Heap-based Buffer Overflow | |
| Buffer Overflow | |
| Information Exposure | |
| Signed to Unsigned Conversion Error | |
| Uncontrolled Memory Allocation | |
| Signed to Unsigned Conversion Error | |
| Integer Overflow or Wraparound | |
| Improper Handling of Length Parameter Inconsistency | |
| Improper Input Validation | |
| CVE-2024-21131 | |
| CVE-2024-21140 | |
| Out-of-bounds Read | |
| Loop with Unreachable Exit Condition ('Infinite Loop') | |
| Integer Overflow or Wraparound | |
| Allocation of Resources Without Limits or Throttling | |
| Integer Overflow or Wraparound | |
| Allocation of Resources Without Limits or Throttling | |
| Deserialization of Untrusted Data | |
| Improper Use of Validation Framework | |
| Improper Output Neutralization for Logs | |
| Out-of-bounds Write | |
| Uncontrolled Memory Allocation | |
| Integer Overflow or Wraparound | |
| Improper Input Validation | |
| Covert Timing Channel | |
| Improper Input Validation | |
| Information Exposure Through Log Files | |
| Improper Input Validation | |
| 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 | |
| CVE-2015-2596 | |
| 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 | |
| Untrusted Search Path | <1:1.7.0.201-2.6.16.1.el7_6 |
| Information Exposure | <1:1.7.0.201-2.6.16.1.el7_6 |
| Improper Access Control | <1:1.7.0.201-2.6.16.1.el7_6 |
| Improper Certificate Validation | <1:1.7.0.201-2.6.16.1.el7_6 |
| Loop with Unreachable Exit Condition ('Infinite Loop') | <1:1.7.0.201-2.6.16.1.el7_6 |
| Improper Verification of Cryptographic Signature | <1:1.7.0.201-2.6.16.1.el7_6 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.191-2.6.15.4.el7_5 |
| Sensitive Information Uncleared Before Release | <1:1.7.0.181-2.6.14.8.el7_5 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.181-2.6.14.5.el7 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.181-2.6.14.5.el7 |
| CVE-2018-2814 | <1:1.7.0.181-2.6.14.5.el7 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.181-2.6.14.5.el7 |
| Deserialization of Untrusted Data | <1:1.7.0.181-2.6.14.5.el7 |
| CVE-2018-2800 | <1:1.7.0.181-2.6.14.5.el7 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.181-2.6.14.5.el7 |
| Improper Verification of Cryptographic Signature | <1:1.7.0.181-2.6.14.5.el7 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.181-2.6.14.5.el7 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.181-2.6.14.5.el7 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.171-2.6.13.0.el7_4 |
| Unsynchronized Access to Shared Data in a Multithreaded Context | <1:1.7.0.171-2.6.13.0.el7_4 |
| Untrusted Search Path | <1:1.7.0.171-2.6.13.0.el7_4 |
| Deserialization of Untrusted Data | <1:1.7.0.171-2.6.13.0.el7_4 |
| Improper Access Control | <1:1.7.0.171-2.6.13.0.el7_4 |
| Improper Input Validation | <1:1.7.0.171-2.6.13.0.el7_4 |
| Use After Free | <1:1.7.0.171-2.6.13.0.el7_4 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.171-2.6.13.0.el7_4 |
| Use of a Broken or Risky Cryptographic Algorithm | <1:1.7.0.171-2.6.13.0.el7_4 |
| Use of Insufficiently Random Values | <1:1.7.0.171-2.6.13.0.el7_4 |
| Improper Input Validation | <1:1.7.0.171-2.6.13.0.el7_4 |
| LDAP Injection | <1:1.7.0.171-2.6.13.0.el7_4 |
| Use After Free | <1:1.7.0.171-2.6.13.0.el7_4 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.171-2.6.13.0.el7_4 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.161-2.6.12.0.el7_4 |
| CVE-2017-10355 | <1:1.7.0.161-2.6.12.0.el7_4 |
| Insufficient Verification of Data Authenticity | <1:1.7.0.161-2.6.12.0.el7_4 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.161-2.6.12.0.el7_4 |
| Use of a Broken or Risky Cryptographic Algorithm | <1:1.7.0.161-2.6.12.0.el7_4 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.161-2.6.12.0.el7_4 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.161-2.6.12.0.el7_4 |
| CVE-2017-10274 | <1:1.7.0.161-2.6.12.0.el7_4 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.161-2.6.12.0.el7_4 |
| CVE-2017-10346 | <1:1.7.0.161-2.6.12.0.el7_4 |
| CVE-2017-10285 | <1:1.7.0.161-2.6.12.0.el7_4 |
| HTTP Response Splitting | <1:1.7.0.161-2.6.12.0.el7_4 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.161-2.6.12.0.el7_4 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.161-2.6.12.0.el7_4 |
| CVE-2017-10096 | <1:1.7.0.151-2.6.11.1.el7_4 |
| CVE-2017-10090 | <1:1.7.0.151-2.6.11.1.el7_4 |
| CVE-2017-10067 | <1:1.7.0.151-2.6.11.1.el7_4 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.151-2.6.11.1.el7_4 |
| CVE-2017-10110 | <1:1.7.0.151-2.6.11.1.el7_4 |
| CVE-2017-10101 | <1:1.7.0.151-2.6.11.1.el7_4 |
| Covert Timing Channel | <1:1.7.0.151-2.6.11.1.el7_4 |
| CVE-2017-10102 | <1:1.7.0.151-2.6.11.1.el7_4 |
| CVE-2017-10193 | <1:1.7.0.161-2.6.12.0.el7_4 |
| CVE-2017-10107 | <1:1.7.0.151-2.6.11.1.el7_4 |
| CVE-2017-10198 | <1:1.7.0.161-2.6.12.0.el7_4 |
| CVE-2017-10116 | <1:1.7.0.151-2.6.11.1.el7_4 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.151-2.6.11.1.el7_4 |
| CVE-2017-10081 | <1:1.7.0.151-2.6.11.1.el7_4 |
| CVE-2017-10243 | <1:1.7.0.151-2.6.11.1.el7_4 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.151-2.6.11.1.el7_4 |
| Integer Overflow or Wraparound | <1:1.7.0.151-2.6.11.1.el7_4 |
| CVE-2017-10087 | <1:1.7.0.151-2.6.11.1.el7_4 |
| CVE-2017-10089 | <1:1.7.0.151-2.6.11.1.el7_4 |
| Covert Timing Channel | <1:1.7.0.151-2.6.11.1.el7_4 |
| Improper Input Validation | <1:1.7.0.141-2.6.10.1.el7_3 |
| Use of a Broken or Risky Cryptographic Algorithm | <1:1.7.0.141-2.6.10.1.el7_3 |
| Improper Input Validation | <1:1.7.0.141-2.6.10.1.el7_3 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.141-2.6.10.1.el7_3 |
| Improper Authentication | <1:1.7.0.141-2.6.10.1.el7_3 |
| Untrusted Search Path | <1:1.7.0.141-2.6.10.1.el7_3 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.131-2.6.9.0.el7_3 |
| CVE-2017-3272 | <1:1.7.0.131-2.6.9.0.el7_3 |
| Information Exposure | <1:1.7.0.131-2.6.9.0.el7_3 |
| Integer Overflow or Wraparound | <1:1.7.0.131-2.6.9.0.el7_3 |
| CVE-2017-3289 | <1:1.7.0.131-2.6.9.0.el7_3 |
| Deserialization of Untrusted Data | <1:1.7.0.131-2.6.9.0.el7_3 |
| Improper Input Validation | <1:1.7.0.131-2.6.9.0.el7_3 |
| Improper Input Validation | <1:1.7.0.131-2.6.9.0.el7_3 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.131-2.6.9.0.el7_3 |
| Covert Timing Channel | <1:1.7.0.131-2.6.9.0.el7_3 |
| Improper Input Validation | <1:1.7.0.131-2.6.9.0.el7_3 |
| CVE-2016-5554 | <1:1.7.0.121-2.6.8.0.el7_3 |
| Access of Resource Using Incompatible Type ('Type Confusion') | <1:1.7.0.121-2.6.8.0.el7_3 |
| Use of a Broken or Risky Cryptographic Algorithm | <1:1.7.0.121-2.6.8.0.el7_3 |
| Cleartext Transmission of Sensitive Information | <1:1.7.0.121-2.6.8.0.el7_3 |
| Improper Input Validation | <1:1.7.0.121-2.6.8.0.el7_3 |
| Out-of-bounds Read | <1:1.7.0.121-2.6.8.0.el7_3 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.111-2.6.7.2.el7_2 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.111-2.6.7.2.el7_2 |
| CVE-2016-3458 | <1:1.7.0.111-2.6.7.2.el7_2 |
| Integer Overflow or Wraparound | <1:1.7.0.111-2.6.7.2.el7_2 |
| CVE-2016-3610 | <1:1.7.0.111-2.6.7.2.el7_2 |
| CVE-2016-3606 | <1:1.7.0.111-2.6.7.2.el7_2 |
| CVE-2016-3598 | <1:1.7.0.111-2.6.7.2.el7_2 |
| CVE-2016-3427 | <1:1.7.0.101-2.6.6.1.el7_2 |
| CVE-2016-0687 | <1:1.7.0.101-2.6.6.1.el7_2 |
| CVE-2016-3425 | <1:1.7.0.101-2.6.6.1.el7_2 |
| CVE-2016-0686 | <1:1.7.0.101-2.6.6.1.el7_2 |
| CVE-2016-0695 | <1:1.7.0.101-2.6.6.1.el7_2 |
| Improperly Implemented Security Check for Standard | <1:1.7.0.99-2.6.5.0.el7_2 |
| Improper Data Handling | <1:1.7.0.95-2.6.4.0.el7_2 |
| Incorrect Conversion between Numeric Types | <1:1.7.0.95-2.6.4.0.el7_2 |
| CVE-2016-0402 | <1:1.7.0.95-2.6.4.0.el7_2 |
| CVE-2016-0466 | <1:1.7.0.95-2.6.4.0.el7_2 |
| Out-of-bounds Write | <1:1.7.0.95-2.6.4.0.el7_2 |
| Information Exposure Through Log Files | <1:1.7.0.95-2.6.4.0.el7_2 |
| CVE-2015-4871 | <1:1.7.0.95-2.6.4.0.el7_2 |
| Out-of-bounds Read | <1:1.7.0.91-2.6.2.1.el7_1 |
| CVE-2015-4844 | <1:1.7.0.91-2.6.2.1.el7_1 |
| CVE-2015-4883 | <1:1.7.0.91-2.6.2.1.el7_1 |
| Information Exposure | <1:1.7.0.91-2.6.2.1.el7_1 |
| CVE-2015-4882 | <1:1.7.0.91-2.6.2.1.el7_1 |
| CVE-2015-4911 | <1:1.7.0.91-2.6.2.1.el7_1 |
| Algorithmic Complexity | <1:1.7.0.91-2.6.2.1.el7_1 |
| Information Exposure | <1:1.7.0.91-2.6.2.1.el7_1 |
| Incorrect Conversion between Numeric Types | <1:1.7.0.91-2.6.2.1.el7_1 |
| CVE-2015-4835 | <1:1.7.0.91-2.6.2.1.el7_1 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.91-2.6.2.1.el7_1 |
| CVE-2015-4860 | <1:1.7.0.91-2.6.2.1.el7_1 |
| Improper Initialization | <1:1.7.0.91-2.6.2.1.el7_1 |
| CVE-2015-4881 | <1:1.7.0.91-2.6.2.1.el7_1 |
| CVE-2015-4903 | <1:1.7.0.91-2.6.2.1.el7_1 |
| Improper Input Validation | <1:1.7.0.91-2.6.2.1.el7_1 |
| CVE-2015-4872 | <1:1.7.0.91-2.6.2.1.el7_1 |
| Improper Certificate Validation | <1:1.7.0.85-2.6.1.2.el7_1 |
| Out-of-bounds Write | <1:1.7.0.85-2.6.1.2.el7_1 |
| CVE-2015-2621 | <1:1.7.0.85-2.6.1.2.el7_1 |
| Improper Check for Certificate Revocation | <1:1.7.0.85-2.6.1.2.el7_1 |
| Access of Resource Using Incompatible Type ('Type Confusion') | <1:1.7.0.85-2.6.1.2.el7_1 |
| CVE-2015-4733 | <1:1.7.0.85-2.6.1.2.el7_1 |
| Missing Release of Resource after Effective Lifetime | <1:1.7.0.85-2.6.1.2.el7_1 |
| Covert Timing Channel | <1:1.7.0.85-2.6.1.2.el7_1 |
| CVE-2015-2590 | <1:1.7.0.85-2.6.1.2.el7_1 |
| Integer Overflow or Wraparound | <1:1.7.0.85-2.6.1.2.el7_1 |
| Unsynchronized Access to Shared Data in a Multithreaded Context | <1:1.7.0.85-2.6.1.2.el7_1 |
| CVE-2015-4731 | <1:1.7.0.85-2.6.1.2.el7_1 |
| Use of a Broken or Risky Cryptographic Algorithm | <1:1.7.0.85-2.6.1.2.el7_1 |
| Use of a Broken or Risky Cryptographic Algorithm | <1:1.7.0.85-2.6.1.2.el7_1 |
| Directory Traversal | <1:1.7.0.79-2.5.5.1.el7_1 |
| Uncaught Exception | <1:1.7.0.79-2.5.5.1.el7_1 |
| Off-by-one Error | <1:1.7.0.79-2.5.5.1.el7_1 |
| Directory Traversal | <1:1.7.0.79-2.5.5.1.el7_1 |
| CVE-2015-0460 | <1:1.7.0.79-2.5.5.1.el7_1 |
| CVE-2015-0477 | <1:1.7.0.79-2.5.5.1.el7_1 |
| Improperly Implemented Security Check for Standard | <1:1.7.0.79-2.5.5.1.el7_1 |
| Loop with Unreachable Exit Condition ('Infinite Loop') | <1:1.7.0.75-2.5.4.2.el7_0 |
| CVE-2014-6593 | <1:1.7.0.75-2.5.4.2.el7_0 |
| Out-of-bounds Read | <1:1.7.0.75-2.5.4.2.el7_0 |
| CVE-2015-0408 | <1:1.7.0.75-2.5.4.2.el7_0 |
| CVE-2015-0407 | <1:1.7.0.75-2.5.4.2.el7_0 |
| NULL Pointer Dereference | <1:1.7.0.75-2.5.4.2.el7_0 |
| CVE-2015-0395 | <1:1.7.0.75-2.5.4.2.el7_0 |
| CVE-2014-6601 | <1:1.7.0.75-2.5.4.2.el7_0 |
| Insecure Temporary File | <1:1.7.0.75-2.5.4.2.el7_0 |
| CVE-2015-0412 | <1:1.7.0.75-2.5.4.2.el7_0 |
| Out-of-bounds Read | <1:1.7.0.75-2.5.4.2.el7_0 |
| Not Failing Securely ('Failing Open') | <1:1.7.0.75-2.5.4.2.el7_0 |
| CVE-2014-6506 | <1:1.7.0.71-2.5.3.1.el7_0 |
| Insufficient Verification of Data Authenticity | <1:1.7.0.71-2.5.3.1.el7_0 |
| CVE-2014-6504 | <1:1.7.0.71-2.5.3.1.el7_0 |
| CVE-2014-6502 | <1:1.7.0.71-2.5.3.1.el7_0 |
| CVE-2014-6511 | <1:1.7.0.71-2.5.3.1.el7_0 |
| CVE-2014-6517 | <1:1.7.0.71-2.5.3.1.el7_0 |
| CVE-2014-6519 | <1:1.7.0.71-2.5.3.1.el7_0 |
| CVE-2014-6531 | <1:1.7.0.71-2.5.3.1.el7_0 |
| CVE-2014-6457 | <1:1.7.0.71-2.5.3.1.el7_0 |
| CVE-2014-6558 | <1:1.7.0.71-2.5.3.1.el7_0 |
| CVE-2014-4252 | <1:1.7.0.65-2.5.1.2.el7_0 |
| CVE-2014-4216 | <1:1.7.0.65-2.5.1.2.el7_0 |
| CVE-2014-4209 | <1:1.7.0.65-2.5.1.2.el7_0 |
| Use of Externally-Controlled Format String | <1:1.7.0.65-2.5.1.2.el7_0 |
| CVE-2014-4263 | <1:1.7.0.65-2.5.1.2.el7_0 |
| CVE-2014-4221 | <1:1.7.0.65-2.5.1.2.el7_0 |
| CVE-2014-4223 | <1:1.7.0.65-2.5.1.2.el7_0 |
| CVE-2014-4218 | <1:1.7.0.65-2.5.1.2.el7_0 |
| CVE-2014-2483 | <1:1.7.0.65-2.5.1.2.el7_0 |
| CVE-2014-4262 | <1:1.7.0.65-2.5.1.2.el7_0 |
| CVE-2014-4219 | <1:1.7.0.65-2.5.1.2.el7_0 |
| Out-of-Bounds | <1:1.7.0.261-2.6.22.2.el7_8 |
| Uncaught Exception | <1:1.7.0.261-2.6.22.2.el7_8 |
| Improper Input Validation | <1:1.7.0.261-2.6.22.2.el7_8 |
| CVE-2014-4244 | <1:1.7.0.65-2.5.1.2.el7_0 |
| CVE-2020-2781 | <1:1.7.0.261-2.6.22.2.el7_8 |
| CVE-2014-4266 | <1:1.7.0.65-2.5.1.2.el7_0 |
| Uncaught Exception | <1:1.7.0.261-2.6.22.2.el7_8 |
| HTTP Response Splitting | <1:1.7.0.261-2.6.22.2.el7_8 |
| Uncaught Exception | <1:1.7.0.261-2.6.22.2.el7_8 |
| Incorrect Regular Expression | <1:1.7.0.261-2.6.22.2.el7_8 |
| CVE-2014-0454 | <1:1.7.0.55-2.4.7.2.el7_0 |
| CVE-2014-0455 | <1:1.7.0.55-2.4.7.2.el7_0 |
| CVE-2014-2414 | <1:1.7.0.55-2.4.7.2.el7_0 |
| CVE-2014-2421 | <1:1.7.0.55-2.4.7.2.el7_0 |
| CVE-2014-0453 | <1:1.7.0.55-2.4.7.2.el7_0 |
| CVE-2014-0452 | <1:1.7.0.55-2.4.7.2.el7_0 |
| CVE-2014-0460 | <1:1.7.0.55-2.4.7.2.el7_0 |
| CVE-2014-2402 | <1:1.7.0.55-2.4.7.2.el7_0 |
| CVE-2014-0429 | <1:1.7.0.55-2.4.7.2.el7_0 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.251-2.6.21.0.el7_7 |
| CVE-2014-2397 | <1:1.7.0.55-2.4.7.2.el7_0 |
| CVE-2014-0461 | <1:1.7.0.55-2.4.7.2.el7_0 |
| CVE-2014-2398 | <1:1.7.0.55-2.4.7.2.el7_0 |
| CVE-2014-2412 | <1:1.7.0.55-2.4.7.2.el7_0 |
| CVE-2014-0457 | <1:1.7.0.55-2.4.7.2.el7_0 |
| CVE-2014-0458 | <1:1.7.0.55-2.4.7.2.el7_0 |
| CVE-2014-2427 | <1:1.7.0.55-2.4.7.2.el7_0 |
| CVE-2014-0446 | <1:1.7.0.55-2.4.7.2.el7_0 |
| CVE-2014-2413 | <1:1.7.0.55-2.4.7.2.el7_0 |
| CVE-2014-0459 | <1:1.7.0.55-2.4.7.2.el7_0 |
| CVE-2014-2423 | <1:1.7.0.55-2.4.7.2.el7_0 |
| CVE-2014-2403 | <1:1.7.0.55-2.4.7.2.el7_0 |
| CVE-2014-0456 | <1:1.7.0.55-2.4.7.2.el7_0 |
| CVE-2014-0451 | <1:1.7.0.55-2.4.7.2.el7_0 |
| Insecure Temporary File | <1:1.7.0.55-2.4.7.2.el7_0 |
| Use of a Broken or Risky Cryptographic Algorithm | <1:1.7.0.251-2.6.21.0.el7_7 |
| Encoding Error | <1:1.7.0.251-2.6.21.0.el7_7 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.251-2.6.21.0.el7_7 |
| Modification of Assumed-Immutable Data (MAID) | <1:1.7.0.251-2.6.21.0.el7_7 |
| Improper Input Validation | <1:1.7.0.251-2.6.21.0.el7_7 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.251-2.6.21.0.el7_7 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.241-2.6.20.0.el7_7 |
| Cross-site Scripting (XSS) | <1:1.7.0.241-2.6.20.0.el7_7 |
| Uncaught Exception | <1:1.7.0.241-2.6.20.0.el7_7 |
| CVE-2019-2945 | <1:1.7.0.241-2.6.20.0.el7_7 |
| Uncaught Exception | <1:1.7.0.241-2.6.20.0.el7_7 |
| Uncaught Exception | <1:1.7.0.241-2.6.20.0.el7_7 |
| Integer Overflow or Wraparound | <1:1.7.0.241-2.6.20.0.el7_7 |
| Uncaught Exception | <1:1.7.0.241-2.6.20.0.el7_7 |
| CVE-2019-2978 | <1:1.7.0.241-2.6.20.0.el7_7 |
| Cross-site Scripting (XSS) | <1:1.7.0.241-2.6.20.0.el7_7 |
| NULL Pointer Dereference | <1:1.7.0.241-2.6.20.0.el7_7 |
| Improper Input Validation | <1:1.7.0.241-2.6.20.0.el7_7 |
| CVE-2019-2762 | <1:1.7.0.231-2.6.19.1.el7_6 |
| Covert Timing Channel | <1:1.7.0.231-2.6.19.1.el7_6 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.231-2.6.19.1.el7_6 |
| Improper Input Validation | <1:1.7.0.231-2.6.19.1.el7_6 |
| CVE-2019-2786 | <1:1.7.0.231-2.6.19.1.el7_6 |
| Out-of-Bounds | <1:1.7.0.231-2.6.19.1.el7_6 |
| Information Exposure | <1:1.7.0.211-2.6.17.1.el7_6 |
| Out-of-bounds Write | <1:1.7.0.221-2.6.18.0.el7_6 |
| CVE-2019-2684 | <1:1.7.0.221-2.6.18.0.el7_6 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.221-2.6.18.0.el7_6 |