2024 Security Vulnerability Report
CVE Statistics for 2024

Growth Curve
There have been 4595 security vulnerabilities (CVEs) published so far in 2024. In 2023 there were 29814.

The average severity is 7.2 out of 10, up by 0.1 from 2023.

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

By Product

#1

Tonybybell Gtkwave

82 vulnerabilities in 2024

#2

Canonical Ubuntu Linux

81 vulnerabilities in 2024

#3

Apple Macos

76 vulnerabilities in 2024

#4

Linux Kernel

60 vulnerabilities in 2024

#5

Fedora Project Fedora

58 vulnerabilities in 2024

#6

Apple iPad OS

51 vulnerabilities in 2024

#7

Apple iOS

51 vulnerabilities in 2024

#8

Red Hat Enterprise Linux (RHEL)

44 vulnerabilities in 2024

#9

Ajaysharma Cups Easy

42 vulnerabilities in 2024

#10

Microsoft Windows 11 22h2

38 vulnerabilities in 2024

#11

Microsoft Windows 11 23h2

38 vulnerabilities in 2024

#12

Microsoft Windows Server 2022

38 vulnerabilities in 2024

#13

Microsoft Windows 11 21h2

37 vulnerabilities in 2024

#14

Microsoft Windows Server 2019

36 vulnerabilities in 2024

#15

Microsoft Windows 10 22h2

36 vulnerabilities in 2024

#16

Microsoft Windows 10 21h2

36 vulnerabilities in 2024

#17

Qnap Qts

35 vulnerabilities in 2024

#18

Qnap Quts Hero

34 vulnerabilities in 2024

#19

Microsoft Windows 10 1809

34 vulnerabilities in 2024

#20

Qnap Qutscloud

27 vulnerabilities in 2024

By Vendor

#1

Microsoft

163 vulnerabilities in 2024

#2

Red Hat

89 vulnerabilities in 2024

#3

Apple

85 vulnerabilities in 2024

#4

Tonybybell

82 vulnerabilities in 2024

#5

Canonical

82 vulnerabilities in 2024

#6

IBM

71 vulnerabilities in 2024

#7

Linux

60 vulnerabilities in 2024

#8

Fedora Project

58 vulnerabilities in 2024

#9

Qnap

44 vulnerabilities in 2024

#10

Oracle

43 vulnerabilities in 2024

#11

Ajaysharma

42 vulnerabilities in 2024

#12

Kashipara

42 vulnerabilities in 2024

#13

Dell

34 vulnerabilities in 2024

#14

TrendMicro

33 vulnerabilities in 2024

#15

Adobe

33 vulnerabilities in 2024

#16

Mozilla

30 vulnerabilities in 2024

#17

Code Projects

30 vulnerabilities in 2024

#18

Siemens

29 vulnerabilities in 2024

#19

Samsung

26 vulnerabilities in 2024

#20

Linecorp

26 vulnerabilities in 2024

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.
646
 
14.1%
#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.
267
 
5.8%
#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.
244
 
5.3%
#4
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.
141
 
3.1%
#5
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.
103
 
2.2%
#6
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.
102
 
2.2%
#7
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.
93
 
2.0%
#8
AuthZ
The software does not perform an authorization check when an actor attempts to access a resource or perform an action.
88
 
1.9%
#9
Dangling pointer
Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code.
78
 
1.7%
#10
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.
74
 
1.6%
#11
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.
63
 
1.4%
#12
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.
52
 
1.1%
#13
Marshaling, Unmarshaling
The application deserializes untrusted data without sufficiently verifying that the resulting data will be valid.
51
 
1.1%
#14
authentification
When an actor claims to have a given identity, the software does not prove or insufficiently proves that the claim is correct.
48
 
1.0%
#15
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.
47
 
1.0%
#16
XSPA
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. By providing URLs to unexpected hosts or ports, attackers can make it appear that the server is sending the request, possibly bypassing access controls such as firewalls that prevent the attackers from accessing the URLs directly. The server can be used as a proxy to conduct port scanning of hosts in internal networks, use other URLs such as that can access documents on the system (using file://), or use other protocols such as gopher:// or tftp://, which may provide greater control over the contents of requests.
42
 
0.9%
#17
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.
40
 
0.9%
#18
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.
39
 
0.8%
#19
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.
36
 
0.8%
#20
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).
34
 
0.7%
#21
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.
33
 
0.7%
#22
Improper Resource Shutdown or Release
The program does not release or incorrectly releases a resource before it is made available for re-use. When a resource is created or allocated, the developer is responsible for properly releasing the resource as well as accounting for all potential paths of expiration or invalidation, such as a set period of time or revocation.
31
 
0.7%
#23
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.
29
 
0.6%
#24
Insertion of Sensitive Information into Log File
Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information.
27
 
0.6%
#25
Authorization
The software does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
27
 
0.6%

By Category

Content Management

MediaWiki

7 vulnerabilities in 2024

Adobe Experience Manager

2 vulnerabilities in 2024

Plone

2 vulnerabilities in 2024

Database

Oracle MySQL

12 vulnerabilities in 2024

PostgreSQL

2 vulnerabilities in 2024

Microsoft SQL Server

1 vulnerability in 2024

Desktop Software

Mozilla Thunderbird

9 vulnerabilities in 2024

Adobe Acrobat

2 vulnerabilities in 2024

Microsoft Office

1 vulnerability in 2024

Development Tools

Oracle Java Development Kit (JDK)

5 vulnerabilities in 2024

Jenkins

2 vulnerabilities in 2024

Microsoft Visual Studio

1 vulnerability in 2024

DevOps

GitLab

10 vulnerabilities in 2024

Java Application Servers

Apache Tomcat

1 vulnerability in 2024

Libraries

Apache Solr

5 vulnerabilities in 2024

OpenSSL

2 vulnerabilities in 2024

Operating Systems

Linux Kernel

59 vulnerabilities in 2024

Apple iPad OS

51 vulnerabilities in 2024

Apple iOS

51 vulnerabilities in 2024

Runtime Environments

Oracle Java Runtime Environment (JRE)

5 vulnerabilities in 2024

Server Software

Microsoft Sharepoint Server

1 vulnerability in 2024

Virtualization

QEMU

2 vulnerabilities in 2024

Web Application Framework

Django Project Django

1 vulnerability in 2024

Web Browsers

Google Chrome

24 vulnerabilities in 2024

Mozilla Firefox

16 vulnerabilities in 2024


Report Last Updated: February 22, 2024