mariadb-embedded-devel vulnerabilities

Direct Vulnerabilities

Known vulnerabilities in the mariadb-embedded-devel package. This does not include vulnerabilities belonging to this package’s dependencies.

How to fix?

Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.

Fix for free
VulnerabilityVulnerable Version
  • M
CVE-2021-2144

<1:5.5.68-1.el7
  • M
CVE-2020-2812

<1:5.5.68-1.el7
  • M
CVE-2020-2780

<1:5.5.68-1.el7
  • M
CVE-2020-2752

<1:5.5.68-1.el7
  • M
Resource Exhaustion

<1:5.5.68-1.el7
  • M
CVE-2019-2974

<1:5.5.68-1.el7
  • M
CVE-2021-2007

<1:5.5.65-1.el7
  • M
Information Exposure

<1:5.5.65-1.el7
  • M
CVE-2019-2805

<1:5.5.65-1.el7
  • M
CVE-2019-2740

<1:5.5.65-1.el7
  • M
CVE-2019-2739

<1:5.5.65-1.el7
  • M
CVE-2019-2737

<1:5.5.65-1.el7
  • M
CVE-2021-2011

<1:5.5.64-1.el7
  • M
CVE-2020-14550

<1:5.5.64-1.el7
  • M
CVE-2019-2627

<1:5.5.64-1.el7
  • M
CVE-2019-2614

<1:5.5.64-1.el7
  • M
CVE-2019-2529

<1:5.5.64-1.el7
  • M
CVE-2019-2503

<1:5.5.64-1.el7
  • M
CVE-2018-3282

<1:5.5.64-1.el7
  • M
CVE-2018-3081

<1:5.5.64-1.el7
  • M
CVE-2018-3066

<1:5.5.64-1.el7
  • M
CVE-2018-3063

<1:5.5.64-1.el7
  • M
CVE-2018-3058

<1:5.5.64-1.el7
  • M
CVE-2019-2455

<1:5.5.60-1.el7_5
  • M
CVE-2018-3133

<1:5.5.60-1.el7_5
  • M
CVE-2018-2819

<1:5.5.60-1.el7_5
  • M
CVE-2018-2817

<1:5.5.60-1.el7_5
  • M
CVE-2018-2813

<1:5.5.60-1.el7_5
  • M
CVE-2018-2781

<1:5.5.60-1.el7_5
  • M
CVE-2018-2771

<1:5.5.60-1.el7_5
  • M
Missing Required Cryptographic Step

<1:5.5.60-1.el7_5
  • M
CVE-2018-2761

<1:5.5.60-1.el7_5
  • M
CVE-2018-2755

<1:5.5.60-1.el7_5
  • M
CVE-2018-2668

<1:5.5.60-1.el7_5
  • M
CVE-2018-2665

<1:5.5.60-1.el7_5
  • M
CVE-2018-2640

<1:5.5.60-1.el7_5
  • M
CVE-2018-2622

<1:5.5.60-1.el7_5
  • M
CVE-2018-2562

<1:5.5.60-1.el7_5
  • M
CVE-2017-3653

<1:5.5.60-1.el7_5
  • M
CVE-2017-3641

<1:5.5.60-1.el7_5
  • M
CVE-2017-3636

<1:5.5.60-1.el7_5
  • M
CVE-2017-10384

<1:5.5.60-1.el7_5
  • M
Information Exposure

<1:5.5.60-1.el7_5
  • M
CVE-2017-10378

<1:5.5.60-1.el7_5
  • M
Information Exposure

<1:5.5.60-1.el7_5
  • H
CVE-2016-8283

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:5.5.52-1.el7
  • H
CVE-2016-5629

<1:5.5.52-1.el7
  • H
CVE-2016-5626

<1:5.5.52-1.el7
  • H
CVE-2016-5624

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
CVE-2016-5612

<1:5.5.52-1.el7
  • H
CVE-2016-3492

<1:5.5.52-1.el7
  • M
CVE-2017-3651

<1:5.5.60-1.el7_5
  • M
Arbitrary Command Injection

<1:5.5.56-2.el7
  • M
CVE-2017-3464

<1:5.5.56-2.el7
  • M
CVE-2017-3456

<1:5.5.56-2.el7
  • M
CVE-2017-3453

<1:5.5.56-2.el7
  • M
CVE-2017-3318

<1:5.5.56-2.el7
  • M
CVE-2017-3317

<1:5.5.56-2.el7
  • M
Information Exposure

<1:5.5.56-2.el7
  • M
CVE-2017-3312

<1:5.5.56-2.el7
  • M
CVE-2017-3309

<1:5.5.56-2.el7
  • M
CVE-2017-3308

<1:5.5.56-2.el7
  • M
Use After Free

<1:5.5.56-2.el7
  • M
Untrusted Search Path

<1:5.5.56-2.el7
  • M
Link Following

<1:5.5.56-2.el7
  • M
Improper Input Validation

<1:5.5.56-2.el7
  • M
CVE-2017-3244

<1:5.5.56-2.el7
  • M
CVE-2017-3243

<1:5.5.56-2.el7
  • M
CVE-2017-3238

<1:5.5.56-2.el7
  • M
Link Following

<1:5.5.56-2.el7
  • M
CVE-2016-5617

<1:5.5.56-2.el7
  • M
Arbitrary Command Injection

<1:5.5.56-2.el7
  • H
CVE-2016-5444

<1:5.5.50-1.el7_2
  • H
CVE-2016-5440

<1:5.5.50-1.el7_2
  • H
CVE-2016-3615

<1:5.5.50-1.el7_2
  • H
CVE-2016-3521

<1:5.5.50-1.el7_2
  • H
CVE-2016-3477

<1:5.5.50-1.el7_2
  • H
CVE-2016-3452

<1:5.5.50-1.el7_2
  • H
CVE-2016-0666

<1:5.5.50-1.el7_2
  • H
CVE-2016-0650

<1:5.5.50-1.el7_2
  • H
CVE-2016-0649

<1:5.5.50-1.el7_2
  • H
CVE-2016-0648

<1:5.5.50-1.el7_2
  • H
CVE-2016-0647

<1:5.5.50-1.el7_2
  • H
CVE-2016-0646

<1:5.5.50-1.el7_2
  • H
CVE-2016-0644

<1:5.5.50-1.el7_2
  • H
CVE-2016-0643

<1:5.5.50-1.el7_2
  • H
CVE-2016-0641

<1:5.5.50-1.el7_2
  • H
CVE-2016-0640

<1:5.5.50-1.el7_2
  • M
CVE-2016-3471

<1:5.5.47-1.el7_2
  • M
Improper Certificate Validation

<1:5.5.47-1.el7_2
  • M
CVE-2016-0651

<1:5.5.47-1.el7_2
  • M
CVE-2016-0642

<1:5.5.47-1.el7_2
  • M
CVE-2016-0616

<1:5.5.47-1.el7_2
  • M
CVE-2016-0609

<1:5.5.47-1.el7_2
  • M
CVE-2016-0608

<1:5.5.47-1.el7_2
  • M
CVE-2016-0606

<1:5.5.47-1.el7_2
  • M
CVE-2016-0600

<1:5.5.47-1.el7_2
  • M
CVE-2016-0598

<1:5.5.47-1.el7_2
  • M
CVE-2016-0597

<1:5.5.47-1.el7_2
  • M
CVE-2016-0596

<1:5.5.47-1.el7_2
  • M
Buffer Overflow

<1:5.5.47-1.el7_2
  • M
CVE-2016-0505

<1:5.5.47-1.el7_2
  • M
CVE-2015-4913

<1:5.5.47-1.el7_2
  • M
CVE-2015-4879

<1:5.5.47-1.el7_2
  • M
CVE-2015-4870

<1:5.5.47-1.el7_2
  • M
CVE-2015-4861

<1:5.5.47-1.el7_2
  • M
CVE-2015-4858

<1:5.5.47-1.el7_2
  • M
CVE-2015-4836

<1:5.5.47-1.el7_2
  • M
CVE-2015-4830

<1:5.5.47-1.el7_2
  • M
CVE-2015-4826

<1:5.5.47-1.el7_2
  • M
Buffer Overflow

<1:5.5.47-1.el7_2
  • M
CVE-2015-4816

<1:5.5.47-1.el7_2
  • M
CVE-2015-4815

<1:5.5.47-1.el7_2
  • M
CVE-2015-4802

<1:5.5.47-1.el7_2
  • M
CVE-2015-4792

<1:5.5.47-1.el7_2
  • M
CVE-2015-4864

<1:5.5.44-1.el7_1
  • M
CVE-2015-4757

<1:5.5.44-1.el7_1
  • M
CVE-2015-4752

<1:5.5.44-1.el7_1
  • M
CVE-2015-4737

<1:5.5.44-1.el7_1
  • M
Improper Access Control

<1:5.5.44-1.el7_1
  • M
CVE-2015-2648

<1:5.5.44-1.el7_1
  • M
CVE-2015-2643

<1:5.5.44-1.el7_1
  • M
CVE-2015-2620

<1:5.5.44-1.el7_1
  • M
CVE-2015-2582

<1:5.5.44-1.el7_1
  • M
CVE-2015-2573

<1:5.5.44-1.el7_1
  • M
CVE-2015-2571

<1:5.5.44-1.el7_1
  • M
CVE-2015-2568

<1:5.5.44-1.el7_1
  • M
CVE-2015-0505

<1:5.5.44-1.el7_1
  • M
CVE-2015-0501

<1:5.5.44-1.el7_1
  • M
CVE-2015-0499

<1:5.5.44-1.el7_1
  • M
CVE-2015-0441

<1:5.5.44-1.el7_1
  • M
CVE-2015-0433

<1:5.5.44-1.el7_1
  • M
CVE-2015-0432

<1:5.5.41-2.el7_0
  • M
CVE-2015-0411

<1:5.5.41-2.el7_0
  • M
CVE-2015-0391

<1:5.5.41-2.el7_0
  • M
CVE-2015-0382

<1:5.5.41-2.el7_0
  • M
CVE-2015-0381

<1:5.5.41-2.el7_0
  • M
CVE-2015-0374

<1:5.5.41-2.el7_0
  • M
CVE-2014-6568

<1:5.5.41-2.el7_0
  • H
CVE-2014-6559

<1:5.5.40-1.el7_0
  • H
CVE-2014-6555

<1:5.5.40-1.el7_0
  • H
CVE-2014-6551

<1:5.5.40-1.el7_0
  • H
CVE-2014-6530

<1:5.5.40-1.el7_0
  • H
CVE-2014-6520

<1:5.5.40-1.el7_0
  • H
CVE-2014-6507

<1:5.5.40-1.el7_0
  • H
CVE-2014-6505

<1:5.5.40-1.el7_0
  • H
CVE-2014-6484

<1:5.5.40-1.el7_0
  • H
CVE-2014-6469

<1:5.5.40-1.el7_0
  • H
CVE-2014-6464

<1:5.5.40-1.el7_0
  • H
CVE-2014-6463

<1:5.5.40-1.el7_0
  • H
CVE-2014-4287

<1:5.5.40-1.el7_0
  • H
CVE-2014-4274

<1:5.5.40-1.el7_0
  • H
CVE-2014-4260

<1:5.5.40-1.el7_0
  • H
CVE-2014-4258

<1:5.5.40-1.el7_0
  • H
CVE-2014-4243

<1:5.5.40-1.el7_0
  • H
CVE-2014-4207

<1:5.5.40-1.el7_0
  • H
CVE-2014-2494

<1:5.5.40-1.el7_0
  • H
Information Exposure

<1:5.5.40-1.el7_0
  • M
CVE-2019-2481

<1:5.5.37-1.el7_0
  • M
CVE-2014-2438

<1:5.5.37-1.el7_0
  • M
CVE-2014-2436

<1:5.5.37-1.el7_0
  • M
CVE-2014-2432

<1:5.5.37-1.el7_0
  • M
CVE-2014-2431

<1:5.5.37-1.el7_0
  • M
CVE-2014-2430

<1:5.5.37-1.el7_0
  • M
CVE-2014-2419

<1:5.5.37-1.el7_0
  • M
CVE-2014-0384

<1:5.5.37-1.el7_0
  • M
NULL Pointer Dereference

*
  • M
Improper Locking

*
  • M
Improper Handling of Values

*
  • M
Improper Handling of Values

*
  • M
Improper Handling of Values

*
  • M
Improper Handling of Values

*
  • M
Improper Handling of Values

*
  • M
Improper Handling of Values

*
  • M
Improper Locking

*
  • M
Improper Resource Shutdown or Release

*
  • M
Improper Locking

*
  • M
Improper Resource Shutdown or Release

*
  • M
CVE-2022-21451

*
  • M
CVE-2022-21427

*
  • M
Reachable Assertion

*
  • M
Reachable Assertion

*
  • M
Reachable Assertion

*
  • M
Reachable Assertion

*
  • M
Reachable Assertion

*
  • M
Reachable Assertion

*
  • M
CVE-2022-27445

*
  • M
Out-of-Bounds

*
  • M
SQL Injection

*
  • M
SQL Injection

*
  • M
Use After Free

*
  • M
SQL Injection

*
  • M
SQL Injection

*
  • M
SQL Injection

*
  • M
SQL Injection

*
  • M
SQL Injection

*
  • M
Reachable Assertion

*
  • M
Use After Free

*
  • M
Improper Use of Validation Framework

*
  • M
Buffer Overflow

*
  • M
Heap-based Buffer Overflow

*
  • M
Improper Input Validation

*
  • M
Use After Free

*
  • L
Resource Exhaustion

*
  • M
Integer Overflow or Wraparound

*
  • L
Improper Input Validation

*
  • L
NULL Pointer Dereference

*
  • L
Improper Input Validation

*
  • L
Improper Input Validation

*
  • L
Improper Input Validation

*
  • L
Improper Input Validation

*
  • L
Improper Input Validation

*
  • L
Improper Input Validation

*
  • L
Improper Input Validation

*
  • M
CVE-2021-35604

*
  • M
CVE-2014-6474

*
  • M
CVE-2014-6489

*
  • M
CVE-2021-2389

*
  • M
CVE-2021-2372

*
  • M
Missing Required Cryptographic Step

<1:5.5.60-1.el7_5
  • M
Missing Required Cryptographic Step

<1:5.5.60-1.el7_5
  • M
Missing Required Cryptographic Step

<1:5.5.60-1.el7_5
  • M
Missing Required Cryptographic Step

<1:5.5.60-1.el7_5
  • M
Missing Required Cryptographic Step

<1:5.5.60-1.el7_5
  • M
Missing Required Cryptographic Step

<1:5.5.60-1.el7_5
  • M
Missing Required Cryptographic Step

<1:5.5.60-1.el7_5
  • M
Missing Required Cryptographic Step

<1:5.5.60-1.el7_5
  • M
Missing Required Cryptographic Step

<1:5.5.60-1.el7_5
  • M
Missing Required Cryptographic Step

<1:5.5.60-1.el7_5
  • M
CVE-2017-10378

<1:5.5.60-1.el7_5
  • M
CVE-2017-10378

<1:5.5.60-1.el7_5
  • M
CVE-2017-10378

<1:5.5.60-1.el7_5
  • M
CVE-2017-10378

<1:5.5.60-1.el7_5
  • M
CVE-2017-10378

<1:5.5.60-1.el7_5
  • M
CVE-2017-10378

<1:5.5.60-1.el7_5
  • M
CVE-2017-10378

<1:5.5.60-1.el7_5
  • M
CVE-2017-10378

<1:5.5.60-1.el7_5
  • M
CVE-2017-10378

<1:5.5.60-1.el7_5
  • M
CVE-2017-10378

<1:5.5.60-1.el7_5
  • M
CVE-2017-10384

<1:5.5.60-1.el7_5
  • M
CVE-2017-10384

<1:5.5.60-1.el7_5
  • M
CVE-2017-10384

<1:5.5.60-1.el7_5
  • M
CVE-2017-10384

<1:5.5.60-1.el7_5
  • M
CVE-2017-10384

<1:5.5.60-1.el7_5
  • M
CVE-2017-10384

<1:5.5.60-1.el7_5
  • M
CVE-2017-10384

<1:5.5.60-1.el7_5
  • M
CVE-2017-10384

<1:5.5.60-1.el7_5
  • M
CVE-2017-10384

<1:5.5.60-1.el7_5
  • M
CVE-2017-10384

<1:5.5.60-1.el7_5
  • M
CVE-2017-3317

<1:5.5.56-2.el7
  • M
CVE-2017-3317

<1:5.5.56-2.el7
  • M
CVE-2017-3317

<1:5.5.56-2.el7
  • M
CVE-2017-3317

<1:5.5.56-2.el7
  • M
CVE-2017-3317

<1:5.5.56-2.el7
  • M
CVE-2017-3317

<1:5.5.56-2.el7
  • M
CVE-2017-3317

<1:5.5.56-2.el7
  • M
CVE-2017-3317

<1:5.5.56-2.el7
  • M
CVE-2017-3317

<1:5.5.56-2.el7
  • M
CVE-2017-3317

<1:5.5.56-2.el7
  • M
CVE-2017-3317

<1:5.5.56-2.el7
  • M
CVE-2017-3317

<1:5.5.56-2.el7
  • M
CVE-2017-3317

<1:5.5.56-2.el7
  • M
CVE-2017-3317

<1:5.5.56-2.el7
  • M
CVE-2017-3317

<1:5.5.56-2.el7
  • M
CVE-2017-3317

<1:5.5.56-2.el7
  • M
CVE-2017-3317

<1:5.5.56-2.el7
  • M
CVE-2017-3317

<1:5.5.56-2.el7
  • M
CVE-2017-3317

<1:5.5.56-2.el7
  • M
CVE-2017-3317

<1:5.5.56-2.el7
  • M
CVE-2017-3317

<1:5.5.56-2.el7
  • M
CVE-2017-3317

<1:5.5.56-2.el7
  • M
CVE-2017-3317

<1:5.5.56-2.el7
  • M
Information Exposure

<1:5.5.56-2.el7
  • M
Information Exposure

<1:5.5.56-2.el7
  • M
Information Exposure

<1:5.5.56-2.el7
  • M
Information Exposure

<1:5.5.56-2.el7
  • M
Information Exposure

<1:5.5.56-2.el7
  • M
Information Exposure

<1:5.5.56-2.el7
  • M
Information Exposure

<1:5.5.56-2.el7
  • M
Information Exposure

<1:5.5.56-2.el7
  • M
Information Exposure

<1:5.5.56-2.el7
  • M
Information Exposure

<1:5.5.56-2.el7
  • M
Information Exposure

<1:5.5.56-2.el7
  • M
Information Exposure

<1:5.5.56-2.el7
  • M
Information Exposure

<1:5.5.56-2.el7
  • M
Information Exposure

<1:5.5.56-2.el7
  • M
Information Exposure

<1:5.5.56-2.el7
  • M
Information Exposure

<1:5.5.56-2.el7
  • M
Information Exposure

<1:5.5.56-2.el7
  • M
Information Exposure

<1:5.5.56-2.el7
  • M
Information Exposure

<1:5.5.56-2.el7
  • M
Information Exposure

<1:5.5.56-2.el7
  • M
Information Exposure

<1:5.5.56-2.el7
  • M
Information Exposure

<1:5.5.56-2.el7
  • M
Information Exposure

<1:5.5.56-2.el7
  • M
CVE-2017-3456

<1:5.5.56-2.el7
  • M
CVE-2017-3456

<1:5.5.56-2.el7
  • M
CVE-2017-3456

<1:5.5.56-2.el7
  • M
CVE-2017-3456

<1:5.5.56-2.el7
  • M
CVE-2017-3456

<1:5.5.56-2.el7
  • M
CVE-2017-3456

<1:5.5.56-2.el7
  • M
CVE-2017-3456

<1:5.5.56-2.el7
  • M
CVE-2017-3456

<1:5.5.56-2.el7
  • M
CVE-2017-3456

<1:5.5.56-2.el7
  • M
CVE-2017-3456

<1:5.5.56-2.el7
  • M
CVE-2017-3456

<1:5.5.56-2.el7
  • M
CVE-2017-3456

<1:5.5.56-2.el7
  • M
CVE-2017-3456

<1:5.5.56-2.el7
  • M
CVE-2017-3456

<1:5.5.56-2.el7
  • M
CVE-2017-3456

<1:5.5.56-2.el7
  • M
CVE-2017-3456

<1:5.5.56-2.el7
  • M
CVE-2017-3456

<1:5.5.56-2.el7
  • M
CVE-2017-3456

<1:5.5.56-2.el7
  • M
CVE-2017-3456

<1:5.5.56-2.el7
  • M
CVE-2017-3456

<1:5.5.56-2.el7
  • M
CVE-2017-3456

<1:5.5.56-2.el7
  • M
CVE-2017-3456

<1:5.5.56-2.el7
  • M
CVE-2017-3456

<1:5.5.56-2.el7
  • M
CVE-2017-3243

<1:5.5.56-2.el7
  • M
CVE-2017-3243

<1:5.5.56-2.el7
  • M
CVE-2017-3243

<1:5.5.56-2.el7
  • M
CVE-2017-3243

<1:5.5.56-2.el7
  • M
CVE-2017-3243

<1:5.5.56-2.el7
  • M
CVE-2017-3243

<1:5.5.56-2.el7
  • M
CVE-2017-3243

<1:5.5.56-2.el7
  • M
CVE-2017-3243

<1:5.5.56-2.el7
  • M
CVE-2017-3243

<1:5.5.56-2.el7
  • M
CVE-2017-3243

<1:5.5.56-2.el7
  • M
CVE-2017-3243

<1:5.5.56-2.el7
  • M
CVE-2017-3243

<1:5.5.56-2.el7
  • M
CVE-2017-3243

<1:5.5.56-2.el7
  • M
CVE-2017-3243

<1:5.5.56-2.el7
  • M
CVE-2017-3243

<1:5.5.56-2.el7
  • M
CVE-2017-3243

<1:5.5.56-2.el7
  • M
CVE-2017-3243

<1:5.5.56-2.el7
  • M
CVE-2017-3243

<1:5.5.56-2.el7
  • M
CVE-2017-3243

<1:5.5.56-2.el7
  • M
CVE-2017-3243

<1:5.5.56-2.el7
  • M
CVE-2017-3243

<1:5.5.56-2.el7
  • M
CVE-2017-3243

<1:5.5.56-2.el7
  • M
CVE-2017-3243

<1:5.5.56-2.el7
  • M
CVE-2017-3238

<1:5.5.56-2.el7
  • M
CVE-2017-3238

<1:5.5.56-2.el7
  • M
CVE-2017-3238

<1:5.5.56-2.el7
  • M
CVE-2017-3238

<1:5.5.56-2.el7
  • M
CVE-2017-3238

<1:5.5.56-2.el7
  • M
CVE-2017-3238

<1:5.5.56-2.el7
  • M
CVE-2017-3238

<1:5.5.56-2.el7
  • M
CVE-2017-3238

<1:5.5.56-2.el7
  • M
CVE-2017-3238

<1:5.5.56-2.el7
  • M
CVE-2017-3238

<1:5.5.56-2.el7
  • M
CVE-2017-3238

<1:5.5.56-2.el7
  • M
CVE-2017-3238

<1:5.5.56-2.el7
  • M
CVE-2017-3238

<1:5.5.56-2.el7
  • M
CVE-2017-3238

<1:5.5.56-2.el7
  • M
CVE-2017-3238

<1:5.5.56-2.el7
  • M
CVE-2017-3238

<1:5.5.56-2.el7
  • M
CVE-2017-3238

<1:5.5.56-2.el7
  • M
CVE-2017-3238

<1:5.5.56-2.el7
  • M
CVE-2017-3238

<1:5.5.56-2.el7
  • M
CVE-2017-3238

<1:5.5.56-2.el7
  • M
CVE-2017-3238

<1:5.5.56-2.el7
  • M
CVE-2017-3238

<1:5.5.56-2.el7
  • M
CVE-2017-3238

<1:5.5.56-2.el7
  • M
CVE-2017-3244

<1:5.5.56-2.el7
  • M
CVE-2017-3244

<1:5.5.56-2.el7
  • M
CVE-2017-3244

<1:5.5.56-2.el7
  • M
CVE-2017-3244

<1:5.5.56-2.el7
  • M
CVE-2017-3244

<1:5.5.56-2.el7
  • M
CVE-2017-3244

<1:5.5.56-2.el7
  • M
CVE-2017-3244

<1:5.5.56-2.el7
  • M
CVE-2017-3244

<1:5.5.56-2.el7
  • M
CVE-2017-3244

<1:5.5.56-2.el7
  • M
CVE-2017-3244

<1:5.5.56-2.el7
  • M
CVE-2017-3244

<1:5.5.56-2.el7
  • M
CVE-2017-3244

<1:5.5.56-2.el7
  • M
CVE-2017-3244

<1:5.5.56-2.el7
  • M
CVE-2017-3244

<1:5.5.56-2.el7
  • M
CVE-2017-3244

<1:5.5.56-2.el7
  • M
CVE-2017-3244

<1:5.5.56-2.el7
  • M
CVE-2017-3244

<1:5.5.56-2.el7
  • M
CVE-2017-3244

<1:5.5.56-2.el7
  • M
CVE-2017-3244

<1:5.5.56-2.el7
  • M
CVE-2017-3244

<1:5.5.56-2.el7
  • M
CVE-2017-3244

<1:5.5.56-2.el7
  • M
CVE-2017-3244

<1:5.5.56-2.el7
  • M
CVE-2017-3244

<1:5.5.56-2.el7
  • M
Improper Input Validation

<1:5.5.56-2.el7
  • M
Improper Input Validation

<1:5.5.56-2.el7
  • M
Improper Input Validation

<1:5.5.56-2.el7
  • M
Improper Input Validation

<1:5.5.56-2.el7
  • M
Improper Input Validation

<1:5.5.56-2.el7
  • M
Improper Input Validation

<1:5.5.56-2.el7
  • M
Improper Input Validation

<1:5.5.56-2.el7
  • M
Improper Input Validation

<1:5.5.56-2.el7
  • M
Improper Input Validation

<1:5.5.56-2.el7
  • M
Improper Input Validation

<1:5.5.56-2.el7
  • M
Improper Input Validation

<1:5.5.56-2.el7
  • M
Improper Input Validation

<1:5.5.56-2.el7
  • M
Improper Input Validation

<1:5.5.56-2.el7
  • M
Improper Input Validation

<1:5.5.56-2.el7
  • M
Improper Input Validation

<1:5.5.56-2.el7
  • M
Improper Input Validation

<1:5.5.56-2.el7
  • M
Improper Input Validation

<1:5.5.56-2.el7
  • M
Improper Input Validation

<1:5.5.56-2.el7
  • M
Improper Input Validation

<1:5.5.56-2.el7
  • M
Improper Input Validation

<1:5.5.56-2.el7
  • M
Improper Input Validation

<1:5.5.56-2.el7
  • M
Improper Input Validation

<1:5.5.56-2.el7
  • M
Improper Input Validation

<1:5.5.56-2.el7
  • M
CVE-2017-3318

<1:5.5.56-2.el7
  • M
CVE-2017-3318

<1:5.5.56-2.el7
  • M
CVE-2017-3318

<1:5.5.56-2.el7
  • M
CVE-2017-3318

<1:5.5.56-2.el7
  • M
CVE-2017-3318

<1:5.5.56-2.el7
  • M
CVE-2017-3318

<1:5.5.56-2.el7
  • M
CVE-2017-3318

<1:5.5.56-2.el7
  • M
CVE-2017-3318

<1:5.5.56-2.el7
  • M
CVE-2017-3318

<1:5.5.56-2.el7
  • M
CVE-2017-3318

<1:5.5.56-2.el7
  • M
CVE-2017-3318

<1:5.5.56-2.el7
  • M
CVE-2017-3318

<1:5.5.56-2.el7
  • M
CVE-2017-3318

<1:5.5.56-2.el7
  • M
CVE-2017-3318

<1:5.5.56-2.el7
  • M
CVE-2017-3318

<1:5.5.56-2.el7
  • M
CVE-2017-3318

<1:5.5.56-2.el7
  • M
CVE-2017-3318

<1:5.5.56-2.el7
  • M
CVE-2017-3318

<1:5.5.56-2.el7
  • M
CVE-2017-3318

<1:5.5.56-2.el7
  • M
CVE-2017-3318

<1:5.5.56-2.el7
  • M
CVE-2017-3318

<1:5.5.56-2.el7
  • M
CVE-2017-3318

<1:5.5.56-2.el7
  • M
CVE-2017-3318

<1:5.5.56-2.el7
  • H
CVE-2016-8283

<1:5.5.52-1.el7
  • H
CVE-2016-8283

<1:5.5.52-1.el7
  • H
CVE-2016-8283

<1:5.5.52-1.el7
  • H
CVE-2016-8283

<1:5.5.52-1.el7
  • H
CVE-2016-8283

<1:5.5.52-1.el7
  • H
CVE-2016-8283

<1:5.5.52-1.el7
  • H
CVE-2016-8283

<1:5.5.52-1.el7
  • H
CVE-2016-8283

<1:5.5.52-1.el7
  • H
CVE-2016-8283

<1:5.5.52-1.el7
  • H
CVE-2016-8283

<1:5.5.52-1.el7
  • H
CVE-2016-8283

<1:5.5.52-1.el7
  • H
CVE-2016-8283

<1:5.5.52-1.el7
  • H
CVE-2016-8283

<1:5.5.52-1.el7
  • H
CVE-2016-8283

<1:5.5.52-1.el7
  • H
CVE-2016-8283

<1:5.5.52-1.el7
  • H
CVE-2016-8283

<1:5.5.52-1.el7
  • H
CVE-2016-8283

<1:5.5.52-1.el7
  • H
CVE-2016-8283

<1:5.5.52-1.el7
  • H
CVE-2016-8283

<1:5.5.52-1.el7
  • H
CVE-2016-8283

<1:5.5.52-1.el7
  • H
CVE-2016-8283

<1:5.5.52-1.el7
  • H
CVE-2016-8283

<1:5.5.52-1.el7
  • H
CVE-2016-8283

<1:5.5.52-1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:5.5.52-1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:5.5.52-1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:5.5.52-1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:5.5.52-1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:5.5.52-1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:5.5.52-1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:5.5.52-1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:5.5.52-1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:5.5.52-1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:5.5.52-1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:5.5.52-1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:5.5.52-1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:5.5.52-1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:5.5.52-1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:5.5.52-1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:5.5.52-1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:5.5.52-1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:5.5.52-1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:5.5.52-1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:5.5.52-1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:5.5.52-1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:5.5.52-1.el7
  • H
Incorrect Permission Assignment for Critical Resource

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
CVE-2016-5612

<1:5.5.52-1.el7
  • H
CVE-2016-5612

<1:5.5.52-1.el7
  • H
CVE-2016-5612

<1:5.5.52-1.el7
  • H
CVE-2016-5612

<1:5.5.52-1.el7
  • H
CVE-2016-5612

<1:5.5.52-1.el7
  • H
CVE-2016-5612

<1:5.5.52-1.el7
  • H
CVE-2016-5612

<1:5.5.52-1.el7
  • H
CVE-2016-5612

<1:5.5.52-1.el7
  • H
CVE-2016-5612

<1:5.5.52-1.el7
  • H
CVE-2016-5612

<1:5.5.52-1.el7
  • H
CVE-2016-5612

<1:5.5.52-1.el7
  • H
CVE-2016-5612

<1:5.5.52-1.el7
  • H
CVE-2016-5612

<1:5.5.52-1.el7
  • H
CVE-2016-5612

<1:5.5.52-1.el7
  • H
CVE-2016-5612

<1:5.5.52-1.el7
  • H
CVE-2016-5612

<1:5.5.52-1.el7
  • H
CVE-2016-5612

<1:5.5.52-1.el7
  • H
CVE-2016-5612

<1:5.5.52-1.el7
  • H
CVE-2016-5612

<1:5.5.52-1.el7
  • H
CVE-2016-5612

<1:5.5.52-1.el7
  • H
CVE-2016-5612

<1:5.5.52-1.el7
  • H
CVE-2016-5612

<1:5.5.52-1.el7
  • H
CVE-2016-5612

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
Race Condition

<1:5.5.52-1.el7
  • H
CVE-2016-3492

<1:5.5.52-1.el7
  • H
CVE-2016-3492

<1:5.5.52-1.el7
  • H
CVE-2016-3492

<1:5.5.52-1.el7
  • H
CVE-2016-3492

<1:5.5.52-1.el7
  • H
CVE-2016-3492

<1:5.5.52-1.el7
  • H
CVE-2016-3492

<1:5.5.52-1.el7
  • H
CVE-2016-3492

<1:5.5.52-1.el7
  • H
CVE-2016-3492

<1:5.5.52-1.el7
  • H
CVE-2016-3492

<1:5.5.52-1.el7
  • H
CVE-2016-3492

<1:5.5.52-1.el7
  • H
CVE-2016-3492

<1:5.5.52-1.el7
  • H
CVE-2016-3492

<1:5.5.52-1.el7
  • H
CVE-2016-3492

<1:5.5.52-1.el7
  • H
CVE-2016-3492

<1:5.5.52-1.el7
  • H
CVE-2016-3492

<1:5.5.52-1.el7
  • H
CVE-2016-3492

<1:5.5.52-1.el7
  • H
CVE-2016-3492

<1:5.5.52-1.el7
  • H
CVE-2016-3492

<1:5.5.52-1.el7
  • H
CVE-2016-3492

<1:5.5.52-1.el7
  • H
CVE-2016-3492

<1:5.5.52-1.el7
  • H
CVE-2016-3492

<1:5.5.52-1.el7
  • H
CVE-2016-3492

<1:5.5.52-1.el7
  • H
CVE-2016-3492

<1:5.5.52-1.el7
  • H
CVE-2016-5629

<1:5.5.52-1.el7
  • H
CVE-2016-5629

<1:5.5.52-1.el7
  • H
CVE-2016-5629

<1:5.5.52-1.el7
  • H
CVE-2016-5629

<1:5.5.52-1.el7
  • H
CVE-2016-5629

<1:5.5.52-1.el7
  • H
CVE-2016-5629

<1:5.5.52-1.el7
  • H
CVE-2016-5629

<1:5.5.52-1.el7
  • H
CVE-2016-5629

<1:5.5.52-1.el7
  • H
CVE-2016-5629

<1:5.5.52-1.el7
  • H
CVE-2016-5629

<1:5.5.52-1.el7
  • H
CVE-2016-5629

<1:5.5.52-1.el7
  • H
CVE-2016-5629

<1:5.5.52-1.el7
  • H
CVE-2016-5629

<1:5.5.52-1.el7
  • H
CVE-2016-5629

<1:5.5.52-1.el7
  • H
CVE-2016-5629

<1:5.5.52-1.el7
  • H
CVE-2016-5629

<1:5.5.52-1.el7
  • H
CVE-2016-5629

<1:5.5.52-1.el7
  • H
CVE-2016-5629

<1:5.5.52-1.el7
  • H
CVE-2016-5629

<1:5.5.52-1.el7
  • H
CVE-2016-5629

<1:5.5.52-1.el7
  • H
CVE-2016-5629

<1:5.5.52-1.el7
  • H
CVE-2016-5629

<1:5.5.52-1.el7
  • H
CVE-2016-5629

<1:5.5.52-1.el7
  • H
CVE-2016-5624

<1:5.5.52-1.el7
  • H
CVE-2016-5624

<1:5.5.52-1.el7
  • H
CVE-2016-5624

<1:5.5.52-1.el7
  • H
CVE-2016-5624

<1:5.5.52-1.el7
  • H
CVE-2016-5624

<1:5.5.52-1.el7
  • H
CVE-2016-5624

<1:5.5.52-1.el7
  • H
CVE-2016-5624

<1:5.5.52-1.el7
  • H
CVE-2016-5624

<1:5.5.52-1.el7
  • H
CVE-2016-5624

<1:5.5.52-1.el7
  • H
CVE-2016-5624

<1:5.5.52-1.el7
  • H
CVE-2016-5624

<1:5.5.52-1.el7
  • H
CVE-2016-5624

<1:5.5.52-1.el7
  • H
CVE-2016-5624

<1:5.5.52-1.el7
  • H
CVE-2016-5624

<1:5.5.52-1.el7
  • H
CVE-2016-5624

<1:5.5.52-1.el7
  • H
CVE-2016-5624

<1:5.5.52-1.el7
  • H
CVE-2016-5624

<1:5.5.52-1.el7
  • H
CVE-2016-5624

<1:5.5.52-1.el7
  • H
CVE-2016-5624

<1:5.5.52-1.el7
  • H
CVE-2016-5624

<1:5.5.52-1.el7
  • H
CVE-2016-5624

<1:5.5.52-1.el7
  • H
CVE-2016-5624

<1:5.5.52-1.el7
  • H
CVE-2016-5624

<1:5.5.52-1.el7
  • H
CVE-2016-5626

<1:5.5.52-1.el7
  • H
CVE-2016-5626

<1:5.5.52-1.el7
  • H
CVE-2016-5626

<1:5.5.52-1.el7
  • H
CVE-2016-5626

<1:5.5.52-1.el7
  • H
CVE-2016-5626

<1:5.5.52-1.el7
  • H
CVE-2016-5626

<1:5.5.52-1.el7
  • H
CVE-2016-5626

<1:5.5.52-1.el7
  • H
CVE-2016-5626

<1:5.5.52-1.el7
  • H
CVE-2016-5626

<1:5.5.52-1.el7
  • H
CVE-2016-5626

<1:5.5.52-1.el7
  • H
CVE-2016-5626

<1:5.5.52-1.el7
  • H
CVE-2016-5626

<1:5.5.52-1.el7
  • H
CVE-2016-5626

<1:5.5.52-1.el7
  • H
CVE-2016-5626

<1:5.5.52-1.el7
  • H
CVE-2016-5626

<1:5.5.52-1.el7
  • H
CVE-2016-5626

<1:5.5.52-1.el7
  • H
CVE-2016-5626

<1:5.5.52-1.el7
  • H
CVE-2016-5626

<1:5.5.52-1.el7
  • H
CVE-2016-5626

<1:5.5.52-1.el7
  • H
CVE-2016-5626

<1:5.5.52-1.el7
  • H
CVE-2016-5626

<1:5.5.52-1.el7
  • H
CVE-2016-5626

<1:5.5.52-1.el7
  • H
CVE-2016-5626

<1:5.5.52-1.el7
  • H
CVE-2016-3615

<1:5.5.50-1.el7_2
  • H
CVE-2016-3615

<1:5.5.50-1.el7_2
  • H
CVE-2016-3615

<1:5.5.50-1.el7_2
  • H
CVE-2016-3615

<1:5.5.50-1.el7_2
  • H
CVE-2016-3615

<1:5.5.50-1.el7_2
  • H
CVE-2016-3615

<1:5.5.50-1.el7_2
  • H
CVE-2016-3615

<1:5.5.50-1.el7_2
  • H
CVE-2016-3615

<1:5.5.50-1.el7_2
  • H
CVE-2016-3615

<1:5.5.50-1.el7_2
  • H
CVE-2016-3615

<1:5.5.50-1.el7_2
  • H
CVE-2016-3615

<1:5.5.50-1.el7_2
  • H
CVE-2016-3615

<1:5.5.50-1.el7_2
  • H
CVE-2016-3615

<1:5.5.50-1.el7_2
  • H
CVE-2016-3615

<1:5.5.50-1.el7_2
  • H
CVE-2016-3615

<1:5.5.50-1.el7_2
  • H
CVE-2016-3615

<1:5.5.50-1.el7_2
  • H
CVE-2016-3615

<1:5.5.50-1.el7_2
  • H
CVE-2016-3615

<1:5.5.50-1.el7_2
  • H
CVE-2016-3615

<1:5.5.50-1.el7_2
  • H
CVE-2016-3615

<1:5.5.50-1.el7_2
  • H
CVE-2016-3615

<1:5.5.50-1.el7_2
  • H
CVE-2016-3615

<1:5.5.50-1.el7_2
  • H
CVE-2016-5444

<1:5.5.50-1.el7_2
  • H
CVE-2016-5444

<1:5.5.50-1.el7_2
  • H
CVE-2016-5444

<1:5.5.50-1.el7_2
  • H
CVE-2016-5444

<1:5.5.50-1.el7_2
  • H
CVE-2016-5444

<1:5.5.50-1.el7_2
  • H
CVE-2016-5444

<1:5.5.50-1.el7_2
  • H
CVE-2016-5444

<1:5.5.50-1.el7_2
  • H
CVE-2016-5444

<1:5.5.50-1.el7_2
  • H
CVE-2016-5444

<1:5.5.50-1.el7_2
  • H
CVE-2016-5444

<1:5.5.50-1.el7_2
  • H
CVE-2016-5444

<1:5.5.50-1.el7_2
  • H
CVE-2016-5444

<1:5.5.50-1.el7_2
  • H
CVE-2016-5444

<1:5.5.50-1.el7_2
  • H
CVE-2016-5444

<1:5.5.50-1.el7_2
  • H
CVE-2016-5444

<1:5.5.50-1.el7_2
  • H
CVE-2016-5444

<1:5.5.50-1.el7_2
  • H
CVE-2016-5444