2019 Security Vulnerability Report
CVE Statistics for 2019

There were 16056 security vulnerabilities (CVEs) published in 2019. In 2018 there were 12781.

The average severity was 7.3 out of 10, which was about the same as in 2018.

Products & Vendors with the most security vulnerabilities published in 2019 Vulnerabilities may exist in multiple products or vendors

By Product

Red Hat Enterprise Linux Server

176 vulnerabilities in 2019

By Vendor

By Weakness

#1

XSS

The software does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

1809

11.3%

#2

Improper Input Validation

The product does not validate or incorrectly validates input that can affect the control flow or data flow of a program.

1006

6.3%

#3

Out-of-bounds Write

The software writes data past the end, or before the beginning, of the intended buffer.

1005

6.3%

#4

Out-of-bounds Read

The software reads data past the end, or before the beginning, of the intended buffer.

820

5.1%

#5

Information Leak

An information exposure is the intentional or unintentional disclosure of information to an actor that is not explicitly authorized to have access to that information.

685

4.3%

#6

Memory Corruption

The software performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer.

609

3.8%

#7

Dangling pointer

Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code.

502

3.1%

#8

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

The software constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component.

439

2.7%

#9

Directory traversal

The software uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the software does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

380

2.4%

#10

Shell injection

The software constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.

325

2.0%

#11

NULL Pointer Dereference

A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit.

235

1.5%

#12

authentification

When an actor claims to have a given identity, the software does not prove or insufficiently proves that the claim is correct.

216

1.3%

#13

Incorrect Permission Assignment for Critical Resource

The software specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.

185

1.2%

#14

Unrestricted File Upload

The software allows the attacker to upload or transfer files of dangerous types that can be automatically processed within the product's environment.

184

1.1%

#15

Improper Control of Generation of Code ('Code Injection')

The software constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.

147

0.9%

#16

Integer Overflow or Wraparound

The software performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control.

144

0.9%

#17

Improper Privilege Management

The software does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.

136

0.8%

#18

Uncontrolled Resource Consumption ('Resource Exhaustion')

The software does not properly restrict the size or amount of resources that are requested or influenced by an actor, which can be used to consume more resources than intended.

134

0.8%

#19

XXE

The software processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.

122

0.8%

#20

Marshaling, Unmarshaling

The application deserializes untrusted data without sufficiently verifying that the resulting data will be valid.

119

0.7%

#21

AuthZ

The software does not perform an authorization check when an actor attempts to access a resource or perform an action.

119

0.7%

#22

Missing Authentication for Critical Function

The software does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

117

0.7%

#23

Insufficiently Protected Credentials

This weakness occurs when the application transmits or stores authentication credentials and uses an insecure method that is susceptible to unauthorized interception and/or retrieval.

117

0.7%

#24

buffer overrun

The program copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow.

110

0.7%

#25

Use of Hard-coded Credentials

The software contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data.

105

0.7%