2022 Security Vulnerability Report
CVE Statistics for 2022

Growth Curve
There have been 1310 security vulnerabilities (CVEs) published so far in 2022. In 2021 there were 20175.

The average severity is 6.7 out of 10, which decreased by 0.4 from 2021.

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

By Product

#1

Bentley View

76 vulnerabilities in 2022

#2

Bentley Microstation

76 vulnerabilities in 2022

#3

Huawei Harmonyos

64 vulnerabilities in 2022

#4

Microsoft Windows Server

47 vulnerabilities in 2022

#5

Microsoft Windows Server 2019

47 vulnerabilities in 2022

#6

Microsoft Windows 10

47 vulnerabilities in 2022

#7

Adobe

41 vulnerabilities in 2022

#8

Microsoft Windows Server 2016

38 vulnerabilities in 2022

#9

Microsoft Windows 11

35 vulnerabilities in 2022

#10

Gpac

31 vulnerabilities in 2022

#11

Microsoft Windows Server 2012

28 vulnerabilities in 2022

#12

Huawei Magic Ui

27 vulnerabilities in 2022

#13

Huawei Emui

27 vulnerabilities in 2022

#14

Microsoft Windows 8.1

26 vulnerabilities in 2022

#15

Google Android

18 vulnerabilities in 2022

#16

Microsoft Windows 7

17 vulnerabilities in 2022

#17

Microsoft Windows Server 2008

17 vulnerabilities in 2022

#19

Debian Linux

12 vulnerabilities in 2022

#20

Canonical Ubuntu Linux

8 vulnerabilities in 2022

By Vendor

#1

Microsoft

100 vulnerabilities in 2022

#2

Bentley

76 vulnerabilities in 2022

#3

Huawei

70 vulnerabilities in 2022

#4

Adobe

46 vulnerabilities in 2022

#5

Gpac

31 vulnerabilities in 2022

#6

Jenkins

19 vulnerabilities in 2022

#7

Google

19 vulnerabilities in 2022

#8

Red Hat

19 vulnerabilities in 2022

#9

Apache

18 vulnerabilities in 2022

#10

Cisco

17 vulnerabilities in 2022

#11

Vehicleservicemanagementsystemproject

13 vulnerabilities in 2022

#12

Debian

12 vulnerabilities in 2022

#13

Libexpatproject

8 vulnerabilities in 2022

#14

Canonical

8 vulnerabilities in 2022

#15

IBM

7 vulnerabilities in 2022

#16

Wolfssl

7 vulnerabilities in 2022

#17

Thekelleys

7 vulnerabilities in 2022

#18

Webassembly

6 vulnerabilities in 2022

#19

Daybydaycrm

6 vulnerabilities in 2022

#20

Silabs

6 vulnerabilities in 2022

By Weakness

#1
Memory Corruption
The software writes data past the end, or before the beginning, of the intended buffer. Typically, this can result in corruption of data, a crash, or code execution. The software may modify an index or perform pointer arithmetic that references a memory location that is outside of the boundaries of the buffer. A subsequent write operation then produces undefined or unexpected results.
92
 
7.0%
#2
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.
84
 
6.4%
#3
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.
50
 
3.8%
#4
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. NULL pointer dereference issues can occur through a number of flaws, including race conditions, and simple programming omissions.
31
 
2.4%
#5
Out-of-bounds Read
The software reads data past the end, or before the beginning, of the intended buffer. Typically, this can allow attackers to read sensitive information from other memory locations or cause a crash. A crash can occur when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string. The expected sentinel might not be located in the out-of-bounds memory, causing excessive data to be read, leading to a segmentation fault or a buffer overflow. The software may modify an index or perform pointer arithmetic that references a memory location that is outside of the boundaries of the buffer. A subsequent read operation then produces undefined or unexpected results.
31
 
2.4%
#6
Dangling pointer
Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code.
29
 
2.2%
#7
Exposure of Resource to Wrong Sphere
The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.
19
 
1.5%
#8
Session Riding
The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. When a web server is designed to receive a request from a client without any mechanism for verifying that it was intentionally sent, then it might be possible for an attacker to trick a client into making an unintentional request to the web server which will be treated as an authentic request. This can be done via a URL, image load, XMLHttpRequest, etc. and can result in exposure of data or unintended code execution.
19
 
1.5%
#9
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.
18
 
1.4%
#10
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.
18
 
1.4%
#11
Resource Exhaustion
The software does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources.
18
 
1.4%
#12
Improper Input Validation
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
16
 
1.2%
#13
Information Disclosure
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
15
 
1.1%
#14
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. An integer overflow or wraparound occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may wrap to become a very small or negative number. While this may be intended behavior in circumstances that rely on wrapping, it can have security consequences if the wrap is unexpected. This is especially the case if the integer overflow can be triggered using user-supplied inputs. This becomes security-critical when the result is used to control looping, make a security decision, or determine the offset or size in behaviors such as memory allocation, copying, concatenation, etc.
14
 
1.1%
#15
Classic Buffer Overflow
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. A buffer overflow condition exists when a program attempts to put more data in a buffer than it can hold, or when a program attempts to put data in a memory area outside of the boundaries of a buffer. The simplest type of error, and the most common cause of buffer overflows, is the "classic" case in which the program copies the buffer without restricting how much is copied. Other variants exist, but the existence of a classic overflow strongly suggests that the programmer is not considering even the most basic of security protections.
13
 
1.0%
#16
assertion failure
The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.
10
 
0.8%
#17
Double-free
The product calls free() twice on the same memory address, potentially leading to modification of unexpected memory locations. When a program calls free() twice with the same argument, the program's memory management data structures become corrupted. This corruption can cause the program to crash or, in some circumstances, cause two later calls to malloc() to return the same pointer. If malloc() returns the same value twice and the program later gives the attacker control over the data that is written into this doubly-allocated memory, the program becomes vulnerable to a buffer overflow attack.
8
 
0.6%
#18
Improper Handling of Exceptional Conditions
The software does not handle or incorrectly handles an exceptional condition.
8
 
0.6%
#19
AuthZ
The software does not perform an authorization check when an actor attempts to access a resource or perform an action.
8
 
0.6%
#20
Command Injection
The software constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
7
 
0.5%
#21
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.
7
 
0.5%
#22
Buffer Overflow
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.
6
 
0.5%
#23
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.
6
 
0.5%
#24
Incorrect Default Permissions
During installation, installed file permissions are set to allow anyone to modify those files.
6
 
0.5%
#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.
5
 
0.4%

By Category

Content Management

Adobe Experience Manager

8 vulnerabilities in 2022

MediaWiki

5 vulnerabilities in 2022

WordPress

4 vulnerabilities in 2022

Desktop Software

Microsoft Office

2 vulnerabilities in 2022

Microsoft Excel

1 vulnerability in 2022

Microsoft Word

1 vulnerability in 2022

Development Tools

Jenkins

1 vulnerability in 2022

DevOps

Kubernetes

1 vulnerability in 2022

Email

Microsoft Exchange Server

2 vulnerabilities in 2022

Libraries

libming Ming

2 vulnerabilities in 2022

Operating Systems

Microsoft Windows Server 2019

47 vulnerabilities in 2022

Microsoft Windows 10

47 vulnerabilities in 2022

Microsoft Windows Server 2016

38 vulnerabilities in 2022

Runtime Environments

Ruby Programming Language Ruby Language

2 vulnerabilities in 2022

GoLang Go

1 vulnerability in 2022

Server Software

Microsoft Sharepoint Enterprise Server

2 vulnerabilities in 2022

Microsoft Sharepoint Server

2 vulnerabilities in 2022

Web Application Framework

Django Project Django

3 vulnerabilities in 2022


Report Last Updated: January 19, 2022