idx int64 | project string | commit_id string | project_url string | commit_url string | commit_message string | target int64 | func string | func_hash float64 | file_name string | file_hash float64 | cwe list | cve string | cve_desc string | nvd_url string |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
309,775 | radvd | 074816cd0b37aac7b3209987e6e998f0a847b275 | https://github.com/reubenhwk/radvd | https://github.com/reubenhwk/radvd/commit/074816cd0b37aac7b3209987e6e998f0a847b275 | privsep_read_loop() should return on unprivileged daemon death /
socket close(), not loop forever with polling read() getting -1. | 0 | privsep_read_loop(void)
{
struct privsep_command cmd;
int ret;
while (1) {
ret = readn(pfd, &cmd, sizeof(cmd));
if (ret <= 0) {
/* Error or EOF, give up */
if (ret < 0) {
flog(LOG_ERR, "Exiting, privsep_read_loop had readn error: %s\n",
strerror(errno));
} else {
flog(LOG_ERR, "Exiting... | 177,232,873,372,361,440,000,000,000,000,000,000,000 | privsep-linux.c | 138,067,310,735,821,540,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3603 | The router advertisement daemon (radvd) before 1.8.2 does not properly handle errors in the privsep_init function, which causes the radvd daemon to run as root and has an unspecified impact. | https://nvd.nist.gov/vuln/detail/CVE-2011-3603 |
200,773 | ImageMagick | 65b7c57502bb2b6d22f607383e87cc3eaed94014 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/65b7c57502bb2b6d22f607383e87cc3eaed94014 | https://github.com/ImageMagick/ImageMagick/issues/588 | 1 | static MagickBooleanType WriteCIPImage(const ImageInfo *image_info,Image *image,
ExceptionInfo *exception)
{
char
buffer[MagickPathExtent];
const char
*value;
MagickBooleanType
status;
register const Quantum
*p;
register ssize_t
i,
x;
ssize_t
y;
unsigned char
byte;
... | 234,537,445,911,289,000,000,000,000,000,000,000,000 | cip.c | 22,509,960,080,023,510,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-11639 | When ImageMagick 7.0.6-1 processes a crafted file in convert, it can lead to a heap-based buffer over-read in the WriteCIPImage() function in coders/cip.c, related to the GetPixelLuma function in MagickCore/pixel-accessor.h. | https://nvd.nist.gov/vuln/detail/CVE-2017-11639 |
309,781 | ImageMagick | 65b7c57502bb2b6d22f607383e87cc3eaed94014 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/65b7c57502bb2b6d22f607383e87cc3eaed94014 | https://github.com/ImageMagick/ImageMagick/issues/588 | 0 | static MagickBooleanType WriteCIPImage(const ImageInfo *image_info,Image *image,
ExceptionInfo *exception)
{
char
buffer[MagickPathExtent];
const char
*value;
MagickBooleanType
status;
register const Quantum
*p;
register ssize_t
i,
x;
ssize_t
y;
unsigned char
byte;
... | 218,187,133,521,568,060,000,000,000,000,000,000,000 | cip.c | 207,991,804,247,893,650,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-11639 | When ImageMagick 7.0.6-1 processes a crafted file in convert, it can lead to a heap-based buffer over-read in the WriteCIPImage() function in coders/cip.c, related to the GetPixelLuma function in MagickCore/pixel-accessor.h. | https://nvd.nist.gov/vuln/detail/CVE-2017-11639 |
200,774 | ruby | b78fa27ae0b717c5569878c106a67d5047e5fb88 | https://github.com/ruby/ruby | https://github.com/ruby/ruby/commit/b78fa27ae0b717c5569878c106a67d5047e5fb88 | unixsocket.c: abstract namespace
* ext/socket/unixsocket.c (unixsock_path_value): fix r62991 for
Linux abstract namespace.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@63000 b2dd03c8-39d4-4d8f-98ff-823fe69b080e | 1 | rsock_init_unixsock(VALUE sock, VALUE path, int server)
{
struct sockaddr_un sockaddr;
socklen_t sockaddrlen;
int fd, status;
rb_io_t *fptr;
FilePathValue(path);
INIT_SOCKADDR_UN(&sockaddr, sizeof(struct sockaddr_un));
if (sizeof(sockaddr.sun_path) < (size_t)RSTRING_LEN(path)) {
rb... | 174,664,950,169,162,180,000,000,000,000,000,000,000 | unixsocket.c | 154,613,522,239,198,170,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2018-8779 | In Ruby before 2.2.10, 2.3.x before 2.3.7, 2.4.x before 2.4.4, 2.5.x before 2.5.1, and 2.6.0-preview1, the UNIXServer.open and UNIXSocket.open methods are not checked for null characters. It may be connected to an unintended socket. | https://nvd.nist.gov/vuln/detail/CVE-2018-8779 |
309,795 | ruby | b78fa27ae0b717c5569878c106a67d5047e5fb88 | https://github.com/ruby/ruby | https://github.com/ruby/ruby/commit/b78fa27ae0b717c5569878c106a67d5047e5fb88 | unixsocket.c: abstract namespace
* ext/socket/unixsocket.c (unixsock_path_value): fix r62991 for
Linux abstract namespace.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@63000 b2dd03c8-39d4-4d8f-98ff-823fe69b080e | 0 | rsock_init_unixsock(VALUE sock, VALUE path, int server)
{
struct sockaddr_un sockaddr;
socklen_t sockaddrlen;
int fd, status;
rb_io_t *fptr;
path = unixsock_path_value(path);
INIT_SOCKADDR_UN(&sockaddr, sizeof(struct sockaddr_un));
if (sizeof(sockaddr.sun_path) < (size_t)RSTRING_LEN(path))... | 276,640,795,225,124,900,000,000,000,000,000,000,000 | unixsocket.c | 294,523,798,467,584,550,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2018-8779 | In Ruby before 2.2.10, 2.3.x before 2.3.7, 2.4.x before 2.4.4, 2.5.x before 2.5.1, and 2.6.0-preview1, the UNIXServer.open and UNIXSocket.open methods are not checked for null characters. It may be connected to an unintended socket. | https://nvd.nist.gov/vuln/detail/CVE-2018-8779 |
200,830 | krb5 | 94e5eda5bb94d1d44733a49c3d9b6d1e42c74def | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/94e5eda5bb94d1d44733a49c3d9b6d1e42c74def | Remove incorrect KDC assertion
The assertion in return_enc_padata() is reachable because
kdc_make_s4u2self_rep() may have previously added encrypted padata.
It is no longer necessary because the code uses add_pa_data_element()
instead of allocating a new list.
CVE-2018-20217:
In MIT krb5 1.8 or later, an authenticat... | 1 | return_enc_padata(krb5_context context, krb5_data *req_pkt,
krb5_kdc_req *request, krb5_keyblock *reply_key,
krb5_db_entry *server, krb5_enc_kdc_rep_part *reply_encpart,
krb5_boolean is_referral)
{
krb5_error_code code = 0;
/* This should be initialized and ... | 197,996,220,497,572,680,000,000,000,000,000,000,000 | kdc_preauth.c | 186,938,281,742,597,440,000,000,000,000,000,000,000 | [
"CWE-617"
] | CVE-2018-20217 | A Reachable Assertion issue was discovered in the KDC in MIT Kerberos 5 (aka krb5) before 1.17. If an attacker can obtain a krbtgt ticket using an older encryption type (single-DES, triple-DES, or RC4), the attacker can crash the KDC by making an S4U2Self request. | https://nvd.nist.gov/vuln/detail/CVE-2018-20217 |
310,215 | krb5 | 94e5eda5bb94d1d44733a49c3d9b6d1e42c74def | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/94e5eda5bb94d1d44733a49c3d9b6d1e42c74def | Remove incorrect KDC assertion
The assertion in return_enc_padata() is reachable because
kdc_make_s4u2self_rep() may have previously added encrypted padata.
It is no longer necessary because the code uses add_pa_data_element()
instead of allocating a new list.
CVE-2018-20217:
In MIT krb5 1.8 or later, an authenticat... | 0 | return_enc_padata(krb5_context context, krb5_data *req_pkt,
krb5_kdc_req *request, krb5_keyblock *reply_key,
krb5_db_entry *server, krb5_enc_kdc_rep_part *reply_encpart,
krb5_boolean is_referral)
{
krb5_error_code code = 0;
/* This should be initialized and ... | 231,551,302,451,688,220,000,000,000,000,000,000,000 | kdc_preauth.c | 218,111,317,851,885,500,000,000,000,000,000,000,000 | [
"CWE-617"
] | CVE-2018-20217 | A Reachable Assertion issue was discovered in the KDC in MIT Kerberos 5 (aka krb5) before 1.17. If an attacker can obtain a krbtgt ticket using an older encryption type (single-DES, triple-DES, or RC4), the attacker can crash the KDC by making an S4U2Self request. | https://nvd.nist.gov/vuln/detail/CVE-2018-20217 |
200,892 | vim | 53575521406739cf20bbe4e384d88e7dca11f040 | https://github.com/vim/vim | https://github.com/vim/vim/commit/53575521406739cf20bbe4e384d88e7dca11f040 | patch 8.1.1365: source command doesn't check for the sandbox
Problem: Source command doesn't check for the sandbox. (Armin Razmjou)
Solution: Check for the sandbox when sourcing a file. | 1 | openscript(
char_u *name,
int directly) /* when TRUE execute directly */
{
if (curscript + 1 == NSCRIPT)
{
emsg(_(e_nesting));
return;
}
#ifdef FEAT_EVAL
if (ignore_script)
/* Not reading from script, also don't open one. Warning message? */
return;
#endif
if (scriptin[curscript] != N... | 162,647,285,126,653,060,000,000,000,000,000,000,000 | None | null | [
"CWE-78"
] | CVE-2019-12735 | getchar.c in Vim before 8.1.1365 and Neovim before 0.3.6 allows remote attackers to execute arbitrary OS commands via the :source! command in a modeline, as demonstrated by execute in Vim, and assert_fails or nvim_input in Neovim. | https://nvd.nist.gov/vuln/detail/CVE-2019-12735 |
312,279 | vim | 53575521406739cf20bbe4e384d88e7dca11f040 | https://github.com/vim/vim | https://github.com/vim/vim/commit/53575521406739cf20bbe4e384d88e7dca11f040 | patch 8.1.1365: source command doesn't check for the sandbox
Problem: Source command doesn't check for the sandbox. (Armin Razmjou)
Solution: Check for the sandbox when sourcing a file. | 0 | openscript(
char_u *name,
int directly) /* when TRUE execute directly */
{
if (curscript + 1 == NSCRIPT)
{
emsg(_(e_nesting));
return;
}
// Disallow sourcing a file in the sandbox, the commands would be executed
// later, possibly outside of the sandbox.
if (check_secure())
return;
... | 121,961,882,524,260,670,000,000,000,000,000,000,000 | None | null | [
"CWE-78"
] | CVE-2019-12735 | getchar.c in Vim before 8.1.1365 and Neovim before 0.3.6 allows remote attackers to execute arbitrary OS commands via the :source! command in a modeline, as demonstrated by execute in Vim, and assert_fails or nvim_input in Neovim. | https://nvd.nist.gov/vuln/detail/CVE-2019-12735 |
200,894 | hexchat | 15600f405f2d5bda6ccf0dd73957395716e0d4d3 | https://github.com/hexchat/hexchat | https://github.com/hexchat/hexchat/commit/15600f405f2d5bda6ccf0dd73957395716e0d4d3 | Sanitize network name for scrollback files
This prevents using invalid chars on Windows or creating directories | 1 | scrollback_get_filename (session *sess)
{
char *net, *chan, *buf, *ret = NULL;
net = server_get_network (sess->server, FALSE);
if (!net)
return NULL;
buf = g_strdup_printf ("%s" G_DIR_SEPARATOR_S "scrollback" G_DIR_SEPARATOR_S "%s" G_DIR_SEPARATOR_S "%s.txt", get_xdir (), net, "");
mkdir_p (buf);
g_free (buf)... | 143,139,466,715,205,830,000,000,000,000,000,000,000 | text.c | 251,821,616,015,300,800,000,000,000,000,000,000,000 | [
"CWE-22"
] | CVE-2016-2087 | Directory traversal vulnerability in the client in HexChat 2.11.0 allows remote IRC servers to read or modify arbitrary files via a .. (dot dot) in the server name. | https://nvd.nist.gov/vuln/detail/CVE-2016-2087 |
312,369 | hexchat | 15600f405f2d5bda6ccf0dd73957395716e0d4d3 | https://github.com/hexchat/hexchat | https://github.com/hexchat/hexchat/commit/15600f405f2d5bda6ccf0dd73957395716e0d4d3 | Sanitize network name for scrollback files
This prevents using invalid chars on Windows or creating directories | 0 | scrollback_get_filename (session *sess)
{
char *net, *chan, *buf, *ret = NULL;
net = server_get_network (sess->server, FALSE);
if (!net)
return NULL;
net = log_create_filename (net);
buf = g_strdup_printf ("%s" G_DIR_SEPARATOR_S "scrollback" G_DIR_SEPARATOR_S "%s" G_DIR_SEPARATOR_S "%s.txt", get_xdir (), net, ... | 103,590,528,563,019,200,000,000,000,000,000,000,000 | text.c | 322,354,928,720,240,700,000,000,000,000,000,000,000 | [
"CWE-22"
] | CVE-2016-2087 | Directory traversal vulnerability in the client in HexChat 2.11.0 allows remote IRC servers to read or modify arbitrary files via a .. (dot dot) in the server name. | https://nvd.nist.gov/vuln/detail/CVE-2016-2087 |
200,896 | ImageMagick6 | dfa1e752bce7b6994765897fb6606d6069345442 | https://github.com/ImageMagick/ImageMagick6 | https://github.com/ImageMagick/ImageMagick6/commit/dfa1e752bce7b6994765897fb6606d6069345442 | https://github.com/ImageMagick/ImageMagick/issues/1453 | 1 | static MagickBooleanType WriteBMPImage(const ImageInfo *image_info,Image *image)
{
BMPInfo
bmp_info;
BMPSubtype
bmp_subtype;
const char
*option;
const StringInfo
*profile;
MagickBooleanType
have_color_info,
status;
MemoryInfo
*pixel_info;
MagickOffsetType
scene;
re... | 20,469,161,862,669,280,000,000,000,000,000,000,000 | bmp.c | 262,370,016,928,103,200,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2019-7398 | In ImageMagick before 7.0.8-25, a memory leak exists in WriteDIBImage in coders/dib.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-7398 |
312,599 | ImageMagick6 | dfa1e752bce7b6994765897fb6606d6069345442 | https://github.com/ImageMagick/ImageMagick6 | https://github.com/ImageMagick/ImageMagick6/commit/dfa1e752bce7b6994765897fb6606d6069345442 | https://github.com/ImageMagick/ImageMagick/issues/1453 | 0 | static MagickBooleanType WriteBMPImage(const ImageInfo *image_info,Image *image)
{
BMPInfo
bmp_info;
BMPSubtype
bmp_subtype;
const char
*option;
const StringInfo
*profile;
MagickBooleanType
have_color_info,
status;
MemoryInfo
*pixel_info;
MagickOffsetType
scene;
re... | 267,760,426,874,115,050,000,000,000,000,000,000,000 | bmp.c | 304,687,732,120,614,630,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2019-7398 | In ImageMagick before 7.0.8-25, a memory leak exists in WriteDIBImage in coders/dib.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-7398 |
200,922 | ImageMagick6 | 6d46f0a046a58e7c4567a86ba1b9cb847d5b1968 | https://github.com/ImageMagick/ImageMagick6 | https://github.com/ImageMagick/ImageMagick6/commit/6d46f0a046a58e7c4567a86ba1b9cb847d5b1968 | https://github.com/ImageMagick/ImageMagick/issues/1553 | 1 | static Image *ReadXWDImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
#define CheckOverflowException(length,width,height) \
(((height) != 0) && ((length)/((size_t) height) != ((size_t) width)))
char
*comment;
Image
*image;
IndexPacket
index;
int
x_status;
MagickBooleanType
... | 192,654,359,557,956,100,000,000,000,000,000,000,000 | xwd.c | 325,455,591,566,963,030,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2019-15139 | The XWD image (X Window System window dumping file) parsing component in ImageMagick 7.0.8-41 Q16 allows attackers to cause a denial-of-service (application crash resulting from an out-of-bounds Read) in ReadXWDImage in coders/xwd.c by crafting a corrupted XWD image file, a different vulnerability than CVE-2019-11472. | https://nvd.nist.gov/vuln/detail/CVE-2019-15139 |
312,948 | ImageMagick6 | 6d46f0a046a58e7c4567a86ba1b9cb847d5b1968 | https://github.com/ImageMagick/ImageMagick6 | https://github.com/ImageMagick/ImageMagick6/commit/6d46f0a046a58e7c4567a86ba1b9cb847d5b1968 | https://github.com/ImageMagick/ImageMagick/issues/1553 | 0 | static Image *ReadXWDImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
#define CheckOverflowException(length,width,height) \
(((height) != 0) && ((length)/((size_t) height) != ((size_t) width)))
char
*comment;
Image
*image;
IndexPacket
index;
int
x_status;
MagickBooleanType
... | 20,429,259,260,290,222,000,000,000,000,000,000,000 | xwd.c | 308,828,352,349,366,360,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2019-15139 | The XWD image (X Window System window dumping file) parsing component in ImageMagick 7.0.8-41 Q16 allows attackers to cause a denial-of-service (application crash resulting from an out-of-bounds Read) in ReadXWDImage in coders/xwd.c by crafting a corrupted XWD image file, a different vulnerability than CVE-2019-11472. | https://nvd.nist.gov/vuln/detail/CVE-2019-15139 |
200,941 | ImageMagick | 12a43437fec6f9245327636dc2730863bb9fdd8b | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/12a43437fec6f9245327636dc2730863bb9fdd8b | https://github.com/ImageMagick/ImageMagick/issues/809 | 1 | static Image *ReadPCDImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
Image
*image;
MagickBooleanType
status;
MagickOffsetType
offset;
MagickSizeType
number_pixels;
register ssize_t
i,
y;
register Quantum
*q;
register unsigned char
*c1,
*c2,
*yy;
... | 6,837,854,870,305,881,000,000,000,000,000,000,000 | pcd.c | 4,717,478,062,973,598,500,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-18251 | An issue was discovered in ImageMagick 7.0.7. A memory leak vulnerability was found in the function ReadPCDImage in coders/pcd.c, which allow remote attackers to cause a denial of service via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2017-18251 |
313,249 | ImageMagick | 12a43437fec6f9245327636dc2730863bb9fdd8b | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/12a43437fec6f9245327636dc2730863bb9fdd8b | https://github.com/ImageMagick/ImageMagick/issues/809 | 0 | static Image *ReadPCDImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
Image
*image;
MagickBooleanType
status;
MagickOffsetType
offset;
MagickSizeType
number_pixels;
register ssize_t
i,
y;
register Quantum
*q;
register unsigned char
*c1,
*c2,
*yy;
... | 136,392,093,115,462,460,000,000,000,000,000,000,000 | pcd.c | 1,055,054,498,085,152,200,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-18251 | An issue was discovered in ImageMagick 7.0.7. A memory leak vulnerability was found in the function ReadPCDImage in coders/pcd.c, which allow remote attackers to cause a denial of service via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2017-18251 |
200,950 | ImageMagick6 | 9eda4b36a8695e4a0cd27bea28b9c173c68a01ec | https://github.com/ImageMagick/ImageMagick6 | https://github.com/ImageMagick/ImageMagick6/commit/9eda4b36a8695e4a0cd27bea28b9c173c68a01ec | Fixed infinite loop (#1095). | 1 | static Image *ReadOneMNGImage(MngInfo* mng_info, const ImageInfo *image_info,
ExceptionInfo *exception)
{
char
page_geometry[MaxTextExtent];
Image
*image;
MagickBooleanType
logging;
volatile int
first_mng_object,
object_id,
term_chunk_found,
skip_to_iend;
volatile ssize_t
... | 156,779,912,196,678,640,000,000,000,000,000,000,000 | png.c | 299,868,079,871,887,300,000,000,000,000,000,000,000 | [
"CWE-835"
] | CVE-2018-10177 | In ImageMagick 7.0.7-28, there is an infinite loop in the ReadOneMNGImage function of the coders/png.c file. Remote attackers could leverage this vulnerability to cause a denial of service via a crafted mng file. | https://nvd.nist.gov/vuln/detail/CVE-2018-10177 |
313,408 | ImageMagick6 | 9eda4b36a8695e4a0cd27bea28b9c173c68a01ec | https://github.com/ImageMagick/ImageMagick6 | https://github.com/ImageMagick/ImageMagick6/commit/9eda4b36a8695e4a0cd27bea28b9c173c68a01ec | Fixed infinite loop (#1095). | 0 | static Image *ReadOneMNGImage(MngInfo* mng_info, const ImageInfo *image_info,
ExceptionInfo *exception)
{
char
page_geometry[MaxTextExtent];
Image
*image;
MagickBooleanType
logging;
volatile int
first_mng_object,
object_id,
term_chunk_found,
skip_to_iend;
volatile ssize_t
... | 282,893,944,872,126,260,000,000,000,000,000,000,000 | png.c | 113,007,104,695,011,190,000,000,000,000,000,000,000 | [
"CWE-835"
] | CVE-2018-10177 | In ImageMagick 7.0.7-28, there is an infinite loop in the ReadOneMNGImage function of the coders/png.c file. Remote attackers could leverage this vulnerability to cause a denial of service via a crafted mng file. | https://nvd.nist.gov/vuln/detail/CVE-2018-10177 |
200,951 | libexpat | f0bec73b018caa07d3e75ec8dd967f3785d71bde | https://github.com/libexpat/libexpat | https://github.com/libexpat/libexpat/commit/f0bec73b018caa07d3e75ec8dd967f3785d71bde | Avoid relying on undefined behavior in CVE-2015-1283 fix. It does not really work: https://godbolt.org/g/Zl8gdF | 1 | XML_GetBuffer(XML_Parser parser, int len)
{
if (len < 0) {
errorCode = XML_ERROR_NO_MEMORY;
return NULL;
}
switch (ps_parsing) {
case XML_SUSPENDED:
errorCode = XML_ERROR_SUSPENDED;
return NULL;
case XML_FINISHED:
errorCode = XML_ERROR_FINISHED;
return NULL;
default: ;
}
if (len... | 265,977,614,244,148,300,000,000,000,000,000,000,000 | xmlparse.c | 255,412,049,757,479,900,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-2716 | Buffer overflow in the XML parser in Mozilla Firefox before 38.0, Firefox ESR 31.x before 31.7, and Thunderbird before 31.7 allows remote attackers to execute arbitrary code by providing a large amount of compressed XML data, a related issue to CVE-2015-1283. | https://nvd.nist.gov/vuln/detail/CVE-2015-2716 |
313,432 | libexpat | f0bec73b018caa07d3e75ec8dd967f3785d71bde | https://github.com/libexpat/libexpat | https://github.com/libexpat/libexpat/commit/f0bec73b018caa07d3e75ec8dd967f3785d71bde | Avoid relying on undefined behavior in CVE-2015-1283 fix. It does not really work: https://godbolt.org/g/Zl8gdF | 0 | XML_GetBuffer(XML_Parser parser, int len)
{
if (len < 0) {
errorCode = XML_ERROR_NO_MEMORY;
return NULL;
}
switch (ps_parsing) {
case XML_SUSPENDED:
errorCode = XML_ERROR_SUSPENDED;
return NULL;
case XML_FINISHED:
errorCode = XML_ERROR_FINISHED;
return NULL;
default: ;
}
if (len... | 322,591,139,256,552,430,000,000,000,000,000,000,000 | xmlparse.c | 161,699,158,063,407,620,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-2716 | Buffer overflow in the XML parser in Mozilla Firefox before 38.0, Firefox ESR 31.x before 31.7, and Thunderbird before 31.7 allows remote attackers to execute arbitrary code by providing a large amount of compressed XML data, a related issue to CVE-2015-1283. | https://nvd.nist.gov/vuln/detail/CVE-2015-2716 |
200,953 | linux | be6123df1ea8f01ee2f896a16c2b7be3e4557a5a | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=be6123df1ea8f01ee2f896a16c2b7be3e4557a5a | usbip: fix stub_send_ret_submit() vulnerability to null transfer_buffer
stub_send_ret_submit() handles urb with a potential null transfer_buffer,
when it replays a packet with potential malicious data that could contain
a null buffer. Add a check for the condition when actual_length > 0 and
transfer_buffer is null.
R... | 1 | static int stub_send_ret_submit(struct stub_device *sdev)
{
unsigned long flags;
struct stub_priv *priv, *tmp;
struct msghdr msg;
size_t txsize;
size_t total_size = 0;
while ((priv = dequeue_from_priv_tx(sdev)) != NULL) {
int ret;
struct urb *urb = priv->urb;
struct usbip_header pdu_header;
struct usbi... | 255,333,746,508,916,340,000,000,000,000,000,000,000 | stub_tx.c | 152,313,205,980,280,350,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-16914 | The "stub_send_ret_submit()" function (drivers/usb/usbip/stub_tx.c) in the Linux Kernel before version 4.14.8, 4.9.71, 4.1.49, and 4.4.107 allows attackers to cause a denial of service (NULL pointer dereference) via a specially crafted USB over IP packet. | https://nvd.nist.gov/vuln/detail/CVE-2017-16914 |
313,482 | linux | be6123df1ea8f01ee2f896a16c2b7be3e4557a5a | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=be6123df1ea8f01ee2f896a16c2b7be3e4557a5a | usbip: fix stub_send_ret_submit() vulnerability to null transfer_buffer
stub_send_ret_submit() handles urb with a potential null transfer_buffer,
when it replays a packet with potential malicious data that could contain
a null buffer. Add a check for the condition when actual_length > 0 and
transfer_buffer is null.
R... | 0 | static int stub_send_ret_submit(struct stub_device *sdev)
{
unsigned long flags;
struct stub_priv *priv, *tmp;
struct msghdr msg;
size_t txsize;
size_t total_size = 0;
while ((priv = dequeue_from_priv_tx(sdev)) != NULL) {
int ret;
struct urb *urb = priv->urb;
struct usbip_header pdu_header;
struct usbi... | 10,136,828,789,580,677,000,000,000,000,000,000,000 | stub_tx.c | 147,491,924,944,177,820,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-16914 | The "stub_send_ret_submit()" function (drivers/usb/usbip/stub_tx.c) in the Linux Kernel before version 4.14.8, 4.9.71, 4.1.49, and 4.4.107 allows attackers to cause a denial of service (NULL pointer dereference) via a specially crafted USB over IP packet. | https://nvd.nist.gov/vuln/detail/CVE-2017-16914 |
200,955 | linux | 434a964daa14b9db083ce20404a4a2add54d037a | https://github.com/torvalds/linux | http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=434a964daa14b9db083ce20404a4a2add54d037a | hfs: fix hfs_find_init() sb->ext_tree NULL ptr oops
Clement Lecigne reports a filesystem which causes a kernel oops in
hfs_find_init() trying to dereference sb->ext_tree which is NULL.
This proves to be because the filesystem has a corrupted MDB extent
record, where the extents file does not fit into the first three ... | 1 | struct hfs_btree *hfs_btree_open(struct super_block *sb, u32 id, btree_keycmp keycmp)
{
struct hfs_btree *tree;
struct hfs_btree_header_rec *head;
struct address_space *mapping;
struct page *page;
unsigned int size;
tree = kzalloc(sizeof(*tree), GFP_KERNEL);
if (!tree)
return NULL;
mutex_init(&tree->tree_lo... | 19,973,278,850,996,690,000,000,000,000,000,000,000 | btree.c | 87,760,018,951,967,960,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-2203 | The hfs_find_init function in the Linux kernel 2.6 allows local users to cause a denial of service (NULL pointer dereference and Oops) by mounting an HFS file system with a malformed MDB extent record. | https://nvd.nist.gov/vuln/detail/CVE-2011-2203 |
313,514 | linux | 434a964daa14b9db083ce20404a4a2add54d037a | https://github.com/torvalds/linux | http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=434a964daa14b9db083ce20404a4a2add54d037a | hfs: fix hfs_find_init() sb->ext_tree NULL ptr oops
Clement Lecigne reports a filesystem which causes a kernel oops in
hfs_find_init() trying to dereference sb->ext_tree which is NULL.
This proves to be because the filesystem has a corrupted MDB extent
record, where the extents file does not fit into the first three ... | 0 | struct hfs_btree *hfs_btree_open(struct super_block *sb, u32 id, btree_keycmp keycmp)
{
struct hfs_btree *tree;
struct hfs_btree_header_rec *head;
struct address_space *mapping;
struct page *page;
unsigned int size;
tree = kzalloc(sizeof(*tree), GFP_KERNEL);
if (!tree)
return NULL;
mutex_init(&tree->tree_lo... | 107,823,270,384,926,560,000,000,000,000,000,000,000 | btree.c | 137,545,881,280,329,640,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-2203 | The hfs_find_init function in the Linux kernel 2.6 allows local users to cause a denial of service (NULL pointer dereference and Oops) by mounting an HFS file system with a malformed MDB extent record. | https://nvd.nist.gov/vuln/detail/CVE-2011-2203 |
200,956 | linux | c171654caa875919be3c533d3518da8be5be966e | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c171654caa875919be3c533d3518da8be5be966e | usbip: usbip_host: fix bad unlock balance during stub_probe()
stub_probe() calls put_busid_priv() in an error path when device isn't
found in the busid_table. Fix it by making put_busid_priv() safe to be
called with null struct bus_id_priv pointer.
This problem happens when "usbip bind" is run without loading usbip_h... | 1 | void put_busid_priv(struct bus_id_priv *bid)
{
spin_unlock(&bid->busid_lock);
} | 30,178,459,441,592,590,000,000,000,000,000,000,000 | stub_main.c | 326,054,074,320,919,300,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2018-5814 | In the Linux Kernel before version 4.16.11, 4.14.43, 4.9.102, and 4.4.133, multiple race condition errors when handling probe, disconnect, and rebind operations can be exploited to trigger a use-after-free condition or a NULL pointer dereference by sending multiple USB over IP packets. | https://nvd.nist.gov/vuln/detail/CVE-2018-5814 |
313,526 | linux | c171654caa875919be3c533d3518da8be5be966e | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c171654caa875919be3c533d3518da8be5be966e | usbip: usbip_host: fix bad unlock balance during stub_probe()
stub_probe() calls put_busid_priv() in an error path when device isn't
found in the busid_table. Fix it by making put_busid_priv() safe to be
called with null struct bus_id_priv pointer.
This problem happens when "usbip bind" is run without loading usbip_h... | 0 | void put_busid_priv(struct bus_id_priv *bid)
{
if (bid)
spin_unlock(&bid->busid_lock);
} | 37,894,960,990,143,783,000,000,000,000,000,000,000 | stub_main.c | 217,383,939,370,297,560,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2018-5814 | In the Linux Kernel before version 4.16.11, 4.14.43, 4.9.102, and 4.4.133, multiple race condition errors when handling probe, disconnect, and rebind operations can be exploited to trigger a use-after-free condition or a NULL pointer dereference by sending multiple USB over IP packets. | https://nvd.nist.gov/vuln/detail/CVE-2018-5814 |
200,959 | libmysofa | 890400ebd092c574707d0c132124f8ff047e20e1 | https://github.com/hoene/libmysofa | https://github.com/hoene/libmysofa/commit/890400ebd092c574707d0c132124f8ff047e20e1 | Fix for issue 163 | 1 | static int readOHDRHeaderMessageDataLayout(struct READER *reader,
struct DATAOBJECT *data) {
int i, err;
unsigned size;
uint8_t dimensionality, layout_class;
uint32_t dataset_element_size;
uint64_t data_address, store, data_size;
UNUSED(dataset_element_size);
... | 303,919,724,976,343,470,000,000,000,000,000,000,000 | dataobject.c | 340,087,383,172,483,800,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-3756 | libmysofa is vulnerable to Heap-based Buffer Overflow | https://nvd.nist.gov/vuln/detail/CVE-2021-3756 |
313,583 | libmysofa | 890400ebd092c574707d0c132124f8ff047e20e1 | https://github.com/hoene/libmysofa | https://github.com/hoene/libmysofa/commit/890400ebd092c574707d0c132124f8ff047e20e1 | Fix for issue 163 | 0 | static int readOHDRHeaderMessageDataLayout(struct READER *reader,
struct DATAOBJECT *data) {
int i, err;
unsigned size;
uint8_t dimensionality, layout_class;
uint32_t dataset_element_size;
uint64_t data_address, store, data_size;
UNUSED(dataset_element_size);
... | 45,954,546,932,527,000,000,000,000,000,000,000,000 | dataobject.c | 15,232,058,106,727,518,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-3756 | libmysofa is vulnerable to Heap-based Buffer Overflow | https://nvd.nist.gov/vuln/detail/CVE-2021-3756 |
200,971 | jasper | c87ad330a8b8d6e5eb0065675601fdfae08ebaab | https://github.com/mdadams/jasper | https://github.com/mdadams/jasper/commit/c87ad330a8b8d6e5eb0065675601fdfae08ebaab | Added fix for CVE-2016-2089. | 1 | void jas_matrix_clip(jas_matrix_t *matrix, jas_seqent_t minval, jas_seqent_t maxval)
{
int i;
int j;
jas_seqent_t v;
jas_seqent_t *rowstart;
jas_seqent_t *data;
int rowstep;
rowstep = jas_matrix_rowstep(matrix);
for (i = matrix->numrows_, rowstart = matrix->rows_[0]; i > 0; --i,
rowstart += rowstep) {
dat... | 56,353,858,046,424,480,000,000,000,000,000,000,000 | jas_seq.c | 78,806,087,802,164,190,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-2089 | The jas_matrix_clip function in jas_seq.c in JasPer 1.900.1 allows remote attackers to cause a denial of service (invalid read and application crash) via a crafted JPEG 2000 image. | https://nvd.nist.gov/vuln/detail/CVE-2016-2089 |
313,642 | jasper | c87ad330a8b8d6e5eb0065675601fdfae08ebaab | https://github.com/mdadams/jasper | https://github.com/mdadams/jasper/commit/c87ad330a8b8d6e5eb0065675601fdfae08ebaab | Added fix for CVE-2016-2089. | 0 | void jas_matrix_clip(jas_matrix_t *matrix, jas_seqent_t minval, jas_seqent_t maxval)
{
int i;
int j;
jas_seqent_t v;
jas_seqent_t *rowstart;
jas_seqent_t *data;
int rowstep;
if (jas_matrix_numrows(matrix) > 0 && jas_matrix_numcols(matrix) > 0) {
assert(matrix->rows_);
rowstep = jas_matrix_rowstep(matrix);
... | 239,409,946,597,081,600,000,000,000,000,000,000,000 | jas_seq.c | 231,791,317,884,716,800,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-2089 | The jas_matrix_clip function in jas_seq.c in JasPer 1.900.1 allows remote attackers to cause a denial of service (invalid read and application crash) via a crafted JPEG 2000 image. | https://nvd.nist.gov/vuln/detail/CVE-2016-2089 |
200,974 | linux | 6e8ab72a812396996035a37e5ca4b3b99b5d214b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6e8ab72a812396996035a37e5ca4b3b99b5d214b | ext4: clear i_data in ext4_inode_info when removing inline data
When converting from an inode from storing the data in-line to a data
block, ext4_destroy_inline_data_nolock() was only clearing the on-disk
copy of the i_blocks[] array. It was not clearing copy of the
i_blocks[] in ext4_inode_info, in i_data[], which i... | 1 | static int ext4_destroy_inline_data_nolock(handle_t *handle,
struct inode *inode)
{
struct ext4_inode_info *ei = EXT4_I(inode);
struct ext4_xattr_ibody_find is = {
.s = { .not_found = 0, },
};
struct ext4_xattr_info i = {
.name_index = EXT4_XATTR_INDEX_SYSTEM,
.name = EXT4_XATTR_SYSTEM_DATA,
.value ... | 98,405,192,362,559,230,000,000,000,000,000,000,000 | inline.c | 102,269,654,588,881,470,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2018-10881 | A flaw was found in the Linux kernel's ext4 filesystem. A local user can cause an out-of-bound access in ext4_get_group_info function, a denial of service, and a system crash by mounting and operating on a crafted ext4 filesystem image. | https://nvd.nist.gov/vuln/detail/CVE-2018-10881 |
313,659 | linux | 6e8ab72a812396996035a37e5ca4b3b99b5d214b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6e8ab72a812396996035a37e5ca4b3b99b5d214b | ext4: clear i_data in ext4_inode_info when removing inline data
When converting from an inode from storing the data in-line to a data
block, ext4_destroy_inline_data_nolock() was only clearing the on-disk
copy of the i_blocks[] array. It was not clearing copy of the
i_blocks[] in ext4_inode_info, in i_data[], which i... | 0 | static int ext4_destroy_inline_data_nolock(handle_t *handle,
struct inode *inode)
{
struct ext4_inode_info *ei = EXT4_I(inode);
struct ext4_xattr_ibody_find is = {
.s = { .not_found = 0, },
};
struct ext4_xattr_info i = {
.name_index = EXT4_XATTR_INDEX_SYSTEM,
.name = EXT4_XATTR_SYSTEM_DATA,
.value ... | 89,935,697,459,733,720,000,000,000,000,000,000,000 | inline.c | 256,578,711,888,485,970,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2018-10881 | A flaw was found in the Linux kernel's ext4 filesystem. A local user can cause an out-of-bound access in ext4_get_group_info function, a denial of service, and a system crash by mounting and operating on a crafted ext4 filesystem image. | https://nvd.nist.gov/vuln/detail/CVE-2018-10881 |
200,975 | evolution | 9c55a311325f5905d8b8403b96607e46cf343f21 | https://git.gnome.org/browse/evolution | https://gitlab.gnome.org/GNOME/evolution/commit/9c55a311325f5905d8b8403b96607e46cf343f21 | I#120 - Show security bar above message headers
Closes https://gitlab.gnome.org/GNOME/evolution/issues/120 | 1 | mail_parser_run (EMailParser *parser,
EMailPartList *part_list,
GCancellable *cancellable)
{
EMailExtensionRegistry *reg;
CamelMimeMessage *message;
EMailPart *mail_part;
GQueue *parsers;
GQueue mail_part_queue = G_QUEUE_INIT;
GList *iter;
GString *part_id;
if (cancellable)
... | 290,388,202,651,309,060,000,000,000,000,000,000,000 | e-mail-parser.c | 67,155,722,424,867,790,000,000,000,000,000,000,000 | [
"CWE-347"
] | CVE-2018-15587 | GNOME Evolution through 3.28.2 is prone to OpenPGP signatures being spoofed for arbitrary messages using a specially crafted email that contains a valid signature from the entity to be impersonated as an attachment. | https://nvd.nist.gov/vuln/detail/CVE-2018-15587 |
313,703 | evolution | 9c55a311325f5905d8b8403b96607e46cf343f21 | https://git.gnome.org/browse/evolution | https://gitlab.gnome.org/GNOME/evolution/commit/9c55a311325f5905d8b8403b96607e46cf343f21 | I#120 - Show security bar above message headers
Closes https://gitlab.gnome.org/GNOME/evolution/issues/120 | 0 | mail_parser_run (EMailParser *parser,
EMailPartList *part_list,
GCancellable *cancellable)
{
EMailExtensionRegistry *reg;
CamelMimeMessage *message;
EMailPart *mail_part;
GQueue *parsers;
GQueue mail_part_queue = G_QUEUE_INIT;
GList *iter;
GString *part_id;
if (cancellable)
... | 2,242,496,258,795,971,200,000,000,000,000,000,000 | e-mail-parser.c | 25,994,638,273,514,145,000,000,000,000,000,000,000 | [
"CWE-347"
] | CVE-2018-15587 | GNOME Evolution through 3.28.2 is prone to OpenPGP signatures being spoofed for arbitrary messages using a specially crafted email that contains a valid signature from the entity to be impersonated as an attachment. | https://nvd.nist.gov/vuln/detail/CVE-2018-15587 |
200,977 | sqlite | effc07ec9c6e08d3bd17665f8800054770f8c643 | https://github.com/sqlite/sqlite | https://github.com/sqlite/sqlite/commit/effc07ec9c6e08d3bd17665f8800054770f8c643 | Fix the whereKeyStats() routine (part of STAT4 processing only) so that it
is able to cope with row-value comparisons against the primary key index
of a WITHOUT ROWID table.
[forum:/forumpost/3607259d3c|Forum post 3607259d3c].
FossilOrigin-Name: 2a6f761864a462de5c2d5bc666b82fb0b7e124a03443cd1482620dde344b34bb | 1 | static int whereKeyStats(
Parse *pParse, /* Database connection */
Index *pIdx, /* Index to consider domain of */
UnpackedRecord *pRec, /* Vector of values to consider */
int roundUp, /* Round up if true. Round down if false */
tRowcnt *aStat /* O... | 48,769,711,458,777,940,000,000,000,000,000,000,000 | where.c | 137,668,648,717,559,740,000,000,000,000,000,000,000 | [
"CWE-129"
] | CVE-2022-35737 | SQLite 1.0.12 through 3.39.x before 3.39.2 sometimes allows an array-bounds overflow if billions of bytes are used in a string argument to a C API. | https://nvd.nist.gov/vuln/detail/CVE-2022-35737 |
313,949 | sqlite | effc07ec9c6e08d3bd17665f8800054770f8c643 | https://github.com/sqlite/sqlite | https://github.com/sqlite/sqlite/commit/effc07ec9c6e08d3bd17665f8800054770f8c643 | Fix the whereKeyStats() routine (part of STAT4 processing only) so that it
is able to cope with row-value comparisons against the primary key index
of a WITHOUT ROWID table.
[forum:/forumpost/3607259d3c|Forum post 3607259d3c].
FossilOrigin-Name: 2a6f761864a462de5c2d5bc666b82fb0b7e124a03443cd1482620dde344b34bb | 0 | static int whereKeyStats(
Parse *pParse, /* Database connection */
Index *pIdx, /* Index to consider domain of */
UnpackedRecord *pRec, /* Vector of values to consider */
int roundUp, /* Round up if true. Round down if false */
tRowcnt *aStat /* O... | 51,488,583,097,733,330,000,000,000,000,000,000,000 | where.c | 112,888,970,864,174,150,000,000,000,000,000,000,000 | [
"CWE-129"
] | CVE-2022-35737 | SQLite 1.0.12 through 3.39.x before 3.39.2 sometimes allows an array-bounds overflow if billions of bytes are used in a string argument to a C API. | https://nvd.nist.gov/vuln/detail/CVE-2022-35737 |
200,978 | dcmtk | 5c14bf53fb42ceca12bbcc0016e8704b1580920d | https://github.com/DCMTK/dcmtk | https://github.com/DCMTK/dcmtk/commit/5c14bf53fb42ceca12bbcc0016e8704b1580920d | Fixed possible NULL pointer dereference.
Thanks to Jinsheng Ba <bajinsheng@u.nus.edu> for the report and patch. | 1 | DU_getStringDOElement(DcmItem *obj, DcmTagKey t, char *s, size_t bufsize)
{
DcmByteString *elem;
DcmStack stack;
OFCondition ec = EC_Normal;
char* aString;
ec = obj->search(t, stack);
elem = (DcmByteString*) stack.top();
if (ec == EC_Normal && elem != NULL) {
if (elem->getLength() =... | 107,010,338,548,374,960,000,000,000,000,000,000,000 | diutil.cc | 115,245,747,608,366,440,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-41689 | DCMTK through 3.6.6 does not handle string copy properly. Sending specific requests to the dcmqrdb program, it would query its database and copy the result even if the result is null, which can incur a head-based overflow. An attacker can use it to launch a DoS attack. | https://nvd.nist.gov/vuln/detail/CVE-2021-41689 |
313,957 | dcmtk | 5c14bf53fb42ceca12bbcc0016e8704b1580920d | https://github.com/DCMTK/dcmtk | https://github.com/DCMTK/dcmtk/commit/5c14bf53fb42ceca12bbcc0016e8704b1580920d | Fixed possible NULL pointer dereference.
Thanks to Jinsheng Ba <bajinsheng@u.nus.edu> for the report and patch. | 0 | DU_getStringDOElement(DcmItem *obj, DcmTagKey t, char *s, size_t bufsize)
{
DcmByteString *elem;
DcmStack stack;
OFCondition ec = EC_Normal;
char* aString;
ec = obj->search(t, stack);
elem = (DcmByteString*) stack.top();
if (ec == EC_Normal && elem != NULL) {
if (elem->getLength() =... | 185,633,881,870,581,070,000,000,000,000,000,000,000 | diutil.cc | 121,565,832,582,889,650,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-41689 | DCMTK through 3.6.6 does not handle string copy properly. Sending specific requests to the dcmqrdb program, it would query its database and copy the result even if the result is null, which can incur a head-based overflow. An attacker can use it to launch a DoS attack. | https://nvd.nist.gov/vuln/detail/CVE-2021-41689 |
201,002 | ghostpdl | 3ebffb1d96ba0cacec23016eccb4047dab365853 | https://github.com/ArtifexSoftware/ghostpdl | http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=3ebffb1d96ba0cacec23016eccb4047dab365853 | Bug 697934: Fix SEGV due to error code being ignored.
The return code from jbig2_decode_text_region was being ignored so the
code continued to try and parse the invalid file using incomplete/empty
structures. | 1 | jbig2_decode_symbol_dict(Jbig2Ctx *ctx,
Jbig2Segment *segment,
const Jbig2SymbolDictParams *params, const byte *data, size_t size, Jbig2ArithCx *GB_stats, Jbig2ArithCx *GR_stats)
{
Jbig2SymbolDict *SDNEWSYMS = NULL;
Jbig2SymbolDict *SDEXSYMS = NULL;
uint32_t... | 55,029,517,433,060,540,000,000,000,000,000,000,000 | jbig2_symbol_dict.c | 172,427,028,252,094,970,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-9216 | libjbig2dec.a in Artifex jbig2dec 0.13, as used in MuPDF and Ghostscript, has a NULL pointer dereference in the jbig2_huffman_get function in jbig2_huffman.c. For example, the jbig2dec utility will crash (segmentation fault) when parsing an invalid file. | https://nvd.nist.gov/vuln/detail/CVE-2017-9216 |
314,425 | ghostpdl | 3ebffb1d96ba0cacec23016eccb4047dab365853 | https://github.com/ArtifexSoftware/ghostpdl | http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=3ebffb1d96ba0cacec23016eccb4047dab365853 | Bug 697934: Fix SEGV due to error code being ignored.
The return code from jbig2_decode_text_region was being ignored so the
code continued to try and parse the invalid file using incomplete/empty
structures. | 0 | jbig2_decode_symbol_dict(Jbig2Ctx *ctx,
Jbig2Segment *segment,
const Jbig2SymbolDictParams *params, const byte *data, size_t size, Jbig2ArithCx *GB_stats, Jbig2ArithCx *GR_stats)
{
Jbig2SymbolDict *SDNEWSYMS = NULL;
Jbig2SymbolDict *SDEXSYMS = NULL;
uint32_t... | 28,653,096,562,962,753,000,000,000,000,000,000,000 | jbig2_symbol_dict.c | 74,460,923,783,160,960,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-9216 | libjbig2dec.a in Artifex jbig2dec 0.13, as used in MuPDF and Ghostscript, has a NULL pointer dereference in the jbig2_huffman_get function in jbig2_huffman.c. For example, the jbig2dec utility will crash (segmentation fault) when parsing an invalid file. | https://nvd.nist.gov/vuln/detail/CVE-2017-9216 |
201,004 | exiv2 | c0ecc2ae36f34462be98623deb85ba1747ae2175 | https://github.com/Exiv2/exiv2 | https://github.com/Exiv2/exiv2/commit/c0ecc2ae36f34462be98623deb85ba1747ae2175 | Avoid integer overflow. | 1 | void CiffDirectory::readDirectory(const byte* pData,
uint32_t size,
ByteOrder byteOrder)
{
if (size < 4)
throw Error(kerCorruptedMetadata);
uint32_t o = getULong(pData + size - 4, byteOrder);
if ... | 234,699,564,507,703,330,000,000,000,000,000,000,000 | crwimage_int.cpp | 127,929,774,243,743,830,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2019-13110 | A CiffDirectory::readDirectory integer overflow and out-of-bounds read in Exiv2 through 0.27.1 allows an attacker to cause a denial of service (SIGSEGV) via a crafted CRW image file. | https://nvd.nist.gov/vuln/detail/CVE-2019-13110 |
314,441 | exiv2 | c0ecc2ae36f34462be98623deb85ba1747ae2175 | https://github.com/Exiv2/exiv2 | https://github.com/Exiv2/exiv2/commit/c0ecc2ae36f34462be98623deb85ba1747ae2175 | Avoid integer overflow. | 0 | void CiffDirectory::readDirectory(const byte* pData,
uint32_t size,
ByteOrder byteOrder)
{
if (size < 4)
throw Error(kerCorruptedMetadata);
uint32_t o = getULong(pData + size - 4, byteOrder);
if ... | 129,470,057,535,671,970,000,000,000,000,000,000,000 | crwimage_int.cpp | 188,792,248,322,457,400,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2019-13110 | A CiffDirectory::readDirectory integer overflow and out-of-bounds read in Exiv2 through 0.27.1 allows an attacker to cause a denial of service (SIGSEGV) via a crafted CRW image file. | https://nvd.nist.gov/vuln/detail/CVE-2019-13110 |
201,005 | ImageMagick | 5af1dffa4b6ab984b5f13d1e91c95760d75f12a6 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/5af1dffa4b6ab984b5f13d1e91c95760d75f12a6 | outside the range of representable values of type 'unsigned char' (#3083)
Co-authored-by: Zhang Xiaohui <ruc_zhangxiaohui@163.com> | 1 | static void ExportIndexQuantum(const Image *image,QuantumInfo *quantum_info,
const MagickSizeType number_pixels,const Quantum *magick_restrict p,
unsigned char *magick_restrict q,ExceptionInfo *exception)
{
ssize_t
x;
ssize_t
bit;
if (image->storage_class != PseudoClass)
{
(void) ThrowMagi... | 169,574,674,742,992,000,000,000,000,000,000,000,000 | quantum-export.c | 14,134,617,435,550,894,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2021-20224 | An integer overflow issue was discovered in ImageMagick's ExportIndexQuantum() function in MagickCore/quantum-export.c. Function calls to GetPixelIndex() could result in values outside the range of representable for the 'unsigned char'. When ImageMagick processes a crafted pdf file, this could lead to an undefined beha... | https://nvd.nist.gov/vuln/detail/CVE-2021-20224 |
314,465 | ImageMagick | 5af1dffa4b6ab984b5f13d1e91c95760d75f12a6 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/5af1dffa4b6ab984b5f13d1e91c95760d75f12a6 | outside the range of representable values of type 'unsigned char' (#3083)
Co-authored-by: Zhang Xiaohui <ruc_zhangxiaohui@163.com> | 0 | static void ExportIndexQuantum(const Image *image,QuantumInfo *quantum_info,
const MagickSizeType number_pixels,const Quantum *magick_restrict p,
unsigned char *magick_restrict q,ExceptionInfo *exception)
{
ssize_t
x;
ssize_t
bit;
if (image->storage_class != PseudoClass)
{
(void) ThrowMagi... | 98,990,446,017,171,350,000,000,000,000,000,000,000 | quantum-export.c | 179,926,645,166,190,050,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2021-20224 | An integer overflow issue was discovered in ImageMagick's ExportIndexQuantum() function in MagickCore/quantum-export.c. Function calls to GetPixelIndex() could result in values outside the range of representable for the 'unsigned char'. When ImageMagick processes a crafted pdf file, this could lead to an undefined beha... | https://nvd.nist.gov/vuln/detail/CVE-2021-20224 |
201,331 | pango | 797d46714d27f147277fdd5346648d838c68fb8c | http://github.com/bratsche/pango | http://git.gnome.org/browse/pango/commit/?id=797d46714d27f147277fdd5346648d838c68fb8c | [HB/GDEF] Fix bug in building synthetic GDEF table | 1 | hb_ot_layout_build_glyph_classes (hb_face_t *face,
uint16_t num_total_glyphs,
hb_codepoint_t *glyphs,
unsigned char *klasses,
uint16_t count)
{
if (HB_OBJECT_IS_INERT (face))
return;
hb_ot_layout_t *layout = &face->ot_layout;
if (HB_UNLIKELY (!count || !glyphs || ... | 100,436,834,578,070,800,000,000,000,000,000,000,000 | hb-ot-layout.cc | 160,813,645,271,251,100,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2010-0421 | Array index error in the hb_ot_layout_build_glyph_classes function in pango/opentype/hb-ot-layout.cc in Pango before 1.27.1 allows context-dependent attackers to cause a denial of service (application crash) via a crafted font file, related to building a synthetic Glyph Definition (aka GDEF) table by using this font's ... | https://nvd.nist.gov/vuln/detail/CVE-2010-0421 |
316,702 | pango | 797d46714d27f147277fdd5346648d838c68fb8c | http://github.com/bratsche/pango | http://git.gnome.org/browse/pango/commit/?id=797d46714d27f147277fdd5346648d838c68fb8c | [HB/GDEF] Fix bug in building synthetic GDEF table | 0 | hb_ot_layout_build_glyph_classes (hb_face_t *face,
uint16_t num_total_glyphs,
hb_codepoint_t *glyphs,
unsigned char *klasses,
uint16_t count)
{
if (HB_OBJECT_IS_INERT (face))
return;
hb_ot_layout_t *layout = &face->ot_layout;
if (HB_UNLIKELY (!count || !glyphs || ... | 229,917,394,272,009,200,000,000,000,000,000,000,000 | hb-ot-layout.cc | 304,776,444,887,744,750,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2010-0421 | Array index error in the hb_ot_layout_build_glyph_classes function in pango/opentype/hb-ot-layout.cc in Pango before 1.27.1 allows context-dependent attackers to cause a denial of service (application crash) via a crafted font file, related to building a synthetic Glyph Definition (aka GDEF) table by using this font's ... | https://nvd.nist.gov/vuln/detail/CVE-2010-0421 |
201,334 | leptonica | 3c18c43b6a3f753f0dfff99610d46ad46b8bfac4 | https://github.com/DanBloomberg/leptonica | https://github.com/DanBloomberg/leptonica/commit/3c18c43b6a3f753f0dfff99610d46ad46b8bfac4 | Fixing oss-fuzz issue 22512: Heap-buffer-overflow in rasteropGeneralLow()
* Simplified the hole-filling function
` | 1 | pixFillMapHoles(PIX *pix,
l_int32 nx,
l_int32 ny,
l_int32 filltype)
{
l_int32 w, h, y, nmiss, goodcol, i, j, found, ival, valtest;
l_uint32 val, lastval;
NUMA *na; /* indicates if there is any data in the column */
PIX *pixt;
PROCNAME("pixFillMapH... | 269,808,131,955,249,960,000,000,000,000,000,000,000 | adaptmap.c | 48,740,609,232,776,170,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2020-36279 | Leptonica before 1.80.0 allows a heap-based buffer over-read in rasteropGeneralLow, related to adaptmap_reg.c and adaptmap.c. | https://nvd.nist.gov/vuln/detail/CVE-2020-36279 |
316,775 | leptonica | 3c18c43b6a3f753f0dfff99610d46ad46b8bfac4 | https://github.com/DanBloomberg/leptonica | https://github.com/DanBloomberg/leptonica/commit/3c18c43b6a3f753f0dfff99610d46ad46b8bfac4 | Fixing oss-fuzz issue 22512: Heap-buffer-overflow in rasteropGeneralLow()
* Simplified the hole-filling function
` | 0 | pixFillMapHoles(PIX *pix,
l_int32 nx,
l_int32 ny,
l_int32 filltype)
{
l_int32 w, h, y, nmiss, goodcol, i, j, found, ival, valtest;
l_uint32 val, lastval;
NUMA *na; /* indicates if there is any data in the column */
PROCNAME("pixFillMapHoles");
if ... | 220,065,928,429,414,630,000,000,000,000,000,000,000 | adaptmap.c | 24,245,234,386,295,843,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2020-36279 | Leptonica before 1.80.0 allows a heap-based buffer over-read in rasteropGeneralLow, related to adaptmap_reg.c and adaptmap.c. | https://nvd.nist.gov/vuln/detail/CVE-2020-36279 |
201,335 | leptonica | 3c18c43b6a3f753f0dfff99610d46ad46b8bfac4 | https://github.com/DanBloomberg/leptonica | https://github.com/DanBloomberg/leptonica/commit/3c18c43b6a3f753f0dfff99610d46ad46b8bfac4 | Fixing oss-fuzz issue 22512: Heap-buffer-overflow in rasteropGeneralLow()
* Simplified the hole-filling function
` | 1 | int main(int argc,
char **argv)
{
l_int32 w, h;
PIX *pixs, *pixg, *pixim, *pixgm, *pixmi, *pix1, *pix2;
PIX *pixmr, *pixmg, *pixmb, *pixmri, *pixmgi, *pixmbi;
PIXA *pixa;
L_REGPARAMS *rp;
if (regTestSetup(argc, argv, &rp))
return 1;
lept_mkdir("lept/adapt")... | 151,244,818,702,939,720,000,000,000,000,000,000,000 | adaptmap_reg.c | 338,292,547,743,803,100,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2020-36279 | Leptonica before 1.80.0 allows a heap-based buffer over-read in rasteropGeneralLow, related to adaptmap_reg.c and adaptmap.c. | https://nvd.nist.gov/vuln/detail/CVE-2020-36279 |
316,752 | leptonica | 3c18c43b6a3f753f0dfff99610d46ad46b8bfac4 | https://github.com/DanBloomberg/leptonica | https://github.com/DanBloomberg/leptonica/commit/3c18c43b6a3f753f0dfff99610d46ad46b8bfac4 | Fixing oss-fuzz issue 22512: Heap-buffer-overflow in rasteropGeneralLow()
* Simplified the hole-filling function
` | 0 | int main(int argc,
char **argv)
{
l_int32 w, h;
PIX *pixs, *pixg, *pixim, *pixgm, *pixmi, *pix1, *pix2;
PIX *pixmr, *pixmg, *pixmb, *pixmri, *pixmgi, *pixmbi;
PIXA *pixa, *pixa2;
L_REGPARAMS *rp;
if (regTestSetup(argc, argv, &rp))
return 1;
lept_mkdir("lept... | 228,107,596,609,370,240,000,000,000,000,000,000,000 | adaptmap_reg.c | 108,656,170,250,014,530,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2020-36279 | Leptonica before 1.80.0 allows a heap-based buffer over-read in rasteropGeneralLow, related to adaptmap_reg.c and adaptmap.c. | https://nvd.nist.gov/vuln/detail/CVE-2020-36279 |
201,350 | qemu | ff0507c239a246fd7215b31c5658fc6a3ee1e4c5 | https://github.com/bonzini/qemu | https://git.qemu.org/?p=qemu.git;a=commit;h=ff0507c239a246fd7215b31c5658fc6a3ee1e4c5 | block/iscsi:fix heap-buffer-overflow in iscsi_aio_ioctl_cb
There is an overflow, the source 'datain.data[2]' is 100 bytes,
but the 'ss' is 252 bytes.This may cause a security issue because
we can access a lot of unrelated memory data.
The len for sbp copy data should take the minimum of mx_sb_len and
sb_len_wr, no... | 1 | iscsi_aio_ioctl_cb(struct iscsi_context *iscsi, int status,
void *command_data, void *opaque)
{
IscsiAIOCB *acb = opaque;
if (status == SCSI_STATUS_CANCELLED) {
if (!acb->bh) {
acb->status = -ECANCELED;
iscsi_schedule_bh(acb);
}
return;
}... | 44,940,427,063,818,650,000,000,000,000,000,000,000 | iscsi.c | 173,130,515,852,083,460,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2020-11947 | iscsi_aio_ioctl_cb in block/iscsi.c in QEMU 4.1.0 has a heap-based buffer over-read that may disclose unrelated information from process memory to an attacker. | https://nvd.nist.gov/vuln/detail/CVE-2020-11947 |
318,045 | qemu | ff0507c239a246fd7215b31c5658fc6a3ee1e4c5 | https://github.com/bonzini/qemu | https://git.qemu.org/?p=qemu.git;a=commit;h=ff0507c239a246fd7215b31c5658fc6a3ee1e4c5 | block/iscsi:fix heap-buffer-overflow in iscsi_aio_ioctl_cb
There is an overflow, the source 'datain.data[2]' is 100 bytes,
but the 'ss' is 252 bytes.This may cause a security issue because
we can access a lot of unrelated memory data.
The len for sbp copy data should take the minimum of mx_sb_len and
sb_len_wr, no... | 0 | iscsi_aio_ioctl_cb(struct iscsi_context *iscsi, int status,
void *command_data, void *opaque)
{
IscsiAIOCB *acb = opaque;
if (status == SCSI_STATUS_CANCELLED) {
if (!acb->bh) {
acb->status = -ECANCELED;
iscsi_schedule_bh(acb);
}
return;
}... | 79,620,249,607,934,530,000,000,000,000,000,000,000 | iscsi.c | 305,139,190,802,895,450,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2020-11947 | iscsi_aio_ioctl_cb in block/iscsi.c in QEMU 4.1.0 has a heap-based buffer over-read that may disclose unrelated information from process memory to an attacker. | https://nvd.nist.gov/vuln/detail/CVE-2020-11947 |
201,354 | linux | 2671fa4dc0109d3fb581bc3078fdf17b5d9080f6 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2671fa4dc0109d3fb581bc3078fdf17b5d9080f6 | netfilter: conntrack: Make global sysctls readonly in non-init netns
These sysctls point to global variables:
- NF_SYSCTL_CT_MAX (&nf_conntrack_max)
- NF_SYSCTL_CT_EXPECT_MAX (&nf_ct_expect_max)
- NF_SYSCTL_CT_BUCKETS (&nf_conntrack_htable_size_user)
Because their data pointers are not updated to point to per-netns
s... | 1 | static int nf_conntrack_standalone_init_sysctl(struct net *net)
{
struct nf_conntrack_net *cnet = net_generic(net, nf_conntrack_net_id);
struct nf_udp_net *un = nf_udp_pernet(net);
struct ctl_table *table;
BUILD_BUG_ON(ARRAY_SIZE(nf_ct_sysctl_table) != NF_SYSCTL_CT_LAST_SYSCTL);
table = kmemdup(nf_ct_sysctl_tabl... | 243,849,601,090,906,000,000,000,000,000,000,000,000 | nf_conntrack_standalone.c | 300,320,494,900,259,100,000,000,000,000,000,000,000 | [
"CWE-203"
] | CVE-2021-38209 | net/netfilter/nf_conntrack_standalone.c in the Linux kernel before 5.12.2 allows observation of changes in any net namespace because these changes are leaked into all other net namespaces. This is related to the NF_SYSCTL_CT_MAX, NF_SYSCTL_CT_EXPECT_MAX, and NF_SYSCTL_CT_BUCKETS sysctls. | https://nvd.nist.gov/vuln/detail/CVE-2021-38209 |
318,132 | linux | 2671fa4dc0109d3fb581bc3078fdf17b5d9080f6 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2671fa4dc0109d3fb581bc3078fdf17b5d9080f6 | netfilter: conntrack: Make global sysctls readonly in non-init netns
These sysctls point to global variables:
- NF_SYSCTL_CT_MAX (&nf_conntrack_max)
- NF_SYSCTL_CT_EXPECT_MAX (&nf_ct_expect_max)
- NF_SYSCTL_CT_BUCKETS (&nf_conntrack_htable_size_user)
Because their data pointers are not updated to point to per-netns
s... | 0 | static int nf_conntrack_standalone_init_sysctl(struct net *net)
{
struct nf_conntrack_net *cnet = net_generic(net, nf_conntrack_net_id);
struct nf_udp_net *un = nf_udp_pernet(net);
struct ctl_table *table;
BUILD_BUG_ON(ARRAY_SIZE(nf_ct_sysctl_table) != NF_SYSCTL_CT_LAST_SYSCTL);
table = kmemdup(nf_ct_sysctl_tabl... | 199,765,398,906,568,340,000,000,000,000,000,000,000 | nf_conntrack_standalone.c | 187,056,384,217,085,730,000,000,000,000,000,000,000 | [
"CWE-203"
] | CVE-2021-38209 | net/netfilter/nf_conntrack_standalone.c in the Linux kernel before 5.12.2 allows observation of changes in any net namespace because these changes are leaked into all other net namespaces. This is related to the NF_SYSCTL_CT_MAX, NF_SYSCTL_CT_EXPECT_MAX, and NF_SYSCTL_CT_BUCKETS sysctls. | https://nvd.nist.gov/vuln/detail/CVE-2021-38209 |
201,366 | linux | 9f834ec18defc369d73ccf9e87a2790bfa05bf46 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9f834ec18defc369d73ccf9e87a2790bfa05bf46 | binfmt_elf: switch to new creds when switching to new mm
We used to delay switching to the new credentials until after we had
mapped the executable (and possible elf interpreter). That was kind of
odd to begin with, since the new executable will actually then _run_
with the new creds, but whatever.
The bigger proble... | 1 | static int load_elf_binary(struct linux_binprm *bprm)
{
struct file *interpreter = NULL; /* to shut gcc up */
unsigned long load_addr = 0, load_bias = 0;
int load_addr_set = 0;
char * elf_interpreter = NULL;
unsigned long error;
struct elf_phdr *elf_ppnt, *elf_phdata, *interp_elf_phdata = NULL;
unsigned long el... | 294,085,057,678,149,060,000,000,000,000,000,000,000 | binfmt_elf.c | 152,216,467,704,658,900,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2019-11190 | The Linux kernel before 4.8 allows local users to bypass ASLR on setuid programs (such as /bin/su) because install_exec_creds() is called too late in load_elf_binary() in fs/binfmt_elf.c, and thus the ptrace_may_access() check has a race condition when reading /proc/pid/stat. | https://nvd.nist.gov/vuln/detail/CVE-2019-11190 |
318,265 | linux | 9f834ec18defc369d73ccf9e87a2790bfa05bf46 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9f834ec18defc369d73ccf9e87a2790bfa05bf46 | binfmt_elf: switch to new creds when switching to new mm
We used to delay switching to the new credentials until after we had
mapped the executable (and possible elf interpreter). That was kind of
odd to begin with, since the new executable will actually then _run_
with the new creds, but whatever.
The bigger proble... | 0 | static int load_elf_binary(struct linux_binprm *bprm)
{
struct file *interpreter = NULL; /* to shut gcc up */
unsigned long load_addr = 0, load_bias = 0;
int load_addr_set = 0;
char * elf_interpreter = NULL;
unsigned long error;
struct elf_phdr *elf_ppnt, *elf_phdata, *interp_elf_phdata = NULL;
unsigned long el... | 260,076,574,970,649,120,000,000,000,000,000,000,000 | binfmt_elf.c | 32,418,080,243,984,980,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2019-11190 | The Linux kernel before 4.8 allows local users to bypass ASLR on setuid programs (such as /bin/su) because install_exec_creds() is called too late in load_elf_binary() in fs/binfmt_elf.c, and thus the ptrace_may_access() check has a race condition when reading /proc/pid/stat. | https://nvd.nist.gov/vuln/detail/CVE-2019-11190 |
201,367 | ntp | 3680c2e4d5f88905ce062c7b43305d610a2c9796 | https://github.com/ntp-project/ntp | https://github.com/ntp-project/ntp/commit/3680c2e4d5f88905ce062c7b43305d610a2c9796 | [Bug 2938] ntpq saveconfig command allows dangerous characters in filenames.
- make sure the file does not exist (no overwrite allowed)
- ensure text mode where applicable (windows) | 1 | save_config(
struct recvbuf *rbufp,
int restrict_mask
)
{
#ifdef SAVECONFIG
static const char savedconfig_eq[] = "savedconfig=";
char filespec[128];
char filename[128];
char fullpath[512];
char savedconfig[sizeof(savedconfig_eq) + sizeof(filename)];
time_t now;
int fd;
FILE *fptr;
int prc;
size_t reqlen;... | 8,669,885,252,846,957,000,000,000,000,000,000,000 | ntp_control.c | 276,983,769,207,846,100,000,000,000,000,000,000,000 | [
"CWE-254"
] | CVE-2015-7976 | The ntpq saveconfig command in NTP 4.1.2, 4.2.x before 4.2.8p6, 4.3, 4.3.25, 4.3.70, and 4.3.77 does not properly filter special characters, which allows attackers to cause unspecified impact via a crafted filename. | https://nvd.nist.gov/vuln/detail/CVE-2015-7976 |
318,349 | ntp | 3680c2e4d5f88905ce062c7b43305d610a2c9796 | https://github.com/ntp-project/ntp | https://github.com/ntp-project/ntp/commit/3680c2e4d5f88905ce062c7b43305d610a2c9796 | [Bug 2938] ntpq saveconfig command allows dangerous characters in filenames.
- make sure the file does not exist (no overwrite allowed)
- ensure text mode where applicable (windows) | 0 | save_config(
struct recvbuf *rbufp,
int restrict_mask
)
{
#ifdef SAVECONFIG
static const char savedconfig_eq[] = "savedconfig=";
/* Build a safe open mode from the available mode flags. We want
* to create a new file and write it in text mode (when
* applicable -- only Windows does this...)
*/
static const... | 84,584,501,160,146,370,000,000,000,000,000,000,000 | ntp_control.c | 303,205,310,010,800,550,000,000,000,000,000,000,000 | [
"CWE-254"
] | CVE-2015-7976 | The ntpq saveconfig command in NTP 4.1.2, 4.2.x before 4.2.8p6, 4.3, 4.3.25, 4.3.70, and 4.3.77 does not properly filter special characters, which allows attackers to cause unspecified impact via a crafted filename. | https://nvd.nist.gov/vuln/detail/CVE-2015-7976 |
201,374 | matio | b53b62b756920f4c1509f4ee06427f66c3b5c9c4 | https://github.com/tbeu/matio | https://github.com/tbeu/matio/commit/b53b62b756920f4c1509f4ee06427f66c3b5c9c4 | Fix memory leak
As reported by https://github.com/tbeu/matio/issues/186 | 1 | ReadNextFunctionHandle(mat_t *mat, matvar_t *matvar)
{
int err;
size_t nelems = 1;
err = Mat_MulDims(matvar, &nelems);
matvar->data_size = sizeof(matvar_t *);
err |= Mul(&matvar->nbytes, nelems, matvar->data_size);
if ( err )
return 0;
matvar->data = malloc(matvar->nbytes);
if ... | 33,040,170,359,985,184,000,000,000,000,000,000,000 | mat5.c | 76,008,122,734,027,390,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2022-1515 | A memory leak was discovered in matio 1.5.21 and earlier in Mat_VarReadNextInfo5() in mat5.c via a crafted file. This issue can potentially result in DoS. | https://nvd.nist.gov/vuln/detail/CVE-2022-1515 |
318,491 | matio | b53b62b756920f4c1509f4ee06427f66c3b5c9c4 | https://github.com/tbeu/matio | https://github.com/tbeu/matio/commit/b53b62b756920f4c1509f4ee06427f66c3b5c9c4 | Fix memory leak
As reported by https://github.com/tbeu/matio/issues/186 | 0 | ReadNextFunctionHandle(mat_t *mat, matvar_t *matvar)
{
int err;
size_t nelems = 1;
err = Mat_MulDims(matvar, &nelems);
matvar->data_size = sizeof(matvar_t *);
err |= Mul(&matvar->nbytes, nelems, matvar->data_size);
if ( err )
return 0;
matvar->data = malloc(matvar->nbytes);
if ... | 105,802,215,979,787,700,000,000,000,000,000,000,000 | mat5.c | 310,563,630,750,759,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2022-1515 | A memory leak was discovered in matio 1.5.21 and earlier in Mat_VarReadNextInfo5() in mat5.c via a crafted file. This issue can potentially result in DoS. | https://nvd.nist.gov/vuln/detail/CVE-2022-1515 |
201,376 | linux-stable | 0c461cb727d146c9ef2d3e86214f498b78b7d125 | https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable | https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=0c461cb727d146c9ef2d3e86214f498b78b7d125 | selinux: fix off-by-one in setprocattr
SELinux tries to support setting/clearing of /proc/pid/attr attributes
from the shell by ignoring terminating newlines and treating an
attribute value that begins with a NUL or newline as an attempt to
clear the attribute. However, the test for clearing attributes has
always bee... | 1 | static int selinux_setprocattr(struct task_struct *p,
char *name, void *value, size_t size)
{
struct task_security_struct *tsec;
struct cred *new;
u32 sid = 0, ptsid;
int error;
char *str = value;
if (current != p) {
/* SELinux only allows a process to change its own
security attributes. */
re... | 167,334,571,331,072,050,000,000,000,000,000,000,000 | None | null | [
"CWE-682"
] | CVE-2017-2618 | A flaw was found in the Linux kernel's handling of clearing SELinux attributes on /proc/pid/attr files before 4.9.10. An empty (null) write to this file can crash the system by causing the system to attempt to access unmapped kernel memory. | https://nvd.nist.gov/vuln/detail/CVE-2017-2618 |
318,596 | linux-stable | 0c461cb727d146c9ef2d3e86214f498b78b7d125 | https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable | https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=0c461cb727d146c9ef2d3e86214f498b78b7d125 | selinux: fix off-by-one in setprocattr
SELinux tries to support setting/clearing of /proc/pid/attr attributes
from the shell by ignoring terminating newlines and treating an
attribute value that begins with a NUL or newline as an attempt to
clear the attribute. However, the test for clearing attributes has
always bee... | 0 | static int selinux_setprocattr(struct task_struct *p,
char *name, void *value, size_t size)
{
struct task_security_struct *tsec;
struct cred *new;
u32 sid = 0, ptsid;
int error;
char *str = value;
if (current != p) {
/* SELinux only allows a process to change its own
security attributes. */
re... | 241,602,476,664,580,800,000,000,000,000,000,000,000 | None | null | [
"CWE-682"
] | CVE-2017-2618 | A flaw was found in the Linux kernel's handling of clearing SELinux attributes on /proc/pid/attr files before 4.9.10. An empty (null) write to this file can crash the system by causing the system to attempt to access unmapped kernel memory. | https://nvd.nist.gov/vuln/detail/CVE-2017-2618 |
201,383 | linux | 1b5e2423164b3670e8bc9174e4762d297990deff | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1b5e2423164b3670e8bc9174e4762d297990deff | brcmfmac: assure SSID length from firmware is limited
The SSID length as received from firmware should not exceed
IEEE80211_MAX_SSID_LEN as that would result in heap overflow.
Reviewed-by: Hante Meuleman <hante.meuleman@broadcom.com>
Reviewed-by: Pieter-Paul Giesberts <pieter-paul.giesberts@broadcom.com>
Reviewed-by:... | 1 | brcmf_wowl_nd_results(struct brcmf_if *ifp, const struct brcmf_event_msg *e,
void *data)
{
struct brcmf_cfg80211_info *cfg = ifp->drvr->config;
struct wiphy *wiphy = cfg_to_wiphy(cfg);
struct brcmf_pno_scanresults_le *pfn_result;
struct brcmf_pno_net_info_le *netinfo;
brcmf_dbg(SCAN, "Enter\n");
if (e->... | 237,040,394,977,019,130,000,000,000,000,000,000,000 | cfg80211.c | 75,301,420,808,193,690,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-9500 | The Broadcom brcmfmac WiFi driver prior to commit 1b5e2423164b3670e8bc9174e4762d297990deff is vulnerable to a heap buffer overflow. If the Wake-up on Wireless LAN functionality is configured, a malicious event frame can be constructed to trigger an heap buffer overflow in the brcmf_wowl_nd_results function. This vulner... | https://nvd.nist.gov/vuln/detail/CVE-2019-9500 |
318,890 | linux | 1b5e2423164b3670e8bc9174e4762d297990deff | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1b5e2423164b3670e8bc9174e4762d297990deff | brcmfmac: assure SSID length from firmware is limited
The SSID length as received from firmware should not exceed
IEEE80211_MAX_SSID_LEN as that would result in heap overflow.
Reviewed-by: Hante Meuleman <hante.meuleman@broadcom.com>
Reviewed-by: Pieter-Paul Giesberts <pieter-paul.giesberts@broadcom.com>
Reviewed-by:... | 0 | brcmf_wowl_nd_results(struct brcmf_if *ifp, const struct brcmf_event_msg *e,
void *data)
{
struct brcmf_cfg80211_info *cfg = ifp->drvr->config;
struct wiphy *wiphy = cfg_to_wiphy(cfg);
struct brcmf_pno_scanresults_le *pfn_result;
struct brcmf_pno_net_info_le *netinfo;
brcmf_dbg(SCAN, "Enter\n");
if (e->... | 103,475,573,760,992,550,000,000,000,000,000,000,000 | cfg80211.c | 11,714,603,675,031,860,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-9500 | The Broadcom brcmfmac WiFi driver prior to commit 1b5e2423164b3670e8bc9174e4762d297990deff is vulnerable to a heap buffer overflow. If the Wake-up on Wireless LAN functionality is configured, a malicious event frame can be constructed to trigger an heap buffer overflow in the brcmf_wowl_nd_results function. This vulner... | https://nvd.nist.gov/vuln/detail/CVE-2019-9500 |
201,385 | passenger | 4043718264095cde6623c2cbe8c644541036d7bf | https://github.com/phusion/passenger | https://github.com/phusion/passenger/commit/4043718264095cde6623c2cbe8c644541036d7bf | Disable unused feature. | 1 | SpawnPreparationInfo prepareSpawn(const Options &options) {
TRACE_POINT();
SpawnPreparationInfo info;
prepareChroot(info, options);
info.userSwitching = prepareUserSwitching(options);
prepareSwitchingWorkingDirectory(info, options);
inferApplicationInfo(info);
return info;
} | 73,551,784,596,076,625,000,000,000,000,000,000,000 | Spawner.h | 247,311,292,649,058,360,000,000,000,000,000,000,000 | [
"CWE-61"
] | CVE-2017-16355 | In agent/Core/SpawningKit/Spawner.h in Phusion Passenger 5.1.10 (fixed in Passenger Open Source 5.1.11 and Passenger Enterprise 5.1.10), if Passenger is running as root, it is possible to list the contents of arbitrary files on a system by symlinking a file named REVISION from the application root folder to a file of c... | https://nvd.nist.gov/vuln/detail/CVE-2017-16355 |
319,026 | passenger | 4043718264095cde6623c2cbe8c644541036d7bf | https://github.com/phusion/passenger | https://github.com/phusion/passenger/commit/4043718264095cde6623c2cbe8c644541036d7bf | Disable unused feature. | 0 | SpawnPreparationInfo prepareSpawn(const Options &options) {
TRACE_POINT();
SpawnPreparationInfo info;
prepareChroot(info, options);
info.userSwitching = prepareUserSwitching(options);
prepareSwitchingWorkingDirectory(info, options);
return info;
} | 336,955,115,859,086,440,000,000,000,000,000,000,000 | Spawner.h | 118,490,051,989,364,130,000,000,000,000,000,000,000 | [
"CWE-61"
] | CVE-2017-16355 | In agent/Core/SpawningKit/Spawner.h in Phusion Passenger 5.1.10 (fixed in Passenger Open Source 5.1.11 and Passenger Enterprise 5.1.10), if Passenger is running as root, it is possible to list the contents of arbitrary files on a system by symlinking a file named REVISION from the application root folder to a file of c... | https://nvd.nist.gov/vuln/detail/CVE-2017-16355 |
201,386 | linux | 6cf97230cd5f36b7665099083272595c55d72be7 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6cf97230cd5f36b7665099083272595c55d72be7 | media: dvb: usb: fix use after free in dvb_usb_device_exit
dvb_usb_device_exit() frees and uses the device name in that order.
Fix by storing the name in a buffer before freeing it.
Signed-off-by: Oliver Neukum <oneukum@suse.com>
Reported-by: syzbot+26ec41e9f788b3eba396@syzkaller.appspotmail.com
Signed-off-by: Sean Y... | 1 | void dvb_usb_device_exit(struct usb_interface *intf)
{
struct dvb_usb_device *d = usb_get_intfdata(intf);
const char *name = "generic DVB-USB module";
usb_set_intfdata(intf, NULL);
if (d != NULL && d->desc != NULL) {
name = d->desc->name;
dvb_usb_exit(d);
}
info("%s successfully deinitialized and disconnecte... | 296,922,085,087,151,430,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2019-15213 | An issue was discovered in the Linux kernel before 5.2.3. There is a use-after-free caused by a malicious USB device in the drivers/media/usb/dvb-usb/dvb-usb-init.c driver. | https://nvd.nist.gov/vuln/detail/CVE-2019-15213 |
319,036 | linux | 6cf97230cd5f36b7665099083272595c55d72be7 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6cf97230cd5f36b7665099083272595c55d72be7 | media: dvb: usb: fix use after free in dvb_usb_device_exit
dvb_usb_device_exit() frees and uses the device name in that order.
Fix by storing the name in a buffer before freeing it.
Signed-off-by: Oliver Neukum <oneukum@suse.com>
Reported-by: syzbot+26ec41e9f788b3eba396@syzkaller.appspotmail.com
Signed-off-by: Sean Y... | 0 | void dvb_usb_device_exit(struct usb_interface *intf)
{
struct dvb_usb_device *d = usb_get_intfdata(intf);
const char *default_name = "generic DVB-USB module";
char name[40];
usb_set_intfdata(intf, NULL);
if (d != NULL && d->desc != NULL) {
strscpy(name, d->desc->name, sizeof(name));
dvb_usb_exit(d);
} else {... | 104,290,770,119,297,300,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2019-15213 | An issue was discovered in the Linux kernel before 5.2.3. There is a use-after-free caused by a malicious USB device in the drivers/media/usb/dvb-usb/dvb-usb-init.c driver. | https://nvd.nist.gov/vuln/detail/CVE-2019-15213 |
201,387 | linux | 7b09c2d052db4b4ad0b27b97918b46a7746966fa | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7b09c2d052db4b4ad0b27b97918b46a7746966fa | ipv6: fix a typo in fib6_rule_lookup()
Yi Ren reported an issue discovered by syzkaller, and bisected
to the cited commit.
Many thanks to Yi, this trivial patch does not reflect the patient
work that has been done.
Fixes: d64a1f574a29 ("ipv6: honor RT6_LOOKUP_F_DST_NOREF in rule lookup logic")
Signed-off-by: Eric Du... | 1 | struct dst_entry *fib6_rule_lookup(struct net *net, struct flowi6 *fl6,
const struct sk_buff *skb,
int flags, pol_lookup_t lookup)
{
struct rt6_info *rt;
rt = lookup(net, net->ipv6.fib6_main_tbl, fl6, skb, flags);
if (rt->dst.error == -EAGAIN) {
ip6_rt_put_flags(rt, flags);
rt = net->ipv6.ip6_null... | 21,410,736,560,642,063,000,000,000,000,000,000,000 | ip6_fib.c | 127,977,201,324,717,770,000,000,000,000,000,000,000 | [
"CWE-755"
] | CVE-2019-20422 | In the Linux kernel before 5.3.4, fib6_rule_lookup in net/ipv6/ip6_fib.c mishandles the RT6_LOOKUP_F_DST_NOREF flag in a reference-count decision, leading to (for example) a crash that was identified by syzkaller, aka CID-7b09c2d052db. | https://nvd.nist.gov/vuln/detail/CVE-2019-20422 |
319,059 | linux | 7b09c2d052db4b4ad0b27b97918b46a7746966fa | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7b09c2d052db4b4ad0b27b97918b46a7746966fa | ipv6: fix a typo in fib6_rule_lookup()
Yi Ren reported an issue discovered by syzkaller, and bisected
to the cited commit.
Many thanks to Yi, this trivial patch does not reflect the patient
work that has been done.
Fixes: d64a1f574a29 ("ipv6: honor RT6_LOOKUP_F_DST_NOREF in rule lookup logic")
Signed-off-by: Eric Du... | 0 | struct dst_entry *fib6_rule_lookup(struct net *net, struct flowi6 *fl6,
const struct sk_buff *skb,
int flags, pol_lookup_t lookup)
{
struct rt6_info *rt;
rt = lookup(net, net->ipv6.fib6_main_tbl, fl6, skb, flags);
if (rt->dst.error == -EAGAIN) {
ip6_rt_put_flags(rt, flags);
rt = net->ipv6.ip6_null... | 74,539,209,352,516,840,000,000,000,000,000,000,000 | ip6_fib.c | 204,329,852,969,685,000,000,000,000,000,000,000,000 | [
"CWE-755"
] | CVE-2019-20422 | In the Linux kernel before 5.3.4, fib6_rule_lookup in net/ipv6/ip6_fib.c mishandles the RT6_LOOKUP_F_DST_NOREF flag in a reference-count decision, leading to (for example) a crash that was identified by syzkaller, aka CID-7b09c2d052db. | https://nvd.nist.gov/vuln/detail/CVE-2019-20422 |
201,419 | psutil | 3a9bccfd2c6d2e6538298cd3892058b1204056e0 | https://github.com/giampaolo/psutil | https://github.com/giampaolo/psutil/commit/3a9bccfd2c6d2e6538298cd3892058b1204056e0 | psutil/_psutil_posix.c: better clear variables to ensure they are NULL (#1624) | 1 | psutil_net_if_addrs(PyObject* self, PyObject* args) {
struct ifaddrs *ifaddr, *ifa;
int family;
PyObject *py_retlist = PyList_New(0);
PyObject *py_tuple = NULL;
PyObject *py_address = NULL;
PyObject *py_netmask = NULL;
PyObject *py_broadcast = NULL;
PyObject *py_ptp = NULL;
if (py_... | 248,731,122,237,860,180,000,000,000,000,000,000,000 | _psutil_posix.c | 90,305,141,945,426,000,000,000,000,000,000,000,000 | [
"CWE-415"
] | CVE-2019-18874 | psutil (aka python-psutil) through 5.6.5 can have a double free. This occurs because of refcount mishandling within a while or for loop that converts system data into a Python object. | https://nvd.nist.gov/vuln/detail/CVE-2019-18874 |
319,185 | psutil | 3a9bccfd2c6d2e6538298cd3892058b1204056e0 | https://github.com/giampaolo/psutil | https://github.com/giampaolo/psutil/commit/3a9bccfd2c6d2e6538298cd3892058b1204056e0 | psutil/_psutil_posix.c: better clear variables to ensure they are NULL (#1624) | 0 | psutil_net_if_addrs(PyObject* self, PyObject* args) {
struct ifaddrs *ifaddr, *ifa;
int family;
PyObject *py_retlist = PyList_New(0);
PyObject *py_tuple = NULL;
PyObject *py_address = NULL;
PyObject *py_netmask = NULL;
PyObject *py_broadcast = NULL;
PyObject *py_ptp = NULL;
if (py_... | 328,559,910,807,004,050,000,000,000,000,000,000,000 | _psutil_posix.c | 248,265,593,642,092,270,000,000,000,000,000,000,000 | [
"CWE-415"
] | CVE-2019-18874 | psutil (aka python-psutil) through 5.6.5 can have a double free. This occurs because of refcount mishandling within a while or for loop that converts system data into a Python object. | https://nvd.nist.gov/vuln/detail/CVE-2019-18874 |
201,470 | linux | dbb2483b2a46fbaf833cfb5deb5ed9cace9c7399 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=dbb2483b2a46fbaf833cfb5deb5ed9cace9c7399 | xfrm: clean up xfrm protocol checks
In commit 6a53b7593233 ("xfrm: check id proto in validate_tmpl()")
I introduced a check for xfrm protocol, but according to Herbert
IPSEC_PROTO_ANY should only be used as a wildcard for lookup, so
it should be removed from validate_tmpl().
And, IPSEC_PROTO_ANY is expected to only m... | 1 | void xfrm_state_fini(struct net *net)
{
unsigned int sz;
flush_work(&net->xfrm.state_hash_work);
flush_work(&xfrm_state_gc_work);
xfrm_state_flush(net, IPSEC_PROTO_ANY, false, true);
WARN_ON(!list_empty(&net->xfrm.state_all));
sz = (net->xfrm.state_hmask + 1) * sizeof(struct hlist_head);
WARN_ON(!hlist_empty(... | 253,266,835,718,097,750,000,000,000,000,000,000,000 | xfrm_state.c | 124,716,370,294,545,540,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2019-25045 | An issue was discovered in the Linux kernel before 5.0.19. The XFRM subsystem has a use-after-free, related to an xfrm_state_fini panic, aka CID-dbb2483b2a46. | https://nvd.nist.gov/vuln/detail/CVE-2019-25045 |
319,593 | linux | dbb2483b2a46fbaf833cfb5deb5ed9cace9c7399 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=dbb2483b2a46fbaf833cfb5deb5ed9cace9c7399 | xfrm: clean up xfrm protocol checks
In commit 6a53b7593233 ("xfrm: check id proto in validate_tmpl()")
I introduced a check for xfrm protocol, but according to Herbert
IPSEC_PROTO_ANY should only be used as a wildcard for lookup, so
it should be removed from validate_tmpl().
And, IPSEC_PROTO_ANY is expected to only m... | 0 | void xfrm_state_fini(struct net *net)
{
unsigned int sz;
flush_work(&net->xfrm.state_hash_work);
flush_work(&xfrm_state_gc_work);
xfrm_state_flush(net, 0, false, true);
WARN_ON(!list_empty(&net->xfrm.state_all));
sz = (net->xfrm.state_hmask + 1) * sizeof(struct hlist_head);
WARN_ON(!hlist_empty(net->xfrm.stat... | 78,309,578,104,130,130,000,000,000,000,000,000,000 | xfrm_state.c | 30,594,301,599,491,854,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2019-25045 | An issue was discovered in the Linux kernel before 5.0.19. The XFRM subsystem has a use-after-free, related to an xfrm_state_fini panic, aka CID-dbb2483b2a46. | https://nvd.nist.gov/vuln/detail/CVE-2019-25045 |
201,481 | postsrsd | 077be98d8c8a9847e4ae0c7dc09e7474cbe27db2 | https://github.com/roehling/postsrsd | https://github.com/roehling/postsrsd/commit/077be98d8c8a9847e4ae0c7dc09e7474cbe27db2 | SECURITY: Fix DoS on overly long input from Postfix
Thanks to Mateusz Jończyk who reported this issue and gave valuable
feedback for its resolution.
PostSRSd would hang on an overly long GET request, because the
fread()/fwrite() logic in the subprocess would get confused by the
remaining input line in its buffer.
Th... | 1 | int main(int argc, char **argv)
{
int opt, timeout = 1800, family = AF_UNSPEC, hashlength = 0, hashmin = 0;
int daemonize = FALSE, always_rewrite = FALSE;
char *listen_addr = NULL, *forward_service = NULL, *reverse_service = NULL,
*user = NULL, *domain = NULL, *chroot_dir = NULL;
char separator... | 53,507,990,997,958,310,000,000,000,000,000,000,000 | postsrsd.c | 65,948,177,914,591,550,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2021-35525 | PostSRSd before 1.11 allows a denial of service (subprocess hang) if Postfix sends certain long data fields such as multiple concatenated email addresses. NOTE: the PostSRSd maintainer acknowledges "theoretically, this error should never occur ... I'm not sure if there's a reliable way to trigger this condition by an e... | https://nvd.nist.gov/vuln/detail/CVE-2021-35525 |
319,987 | postsrsd | 077be98d8c8a9847e4ae0c7dc09e7474cbe27db2 | https://github.com/roehling/postsrsd | https://github.com/roehling/postsrsd/commit/077be98d8c8a9847e4ae0c7dc09e7474cbe27db2 | SECURITY: Fix DoS on overly long input from Postfix
Thanks to Mateusz Jończyk who reported this issue and gave valuable
feedback for its resolution.
PostSRSd would hang on an overly long GET request, because the
fread()/fwrite() logic in the subprocess would get confused by the
remaining input line in its buffer.
Th... | 0 | int main(int argc, char **argv)
{
int opt, timeout = 1800, family = AF_UNSPEC, hashlength = 0, hashmin = 0;
int daemonize = FALSE, always_rewrite = FALSE;
char *listen_addr = NULL, *forward_service = NULL, *reverse_service = NULL,
*user = NULL, *domain = NULL, *chroot_dir = NULL;
char separator... | 327,721,493,235,325,300,000,000,000,000,000,000,000 | postsrsd.c | 157,395,696,981,603,540,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2021-35525 | PostSRSd before 1.11 allows a denial of service (subprocess hang) if Postfix sends certain long data fields such as multiple concatenated email addresses. NOTE: the PostSRSd maintainer acknowledges "theoretically, this error should never occur ... I'm not sure if there's a reliable way to trigger this condition by an e... | https://nvd.nist.gov/vuln/detail/CVE-2021-35525 |
201,483 | linux | 5f936e19cc0ef97dbe3a56e9498922ad5ba1edef | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5f936e19cc0ef97dbe3a56e9498922ad5ba1edef | alarmtimer: Prevent overflow for relative nanosleep
Air Icy reported:
UBSAN: Undefined behaviour in kernel/time/alarmtimer.c:811:7
signed integer overflow:
1529859276030040771 + 9223372036854775807 cannot be represented in type 'long long int'
Call Trace:
alarm_timer_nsleep+0x44c/0x510 kernel/time/alarmtim... | 1 | static int alarm_timer_nsleep(const clockid_t which_clock, int flags,
const struct timespec64 *tsreq)
{
enum alarmtimer_type type = clock2alarm(which_clock);
struct restart_block *restart = ¤t->restart_block;
struct alarm alarm;
ktime_t exp;
int ret = 0;
if (!alarmtimer_get_rtcdev())
return -EN... | 65,297,629,569,614,080,000,000,000,000,000,000,000 | alarmtimer.c | 106,611,362,425,363,820,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2018-13053 | The alarm_timer_nsleep function in kernel/time/alarmtimer.c in the Linux kernel through 4.17.3 has an integer overflow via a large relative timeout because ktime_add_safe is not used. | https://nvd.nist.gov/vuln/detail/CVE-2018-13053 |
320,007 | linux | 5f936e19cc0ef97dbe3a56e9498922ad5ba1edef | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5f936e19cc0ef97dbe3a56e9498922ad5ba1edef | alarmtimer: Prevent overflow for relative nanosleep
Air Icy reported:
UBSAN: Undefined behaviour in kernel/time/alarmtimer.c:811:7
signed integer overflow:
1529859276030040771 + 9223372036854775807 cannot be represented in type 'long long int'
Call Trace:
alarm_timer_nsleep+0x44c/0x510 kernel/time/alarmtim... | 0 | static int alarm_timer_nsleep(const clockid_t which_clock, int flags,
const struct timespec64 *tsreq)
{
enum alarmtimer_type type = clock2alarm(which_clock);
struct restart_block *restart = ¤t->restart_block;
struct alarm alarm;
ktime_t exp;
int ret = 0;
if (!alarmtimer_get_rtcdev())
return -EN... | 319,722,804,190,635,720,000,000,000,000,000,000,000 | alarmtimer.c | 300,653,286,276,828,530,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2018-13053 | The alarm_timer_nsleep function in kernel/time/alarmtimer.c in the Linux kernel through 4.17.3 has an integer overflow via a large relative timeout because ktime_add_safe is not used. | https://nvd.nist.gov/vuln/detail/CVE-2018-13053 |
201,484 | ImageMagick | 8187d2d8fd010d2d6b1a3a8edd935beec404dddc | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/8187d2d8fd010d2d6b1a3a8edd935beec404dddc | https://github.com/ImageMagick/ImageMagick/issues/1610 | 1 | static inline Quantum GetPixelChannel(const Image *magick_restrict image,
const PixelChannel channel,const Quantum *magick_restrict pixel)
{
if (image->channel_map[channel].traits == UndefinedPixelTrait)
return((Quantum) 0);
return(pixel[image->channel_map[channel].offset]);
} | 333,677,389,946,400,400,000,000,000,000,000,000,000 | pixel-accessor.h | 30,621,243,800,993,260,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2019-13299 | ImageMagick 7.0.8-50 Q16 has a heap-based buffer over-read at MagickCore/pixel-accessor.h in GetPixelChannel. | https://nvd.nist.gov/vuln/detail/CVE-2019-13299 |
320,126 | ImageMagick | 8187d2d8fd010d2d6b1a3a8edd935beec404dddc | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/8187d2d8fd010d2d6b1a3a8edd935beec404dddc | https://github.com/ImageMagick/ImageMagick/issues/1610 | 0 | static inline Quantum GetPixelChannel(const Image *magick_restrict image,
const PixelChannel channel,const Quantum *magick_restrict pixel)
{
if (image->channel_map[image->channel_map[channel].offset].traits == UndefinedPixelTrait)
return((Quantum) 0);
return(pixel[image->channel_map[channel].offset]);
} | 157,668,121,016,567,180,000,000,000,000,000,000,000 | pixel-accessor.h | 61,038,256,387,916,500,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2019-13299 | ImageMagick 7.0.8-50 Q16 has a heap-based buffer over-read at MagickCore/pixel-accessor.h in GetPixelChannel. | https://nvd.nist.gov/vuln/detail/CVE-2019-13299 |
201,793 | irssi | 5b5bfef03596d95079c728f65f523570dd7b03aa | https://github.com/irssi/irssi | https://github.com/irssi/irssi/commit/5b5bfef03596d95079c728f65f523570dd7b03aa | check the error condition of mainwindow_create | 1 | static void _cmd_window_show_opt(const char *data, int right)
{
MAIN_WINDOW_REC *parent;
WINDOW_REC *window;
if (*data == '\0') cmd_return_error(CMDERR_NOT_ENOUGH_PARAMS);
if (is_numeric(data, '\0')) {
window = window_find_refnum(atoi(data));
if (window == NULL) {
printformat_window(active_win, MSGLEVEL_CL... | 45,947,677,600,377,960,000,000,000,000,000,000,000 | mainwindows.c | 201,009,220,651,750,620,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2018-7052 | An issue was discovered in Irssi before 1.0.7 and 1.1.x before 1.1.1. When the number of windows exceeds the available space, a crash due to a NULL pointer dereference would occur. | https://nvd.nist.gov/vuln/detail/CVE-2018-7052 |
321,733 | irssi | 5b5bfef03596d95079c728f65f523570dd7b03aa | https://github.com/irssi/irssi | https://github.com/irssi/irssi/commit/5b5bfef03596d95079c728f65f523570dd7b03aa | check the error condition of mainwindow_create | 0 | static void _cmd_window_show_opt(const char *data, int right)
{
MAIN_WINDOW_REC *parent;
WINDOW_REC *window;
if (*data == '\0') cmd_return_error(CMDERR_NOT_ENOUGH_PARAMS);
if (is_numeric(data, '\0')) {
window = window_find_refnum(atoi(data));
if (window == NULL) {
printformat_window(active_win, MSGLEVEL_CL... | 107,185,979,866,156,070,000,000,000,000,000,000,000 | mainwindows.c | 37,940,817,019,264,070,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2018-7052 | An issue was discovered in Irssi before 1.0.7 and 1.1.x before 1.1.1. When the number of windows exceeds the available space, a crash due to a NULL pointer dereference would occur. | https://nvd.nist.gov/vuln/detail/CVE-2018-7052 |
201,804 | qemu | 1d7678dec4761acdc43439da6ceda41a703ba1a6 | https://github.com/bonzini/qemu | http://git.qemu.org/?p=qemu.git;a=commit;h=1d7678dec4761acdc43439da6ceda41a703ba1a6 | vhdx: Bounds checking for block_size and logical_sector_size (CVE-2014-0148)
Other variables (e.g. sectors_per_block) are calculated using these
variables, and if not range-checked illegal values could be obtained
causing infinite loops and other potential issues when calculating
BAT entries.
The 1.00 VHDX spec requi... | 1 | static int vhdx_parse_metadata(BlockDriverState *bs, BDRVVHDXState *s)
{
int ret = 0;
uint8_t *buffer;
int offset = 0;
uint32_t i = 0;
VHDXMetadataTableEntry md_entry;
buffer = qemu_blockalign(bs, VHDX_METADATA_TABLE_MAX_SIZE);
ret = bdrv_pread(bs->file, s->metadata_rt.file_offset, buffer,... | 317,060,471,079,696,000,000,000,000,000,000,000,000 | vhdx.c | 231,074,672,312,740,900,000,000,000,000,000,000,000 | [
"CWE-835"
] | CVE-2014-0148 | Qemu before 2.0 block driver for Hyper-V VHDX Images is vulnerable to infinite loops and other potential issues when calculating BAT entries, due to missing bounds checks for block_size and logical_sector_size variables. These are used to derive other fields like 'sectors_per_block' etc. A user able to alter the Qemu d... | https://nvd.nist.gov/vuln/detail/CVE-2014-0148 |
321,844 | qemu | 1d7678dec4761acdc43439da6ceda41a703ba1a6 | https://github.com/bonzini/qemu | http://git.qemu.org/?p=qemu.git;a=commit;h=1d7678dec4761acdc43439da6ceda41a703ba1a6 | vhdx: Bounds checking for block_size and logical_sector_size (CVE-2014-0148)
Other variables (e.g. sectors_per_block) are calculated using these
variables, and if not range-checked illegal values could be obtained
causing infinite loops and other potential issues when calculating
BAT entries.
The 1.00 VHDX spec requi... | 0 | static int vhdx_parse_metadata(BlockDriverState *bs, BDRVVHDXState *s)
{
int ret = 0;
uint8_t *buffer;
int offset = 0;
uint32_t i = 0;
VHDXMetadataTableEntry md_entry;
buffer = qemu_blockalign(bs, VHDX_METADATA_TABLE_MAX_SIZE);
ret = bdrv_pread(bs->file, s->metadata_rt.file_offset, buffer,... | 180,677,667,384,030,870,000,000,000,000,000,000,000 | vhdx.c | 28,895,005,318,200,727,000,000,000,000,000,000,000 | [
"CWE-835"
] | CVE-2014-0148 | Qemu before 2.0 block driver for Hyper-V VHDX Images is vulnerable to infinite loops and other potential issues when calculating BAT entries, due to missing bounds checks for block_size and logical_sector_size variables. These are used to derive other fields like 'sectors_per_block' etc. A user able to alter the Qemu d... | https://nvd.nist.gov/vuln/detail/CVE-2014-0148 |
201,805 | qemu | ac2071c3791b67fc7af78b8ceb320c01ca1b5df7 | https://github.com/bonzini/qemu | https://git.qemu.org/?p=qemu.git;a=commit;h=ac2071c3791b67fc7af78b8ceb320c01ca1b5df7 | ati-vga: Fix checks in ati_2d_blt() to avoid crash
In some corner cases (that never happen during normal operation but a
malicious guest could program wrong values) pixman functions were
called with parameters that result in a crash. Fix this and add more
checks to disallow such cases.
Reported-by: Ziming Zhang <ezra... | 1 | void ati_2d_blt(ATIVGAState *s)
{
/* FIXME it is probably more complex than this and may need to be */
/* rewritten but for now as a start just to get some output: */
DisplaySurface *ds = qemu_console_surface(s->vga.con);
DPRINTF("%p %u ds: %p %d %d rop: %x\n", s->vga.vram_ptr,
s->vga.vbe_st... | 32,747,782,590,130,686,000,000,000,000,000,000,000 | None | null | [
"CWE-190"
] | CVE-2020-11869 | An integer overflow was found in QEMU 4.0.1 through 4.2.0 in the way it implemented ATI VGA emulation. This flaw occurs in the ati_2d_blt() routine in hw/display/ati-2d.c while handling MMIO write operations through the ati_mm_write() callback. A malicious guest could abuse this flaw to crash the QEMU process, resultin... | https://nvd.nist.gov/vuln/detail/CVE-2020-11869 |
321,864 | qemu | ac2071c3791b67fc7af78b8ceb320c01ca1b5df7 | https://github.com/bonzini/qemu | https://git.qemu.org/?p=qemu.git;a=commit;h=ac2071c3791b67fc7af78b8ceb320c01ca1b5df7 | ati-vga: Fix checks in ati_2d_blt() to avoid crash
In some corner cases (that never happen during normal operation but a
malicious guest could program wrong values) pixman functions were
called with parameters that result in a crash. Fix this and add more
checks to disallow such cases.
Reported-by: Ziming Zhang <ezra... | 0 | void ati_2d_blt(ATIVGAState *s)
{
/* FIXME it is probably more complex than this and may need to be */
/* rewritten but for now as a start just to get some output: */
DisplaySurface *ds = qemu_console_surface(s->vga.con);
DPRINTF("%p %u ds: %p %d %d rop: %x\n", s->vga.vram_ptr,
s->vga.vbe_st... | 250,978,914,248,131,350,000,000,000,000,000,000,000 | None | null | [
"CWE-190"
] | CVE-2020-11869 | An integer overflow was found in QEMU 4.0.1 through 4.2.0 in the way it implemented ATI VGA emulation. This flaw occurs in the ati_2d_blt() routine in hw/display/ati-2d.c while handling MMIO write operations through the ati_mm_write() callback. A malicious guest could abuse this flaw to crash the QEMU process, resultin... | https://nvd.nist.gov/vuln/detail/CVE-2020-11869 |
201,807 | sound | daac07156b330b18eb5071aec4b3ddca1c377f2c | https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound | https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=daac07156b330b18eb5071aec4b3ddca1c377f2c | ALSA: usb-audio: Fix an OOB bug in parse_audio_mixer_unit
The `uac_mixer_unit_descriptor` shown as below is read from the
device side. In `parse_audio_mixer_unit`, `baSourceID` field is
accessed from index 0 to `bNrInPins` - 1, the current implementation
assumes that descriptor is always valid (the length of descript... | 1 | static int uac_mixer_unit_get_channels(struct mixer_build *state,
struct uac_mixer_unit_descriptor *desc)
{
int mu_channels;
void *c;
if (desc->bLength < sizeof(*desc))
return -EINVAL;
if (!desc->bNrInPins)
return -EINVAL;
switch (state->mixer->protocol) {
case UAC_VERSION_1:
case UAC_VERSION_2:... | 90,578,052,965,352,200,000,000,000,000,000,000,000 | mixer.c | 206,125,543,953,658,860,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2019-15117 | parse_audio_mixer_unit in sound/usb/mixer.c in the Linux kernel through 5.2.9 mishandles a short descriptor, leading to out-of-bounds memory access. | https://nvd.nist.gov/vuln/detail/CVE-2019-15117 |
321,886 | sound | daac07156b330b18eb5071aec4b3ddca1c377f2c | https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound | https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=daac07156b330b18eb5071aec4b3ddca1c377f2c | ALSA: usb-audio: Fix an OOB bug in parse_audio_mixer_unit
The `uac_mixer_unit_descriptor` shown as below is read from the
device side. In `parse_audio_mixer_unit`, `baSourceID` field is
accessed from index 0 to `bNrInPins` - 1, the current implementation
assumes that descriptor is always valid (the length of descript... | 0 | static int uac_mixer_unit_get_channels(struct mixer_build *state,
struct uac_mixer_unit_descriptor *desc)
{
int mu_channels;
void *c;
if (desc->bLength < sizeof(*desc))
return -EINVAL;
if (!desc->bNrInPins)
return -EINVAL;
if (desc->bLength < sizeof(*desc) + desc->bNrInPins)
return -EINVAL;
swi... | 12,399,295,220,224,576,000,000,000,000,000,000,000 | mixer.c | 217,929,766,023,230,020,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2019-15117 | parse_audio_mixer_unit in sound/usb/mixer.c in the Linux kernel through 5.2.9 mishandles a short descriptor, leading to out-of-bounds memory access. | https://nvd.nist.gov/vuln/detail/CVE-2019-15117 |
201,808 | linux | e0b0cb9388642c104838fac100a4af32745621e2 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e0b0cb9388642c104838fac100a4af32745621e2 | virt: vbox: fix memory leak in hgcm_call_preprocess_linaddr
In hgcm_call_preprocess_linaddr memory is allocated for bounce_buf but
is not released if copy_form_user fails. In order to prevent memory leak
in case of failure, the assignment to bounce_buf_ret is moved before the
error check. This way the allocated bounce... | 1 | static int hgcm_call_preprocess_linaddr(
const struct vmmdev_hgcm_function_parameter *src_parm,
void **bounce_buf_ret, size_t *extra)
{
void *buf, *bounce_buf;
bool copy_in;
u32 len;
int ret;
buf = (void *)src_parm->u.pointer.u.linear_addr;
len = src_parm->u.pointer.size;
copy_in = src_parm->type != VMMDEV_HG... | 319,620,124,094,104,600,000,000,000,000,000,000,000 | vboxguest_utils.c | 79,840,664,692,412,145,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2019-19048 | A memory leak in the crypto_reportstat() function in drivers/virt/vboxguest/vboxguest_utils.c in the Linux kernel before 5.3.9 allows attackers to cause a denial of service (memory consumption) by triggering copy_form_user() failures, aka CID-e0b0cb938864. | https://nvd.nist.gov/vuln/detail/CVE-2019-19048 |
321,961 | linux | e0b0cb9388642c104838fac100a4af32745621e2 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e0b0cb9388642c104838fac100a4af32745621e2 | virt: vbox: fix memory leak in hgcm_call_preprocess_linaddr
In hgcm_call_preprocess_linaddr memory is allocated for bounce_buf but
is not released if copy_form_user fails. In order to prevent memory leak
in case of failure, the assignment to bounce_buf_ret is moved before the
error check. This way the allocated bounce... | 0 | static int hgcm_call_preprocess_linaddr(
const struct vmmdev_hgcm_function_parameter *src_parm,
void **bounce_buf_ret, size_t *extra)
{
void *buf, *bounce_buf;
bool copy_in;
u32 len;
int ret;
buf = (void *)src_parm->u.pointer.u.linear_addr;
len = src_parm->u.pointer.size;
copy_in = src_parm->type != VMMDEV_HG... | 19,070,941,680,693,952,000,000,000,000,000,000,000 | vboxguest_utils.c | 169,568,409,885,078,700,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2019-19048 | A memory leak in the crypto_reportstat() function in drivers/virt/vboxguest/vboxguest_utils.c in the Linux kernel before 5.3.9 allows attackers to cause a denial of service (memory consumption) by triggering copy_form_user() failures, aka CID-e0b0cb938864. | https://nvd.nist.gov/vuln/detail/CVE-2019-19048 |
201,811 | ImageMagick | 930ff0d1a9bc42925a7856e9ea53f5fc9f318bf3 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/930ff0d1a9bc42925a7856e9ea53f5fc9f318bf3 | eliminate heap buffer overflow vulnerability, thanks to ZhangJiaxing (@r0fm1a) from Codesafe Team of Legendsec at Qi'anxin Group | 1 | static Image *ReadTIFFImage(const ImageInfo *image_info,
ExceptionInfo *exception)
{
#define ThrowTIFFException(severity,message) \
{ \
if (pixel_info != (MemoryInfo *) NULL) \
pixel_info=RelinquishVirtualMemory(pixel_info); \
if (quantum_info != (QuantumInfo *) NULL) \
quantum_info=DestroyQuantumInfo(qua... | 20,942,361,662,597,316,000,000,000,000,000,000,000 | tiff.c | 286,384,013,733,912,600,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-3610 | A heap-based buffer overflow vulnerability was found in ImageMagick in versions prior to 7.0.11-14 in ReadTIFFImage() in coders/tiff.c. This issue is due to an incorrect setting of the pixel array size, which can lead to a crash and segmentation fault. | https://nvd.nist.gov/vuln/detail/CVE-2021-3610 |
322,075 | ImageMagick | 930ff0d1a9bc42925a7856e9ea53f5fc9f318bf3 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/930ff0d1a9bc42925a7856e9ea53f5fc9f318bf3 | eliminate heap buffer overflow vulnerability, thanks to ZhangJiaxing (@r0fm1a) from Codesafe Team of Legendsec at Qi'anxin Group | 0 | static Image *ReadTIFFImage(const ImageInfo *image_info,
ExceptionInfo *exception)
{
#define ThrowTIFFException(severity,message) \
{ \
if (pixel_info != (MemoryInfo *) NULL) \
pixel_info=RelinquishVirtualMemory(pixel_info); \
if (quantum_info != (QuantumInfo *) NULL) \
quantum_info=DestroyQuantumInfo(qua... | 272,088,685,911,031,600,000,000,000,000,000,000,000 | tiff.c | 106,918,391,118,700,650,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-3610 | A heap-based buffer overflow vulnerability was found in ImageMagick in versions prior to 7.0.11-14 in ReadTIFFImage() in coders/tiff.c. This issue is due to an incorrect setting of the pixel array size, which can lead to a crash and segmentation fault. | https://nvd.nist.gov/vuln/detail/CVE-2021-3610 |
201,849 | sqlite | ebd70eedd5d6e6a890a670b5ee874a5eae86b4dd | https://github.com/sqlite/sqlite | https://github.com/sqlite/sqlite/commit/ebd70eedd5d6e6a890a670b5ee874a5eae86b4dd | Fix the NOT NULL verification logic in PRAGMA integrity_check so that it
works for generated columns whose value is the result of a comparison operator.
Ticket [bd8c280671ba44a7]
FossilOrigin-Name: f3b39c71b88cb6721f443de56cdce4c08252453a5e340b00a2bd88dc10c42400 | 1 | void sqlite3Pragma(
Parse *pParse,
Token *pId1, /* First part of [schema.]id field */
Token *pId2, /* Second part of [schema.]id field, or NULL */
Token *pValue, /* Token for <value>, or NULL */
int minusFlag /* True if a '-' sign preceded <value> */
){
char *zLeft = 0; /* Nu... | 329,716,642,166,440,300,000,000,000,000,000,000,000 | pragma.c | 175,480,922,645,420,300,000,000,000,000,000,000,000 | [
"CWE-754"
] | CVE-2019-19646 | pragma.c in SQLite through 3.30.1 mishandles NOT NULL in an integrity_check PRAGMA command in certain cases of generated columns. | https://nvd.nist.gov/vuln/detail/CVE-2019-19646 |
323,103 | sqlite | ebd70eedd5d6e6a890a670b5ee874a5eae86b4dd | https://github.com/sqlite/sqlite | https://github.com/sqlite/sqlite/commit/ebd70eedd5d6e6a890a670b5ee874a5eae86b4dd | Fix the NOT NULL verification logic in PRAGMA integrity_check so that it
works for generated columns whose value is the result of a comparison operator.
Ticket [bd8c280671ba44a7]
FossilOrigin-Name: f3b39c71b88cb6721f443de56cdce4c08252453a5e340b00a2bd88dc10c42400 | 0 | void sqlite3Pragma(
Parse *pParse,
Token *pId1, /* First part of [schema.]id field */
Token *pId2, /* Second part of [schema.]id field, or NULL */
Token *pValue, /* Token for <value>, or NULL */
int minusFlag /* True if a '-' sign preceded <value> */
){
char *zLeft = 0; /* Nu... | 127,434,554,087,922,330,000,000,000,000,000,000,000 | pragma.c | 172,478,359,240,592,700,000,000,000,000,000,000,000 | [
"CWE-754"
] | CVE-2019-19646 | pragma.c in SQLite through 3.30.1 mishandles NOT NULL in an integrity_check PRAGMA command in certain cases of generated columns. | https://nvd.nist.gov/vuln/detail/CVE-2019-19646 |
201,856 | gnutls | 964632f37dfdfb914ebc5e49db4fa29af35b1de9 | http://git.savannah.gnu.org/cgit/gnutls | https://gitlab.com/gnutls/gnutls/commit/964632f37dfdfb914ebc5e49db4fa29af35b1de9 | ocsp: corrected the comparison of the serial size in OCSP response
Previously the OCSP certificate check wouldn't verify the serial length
and could succeed in cases it shouldn't.
Reported by Stefan Buehler. | 1 | gnutls_ocsp_resp_check_crt(gnutls_ocsp_resp_t resp,
unsigned int indx, gnutls_x509_crt_t crt)
{
int ret;
gnutls_digest_algorithm_t digest;
gnutls_datum_t rdn_hash = { NULL, 0 }, rserial = {
NULL, 0};
gnutls_datum_t cserial = { NULL, 0 };
gnutls_datum_t dn = { NULL, 0 };
uint8_t cdn_hash[MAX_HASH_SIZE];
si... | 318,229,799,554,199,440,000,000,000,000,000,000,000 | ocsp.c | 206,847,423,066,963,560,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2016-7444 | The gnutls_ocsp_resp_check_crt function in lib/x509/ocsp.c in GnuTLS before 3.4.15 and 3.5.x before 3.5.4 does not verify the serial length of an OCSP response, which might allow remote attackers to bypass an intended certificate validation mechanism via vectors involving trailing bytes left by gnutls_malloc. | https://nvd.nist.gov/vuln/detail/CVE-2016-7444 |
323,201 | gnutls | 964632f37dfdfb914ebc5e49db4fa29af35b1de9 | http://git.savannah.gnu.org/cgit/gnutls | https://gitlab.com/gnutls/gnutls/commit/964632f37dfdfb914ebc5e49db4fa29af35b1de9 | ocsp: corrected the comparison of the serial size in OCSP response
Previously the OCSP certificate check wouldn't verify the serial length
and could succeed in cases it shouldn't.
Reported by Stefan Buehler. | 0 | gnutls_ocsp_resp_check_crt(gnutls_ocsp_resp_t resp,
unsigned int indx, gnutls_x509_crt_t crt)
{
int ret;
gnutls_digest_algorithm_t digest;
gnutls_datum_t rdn_hash = { NULL, 0 }, rserial = {
NULL, 0};
gnutls_datum_t cserial = { NULL, 0 };
gnutls_datum_t dn = { NULL, 0 };
uint8_t cdn_hash[MAX_HASH_SIZE];
si... | 26,719,325,743,500,717,000,000,000,000,000,000,000 | ocsp.c | 145,137,143,893,199,900,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2016-7444 | The gnutls_ocsp_resp_check_crt function in lib/x509/ocsp.c in GnuTLS before 3.4.15 and 3.5.x before 3.5.4 does not verify the serial length of an OCSP response, which might allow remote attackers to bypass an intended certificate validation mechanism via vectors involving trailing bytes left by gnutls_malloc. | https://nvd.nist.gov/vuln/detail/CVE-2016-7444 |
201,859 | net-snmp | 5f881d3bf24599b90d67a45cae7a3eb099cd71c9 | https://github.com/net-snmp/net-snmp | https://github.com/net-snmp/net-snmp/commit/5f881d3bf24599b90d67a45cae7a3eb099cd71c9 | libsnmp, USM: Introduce a reference count in struct usmStateReference
This patch fixes https://sourceforge.net/p/net-snmp/bugs/2956/. | 1 | usm_free_usmStateReference(void *old)
{
struct usmStateReference *old_ref = (struct usmStateReference *) old;
if (old_ref) {
if (old_ref->usr_name_length)
SNMP_FREE(old_ref->usr_name);
if (old_ref->usr_engine_id_length)
SNMP_FREE(old_ref->usr_engine_id);
if (old... | 268,188,258,183,509,480,000,000,000,000,000,000,000 | snmpusm.c | 144,534,479,018,148,550,000,000,000,000,000,000,000 | [
"CWE-415"
] | CVE-2019-20892 | net-snmp before 5.8.1.pre1 has a double free in usm_free_usmStateReference in snmplib/snmpusm.c via an SNMPv3 GetBulk request. NOTE: this affects net-snmp packages shipped to end users by multiple Linux distributions, but might not affect an upstream release. | https://nvd.nist.gov/vuln/detail/CVE-2019-20892 |
323,254 | net-snmp | 5f881d3bf24599b90d67a45cae7a3eb099cd71c9 | https://github.com/net-snmp/net-snmp | https://github.com/net-snmp/net-snmp/commit/5f881d3bf24599b90d67a45cae7a3eb099cd71c9 | libsnmp, USM: Introduce a reference count in struct usmStateReference
This patch fixes https://sourceforge.net/p/net-snmp/bugs/2956/. | 0 | usm_free_usmStateReference(void *old)
{
struct usmStateReference *ref = old;
if (!ref)
return;
if (--ref->refcnt > 0)
return;
SNMP_FREE(ref->usr_name);
SNMP_FREE(ref->usr_engine_id);
SNMP_FREE(ref->usr_auth_protocol);
SNMP_FREE(ref->usr_priv_protocol);
if (ref->usr_au... | 155,277,545,461,962,020,000,000,000,000,000,000,000 | snmpusm.c | 44,992,709,525,642,160,000,000,000,000,000,000,000 | [
"CWE-415"
] | CVE-2019-20892 | net-snmp before 5.8.1.pre1 has a double free in usm_free_usmStateReference in snmplib/snmpusm.c via an SNMPv3 GetBulk request. NOTE: this affects net-snmp packages shipped to end users by multiple Linux distributions, but might not affect an upstream release. | https://nvd.nist.gov/vuln/detail/CVE-2019-20892 |
201,870 | irssi | 5a4e7ab659aba2855895c9f43e9a7a131f4e89b3 | https://github.com/irssi/irssi | https://github.com/irssi/irssi/commit/5a4e7ab659aba2855895c9f43e9a7a131f4e89b3 | fix use after free receiving caps
fixes GL#34 | 1 | static void event_cap (IRC_SERVER_REC *server, char *args, char *nick, char *address)
{
GSList *tmp;
GString *cmd;
char *params, *evt, *list, *star, **caps;
int i, caps_length, disable, avail_caps, multiline;
params = event_get_params(args, 4, NULL, &evt, &star, &list);
if (params == NULL)
return;
/* Multili... | 222,787,458,070,144,950,000,000,000,000,000,000,000 | irc-cap.c | 184,417,256,591,258,800,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2019-15717 | Irssi 1.2.x before 1.2.2 has a use-after-free if the IRC server sends a double CAP. | https://nvd.nist.gov/vuln/detail/CVE-2019-15717 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.