Homepage

java-1.7.0-ibm-devel

Report a new vulnerability Found a mistake?

Direct Vulnerabilities

Known vulnerabilities in the java-1.7.0-ibm-devel 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.7.0.8.0-1jpp.1.el5
  • H
Covert Timing Channel

<1:1.7.0.10.1-1jpp.1.el5_11
  • C
CVE-2013-0441

<1:1.7.0.4.0-1jpp.2.el5_9
  • M
CVE-2014-4266

<1:1.7.0.7.1-1jpp.1.el5_10
  • M
CVE-2014-6531

<1:1.7.0.8.0-1jpp.1.el5
  • C
CVE-2017-3272

<1:1.7.0.10.1-1jpp.1.el5_11
  • C
CVE-2015-2638

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

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

<1:1.7.0.8.0-1jpp.1.el5
  • H
CVE-2013-5878

<1:1.7.0.6.1-1jpp.1.el5_10
  • M
Out-of-bounds Read

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

<1:1.7.0.5.0-1jpp.2.el5_9
  • C
CVE-2015-4835

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

<1:1.7.0.9.30-1jpp.1.el5
  • C
CVE-2015-4731

<1:1.7.0.9.10-1jpp.2.el5
  • M
CVE-2015-0477

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

<1:1.7.0.10.1-1jpp.1.el5_11
  • M
CVE-2013-2424

<1:1.7.0.4.2-1jpp.1.el5_9
  • C
Access Restriction Bypass

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

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

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

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

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

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

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

<1:1.7.0.4.2-1jpp.1.el5_9
  • L
Incorrect Permission Assignment for Critical Resource

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

<1:1.7.0.4.2-1jpp.1.el5_9
  • C
CVE-2013-1558

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

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

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

<1:1.7.0.4.2-1jpp.1.el5_9
  • C
CVE-2013-2422

<1:1.7.0.4.2-1jpp.1.el5_9
  • C
CVE-2013-2426

<1:1.7.0.4.2-1jpp.1.el5_9
  • C
CVE-2013-2436

<1:1.7.0.4.2-1jpp.1.el5_9
  • H
CVE-2013-3006

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

<1:1.7.0.4.2-1jpp.1.el5_9
  • H
CVE-2013-3007

<1:1.7.0.5.0-1jpp.2.el5_9
  • H
CVE-2013-3008

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

<1:1.7.0.5.0-1jpp.2.el5_9
  • H
CVE-2013-3010

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

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

<1:1.7.0.5.0-1jpp.2.el5_9
  • C
CVE-2013-5457

<1:1.7.0.6.0-1jpp.1.el5_10
  • C
CVE-2013-5458

<1:1.7.0.6.0-1jpp.1.el5_10
  • M
CVE-2013-5375

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

<1:1.7.0.6.0-1jpp.1.el5_10
  • C
CVE-2013-5456

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

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

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

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

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

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

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

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

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

<1:1.7.0.9.0-1jpp.1.el5
  • M
Buffer Overflow

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

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

<1:1.7.0.9.10-1jpp.2.el5
  • M
Buffer Overflow

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

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

<1:1.7.0.9.30-1jpp.1.el5
  • H
Covert Timing Channel

<1:1.7.0.10.1-1jpp.1.el5_11
  • C
CVE-2017-3289

<1:1.7.0.10.1-1jpp.1.el5_11
  • C
Deserialization of Untrusted Data

<1:1.7.0.10.1-1jpp.1.el5_11
  • M
Allocation of Resources Without Limits or Throttling

<1:1.7.0.10.1-1jpp.1.el5_11
  • M
Improper Input Validation

<1:1.7.0.10.1-1jpp.1.el5_11
  • M
Improper Input Validation

<1:1.7.0.10.1-1jpp.1.el5_11
  • M
Improper Input Validation

<1:1.7.0.10.1-1jpp.1.el5_11
  • M
Integer Overflow or Wraparound

<1:1.7.0.10.1-1jpp.1.el5_11
  • M
Information Exposure

<1:1.7.0.10.1-1jpp.1.el5_11
  • C
Arbitrary Code Injection

<1:1.7.0.4.2-1jpp.1.el5_9
  • C
CVE-2013-2465

<1:1.7.0.5.0-1jpp.2.el5_9
  • M
CVE-2013-0431

<1:1.7.0.4.0-1jpp.2.el5_9
  • C
CVE-2013-2460

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

<1:1.7.0.4.0-1jpp.2.el5_9
  • M
CVE-2017-3259

<1:1.7.0.10.1-1jpp.1.el5_11
  • M
CVE-2016-5554

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

<1:1.7.0.9.60-1jpp.1.el5_11
  • C
Improper Access Control

<1:1.7.0.9.60-1jpp.1.el5_11
  • M
Cleartext Transmission of Sensitive Information

<1:1.7.0.9.60-1jpp.1.el5_11
  • H
Improper Input Validation

<1:1.7.0.9.60-1jpp.1.el5_11
  • M
CVE-2016-3511

<1:1.7.0.9.50-1jpp.1.el5_11
  • C
CVE-2016-3598

<1:1.7.0.9.50-1jpp.1.el5_11
  • C
CVE-2016-0376

<1:1.7.0.9.40-1jpp.1.el5
  • H
Buffer Overflow

<1:1.7.0.9.40-1jpp.1.el5
  • M
CVE-2016-3422

<1:1.7.0.9.40-1jpp.1.el5
  • C
CVE-2016-3427

<1:1.7.0.9.40-1jpp.1.el5
  • C
CVE-2016-3443

<1:1.7.0.9.40-1jpp.1.el5
  • H
CVE-2016-3449

<1:1.7.0.9.40-1jpp.1.el5
  • L
CVE-2016-3426

<1:1.7.0.9.40-1jpp.1.el5
  • C
CVE-2016-0686

<1:1.7.0.9.40-1jpp.1.el5
  • C
CVE-2016-0687

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

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

<1:1.7.0.7.1-1jpp.1.el5_10
  • C
Incorrect Conversion between Numeric Types

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

<1:1.7.0.9.30-1jpp.1.el5
  • M
CVE-2016-0466

<1:1.7.0.9.30-1jpp.1.el5
  • M
CVE-2016-0402

<1:1.7.0.9.30-1jpp.1.el5
  • M
Information Exposure Through Log Files

<1:1.7.0.9.30-1jpp.1.el5
  • M
CVE-2015-4903

<1:1.7.0.9.20-1jpp.1.el5
  • M
Allocation of Resources Without Limits or Throttling

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

<1:1.7.0.9.20-1jpp.1.el5
  • M
Algorithmic Complexity

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

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

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

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

<1:1.7.0.9.20-1jpp.1.el5
  • M
CVE-2015-4882

<1:1.7.0.9.20-1jpp.1.el5
  • M
CVE-2015-4871

<1:1.7.0.9.20-1jpp.1.el5
  • H
CVE-2015-4810

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

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

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

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

<1:1.7.0.9.20-1jpp.1.el5
  • M
CVE-2015-2619

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

<1:1.7.0.9.10-1jpp.2.el5
  • C
CVE-2015-2590

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

<1:1.7.0.9.10-1jpp.2.el5
  • C
CVE-2015-4736

<1:1.7.0.9.10-1jpp.2.el5
  • M
CVE-2015-4729

<1:1.7.0.9.10-1jpp.2.el5
  • M
Improperly Implemented Security Check for Standard

<1:1.7.0.9.10-1jpp.2.el5
  • M
CVE-2015-2664

<1:1.7.0.9.10-1jpp.2.el5
  • C
CVE-2015-4733

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

<1:1.7.0.9.10-1jpp.2.el5
  • M
CVE-2015-2621

<1:1.7.0.9.10-1jpp.2.el5
  • M
Integer Overflow or Wraparound

<1:1.7.0.9.10-1jpp.2.el5
  • M
Improper Check for Certificate Revocation

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

<1:1.7.0.9.10-1jpp.2.el5
  • M
Covert Timing Channel

<1:1.7.0.9.10-1jpp.2.el5
  • L
Improper Certificate Validation

<1:1.7.0.9.10-1jpp.2.el5
  • H
CVE-2015-0458

<1:1.7.0.9.0-1jpp.1.el5
  • M
Uncaught Exception

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

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

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

<1:1.7.0.9.0-1jpp.1.el5
  • M
CVE-2015-0406

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

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

<1:1.7.0.8.10-1jpp.4.el5
  • H
CVE-2015-0403

<1:1.7.0.8.10-1jpp.4.el5
  • L
NULL Pointer Dereference

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

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

<1:1.7.0.8.10-1jpp.4.el5
  • C
CVE-2014-6549

<1:1.7.0.8.10-1jpp.4.el5
  • C
CVE-2015-0412

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

<1:1.7.0.8.10-1jpp.4.el5
  • L
Credentials Management

<1:1.7.0.7.1-1jpp.1.el5_10
  • M
CVE-2014-6476

<1:1.7.0.8.0-1jpp.1.el5
  • M
CVE-2014-6515

<1:1.7.0.8.0-1jpp.1.el5
  • C
CVE-2014-6503

<1:1.7.0.8.0-1jpp.1.el5
  • M
CVE-2014-6458

<1:1.7.0.8.0-1jpp.1.el5
  • C
CVE-2014-6532

<1:1.7.0.8.0-1jpp.1.el5
  • L
CVE-2014-6527

<1:1.7.0.8.0-1jpp.1.el5
  • C
CVE-2014-6456

<1:1.7.0.8.0-1jpp.1.el5
  • M
CVE-2014-6511

<1:1.7.0.8.0-1jpp.1.el5
  • H
CVE-2014-6493

<1:1.7.0.8.0-1jpp.1.el5
  • H
CVE-2014-6492

<1:1.7.0.8.0-1jpp.1.el5
  • H
CVE-2014-4288

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

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

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

<1:1.7.0.8.0-1jpp.1.el5
  • C
CVE-2014-4227

<1:1.7.0.7.1-1jpp.1.el5_10
  • M
CVE-2014-4265

<1:1.7.0.7.1-1jpp.1.el5_10
  • M
CVE-2014-4221

<1:1.7.0.7.1-1jpp.1.el5_10
  • M
CVE-2014-4263

<1:1.7.0.7.1-1jpp.1.el5_10
  • L
CVE-2014-4208

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

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

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

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

<1:1.7.0.7.1-1jpp.1.el5_10
  • M
CVE-2014-4220

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

<1:1.7.0.7.1-1jpp.1.el5_10
  • H
CVE-2014-0448

<1:1.7.0.7.0-1jpp.1.el5_10
  • H
CVE-2014-2428

<1:1.7.0.7.0-1jpp.1.el5_10
  • M
CVE-2014-0449

<1:1.7.0.7.0-1jpp.1.el5_10
  • H
CVE-2014-0454

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

<1:1.7.0.7.0-1jpp.1.el5_10
  • M
CVE-2014-2409

<1:1.7.0.7.0-1jpp.1.el5_10
  • L
CVE-2014-2420

<1:1.7.0.7.0-1jpp.1.el5_10
  • M
CVE-2014-0459

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

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

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

<1:1.7.0.7.0-1jpp.1.el5_10
  • H
CVE-2014-2414

<1:1.7.0.7.0-1jpp.1.el5_10
  • C
CVE-2014-0455

<1:1.7.0.7.0-1jpp.1.el5_10
  • H
CVE-2014-0458

<1:1.7.0.7.0-1jpp.1.el5_10
  • H
CVE-2014-0452

<1:1.7.0.7.0-1jpp.1.el5_10
  • H
CVE-2014-2402

<1:1.7.0.7.0-1jpp.1.el5_10
  • C
CVE-2014-0461

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

<1:1.7.0.7.0-1jpp.1.el5_10
  • H
CVE-2014-2423

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

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

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

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

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

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

<1:1.7.0.7.0-1jpp.1.el5_10
  • M
CVE-2013-5888

<1:1.7.0.6.1-1jpp.1.el5_10
  • M
CVE-2013-5898

<1:1.7.0.6.1-1jpp.1.el5_10
  • M
CVE-2014-0403

<1:1.7.0.6.1-1jpp.1.el5_10
  • H
CVE-2014-0424

<1:1.7.0.6.1-1jpp.1.el5_10
  • C
CVE-2013-5889

<1:1.7.0.6.1-1jpp.1.el5_10
  • M
CVE-2013-5887

<1:1.7.0.6.1-1jpp.1.el5_10
  • C
CVE-2014-0410

<1:1.7.0.6.1-1jpp.1.el5_10
  • M
CVE-2014-0375

<1:1.7.0.6.1-1jpp.1.el5_10
  • M
CVE-2013-5899

<1:1.7.0.6.1-1jpp.1.el5_10
  • C
CVE-2014-0415

<1:1.7.0.6.1-1jpp.1.el5_10
  • H
CVE-2014-0387

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

<1:1.7.0.6.1-1jpp.1.el5_10
  • M
CVE-2013-5896

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

<1:1.7.0.6.1-1jpp.1.el5_10
  • M
CVE-2013-5884

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

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

<1:1.7.0.6.1-1jpp.1.el5_10
  • M
CVE-2013-5910

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

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

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

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

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

<1:1.7.0.6.1-1jpp.1.el5_10
  • L
CVE-2013-6954

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

<1:1.7.0.6.1-1jpp.1.el5_10
  • C
CVE-2013-5789

<1:1.7.0.6.0-1jpp.1.el5_10
  • M
CVE-2013-5818

<1:1.7.0.6.0-1jpp.1.el5_10
  • M
CVE-2013-5776

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

<1:1.7.0.6.0-1jpp.1.el5_10
  • C
CVE-2013-5832

<1:1.7.0.6.0-1jpp.1.el5_10
  • M
CVE-2013-5812

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

<1:1.7.0.6.0-1jpp.1.el5_10
  • M
CVE-2013-5831

<1:1.7.0.6.0-1jpp.1.el5_10
  • M
CVE-2013-5848

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

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

<1:1.7.0.6.0-1jpp.1.el5_10
  • M
CVE-2013-5823

<1:1.7.0.6.0-1jpp.1.el5_10
  • M
CVE-2013-5819

<1:1.7.0.6.0-1jpp.1.el5_10
  • C
CVE-2013-5838

<1:1.7.0.6.0-1jpp.1.el5_10
  • C
CVE-2013-5787

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

<1:1.7.0.6.0-1jpp.1.el5_10
  • C
CVE-2013-5850

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

<1:1.7.0.6.0-1jpp.1.el5_10
  • C
CVE-2013-5824

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

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

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

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

<1:1.7.0.6.0-1jpp.1.el5_10
  • C
CVE-2013-5788

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

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

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

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

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

<1:1.7.0.6.0-1jpp.1.el5_10
  • M
CVE-2013-5851

<1:1.7.0.6.0-1jpp.1.el5_10
  • M
CVE-2013-5820

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

<1:1.7.0.6.0-1jpp.1.el5_10
  • L
CVE-2013-5772

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

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

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

<1:1.7.0.6.0-1jpp.1.el5_10
  • M
CVE-2013-5784

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

<1:1.7.0.6.0-1jpp.1.el5_10
  • M
CVE-2013-5800

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

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

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

<1:1.7.0.5.0-1jpp.2.el5_9
  • M
CVE-2013-2400

<1:1.7.0.5.0-1jpp.2.el5_9
  • M
CVE-2013-2437

<1:1.7.0.5.0-1jpp.2.el5_9
  • C
CVE-2013-2462

<1:1.7.0.5.0-1jpp.2.el5_9
  • C
CVE-2013-2468

<1:1.7.0.5.0-1jpp.2.el5_9
  • H
CVE-2013-2442

<1:1.7.0.5.0-1jpp.2.el5_9
  • M
CVE-2013-3744

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

<1:1.7.0.5.0-1jpp.2.el5_9
  • M
CVE-2013-2453

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

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

<1:1.7.0.5.0-1jpp.2.el5_9
  • C
CVE-2013-2466

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

<1:1.7.0.5.0-1jpp.2.el5_9
  • L
CVE-2013-2451

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

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

<1:1.7.0.5.0-1jpp.2.el5_9
  • M
CVE-2013-2449

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

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

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

<1:1.7.0.5.0-1jpp.2.el5_9
  • M
CVE-2013-2458

<1:1.7.0.5.0-1jpp.2.el5_9
  • M
CVE-2013-2407

<1:1.7.0.5.0-1jpp.2.el5_9
  • M
CVE-2013-2412

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

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

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

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

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

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

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

<1:1.7.0.5.0-1jpp.2.el5_9
  • C
CVE-2013-2434

<1:1.7.0.4.2-1jpp.1.el5_9
  • C
CVE-2013-2435

<1:1.7.0.4.2-1jpp.1.el5_9
  • C
CVE-2013-2440

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

<1:1.7.0.4.2-1jpp.1.el5_9
  • M
CVE-2013-2418

<1:1.7.0.4.2-1jpp.1.el5_9
  • M
CVE-2013-1563

<1:1.7.0.4.2-1jpp.1.el5_9
  • M
CVE-2013-2416

<1:1.7.0.4.2-1jpp.1.el5_9
  • M
CVE-2013-1540

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

<1:1.7.0.4.2-1jpp.1.el5_9
  • M
CVE-2013-2433

<1:1.7.0.4.2-1jpp.1.el5_9
  • C
CVE-2013-2438

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

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

<1:1.7.0.4.0-1jpp.2.el5_9
  • M
CVE-2013-1485

<1:1.7.0.4.0-1jpp.2.el5_9
  • C
CVE-2013-1484

<1:1.7.0.4.0-1jpp.2.el5_9
  • C
CVE-2013-1487

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

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

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

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

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

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

<1:1.7.0.4.0-1jpp.2.el5_9
  • C
CVE-2013-0444

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

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

<1:1.7.0.4.0-1jpp.2.el5_9
  • C
CVE-2012-3213

<1:1.7.0.4.0-1jpp.2.el5_9
  • C
CVE-2012-3342

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

<1:1.7.0.4.0-1jpp.2.el5_9
  • M
CVE-2013-0419

<1:1.7.0.4.0-1jpp.2.el5_9
  • C
CVE-2013-0437

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

<1:1.7.0.4.0-1jpp.2.el5_9
  • C
CVE-2013-0446

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

<1:1.7.0.4.0-1jpp.2.el5_9
  • M
CVE-2013-0435

<1:1.7.0.4.0-1jpp.2.el5_9
  • M
CVE-2013-0438

<1:1.7.0.4.0-1jpp.2.el5_9
  • M
CVE-2013-1473

<1:1.7.0.4.0-1jpp.2.el5_9
  • C
CVE-2012-1541

<1:1.7.0.4.0-1jpp.2.el5_9
  • M
CVE-2013-0423

<1:1.7.0.4.0-1jpp.2.el5_9
  • H
CVE-2013-0351

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

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

<1:1.7.0.4.0-1jpp.2.el5_9
  • M
CVE-2013-0449

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

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

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

<1:1.7.0.4.0-1jpp.2.el5_9
  • L
CVE-2012-5085

<1:1.7.0.4.0-1jpp.2.el5_9
  • M
CVE-2013-0440

<1:1.7.0.4.0-1jpp.2.el5_9
  • L
Directory Traversal

<1:1.7.0.9.0-1jpp.1.el5
  • M
Allocation of Resources Without Limits or Throttling

<1:1.7.0.10.1-1jpp.1.el5_11
  • C
Off-by-one Error

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

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

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

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

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

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

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

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

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

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

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

<1:1.7.0.9.0-1jpp.1.el5
  • M
Improper Data Handling

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

<1:1.7.0.9.10-1jpp.2.el5
  • C
CVE-2013-0422

<1:1.7.0.4.0-1jpp.2.el5_9
  • M
CVE-2013-2423

<1:1.7.0.4.2-1jpp.1.el5_9