2023 Security Vulnerability Report
CVE Statistics for 2023

Growth Curve
There have been 2252 security vulnerabilities (CVEs) published so far in 2023. In 2022 there were 25087.

The average severity is 7.4 out of 10, up by 0.2 from 2022.

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

By Product

#1

Microsoft Windows Server 2022

63 vulnerabilities in 2023

#2

Microsoft Windows Server 2019

58 vulnerabilities in 2023

#3

Microsoft Windows Server 2016

51 vulnerabilities in 2023

#4

Microsoft Windows 10 21h2

51 vulnerabilities in 2023

#5

Microsoft Windows 10 22h2

51 vulnerabilities in 2023

#6

Microsoft Windows 11 22h2

50 vulnerabilities in 2023

#7

Microsoft Windows 10 20h2

50 vulnerabilities in 2023

#8

Microsoft Windows 11 21h2

50 vulnerabilities in 2023

#9

Microsoft Windows 10 1809

48 vulnerabilities in 2023

#10

Microsoft Windows Server 2012

48 vulnerabilities in 2023

#11

Microsoft Windows Rt 8 1

47 vulnerabilities in 2023

#12

Microsoft Windows 8.1

46 vulnerabilities in 2023

#13

Microsoft Windows 10 1607

43 vulnerabilities in 2023

#14

Microsoft Windows 7

43 vulnerabilities in 2023

#15

Microsoft Windows Server 2008

41 vulnerabilities in 2023

#16

Tracker Software Pdf Xchange Editor

37 vulnerabilities in 2023

#17

Gpac

22 vulnerabilities in 2023

#18

Linux Kernel

15 vulnerabilities in 2023

#19

Google Chrome

14 vulnerabilities in 2023

#20

Microsoft 3d Builder

14 vulnerabilities in 2023

By Vendor

#1

Microsoft

120 vulnerabilities in 2023

#2

Oracle

74 vulnerabilities in 2023

#3

Tracker Software

37 vulnerabilities in 2023

#4

Cisco

24 vulnerabilities in 2023

#5

Gpac

22 vulnerabilities in 2023

#6

Aruba Networks

20 vulnerabilities in 2023

#7

Red Hat

17 vulnerabilities in 2023

#8

Apache

16 vulnerabilities in 2023

#9

Linux

15 vulnerabilities in 2023

#10

Google

14 vulnerabilities in 2023

#11

Royal Elementor Addons

13 vulnerabilities in 2023

#12

Canonical

12 vulnerabilities in 2023

#13

GitLab

12 vulnerabilities in 2023

#14

Juniper Networks

11 vulnerabilities in 2023

#15

Siemens

10 vulnerabilities in 2023

#16

IBM

10 vulnerabilities in 2023

#17

Sewio

9 vulnerabilities in 2023

#18

Discourse

9 vulnerabilities in 2023

#19

Phpmyfaq

9 vulnerabilities in 2023

#20

Dynamictransactionqueuingsystemproject

8 vulnerabilities in 2023

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.
293
 
13.0%
#2
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.
223
 
9.9%
#3
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.
93
 
4.1%
#4
Stack Overflow
A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
62
 
2.8%
#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.
62
 
2.8%
#6
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.
55
 
2.4%
#7
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.
48
 
2.1%
#8
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.
34
 
1.5%
#9
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.
32
 
1.4%
#10
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.
32
 
1.4%
#11
AuthZ
The software does not perform an authorization check when an actor attempts to access a resource or perform an action.
29
 
1.3%
#12
Dangling pointer
Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code.
23
 
1.0%
#13
Information Disclosure
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
22
 
1.0%
#14
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.
21
 
0.9%
#15
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.
19
 
0.8%
#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. 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.
19
 
0.8%
#17
ReDoS
The product uses a regular expression with an inefficient, possibly exponential worst-case computational complexity that consumes excessive CPU cycles. Some regular expression engines have a feature called "backtracking". If the token cannot match, the engine "backtracks" to a position that may result in a different token that can match. Backtracking becomes a weakness if all of these conditions are met:
17
 
0.8%
#18
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.
17
 
0.8%
#19
Authorization
The software does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
17
 
0.8%
#20
authentification
When an actor claims to have a given identity, the software does not prove or insufficiently proves that the claim is correct.
16
 
0.7%
#21
AuthZ
The software performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions.
16
 
0.7%
#22
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.
14
 
0.6%
#23
Marshaling, Unmarshaling
The application deserializes untrusted data without sufficiently verifying that the resulting data will be valid.
14
 
0.6%
#24
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.
13
 
0.6%
#25
Injection
The software constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. Software has certain assumptions about what constitutes data and control respectively. It is the lack of verification of these assumptions for user-controlled input that leads to injection problems. Injection problems encompass a wide variety of issues -- all mitigated in very different ways and usually attempted in order to alter the control flow of the process. For this reason, the most effective way to discuss these weaknesses is to note the distinct features which classify them as injection weaknesses. The most important issue to note is that all injection problems share one thing in common -- i.e., they allow for the injection of control plane data into the user-controlled data plane. This means that the execution of the process may be altered by sending code in through legitimate data channels, using no other mechanism. While buffer overflows, and many other flaws, involve the use of some further issue to gain execution, injection problems need only for the data to be parsed. The most classic instantiations of this category of weakness are SQL injection and format string vulnerabilities.
13
 
0.6%

By Category

Content Management

MediaWiki

6 vulnerabilities in 2023

WordPress

1 vulnerability in 2023

Database

Oracle MySQL

10 vulnerabilities in 2023

Oracle Database Server

1 vulnerability in 2023

MariaDB

1 vulnerability in 2023

Desktop Software

Microsoft Office

6 vulnerabilities in 2023

Development Tools

Oracle Java Development Kit (JDK)

3 vulnerabilities in 2023

DevOps

GitLab

11 vulnerabilities in 2023

Email

Microsoft Exchange Server

5 vulnerabilities in 2023

Java Application Servers

Oracle Weblogic Server

5 vulnerabilities in 2023

Apache Tomcat

1 vulnerability in 2023

Operating Systems

Microsoft Windows Server 2019

58 vulnerabilities in 2023

Microsoft Windows Server 2016

51 vulnerabilities in 2023

Microsoft Windows Server 2012

48 vulnerabilities in 2023

Runtime Environments

Oracle Java Runtime Environment (JRE)

3 vulnerabilities in 2023

Server Software

Microsoft Sharepoint Server

3 vulnerabilities in 2023

Virtualization

Oracle VM VirtualBox

6 vulnerabilities in 2023

Web Browsers

Google Chrome

14 vulnerabilities in 2023

Web Servers

Apache HTTP Server

3 vulnerabilities in 2023


Report Last Updated: January 28, 2023