Homepage

java-1.5.0-ibm-accessibility

Report a new vulnerability Found a mistake?

Direct Vulnerabilities

Known vulnerabilities in the java-1.5.0-ibm-accessibility package. This does not include vulnerabilities belonging to this package’s dependencies.

Fix vulnerabilities automatically

Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

Fix for free
VulnerabilityVulnerable Version
  • H
Information Exposure

<1:1.5.0.16.8-1jpp.1.el5
  • M
CVE-2014-6531

<1:1.5.0.16.8-1jpp.1.el5
  • C
CVE-2015-2638

<1:1.5.0.16.13-1jpp.3.el5
  • L
Out-of-bounds Read

<1:1.5.0.16.9-1jpp.1.el5
  • M
CVE-2014-6457

<1:1.5.0.16.8-1jpp.1.el5
  • M
Out-of-bounds Read

<1:1.5.0.16.4-1jpp.1.el5_10
  • M
Improper Input Validation

<1:1.5.0.16.3-1jpp.1.el5_9
  • C
CVE-2015-4731

<1:1.5.0.16.13-1jpp.3.el5
  • M
CVE-2015-0477

<1:1.5.0.16.10-1jpp.1.el5
  • M
CVE-2007-5273

<1:1.5.0.6-1jpp.1.el5
  • M
CVE-2007-5274

<1:1.5.0.6-1jpp.1.el5
  • M
CVE-2007-5232

<1:1.5.0.6-1jpp.1.el5
  • M
CVE-2007-5240

<1:1.5.0.6-1jpp.1.el5
  • M
Access Restriction Bypass

<1:1.5.0.6-1jpp.1.el5
  • M
Access Restriction Bypass

<1:1.5.0.6-1jpp.1.el5
  • H
Access Restriction Bypass

<1:1.5.0.7-1jpp.2.el5
  • C
Access Restriction Bypass

<1:1.5.0.7-1jpp.2.el5
  • C
Access Restriction Bypass

<1:1.5.0.7-1jpp.2.el5
  • C
Access Restriction Bypass

<1:1.5.0.7-1jpp.2.el5
  • C
Out-of-Bounds

<1:1.5.0.7-1jpp.2.el5
  • C
Out-of-Bounds

<1:1.5.0.7-1jpp.2.el5
  • C
CVE-2008-1194

<1:1.5.0.7-1jpp.2.el5
  • C
Out-of-Bounds

<1:1.5.0.7-1jpp.2.el5
  • C
Security Features

<1:1.5.0.7-1jpp.2.el5
  • C
Security Features

<1:1.5.0.7-1jpp.2.el5
  • C
Access Restriction Bypass

<1:1.5.0.8-1jpp.1.el5
  • M
Information Exposure

<1:1.5.0.8-1jpp.1.el5
  • M
Access Restriction Bypass

<1:1.5.0.8-1jpp.2.el5
  • C
Out-of-Bounds

<1:1.5.0.8-1jpp.1.el5
  • C
Improper Input Validation

<1:1.5.0.8-1jpp.1.el5
  • C
Access Restriction Bypass

<1:1.5.0.8-1jpp.1.el5
  • C
Access Restriction Bypass

<1:1.5.0.8-1jpp.1.el5
  • M
CVE-2008-5348

<1:1.5.0.9-1jpp.2.el5
  • C
Numeric Errors

<1:1.5.0.9-1jpp.2.el5
  • C
Access Restriction Bypass

<1:1.5.0.9-1jpp.2.el5
  • C
Out-of-Bounds

<1:1.5.0.9-1jpp.2.el5
  • L
CVE-2008-5360

<1:1.5.0.9-1jpp.2.el5
  • C
Out-of-Bounds

<1:1.5.0.9-1jpp.2.el5
  • M
Information Exposure

<1:1.5.0.9-1jpp.2.el5
  • H
Information Exposure

<1:1.5.0.9-1jpp.2.el5
  • M
CVE-2008-5349

<1:1.5.0.9-1jpp.2.el5
  • M
Information Exposure

<1:1.5.0.9-1jpp.2.el5
  • M
CVE-2008-5345

<1:1.5.0.9-1jpp.2.el5
  • H
CVE-2008-5339

<1:1.5.0.9-1jpp.2.el5
  • H
Arbitrary Code Injection

<1:1.5.0.9-1jpp.2.el5
  • C
Numeric Errors

<1:1.5.0.9-1jpp.2.el5
  • H
Access Restriction Bypass

<1:1.5.0.9-1jpp.2.el5
  • H
CVE-2008-5343

<1:1.5.0.9-1jpp.2.el5
  • C
CVE-2008-5353

<1:1.5.0.9-1jpp.2.el5
  • M
CVE-2008-5344

<1:1.5.0.9-1jpp.2.el5
  • M
Out-of-Bounds

<1:1.5.0.9-1jpp.2.el5
  • M
Information Exposure

<1:1.5.0.9-1jpp.2.el5
  • M
CVE-2009-1107

<1:1.5.0.9-1jpp.3.el5
  • M
Configuration

<1:1.5.0.9-1jpp.3.el5
  • L
CVE-2009-1100

<1:1.5.0.9-1jpp.3.el5
  • C
Out-of-Bounds

<1:1.5.0.9-1jpp.3.el5
  • C
Numeric Errors

<1:1.5.0.9-1jpp.3.el5
  • C
Out-of-Bounds

<1:1.5.0.9-1jpp.3.el5
  • H
CVE-2009-1101

<1:1.5.0.9-1jpp.3.el5
  • C
CVE-2009-1105

<1:1.5.0.9-1jpp.3.el5
  • C
CVE-2009-1103

<1:1.5.0.9-1jpp.3.el5
  • H
Configuration

<1:1.5.0.9-1jpp.3.el5
  • C
Out-of-Bounds

<1:1.5.0.9-1jpp.3.el5
  • C
CVE-2009-1094

<1:1.5.0.9-1jpp.3.el5
  • C
Numeric Errors

<1:1.5.0.9-1jpp.3.el5
  • M
Improper Input Validation

<1:1.5.0.9-1jpp.3.el5
  • C
Integer Overflow or Wraparound

<1:1.5.0.10-1jpp.4.el5
  • M
Access Restriction Bypass

<1:1.5.0.10-1jpp.4.el5
  • H
CVE-2009-2671

<1:1.5.0.10-1jpp.4.el5
  • H
Access Restriction Bypass

<1:1.5.0.10-1jpp.4.el5
  • M
CVE-2009-2625

<1:1.5.0.10-1jpp.4.el5
  • H
Out-of-Bounds

<1:1.5.0.11-1jpp.1.el5
  • M
Cryptographic Issues

<1:1.5.0.11-1jpp.1.el5
  • H
Stack-based Buffer Overflow

<1:1.5.0.11-1jpp.1.el5
  • H
Numeric Errors

<1:1.5.0.11-1jpp.1.el5
  • H
Out-of-Bounds

<1:1.5.0.11-1jpp.1.el5
  • M
Resource Management Errors

<1:1.5.0.11-1jpp.1.el5
  • C
CVE-2009-3872

<1:1.5.0.11-1jpp.1.el5
  • H
Out-of-Bounds

<1:1.5.0.11-1jpp.1.el5
  • H
Out-of-Bounds

<1:1.5.0.11-1jpp.1.el5
  • M
Resource Management Errors

<1:1.5.0.11-1jpp.1.el5
  • C
CVE-2010-0837

<1:1.5.0.11.1-1jpp.3.el5
  • C
CVE-2010-0848

<1:1.5.0.11.2-1jpp.1.el5
  • C
CVE-2010-0847

<1:1.5.0.11.2-1jpp.1.el5
  • C
CVE-2010-0838

<1:1.5.0.11.1-1jpp.3.el5
  • C
CVE-2010-0840

<1:1.5.0.11.2-1jpp.1.el5
  • M
CVE-2010-0084

<1:1.5.0.11.1-1jpp.3.el5
  • H
Integer Overflow or Wraparound

<1:1.5.0.11.2-1jpp.1.el5
  • M
CVE-2010-0091

<1:1.5.0.11.1-1jpp.3.el5
  • M
CVE-2010-0092

<1:1.5.0.11.1-1jpp.3.el5
  • H
CVE-2010-0094

<1:1.5.0.11.1-1jpp.3.el5
  • H
CVE-2010-0849

<1:1.5.0.11.2-1jpp.1.el5
  • H
CVE-2010-0095

<1:1.5.0.11.1-1jpp.3.el5
  • H
CVE-2010-0088

<1:1.5.0.11.1-1jpp.3.el5
  • H
CVE-2010-0842

<1:1.5.0.11.2-1jpp.1.el5
  • H
CVE-2010-0087

<1:1.5.0.11.1-1jpp.3.el5
  • H
CVE-2010-0846

<1:1.5.0.11.2-1jpp.1.el5
  • H
CVE-2010-0843

<1:1.5.0.11.2-1jpp.1.el5
  • H
CVE-2010-0839

<1:1.5.0.11.1-1jpp.3.el5
  • H
CVE-2010-0844

<1:1.5.0.11.2-1jpp.1.el5
  • M
CVE-2010-0089

<1:1.5.0.11.1-1jpp.3.el5
  • H
CVE-2010-3557

<1:1.5.0.12.3-1jpp.1.el5
  • M
CVE-2010-3548

<1:1.5.0.12.2-1jpp.1.el5
  • M
CVE-2010-3551

<1:1.5.0.12.2-1jpp.1.el5
  • M
CVE-2010-3574

<1:1.5.0.12.2-1jpp.1.el5
  • M
CVE-2010-3573

<1:1.5.0.12.2-1jpp.1.el5
  • H
CVE-2010-3550

<1:1.5.0.12.2-1jpp.1.el5
  • C
CVE-2010-3556

<1:1.5.0.12.2-1jpp.1.el5
  • H
CVE-2010-3562

<1:1.5.0.12.2-1jpp.1.el5
  • H
CVE-2010-3565

<1:1.5.0.12.2-1jpp.1.el5
  • H
CVE-2010-3566

<1:1.5.0.12.2-1jpp.1.el5
  • H
CVE-2010-3569

<1:1.5.0.12.2-1jpp.1.el5
  • H
CVE-2010-3553

<1:1.5.0.12.3-1jpp.1.el5
  • M
CVE-2010-3541

<1:1.5.0.12.2-1jpp.1.el5
  • H
CVE-2010-3568

<1:1.5.0.12.2-1jpp.1.el5
  • H
CVE-2010-3549

<1:1.5.0.12.2-1jpp.1.el5
  • C
CVE-2010-3572

<1:1.5.0.12.2-1jpp.1.el5
  • C
CVE-2010-3571

<1:1.5.0.12.3-1jpp.1.el5
  • C
CVE-2010-3559

<1:1.5.0.12.2-1jpp.1.el5
  • M
CVE-2010-4475

<1:1.5.0.12.4-1jpp.1.el5
  • M
CVE-2010-4476

<1:1.5.0.12.3-1jpp.2.el5
  • H
CVE-2010-4465

<1:1.5.0.12.4-1jpp.1.el5
  • L
CVE-2010-4450

<1:1.5.0.12.4-1jpp.1.el5
  • L
CVE-2010-4448

<1:1.5.0.12.4-1jpp.1.el5
  • M
CVE-2010-4447

<1:1.5.0.12.4-1jpp.1.el5
  • M
CVE-2010-4466

<1:1.5.0.12.4-1jpp.1.el5
  • M
CVE-2010-4471

<1:1.5.0.12.4-1jpp.1.el5
  • H
CVE-2010-4462

<1:1.5.0.12.4-1jpp.1.el5
  • M
CVE-2010-4468

<1:1.5.0.12.4-1jpp.1.el5
  • H
CVE-2010-4454

<1:1.5.0.12.4-1jpp.1.el5
  • H
CVE-2010-4473

<1:1.5.0.12.4-1jpp.1.el5
  • C
CVE-2011-0873

<1:1.5.0.12.5-1jpp.1.el5
  • C
Integer Overflow or Wraparound

<1:1.5.0.12.5-1jpp.1.el5
  • C
CVE-2011-0814

<1:1.5.0.12.5-1jpp.1.el5
  • M
CVE-2011-0867

<1:1.5.0.12.5-1jpp.1.el5
  • C
CVE-2011-0802

<1:1.5.0.12.5-1jpp.1.el5
  • C
CVE-2011-0871

<1:1.5.0.12.5-1jpp.1.el5
  • L
CVE-2011-0865

<1:1.5.0.12.5-1jpp.1.el5
  • C
CVE-2012-0498

<1:1.5.0.13.1-1jpp.1.el5
  • C
CVE-2012-0499

<1:1.5.0.13.1-1jpp.1.el5
  • C
CVE-2012-1725

<1:1.5.0.14.0-1jpp.1.el5_8
  • L
Incorrect Permission Assignment for Critical Resource

<1:1.5.0.14.0-1jpp.1.el5_8
  • C
CVE-2012-1716

<1:1.5.0.14.0-1jpp.1.el5_8
  • M
CVE-2012-1719

<1:1.5.0.14.0-1jpp.1.el5_8
  • C
CVE-2012-1713

<1:1.5.0.14.0-1jpp.1.el5_8
  • M
CVE-2012-1718

<1:1.5.0.14.0-1jpp.1.el5_8
  • L
CVE-2012-3216

<1:1.5.0.15.0-1jpp.1.el5_8
  • M
CVE-2013-2424

<1:1.5.0.16.2-1jpp.1.el5_9
  • C
Arbitrary Code Injection

<1:1.5.0.16.2-1jpp.1.el5_9
  • C
CVE-2013-2383

<1:1.5.0.16.2-1jpp.1.el5_9
  • C
CVE-2013-1537

<1:1.5.0.16.2-1jpp.1.el5_9
  • M
CVE-2013-2419

<1:1.5.0.16.2-1jpp.1.el5_9
  • C
CVE-2013-2420

<1:1.5.0.16.2-1jpp.1.el5_9
  • C
CVE-2013-1557

<1:1.5.0.16.2-1jpp.1.el5_9
  • M
CVE-2013-2417

<1:1.5.0.16.2-1jpp.1.el5_9
  • H
CVE-2013-2430

<1:1.5.0.16.2-1jpp.1.el5_9
  • C
Arbitrary Code Injection

<1:1.5.0.16.2-1jpp.1.el5_9
  • C
CVE-2013-2384

<1:1.5.0.16.2-1jpp.1.el5_9
  • H
CVE-2013-2429

<1:1.5.0.16.2-1jpp.1.el5_9
  • C
CVE-2013-1569

<1:1.5.0.16.2-1jpp.1.el5_9
  • H
CVE-2013-3009

<1:1.5.0.16.3-1jpp.1.el5_9
  • H
CVE-2013-3011

<1:1.5.0.16.3-1jpp.1.el5_9
  • H
CVE-2013-3012

<1:1.5.0.16.3-1jpp.1.el5_9
  • M
CVE-2013-5375

<1:1.5.0.16.4-1jpp.1.el5_10
  • M
Resource Management Errors

<1:1.5.0.16.4-1jpp.1.el5_10
  • M
Missing Initialization of a Variable

<1:1.5.0.16.6-1jpp.1.el5_10
  • C
CVE-2013-4041

<1:1.5.0.16.4-1jpp.1.el5_10
  • M
Cryptographic Issues

<1:1.5.0.16.6-1jpp.1.el5_10
  • M
Arbitrary Code Injection

<1:1.5.0.16.8-1jpp.1.el5
  • C
CVE-2014-8891

<1:1.5.0.16.9-1jpp.1.el5
  • M
CVE-2014-8892

<1:1.5.0.16.9-1jpp.1.el5
  • C
CVE-2015-0192

<1:1.5.0.16.10-1jpp.1.el5
  • M
Use of a Broken or Risky Cryptographic Algorithm

<1:1.5.0.16.10-1jpp.1.el5
  • M
Information Exposure

<1:1.5.0.16.10-1jpp.1.el5
  • L
Cleartext Storage of Sensitive Information

<1:1.5.0.16.13-1jpp.3.el5
  • M
Access Restriction Bypass

<1:1.5.0.8-1jpp.1.el5
  • C
CVE-2012-0507

<1:1.5.0.13.1-1jpp.1.el5
  • C
CVE-2013-2465

<1:1.5.0.16.3-1jpp.1.el5_9
  • C
Out-of-Bounds

<1:1.5.0.16.0-1jpp.1.el5_9
  • C
CVE-2011-3556

<1:1.5.0.13.0-1jpp.1.el5
  • M
Incorrect Privilege Assignment

<1:1.5.0.16.7-1jpp.1.el5_10
  • M
CVE-2015-4903

<1:1.5.0.16.14-1jpp.1.el5
  • M
CVE-2015-4902

<1:1.5.0.16.14-1jpp.1.el5
  • C
CVE-2015-4860

<1:1.5.0.16.14-1jpp.1.el5
  • C
Improper Initialization

<1:1.5.0.16.14-1jpp.1.el5
  • M
CVE-2015-4872

<1:1.5.0.16.14-1jpp.1.el5
  • C
CVE-2015-4844

<1:1.5.0.16.14-1jpp.1.el5
  • C
Out-of-bounds Write

<1:1.5.0.16.14-1jpp.1.el5
  • C
CVE-2015-4883

<1:1.5.0.16.14-1jpp.1.el5
  • M
CVE-2015-2637

<1:1.5.0.16.13-1jpp.3.el5
  • C
CVE-2015-2590

<1:1.5.0.16.13-1jpp.3.el5
  • C
Out-of-bounds Write

<1:1.5.0.16.13-1jpp.3.el5
  • M
CVE-2015-2664

<1:1.5.0.16.13-1jpp.3.el5
  • C
CVE-2015-4733

<1:1.5.0.16.13-1jpp.3.el5
  • C
Unsynchronized Access to Shared Data in a Multithreaded Context

<1:1.5.0.16.13-1jpp.3.el5
  • M
CVE-2015-2621

<1:1.5.0.16.13-1jpp.3.el5
  • M
Integer Overflow or Wraparound

<1:1.5.0.16.13-1jpp.3.el5
  • M
Improper Check for Certificate Revocation

<1:1.5.0.16.13-1jpp.3.el5
  • M
Missing Release of Resource after Effective Lifetime

<1:1.5.0.16.13-1jpp.3.el5
  • M
Covert Timing Channel

<1:1.5.0.16.13-1jpp.3.el5
  • M
Uncaught Exception

<1:1.5.0.16.10-1jpp.1.el5
  • C
CVE-2015-0459

<1:1.5.0.16.10-1jpp.1.el5
  • L
Directory Traversal

<1:1.5.0.16.10-1jpp.1.el5
  • C
CVE-2015-0491

<1:1.5.0.16.10-1jpp.1.el5
  • M
Loop with Unreachable Exit Condition ('Infinite Loop')

<1:1.5.0.16.9-1jpp.1.el5
  • L
Out-of-bounds Read

<1:1.5.0.16.9-1jpp.1.el5
  • M
CVE-2015-0407

<1:1.5.0.16.9-1jpp.1.el5
  • M
CVE-2014-6593

<1:1.5.0.16.9-1jpp.1.el5
  • C
CVE-2015-0408

<1:1.5.0.16.9-1jpp.1.el5
  • C
CVE-2015-0395

<1:1.5.0.16.9-1jpp.1.el5
  • L
Credentials Management

<1:1.5.0.16.7-1jpp.1.el5_10
  • M
CVE-2014-6511

<1:1.5.0.16.8-1jpp.1.el5
  • L
CVE-2014-6558

<1:1.5.0.16.8-1jpp.1.el5
  • H
CVE-2014-6506

<1:1.5.0.16.8-1jpp.1.el5
  • L
CVE-2014-6502

<1:1.5.0.16.8-1jpp.1.el5
  • M
CVE-2014-4263

<1:1.5.0.16.7-1jpp.1.el5_10
  • M
CVE-2014-4218

<1:1.5.0.16.7-1jpp.1.el5_10
  • C
CVE-2014-4219

<1:1.5.0.16.7-1jpp.1.el5_10
  • M
CVE-2014-4252

<1:1.5.0.16.7-1jpp.1.el5_10
  • M
CVE-2014-4209

<1:1.5.0.16.7-1jpp.1.el5_10
  • M
CVE-2014-4244

<1:1.5.0.16.7-1jpp.1.el5_10
  • H
CVE-2014-0446

<1:1.5.0.16.6-1jpp.1.el5_10
  • M
CVE-2014-0460

<1:1.5.0.16.6-1jpp.1.el5_10
  • H
CVE-2014-2427

<1:1.5.0.16.6-1jpp.1.el5_10
  • M
CVE-2014-2401

<1:1.5.0.16.6-1jpp.1.el5_10
  • H
CVE-2014-2412

<1:1.5.0.16.6-1jpp.1.el5_10
  • M
CVE-2014-0453

<1:1.5.0.16.6-1jpp.1.el5_10
  • H
CVE-2014-0451

<1:1.5.0.16.6-1jpp.1.el5_10
  • C
CVE-2014-0429

<1:1.5.0.16.6-1jpp.1.el5_10
  • C
CVE-2014-2421

<1:1.5.0.16.6-1jpp.1.el5_10
  • C
CVE-2014-0457

<1:1.5.0.16.6-1jpp.1.el5_10
  • L
Insecure Temporary File

<1:1.5.0.16.6-1jpp.1.el5_10
  • M
CVE-2014-0423

<1:1.5.0.16.5-1jpp.1.el5_10
  • C
CVE-2014-0417

<1:1.5.0.16.5-1jpp.1.el5_10
  • M
CVE-2014-0411

<1:1.5.0.16.5-1jpp.1.el5_10
  • M
CVE-2014-0416

<1:1.5.0.16.5-1jpp.1.el5_10
  • C
CVE-2013-5907

<1:1.5.0.16.5-1jpp.1.el5_10
  • M
CVE-2014-0376

<1:1.5.0.16.5-1jpp.1.el5_10
  • M
CVE-2014-0368

<1:1.5.0.16.5-1jpp.1.el5_10
  • C
CVE-2014-0428

<1:1.5.0.16.5-1jpp.1.el5_10
  • H
CVE-2014-0373

<1:1.5.0.16.5-1jpp.1.el5_10
  • C
CVE-2014-0422

<1:1.5.0.16.5-1jpp.1.el5_10
  • C
CVE-2013-5843

<1:1.5.0.16.4-1jpp.1.el5_10
  • M
CVE-2013-5801

<1:1.5.0.16.4-1jpp.1.el5_10
  • M
CVE-2013-5774

<1:1.5.0.16.4-1jpp.1.el5_10
  • C
CVE-2013-5814

<1:1.5.0.16.4-1jpp.1.el5_10
  • C
CVE-2013-5842

<1:1.5.0.16.4-1jpp.1.el5_10
  • C
CVE-2013-5829

<1:1.5.0.16.4-1jpp.1.el5_10
  • M
CVE-2013-5783

<1:1.5.0.16.4-1jpp.1.el5_10
  • C
CVE-2013-5817

<1:1.5.0.16.4-1jpp.1.el5_10
  • M
CVE-2013-5825

<1:1.5.0.16.4-1jpp.1.el5_10
  • M
CVE-2013-5804

<1:1.5.0.16.4-1jpp.1.el5_10
  • C
CVE-2013-5809

<1:1.5.0.16.4-1jpp.1.el5_10
  • H
CVE-2013-5802

<1:1.5.0.16.4-1jpp.1.el5_10
  • M
CVE-2013-3829

<1:1.5.0.16.4-1jpp.1.el5_10
  • C
CVE-2013-5830

<1:1.5.0.16.4-1jpp.1.el5_10
  • M
CVE-2013-5840

<1:1.5.0.16.4-1jpp.1.el5_10
  • L
CVE-2013-5803

<1:1.5.0.16.4-1jpp.1.el5_10
  • C
CVE-2013-5782

<1:1.5.0.16.4-1jpp.1.el5_10
  • M
CVE-2013-5780

<1:1.5.0.16.4-1jpp.1.el5_10
  • M
CVE-2013-5849

<1:1.5.0.16.4-1jpp.1.el5_10
  • M
CVE-2013-5790

<1:1.5.0.16.4-1jpp.1.el5_10
  • L
CVE-2013-5797

<1:1.5.0.16.4-1jpp.1.el5_10
  • C
CVE-2013-2464

<1:1.5.0.16.3-1jpp.1.el5_9
  • M
CVE-2013-2457

<1:1.5.0.16.3-1jpp.1.el5_9
  • C
CVE-2013-3743

<1:1.5.0.16.3-1jpp.1.el5_9
  • M
CVE-2013-2450

<1:1.5.0.16.3-1jpp.1.el5_9
  • M
CVE-2013-2447

<1:1.5.0.16.3-1jpp.1.el5_9
  • M
CVE-2013-2452

<1:1.5.0.16.3-1jpp.1.el5_9
  • M
CVE-2013-2455

<1:1.5.0.16.3-1jpp.1.el5_9
  • M
CVE-2013-2443

<1:1.5.0.16.3-1jpp.1.el5_9
  • M
CVE-2013-2456

<1:1.5.0.16.3-1jpp.1.el5_9
  • M
CVE-2013-2448

<1:1.5.0.16.3-1jpp.1.el5_9
  • M
CVE-2013-2454

<1:1.5.0.16.3-1jpp.1.el5_9
  • C
CVE-2013-2471

<1:1.5.0.16.3-1jpp.1.el5_9
  • C
CVE-2013-2470

<1:1.5.0.16.3-1jpp.1.el5_9
  • C
Integer Overflow or Wraparound

<1:1.5.0.16.3-1jpp.1.el5_9
  • C
CVE-2013-2472

<1:1.5.0.16.3-1jpp.1.el5_9
  • M
CVE-2013-2446

<1:1.5.0.16.3-1jpp.1.el5_9
  • C
CVE-2013-2469

<1:1.5.0.16.3-1jpp.1.el5_9
  • C
CVE-2013-2473

<1:1.5.0.16.3-1jpp.1.el5_9
  • M
CVE-2013-2444

<1:1.5.0.16.3-1jpp.1.el5_9
  • C
CVE-2013-2463

<1:1.5.0.16.3-1jpp.1.el5_9
  • H
CVE-2013-2394

<1:1.5.0.16.2-1jpp.1.el5_9
  • C
CVE-2013-2432

<1:1.5.0.16.2-1jpp.1.el5_9
  • C
Integer Overflow or Wraparound

<1:1.5.0.16.0-1jpp.1.el5_9
  • C
CVE-2013-1486

<1:1.5.0.16.0-1jpp.1.el5_9
  • C
CVE-2013-0426

<1:1.5.0.16.0-1jpp.1.el5_9
  • M
CVE-2013-0434

<1:1.5.0.16.0-1jpp.1.el5_9
  • C
CVE-2013-1476

<1:1.5.0.16.0-1jpp.1.el5_9
  • M
CVE-2013-0432

<1:1.5.0.16.0-1jpp.1.el5_9
  • C
CVE-2013-0428

<1:1.5.0.16.0-1jpp.1.el5_9
  • M
CVE-2013-0427

<1:1.5.0.16.0-1jpp.1.el5_9
  • M
CVE-2013-0433

<1:1.5.0.16.0-1jpp.1.el5_9
  • M
CVE-2013-0409

<1:1.5.0.16.0-1jpp.1.el5_9
  • M
CVE-2013-0443

<1:1.5.0.16.0-1jpp.1.el5_9
  • C
CVE-2013-1481

<1:1.5.0.16.0-1jpp.1.el5_9
  • C
CVE-2013-0425

<1:1.5.0.16.0-1jpp.1.el5_9
  • C
CVE-2013-1478

<1:1.5.0.16.0-1jpp.1.el5_9
  • M
Cross-site Scripting (XSS)

<1:1.5.0.16.0-1jpp.1.el5_9
  • C
CVE-2013-0442

<1:1.5.0.16.0-1jpp.1.el5_9
  • C
CVE-2013-0445

<1:1.5.0.16.0-1jpp.1.el5_9
  • C
CVE-2013-1480

<1:1.5.0.16.0-1jpp.1.el5_9
  • C
CVE-2013-0450

<1:1.5.0.16.0-1jpp.1.el5_9
  • H
CVE-2012-4822

<1:1.5.0.15.0-1jpp.1.el5_8
  • H
CVE-2012-4820

<1:1.5.0.15.0-1jpp.1.el5_8
  • H
CVE-2012-5089

<1:1.5.0.15.0-1jpp.1.el5_8
  • C
CVE-2012-1531

<1:1.5.0.15.0-1jpp.1.el5_8
  • M
CVE-2012-5079

<1:1.5.0.15.0-1jpp.1.el5_8
  • H
CVE-2012-5084

<1:1.5.0.15.0-1jpp.1.el5_8
  • C
CVE-2012-3143

<1:1.5.0.15.0-1jpp.1.el5_8
  • M
CVE-2012-5075

<1:1.5.0.15.0-1jpp.1.el5_8
  • C
CVE-2012-5083

<1:1.5.0.15.0-1jpp.1.el5_8
  • H
CVE-2012-5071

<1:1.5.0.15.0-1jpp.1.el5_8
  • L
CVE-2012-5085

<1:1.5.0.16.0-1jpp.1.el5_9
  • H
CVE-2012-5069

<1:1.5.0.15.0-1jpp.1.el5_8
  • C
CVE-2013-1475

<1:1.5.0.15.0-1jpp.1.el5_8
  • M
CVE-2012-5073

<1:1.5.0.15.0-1jpp.1.el5_8
  • M
CVE-2013-0440

<1:1.5.0.16.0-1jpp.1.el5_9
  • M
CVE-2012-5081

<1:1.5.0.15.0-1jpp.1.el5_8
  • M
CVE-2011-3563

<1:1.5.0.13.1-1jpp.1.el5
  • C
CVE-2012-0505

<1:1.5.0.13.1-1jpp.1.el5
  • M
CVE-2012-0506

<1:1.5.0.13.1-1jpp.1.el5
  • M
CVE-2012-0502

<1:1.5.0.13.1-1jpp.1.el5
  • C
CVE-2012-0503

<1:1.5.0.13.1-1jpp.1.el5
  • L
Off-by-one Error

<1:1.5.0.13.1-1jpp.1.el5
  • C
CVE-2011-3545

<1:1.5.0.13.0-1jpp.1.el5
  • C
CVE-2011-3548

<1:1.5.0.13.0-1jpp.1.el5
  • M
CVE-2011-3560

<1:1.5.0.13.1-1jpp.1.el5
  • M
CVE-2011-3547

<1:1.5.0.13.0-1jpp.1.el5
  • C
CVE-2011-3549

<1:1.5.0.13.0-1jpp.1.el5
  • L
CVE-2011-3552

<1:1.5.0.13.0-1jpp.1.el5
  • H
CVE-2011-3557

<1:1.5.0.13.1-1jpp.1.el5
  • C
CVE-2011-3554

<1:1.5.0.13.0-1jpp.1.el5
  • L
Directory Traversal

<1:1.5.0.16.10-1jpp.1.el5
  • M
Inadequate Encryption Strength

<1:1.5.0.13.1-1jpp.1.el5
  • M
Time-of-check Time-of-use (TOCTOU)

<1:1.5.0.11.1-1jpp.3.el5
  • C
Off-by-one Error

<1:1.5.0.16.10-1jpp.1.el5
  • H
Access Restriction Bypass

<1:1.5.0.10-1jpp.4.el5
  • M
Man-in-the-Middle (MitM)

<1:1.5.0.11.1-1jpp.3.el5
  • H
NULL Pointer Dereference

<1:1.5.0.12.2-1jpp.1.el5
  • C
CVE-2014-4262

<1:1.5.0.16.7-1jpp.1.el5_10
  • L
Insufficient Verification of Data Authenticity

<1:1.5.0.16.8-1jpp.1.el5
  • L
CVE-2014-2398

<1:1.5.0.16.6-1jpp.1.el5_10
  • L
Improperly Implemented Security Check for Standard

<1:1.5.0.16.10-1jpp.1.el5
  • M
Improper Input Validation

<1:1.5.0.16.14-1jpp.1.el5
  • L
CVE-2013-1500

<1:1.5.0.16.3-1jpp.1.el5_9
  • M
CVE-2013-1571

<1:1.5.0.16.3-1jpp.1.el5_9
  • L
Arbitrary Code Injection

<1:1.5.0.16.5-1jpp.1.el5_10
  • M
Cryptographic Issues

<1:1.5.0.16.2-1jpp.1.el5_9
  • M
Use of a Broken or Risky Cryptographic Algorithm

<1:1.5.0.16.10-1jpp.1.el5
  • M
Use of a Broken or Risky Cryptographic Algorithm

<1:1.5.0.16.13-1jpp.3.el5