| Resource Exhaustion | |
| Improper Verification of Cryptographic Signature | |
| Improper Certificate Validation | |
| Inefficient Regular Expression Complexity | |
| Improper Certificate Validation | |
| Resource Exhaustion | |
| NULL Pointer Dereference | |
| Out-of-bounds Write | |
| Out-of-bounds Write | |
| Integer Overflow or Wraparound | |
| CVE-2026-23865 | |
| Out-of-bounds Write | |
| Heap-based Buffer Overflow | |
| Use of a Broken or Risky Cryptographic Algorithm | |
| Out-of-bounds Read | |
| Loop with Unreachable Exit Condition ('Infinite Loop') | |
| Use of a Broken or Risky Cryptographic Algorithm | |
| Uncontrolled Recursion | |
| XML External Entity (XXE) Injection | |
| Cleartext Transmission of Sensitive Information | |
| Improper Certificate Validation | |
| Key Exchange without Entity Authentication | |
| Improper Validation of Specified Type of Input | |
| CRLF Injection | |
| CVE-2025-53066 | |
| Inappropriate Encoding for Output Context | |
| Information Exposure | |
| Heap-based Buffer Overflow | |
| Heap-based Buffer Overflow | |
| Missing Required Cryptographic Step | |
| CVE-2025-30761 | |
| Heap-based Buffer Overflow | |
| Buffer Overflow | |
| Information Exposure | |
| Signed to Unsigned Conversion Error | |
| Improper Handling of Length Parameter Inconsistency | |
| Uncontrolled Memory Allocation | |
| Integer Overflow or Wraparound | |
| Signed to Unsigned Conversion Error | |
| Loop with Unreachable Exit Condition ('Infinite Loop') | |
| CVE-2024-21147 | |
| CVE-2024-21140 | |
| CVE-2024-21131 | |
| Out-of-bounds Write | |
| Improper Validation of Specified Quantity in Input | |
| Allocation of Resources Without Limits or Throttling | |
| Deserialization of Untrusted Data | |
| Integer Overflow or Wraparound | |
| Allocation of Resources Without Limits or Throttling | |
| Deserialization of Untrusted Data | |
| Allocation of Resources Without Limits or Throttling | |
| 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 | |
| Out-of-bounds Write | |
| 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') | |
| Allocation of Resources Without Limits or Throttling | |
| Loop with Unreachable Exit Condition ('Infinite Loop') | |
| XML External Entity (XXE) Injection | |
| Allocation of Resources Without Limits or Throttling | |
| Deserialization of Untrusted Data | |
| Uncaught Exception | |
| Improper Cross-boundary Removal of Sensitive Data | |
| Cryptographic Issues | |
| Untrusted Search Path | <1:1.7.0.201-2.6.16.0.el6_10 |
| Information Exposure | <1:1.7.0.201-2.6.16.0.el6_10 |
| Improper Access Control | <1:1.7.0.201-2.6.16.0.el6_10 |
| Improper Certificate Validation | <1:1.7.0.201-2.6.16.0.el6_10 |
| Loop with Unreachable Exit Condition ('Infinite Loop') | <1:1.7.0.201-2.6.16.0.el6_10 |
| Improper Verification of Cryptographic Signature | <1:1.7.0.201-2.6.16.0.el6_10 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.191-2.6.15.4.el6_10 |
| Covert Timing Channel | <1:1.7.0.181-2.6.14.8.el6_9 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.181-2.6.14.1.el6_9 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.181-2.6.14.1.el6_9 |
| CVE-2018-2814 | <1:1.7.0.181-2.6.14.1.el6_9 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.181-2.6.14.1.el6_9 |
| Deserialization of Untrusted Data | <1:1.7.0.181-2.6.14.1.el6_9 |
| CVE-2018-2800 | <1:1.7.0.181-2.6.14.1.el6_9 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.181-2.6.14.1.el6_9 |
| Improper Verification of Cryptographic Signature | <1:1.7.0.181-2.6.14.1.el6_9 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.181-2.6.14.1.el6_9 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.181-2.6.14.1.el6_9 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.171-2.6.13.0.el6_9 |
| Unsynchronized Access to Shared Data in a Multithreaded Context | <1:1.7.0.171-2.6.13.0.el6_9 |
| Untrusted Search Path | <1:1.7.0.171-2.6.13.0.el6_9 |
| Deserialization of Untrusted Data | <1:1.7.0.171-2.6.13.0.el6_9 |
| Improper Access Control | <1:1.7.0.171-2.6.13.0.el6_9 |
| Improper Input Validation | <1:1.7.0.171-2.6.13.0.el6_9 |
| Use After Free | <1:1.7.0.171-2.6.13.0.el6_9 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.171-2.6.13.0.el6_9 |
| Use of a Broken or Risky Cryptographic Algorithm | <1:1.7.0.171-2.6.13.0.el6_9 |
| Use of Insufficiently Random Values | <1:1.7.0.171-2.6.13.0.el6_9 |
| Improper Input Validation | <1:1.7.0.171-2.6.13.0.el6_9 |
| LDAP Injection | <1:1.7.0.171-2.6.13.0.el6_9 |
| Use After Free | <1:1.7.0.171-2.6.13.0.el6_9 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.171-2.6.13.0.el6_9 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.161-2.6.12.0.el6_9 |
| CVE-2017-10355 | <1:1.7.0.161-2.6.12.0.el6_9 |
| Arbitrary Code Injection | <1:1.7.0.51-2.4.4.1.el6_5 |
| Insufficient Verification of Data Authenticity | <1:1.7.0.161-2.6.12.0.el6_9 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.161-2.6.12.0.el6_9 |
| Use of a Broken or Risky Cryptographic Algorithm | <1:1.7.0.161-2.6.12.0.el6_9 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.161-2.6.12.0.el6_9 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.161-2.6.12.0.el6_9 |
| CVE-2017-10274 | <1:1.7.0.161-2.6.12.0.el6_9 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.161-2.6.12.0.el6_9 |
| CVE-2017-10346 | <1:1.7.0.161-2.6.12.0.el6_9 |
| CVE-2017-10285 | <1:1.7.0.161-2.6.12.0.el6_9 |
| HTTP Response Splitting | <1:1.7.0.161-2.6.12.0.el6_9 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.161-2.6.12.0.el6_9 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.161-2.6.12.0.el6_9 |
| CVE-2013-5893 | <1:1.7.0.51-2.4.4.1.el6_5 |
| CVE-2013-5851 | <1:1.7.0.45-2.4.3.2.el6_4 |
| CVE-2013-5809 | <1:1.7.0.45-2.4.3.2.el6_4 |
| CVE-2013-5800 | <1:1.7.0.45-2.4.3.2.el6_4 |
| CVE-2013-5780 | <1:1.7.0.45-2.4.3.2.el6_4 |
| CVE-2013-5782 | <1:1.7.0.45-2.4.3.2.el6_4 |
| CVE-2013-5850 | <1:1.7.0.45-2.4.3.2.el6_4 |
| CVE-2013-5783 | <1:1.7.0.45-2.4.3.2.el6_4 |
| CVE-2013-5825 | <1:1.7.0.45-2.4.3.2.el6_4 |
| CVE-2013-5842 | <1:1.7.0.45-2.4.3.2.el6_4 |
| CVE-2013-5829 | <1:1.7.0.45-2.4.3.2.el6_4 |
| CVE-2013-5784 | <1:1.7.0.45-2.4.3.2.el6_4 |
| CVE-2013-5820 | <1:1.7.0.45-2.4.3.2.el6_4 |
| CVE-2013-5838 | <1:1.7.0.45-2.4.3.2.el6_4 |
| CVE-2013-5797 | <1:1.7.0.45-2.4.3.2.el6_4 |
| CVE-2013-5840 | <1:1.7.0.45-2.4.3.2.el6_4 |
| CVE-2013-5774 | <1:1.7.0.45-2.4.3.2.el6_4 |
| Out-of-bounds Read | <1:1.7.0.45-2.4.3.2.el6_4 |
| CVE-2013-5823 | <1:1.7.0.45-2.4.3.2.el6_4 |
| CVE-2013-5803 | <1:1.7.0.45-2.4.3.2.el6_4 |
| CVE-2013-5772 | <1:1.7.0.45-2.4.3.2.el6_4 |
| CVE-2013-5804 | <1:1.7.0.45-2.4.3.2.el6_4 |
| CVE-2013-5817 | <1:1.7.0.45-2.4.3.2.el6_4 |
| CVE-2013-5849 | <1:1.7.0.45-2.4.3.2.el6_4 |
| CVE-2013-5802 | <1:1.7.0.45-2.4.3.2.el6_4 |
| CVE-2013-5814 | <1:1.7.0.45-2.4.3.2.el6_4 |
| CVE-2013-3829 | <1:1.7.0.45-2.4.3.2.el6_4 |
| CVE-2013-5790 | <1:1.7.0.45-2.4.3.2.el6_4 |
| CVE-2013-5830 | <1:1.7.0.45-2.4.3.2.el6_4 |
| CVE-2017-10096 | <1:1.7.0.151-2.6.11.0.el6_9 |
| CVE-2017-10090 | <1:1.7.0.151-2.6.11.0.el6_9 |
| CVE-2013-2463 | <1:1.7.0.25-2.3.10.3.el6_4 |
| CVE-2017-10067 | <1:1.7.0.151-2.6.11.0.el6_9 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.151-2.6.11.0.el6_9 |
| CVE-2013-2457 | <1:1.7.0.25-2.3.10.3.el6_4 |
| CVE-2013-2458 | <1:1.7.0.25-2.3.10.3.el6_4 |
| CVE-2013-2465 | <1:1.7.0.25-2.3.10.3.el6_4 |
| CVE-2013-2472 | <1:1.7.0.25-2.3.10.3.el6_4 |
| CVE-2013-2473 | <1:1.7.0.25-2.3.10.3.el6_4 |
| CVE-2017-10110 | <1:1.7.0.151-2.6.11.0.el6_9 |
| CVE-2017-10101 | <1:1.7.0.151-2.6.11.0.el6_9 |
| Covert Timing Channel | <1:1.7.0.151-2.6.11.0.el6_9 |
| CVE-2017-10102 | <1:1.7.0.151-2.6.11.0.el6_9 |
| CVE-2013-2452 | <1:1.7.0.25-2.3.10.3.el6_4 |
| CVE-2017-10193 | <1:1.7.0.161-2.6.12.0.el6_9 |
| CVE-2013-2461 | <1:1.7.0.25-2.3.10.3.el6_4 |
| CVE-2017-10107 | <1:1.7.0.151-2.6.11.0.el6_9 |
| CVE-2017-10198 | <1:1.7.0.161-2.6.12.0.el6_9 |
| CVE-2013-2456 | <1:1.7.0.25-2.3.10.3.el6_4 |
| CVE-2013-2469 | <1:1.7.0.25-2.3.10.3.el6_4 |
| CVE-2013-2449 | <1:1.7.0.25-2.3.10.3.el6_4 |
| CVE-2013-2446 | <1:1.7.0.25-2.3.10.3.el6_4 |
| CVE-2013-2412 | <1:1.7.0.25-2.3.10.3.el6_4 |
| CVE-2013-2471 | <1:1.7.0.25-2.3.10.3.el6_4 |
| CVE-2013-2453 | <1:1.7.0.25-2.3.10.3.el6_4 |
| CVE-2013-2450 | <1:1.7.0.25-2.3.10.3.el6_4 |
| CVE-2013-2460 | <1:1.7.0.25-2.3.10.3.el6_4 |
| CVE-2013-2445 | <1:1.7.0.25-2.3.10.3.el6_4 |
| Integer Overflow or Wraparound | <1:1.7.0.25-2.3.10.3.el6_4 |
| CVE-2017-10116 | <1:1.7.0.151-2.6.11.0.el6_9 |
| CVE-2013-2447 | <1:1.7.0.25-2.3.10.3.el6_4 |
| CVE-2013-2470 | <1:1.7.0.25-2.3.10.3.el6_4 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.151-2.6.11.0.el6_9 |
| CVE-2017-10081 | <1:1.7.0.151-2.6.11.0.el6_9 |
| CVE-2017-10243 | <1:1.7.0.151-2.6.11.0.el6_9 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.151-2.6.11.0.el6_9 |
| Integer Overflow or Wraparound | <1:1.7.0.151-2.6.11.0.el6_9 |
| CVE-2013-2407 | <1:1.7.0.25-2.3.10.3.el6_4 |
| CVE-2017-10087 | <1:1.7.0.151-2.6.11.0.el6_9 |
| CVE-2013-2444 | <1:1.7.0.25-2.3.10.3.el6_4 |
| CVE-2013-2443 | <1:1.7.0.25-2.3.10.3.el6_4 |
| CVE-2013-2448 | <1:1.7.0.25-2.3.10.3.el6_4 |
| CVE-2013-1571 | <1:1.7.0.25-2.3.10.3.el6_4 |
| CVE-2013-1500 | <1:1.7.0.25-2.3.10.3.el6_4 |
| CVE-2017-10089 | <1:1.7.0.151-2.6.11.0.el6_9 |
| CVE-2013-2454 | <1:1.7.0.25-2.3.10.3.el6_4 |
| CVE-2013-2455 | <1:1.7.0.25-2.3.10.3.el6_4 |
| Covert Timing Channel | <1:1.7.0.151-2.6.11.0.el6_9 |
| Improper Input Validation | <1:1.7.0.141-2.6.10.1.el6_9 |
| Use of a Broken or Risky Cryptographic Algorithm | <1:1.7.0.141-2.6.10.1.el6_9 |
| Improper Input Validation | <1:1.7.0.141-2.6.10.1.el6_9 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.141-2.6.10.1.el6_9 |
| Improper Authentication | <1:1.7.0.141-2.6.10.1.el6_9 |
| Untrusted Search Path | <1:1.7.0.141-2.6.10.1.el6_9 |
| CVE-2013-2426 | <1:1.7.0.19-2.3.9.1.el6_4 |
| CVE-2013-1558 | <1:1.7.0.19-2.3.9.1.el6_4 |
| CVE-2013-1537 | <1:1.7.0.19-2.3.9.1.el6_4 |
| CVE-2013-1518 | <1:1.7.0.19-2.3.9.1.el6_4 |
| CVE-2013-2429 | <1:1.7.0.19-2.3.9.1.el6_4 |
| Arbitrary Code Injection | <1:1.7.0.19-2.3.9.1.el6_4 |
| CVE-2013-2422 | <1:1.7.0.19-2.3.9.1.el6_4 |
| CVE-2013-1557 | <1:1.7.0.19-2.3.9.1.el6_4 |
| CVE-2013-2431 | <1:1.7.0.19-2.3.9.1.el6_4 |
| CVE-2013-2417 | <1:1.7.0.19-2.3.9.1.el6_4 |
| Incorrect Permission Assignment for Critical Resource | <1:1.7.0.19-2.3.9.1.el6_4 |
| CVE-2013-2430 | <1:1.7.0.19-2.3.9.1.el6_4 |
| Arbitrary Code Injection | <1:1.7.0.19-2.3.9.1.el6_4 |
| CVE-2013-2424 | <1:1.7.0.19-2.3.9.1.el6_4 |
| CVE-2013-2421 | <1:1.7.0.19-2.3.9.1.el6_4 |
| CVE-2013-2420 | <1:1.7.0.19-2.3.9.1.el6_4 |
| CVE-2013-2436 | <1:1.7.0.19-2.3.9.1.el6_4 |
| CVE-2013-2423 | <1:1.7.0.19-2.3.9.1.el6_4 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.131-2.6.9.0.el6_8 |
| CVE-2017-3272 | <1:1.7.0.131-2.6.9.0.el6_8 |
| Information Exposure | <1:1.7.0.131-2.6.9.0.el6_8 |
| Integer Overflow or Wraparound | <1:1.7.0.131-2.6.9.0.el6_8 |
| CVE-2017-3289 | <1:1.7.0.131-2.6.9.0.el6_8 |
| Deserialization of Untrusted Data | <1:1.7.0.131-2.6.9.0.el6_8 |
| Improper Input Validation | <1:1.7.0.131-2.6.9.0.el6_8 |
| Improper Input Validation | <1:1.7.0.131-2.6.9.0.el6_8 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.131-2.6.9.0.el6_8 |
| Covert Timing Channel | <1:1.7.0.131-2.6.9.0.el6_8 |
| Improper Input Validation | <1:1.7.0.131-2.6.9.0.el6_8 |
| Integer Overflow or Wraparound | |
| Out-of-Bounds | |
| CVE-2013-1484 | |
| CVE-2013-1485 | |
| CVE-2013-0437 | |
| Cryptographic Issues | |
| CVE-2013-1486 | |
| CVE-2013-0444 | |
| CVE-2016-5554 | <1:1.7.0.121-2.6.8.1.el6_8 |
| CVE-2013-0428 | |
| CVE-2013-0435 | |
| CVE-2013-1478 | |
| CVE-2013-0431 | |
| CVE-2013-0445 | |
| CVE-2013-1476 | |
| CVE-2013-0442 | |
| CVE-2013-0429 | |
| CVE-2013-0426 | |
| CVE-2013-0432 | |
| CVE-2013-0434 | |
| CVE-2013-0427 | |
| CVE-2013-1481 | |
| CVE-2013-1480 | |
| CVE-2012-3213 | |
| CVE-2013-0450 | |
| CVE-2013-0441 | |
| CVE-2013-0425 | |
| CVE-2013-0440 | |
| CVE-2013-0433 | |
| CVE-2013-0443 | |
| CVE-2013-0409 | |
| Cross-site Scripting (XSS) | |
| Access of Resource Using Incompatible Type ('Type Confusion') | <1:1.7.0.121-2.6.8.1.el6_8 |
| Use of a Broken or Risky Cryptographic Algorithm | <1:1.7.0.121-2.6.8.1.el6_8 |
| Cleartext Transmission of Sensitive Information | <1:1.7.0.121-2.6.8.1.el6_8 |
| Improper Input Validation | <1:1.7.0.121-2.6.8.1.el6_8 |
| Out-of-bounds Read | <1:1.7.0.121-2.6.8.1.el6_8 |
| Access Restriction Bypass | |
| Access Restriction Bypass | |
| CVE-2013-1475 | |
| CVE-2012-5074 | |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.111-2.6.7.2.el6_8 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.111-2.6.7.2.el6_8 |
| CVE-2016-3458 | <1:1.7.0.111-2.6.7.2.el6_8 |
| Integer Overflow or Wraparound | <1:1.7.0.111-2.6.7.2.el6_8 |
| CVE-2016-3610 | <1:1.7.0.111-2.6.7.2.el6_8 |
| CVE-2016-3606 | <1:1.7.0.111-2.6.7.2.el6_8 |
| CVE-2016-3598 | <1:1.7.0.111-2.6.7.2.el6_8 |
| CVE-2012-5073 | |
| CVE-2012-5081 | |
| CVE-2012-5069 | |
| CVE-2012-5079 | |
| CVE-2012-5071 | |
| CVE-2012-5070 | |
| CVE-2012-5075 | |
| CVE-2012-5086 | |
| CVE-2012-5072 | |
| CVE-2012-5076 | |
| CVE-2012-5087 | |
| CVE-2012-5088 | |
| CVE-2012-5089 | |
| CVE-2012-4416 | |
| CVE-2012-5068 | |
| CVE-2012-3216 | |
| CVE-2012-5085 | |
| CVE-2012-5084 | |
| CVE-2012-5077 | |
| CVE-2016-3427 | <1:1.7.0.101-2.6.6.1.el6_7 |
| CVE-2016-0687 | <1:1.7.0.101-2.6.6.1.el6_7 |
| CVE-2016-3425 | <1:1.7.0.101-2.6.6.1.el6_7 |
| CVE-2016-0686 | <1:1.7.0.101-2.6.6.1.el6_7 |
| CVE-2016-0695 | <1:1.7.0.101-2.6.6.1.el6_7 |
| CVE-2012-1682 | |
| CVE-2012-3136 | |
| CVE-2012-0547 | |
| CVE-2012-4681 | |
| Improperly Implemented Security Check for Standard | <1:1.7.0.99-2.6.5.0.el6_7 |
| CVE-2012-1726 | |
| Loop with Unreachable Exit Condition ('Infinite Loop') | |
| Improper Data Handling | <1:1.7.0.95-2.6.4.0.el6_7 |
| Incorrect Conversion between Numeric Types | <1:1.7.0.95-2.6.4.0.el6_7 |
| CVE-2016-0402 | <1:1.7.0.95-2.6.4.0.el6_7 |
| CVE-2016-0466 | <1:1.7.0.95-2.6.4.0.el6_7 |
| Out-of-bounds Write | <1:1.7.0.95-2.6.4.0.el6_7 |
| Information Exposure Through Log Files | <1:1.7.0.95-2.6.4.0.el6_7 |
| CVE-2012-1723 | |
| CVE-2012-1719 | |
| CVE-2012-1716 | |
| CVE-2012-1718 | |
| CVE-2012-1725 | |
| CVE-2012-1711 | |
| CVE-2012-1713 | |
| Incorrect Permission Assignment for Critical Resource | |
| CVE-2015-4871 | <1:1.7.0.95-2.6.4.0.el6_7 |
| Out-of-bounds Read | <1:1.7.0.91-2.6.2.2.el6_7 |
| CVE-2015-4844 | <1:1.7.0.91-2.6.2.2.el6_7 |
| CVE-2015-4883 | <1:1.7.0.91-2.6.2.2.el6_7 |
| Information Exposure | <1:1.7.0.91-2.6.2.2.el6_7 |
| CVE-2015-4882 | <1:1.7.0.91-2.6.2.2.el6_7 |
| CVE-2015-4911 | <1:1.7.0.91-2.6.2.2.el6_7 |
| Algorithmic Complexity | <1:1.7.0.91-2.6.2.2.el6_7 |
| Information Exposure | <1:1.7.0.91-2.6.2.2.el6_7 |
| Out-of-bounds Write | <1:1.7.0.91-2.6.2.2.el6_7 |
| CVE-2015-4835 | <1:1.7.0.91-2.6.2.2.el6_7 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.91-2.6.2.2.el6_7 |
| CVE-2015-4860 | <1:1.7.0.91-2.6.2.2.el6_7 |
| Improper Initialization | <1:1.7.0.91-2.6.2.2.el6_7 |
| CVE-2015-4881 | <1:1.7.0.91-2.6.2.2.el6_7 |
| CVE-2015-4903 | <1:1.7.0.91-2.6.2.2.el6_7 |
| Improper Input Validation | <1:1.7.0.91-2.6.2.2.el6_7 |
| CVE-2015-4872 | <1:1.7.0.91-2.6.2.2.el6_7 |
| Improper Certificate Validation | <1:1.7.0.85-2.6.1.3.el6_6 |
| Out-of-bounds Write | <1:1.7.0.85-2.6.1.3.el6_6 |
| CVE-2015-2621 | <1:1.7.0.85-2.6.1.3.el6_6 |
| Improper Check for Certificate Revocation | <1:1.7.0.85-2.6.1.3.el6_6 |
| Access of Resource Using Incompatible Type ('Type Confusion') | <1:1.7.0.85-2.6.1.3.el6_6 |
| CVE-2015-4733 | <1:1.7.0.85-2.6.1.3.el6_6 |
| Missing Release of Resource after Effective Lifetime | <1:1.7.0.85-2.6.1.3.el6_6 |
| Covert Timing Channel | <1:1.7.0.85-2.6.1.3.el6_6 |
| CVE-2015-2590 | <1:1.7.0.85-2.6.1.3.el6_6 |
| Integer Overflow or Wraparound | <1:1.7.0.85-2.6.1.3.el6_6 |
| Unsynchronized Access to Shared Data in a Multithreaded Context | <1:1.7.0.85-2.6.1.3.el6_6 |
| CVE-2015-4731 | <1:1.7.0.85-2.6.1.3.el6_6 |
| Use of a Broken or Risky Cryptographic Algorithm | <1:1.7.0.85-2.6.1.3.el6_6 |
| Use of a Broken or Risky Cryptographic Algorithm | <1:1.7.0.85-2.6.1.3.el6_6 |
| Directory Traversal | <1:1.7.0.79-2.5.5.1.el6_6 |
| Uncaught Exception | <1:1.7.0.79-2.5.5.1.el6_6 |
| Off-by-one Error | <1:1.7.0.79-2.5.5.1.el6_6 |
| Directory Traversal | <1:1.7.0.79-2.5.5.1.el6_6 |
| CVE-2015-0460 | <1:1.7.0.79-2.5.5.1.el6_6 |
| CVE-2015-0477 | <1:1.7.0.79-2.5.5.1.el6_6 |
| Improperly Implemented Security Check for Standard | <1:1.7.0.79-2.5.5.1.el6_6 |
| Loop with Unreachable Exit Condition ('Infinite Loop') | <1:1.7.0.75-2.5.4.0.el6_6 |
| CVE-2014-6593 | <1:1.7.0.75-2.5.4.0.el6_6 |
| Out-of-bounds Read | <1:1.7.0.75-2.5.4.0.el6_6 |
| CVE-2015-0408 | <1:1.7.0.75-2.5.4.0.el6_6 |
| CVE-2015-0407 | <1:1.7.0.75-2.5.4.0.el6_6 |
| NULL Pointer Dereference | <1:1.7.0.75-2.5.4.0.el6_6 |
| CVE-2015-0395 | <1:1.7.0.75-2.5.4.0.el6_6 |
| CVE-2014-6601 | <1:1.7.0.75-2.5.4.0.el6_6 |
| Insecure Temporary File | <1:1.7.0.75-2.5.4.0.el6_6 |
| CVE-2015-0412 | <1:1.7.0.75-2.5.4.0.el6_6 |
| Out-of-bounds Read | <1:1.7.0.75-2.5.4.0.el6_6 |
| Information Exposure | <1:1.7.0.75-2.5.4.0.el6_6 |
| 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 | |
| Improper Input Validation | <1:1.7.0.45-2.4.3.2.el6_4 |
| CVE-2014-4252 | <1:1.7.0.65-2.5.1.2.el6_5 |
| CVE-2014-4216 | <1:1.7.0.65-2.5.1.2.el6_5 |
| CVE-2014-4209 | <1:1.7.0.65-2.5.1.2.el6_5 |
| Use of Externally-Controlled Format String | <1:1.7.0.65-2.5.1.2.el6_5 |
| CVE-2014-4263 | <1:1.7.0.65-2.5.1.2.el6_5 |
| CVE-2014-4221 | <1:1.7.0.65-2.5.1.2.el6_5 |
| CVE-2014-4223 | <1:1.7.0.65-2.5.1.2.el6_5 |
| CVE-2014-4218 | <1:1.7.0.65-2.5.1.2.el6_5 |
| CVE-2014-2483 | <1:1.7.0.65-2.5.1.2.el6_5 |
| CVE-2014-4262 | <1:1.7.0.65-2.5.1.2.el6_5 |
| CVE-2014-4219 | <1:1.7.0.65-2.5.1.2.el6_5 |
| CVE-2014-0428 | <1:1.7.0.51-2.4.4.1.el6_5 |
| Out-of-Bounds | <1:1.7.0.261-2.6.22.1.el6_10 |
| Uncaught Exception | <1:1.7.0.261-2.6.22.1.el6_10 |
| CVE-2014-0373 | <1:1.7.0.51-2.4.4.1.el6_5 |
| Improper Input Validation | <1:1.7.0.261-2.6.22.1.el6_10 |
| CVE-2014-4244 | <1:1.7.0.65-2.5.1.2.el6_5 |
| CVE-2020-2781 | <1:1.7.0.261-2.6.22.1.el6_10 |
| CVE-2013-5878 | <1:1.7.0.51-2.4.4.1.el6_5 |
| CVE-2014-4266 | <1:1.7.0.65-2.5.1.2.el6_5 |
| Uncaught Exception | <1:1.7.0.261-2.6.22.1.el6_10 |
| HTTP Response Splitting | <1:1.7.0.261-2.6.22.1.el6_10 |
| Uncaught Exception | <1:1.7.0.261-2.6.22.1.el6_10 |
| Inefficient Regular Expression Complexity | <1:1.7.0.261-2.6.22.1.el6_10 |
| CVE-2013-5884 | <1:1.7.0.51-2.4.4.1.el6_5 |
| CVE-2013-5896 | <1:1.7.0.51-2.4.4.1.el6_5 |
| CVE-2014-0411 | <1:1.7.0.51-2.4.4.1.el6_5 |
| CVE-2014-0416 | <1:1.7.0.51-2.4.4.1.el6_5 |
| CVE-2014-0368 | <1:1.7.0.51-2.4.4.1.el6_5 |
| CVE-2013-5907 | <1:1.7.0.51-2.4.4.1.el6_5 |
| CVE-2014-0376 | <1:1.7.0.51-2.4.4.1.el6_5 |
| CVE-2014-0423 | <1:1.7.0.51-2.4.4.1.el6_5 |
| CVE-2014-0422 | <1:1.7.0.51-2.4.4.1.el6_5 |
| CVE-2013-5910 | <1:1.7.0.51-2.4.4.1.el6_5 |
| CVE-2014-0454 | <1:1.7.0.55-2.4.7.1.el6_5 |
| CVE-2014-0455 | <1:1.7.0.55-2.4.7.1.el6_5 |
| CVE-2014-2414 | <1:1.7.0.55-2.4.7.1.el6_5 |
| CVE-2014-2421 | <1:1.7.0.55-2.4.7.1.el6_5 |
| CVE-2014-0453 | <1:1.7.0.55-2.4.7.1.el6_5 |
| CVE-2014-0452 | <1:1.7.0.55-2.4.7.1.el6_5 |
| CVE-2014-0460 | <1:1.7.0.55-2.4.7.1.el6_5 |
| CVE-2014-2402 | <1:1.7.0.55-2.4.7.1.el6_5 |
| CVE-2014-0429 | <1:1.7.0.55-2.4.7.1.el6_5 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.251-2.6.21.0.el6_10 |
| CVE-2014-2397 | <1:1.7.0.55-2.4.7.1.el6_5 |
| CVE-2014-0461 | <1:1.7.0.55-2.4.7.1.el6_5 |
| CVE-2014-2398 | <1:1.7.0.55-2.4.7.1.el6_5 |
| CVE-2014-2412 | <1:1.7.0.55-2.4.7.1.el6_5 |
| CVE-2014-0457 | <1:1.7.0.55-2.4.7.1.el6_5 |
| CVE-2014-0458 | <1:1.7.0.55-2.4.7.1.el6_5 |
| CVE-2014-2427 | <1:1.7.0.55-2.4.7.1.el6_5 |
| CVE-2014-0446 | <1:1.7.0.55-2.4.7.1.el6_5 |
| CVE-2014-2413 | <1:1.7.0.55-2.4.7.1.el6_5 |
| CVE-2014-0459 | <1:1.7.0.55-2.4.7.1.el6_5 |
| CVE-2014-2423 | <1:1.7.0.55-2.4.7.1.el6_5 |
| CVE-2014-2403 | <1:1.7.0.55-2.4.7.1.el6_5 |
| CVE-2014-0456 | <1:1.7.0.55-2.4.7.1.el6_5 |
| CVE-2014-0451 | <1:1.7.0.55-2.4.7.1.el6_5 |
| Insecure Temporary File | <1:1.7.0.55-2.4.7.1.el6_5 |
| Use of a Broken or Risky Cryptographic Algorithm | <1:1.7.0.251-2.6.21.0.el6_10 |
| Encoding Error | <1:1.7.0.251-2.6.21.0.el6_10 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.251-2.6.21.0.el6_10 |
| Modification of Assumed-Immutable Data (MAID) | <1:1.7.0.251-2.6.21.0.el6_10 |
| Improper Input Validation | <1:1.7.0.251-2.6.21.0.el6_10 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.251-2.6.21.0.el6_10 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.241-2.6.20.0.el6_10 |
| Cross-site Scripting (XSS) | <1:1.7.0.241-2.6.20.0.el6_10 |
| Uncaught Exception | <1:1.7.0.241-2.6.20.0.el6_10 |
| CVE-2019-2945 | <1:1.7.0.241-2.6.20.0.el6_10 |
| Uncaught Exception | <1:1.7.0.241-2.6.20.0.el6_10 |
| Uncaught Exception | <1:1.7.0.241-2.6.20.0.el6_10 |
| Integer Overflow or Wraparound | <1:1.7.0.241-2.6.20.0.el6_10 |
| Uncaught Exception | <1:1.7.0.241-2.6.20.0.el6_10 |
| CVE-2019-2978 | <1:1.7.0.241-2.6.20.0.el6_10 |
| Cross-site Scripting (XSS) | <1:1.7.0.241-2.6.20.0.el6_10 |
| NULL Pointer Dereference | <1:1.7.0.241-2.6.20.0.el6_10 |
| Improper Input Validation | <1:1.7.0.241-2.6.20.0.el6_10 |
| CVE-2019-2762 | <1:1.7.0.231-2.6.19.1.el6_10 |
| Covert Timing Channel | <1:1.7.0.231-2.6.19.1.el6_10 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.231-2.6.19.1.el6_10 |
| Improper Input Validation | <1:1.7.0.231-2.6.19.1.el6_10 |
| CVE-2019-2786 | <1:1.7.0.231-2.6.19.1.el6_10 |
| Out-of-Bounds | <1:1.7.0.231-2.6.19.1.el6_10 |
| Information Exposure | <1:1.7.0.211-2.6.17.1.el6_10 |
| Out-of-bounds Write | <1:1.7.0.221-2.6.18.0.el6_10 |
| CVE-2019-2684 | <1:1.7.0.221-2.6.18.0.el6_10 |
| Allocation of Resources Without Limits or Throttling | <1:1.7.0.221-2.6.18.0.el6_10 |
| CVE-2013-2419 | <1:1.7.0.19-2.3.9.1.el6_4 |
| CVE-2013-2384 | <1:1.7.0.19-2.3.9.1.el6_4 |
| CVE-2013-2383 | <1:1.7.0.19-2.3.9.1.el6_4 |
| CVE-2013-1569 | <1:1.7.0.19-2.3.9.1.el6_4 |