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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
397,595 | ghostpdl | d621292fb2c8157d9899dcd83fd04dd250e30fe4 | https://github.com/ArtifexSoftware/ghostpdl | http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=d621292fb2c8157d9899dcd83fd04dd250e30fe4 | Bug 697444 Unmatched transparency group pop
This issue can only occur if there is an unmatched group pop.
If the interpreter is doing that, then the interpreter is
broken. With this bug the user is intentionally doing it.
We now throw and error when it occurs. | 0 | pdf14_pop_transparency_group(gs_gstate *pgs, pdf14_ctx *ctx,
const pdf14_nonseparable_blending_procs_t * pblend_procs,
int tos_num_color_comp, cmm_profile_t *curr_icc_profile, gx_device *dev)
{
pdf14_buf *tos = ctx->stack;
pdf14_buf *nos = tos->saved;
pdf14_mask_t *mask_stack = tos->mask_stack;
... | 209,574,904,249,471,170,000,000,000,000,000,000,000 | gdevp14.c | 77,631,951,932,636,340,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2016-10218 | The pdf14_pop_transparency_group function in base/gdevp14.c in the PDF Transparency module in Artifex Software, Inc. Ghostscript 9.20 allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2016-10218 |
207,458 | libxml2 | 6a36fbe3b3e001a8a840b5c1fdd81cefc9947f0d | https://github.com/GNOME/libxml2 | http://git.gnome.org/browse/libxml2/commit/?id=6a36fbe3b3e001a8a840b5c1fdd81cefc9947f0d | Fix potential out of bound access | 1 | xmlParseAttValueComplex(xmlParserCtxtPtr ctxt, int *attlen, int normalize) {
xmlChar limit = 0;
xmlChar *buf = NULL;
xmlChar *rep = NULL;
size_t len = 0;
size_t buf_size = 0;
int c, l, in_space = 0;
xmlChar *current = NULL;
xmlEntityPtr ent;
if (NXT(0) == '"') {
ctxt->instate = XML... | 172,625,620,833,433,350,000,000,000,000,000,000,000 | parser.c | 78,326,408,068,852,810,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2012-5134 | Heap-based buffer underflow in the xmlParseAttValueComplex function in parser.c in libxml2 2.9.0 and earlier, as used in Google Chrome before 23.0.1271.91 and other products, allows remote attackers to cause a denial of service or possibly execute arbitrary code via crafted entities in an XML document. | https://nvd.nist.gov/vuln/detail/CVE-2012-5134 |
397,614 | libxml2 | 6a36fbe3b3e001a8a840b5c1fdd81cefc9947f0d | https://github.com/GNOME/libxml2 | http://git.gnome.org/browse/libxml2/commit/?id=6a36fbe3b3e001a8a840b5c1fdd81cefc9947f0d | Fix potential out of bound access | 0 | xmlParseAttValueComplex(xmlParserCtxtPtr ctxt, int *attlen, int normalize) {
xmlChar limit = 0;
xmlChar *buf = NULL;
xmlChar *rep = NULL;
size_t len = 0;
size_t buf_size = 0;
int c, l, in_space = 0;
xmlChar *current = NULL;
xmlEntityPtr ent;
if (NXT(0) == '"') {
ctxt->instate = XML... | 22,882,292,213,860,210,000,000,000,000,000,000,000 | parser.c | 219,671,658,828,454,300,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2012-5134 | Heap-based buffer underflow in the xmlParseAttValueComplex function in parser.c in libxml2 2.9.0 and earlier, as used in Google Chrome before 23.0.1271.91 and other products, allows remote attackers to cause a denial of service or possibly execute arbitrary code via crafted entities in an XML document. | https://nvd.nist.gov/vuln/detail/CVE-2012-5134 |
207,475 | libgcrypt | 78130828e9a140a9de4dafadbc844dbb64cb709a | https://github.com/gpg/libgcrypt | https://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git;a=commit;h=78130828e9a140a9de4dafadbc844dbb64cb709a | Same computation for square and multiply.
* mpi/mpi-pow.c (_gcry_mpi_powm): Compare msize for max_u_size. Move
the assignment to base_u into the loop. Copy content refered by RP to
BASE_U except the last of the loop.
--
Signed-off-by: NIIBE Yutaka <gniibe@fsij.org> | 1 | _gcry_mpi_powm (gcry_mpi_t res,
gcry_mpi_t base, gcry_mpi_t expo, gcry_mpi_t mod)
{
/* Pointer to the limbs of the arguments, their size and signs. */
mpi_ptr_t rp, ep, mp, bp;
mpi_size_t esize, msize, bsize, rsize;
int msign, bsign, rsign;
/* Flags telling the secure allocation... | 172,156,630,880,528,370,000,000,000,000,000,000,000 | mpi-pow.c | 170,844,529,919,473,130,000,000,000,000,000,000,000 | [
"CWE-310"
] | CVE-2017-7526 | libgcrypt before version 1.7.8 is vulnerable to a cache side-channel attack resulting into a complete break of RSA-1024 while using the left-to-right method for computing the sliding-window expansion. The same attack is believed to work on RSA-2048 with moderately more computation. This side-channel requires that attac... | https://nvd.nist.gov/vuln/detail/CVE-2017-7526 |
398,043 | libgcrypt | 78130828e9a140a9de4dafadbc844dbb64cb709a | https://github.com/gpg/libgcrypt | https://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git;a=commit;h=78130828e9a140a9de4dafadbc844dbb64cb709a | Same computation for square and multiply.
* mpi/mpi-pow.c (_gcry_mpi_powm): Compare msize for max_u_size. Move
the assignment to base_u into the loop. Copy content refered by RP to
BASE_U except the last of the loop.
--
Signed-off-by: NIIBE Yutaka <gniibe@fsij.org> | 0 | _gcry_mpi_powm (gcry_mpi_t res,
gcry_mpi_t base, gcry_mpi_t expo, gcry_mpi_t mod)
{
/* Pointer to the limbs of the arguments, their size and signs. */
mpi_ptr_t rp, ep, mp, bp;
mpi_size_t esize, msize, bsize, rsize;
int msign, bsign, rsign;
/* Flags telling the secure allocation... | 126,516,520,577,687,280,000,000,000,000,000,000,000 | mpi-pow.c | 222,861,010,617,834,130,000,000,000,000,000,000,000 | [
"CWE-310"
] | CVE-2017-7526 | libgcrypt before version 1.7.8 is vulnerable to a cache side-channel attack resulting into a complete break of RSA-1024 while using the left-to-right method for computing the sliding-window expansion. The same attack is believed to work on RSA-2048 with moderately more computation. This side-channel requires that attac... | https://nvd.nist.gov/vuln/detail/CVE-2017-7526 |
207,479 | nanopb | 4fe23595732b6f1254cfc11a9b8d6da900b55b0c | https://github.com/nanopb/nanopb | https://github.com/nanopb/nanopb/commit/4fe23595732b6f1254cfc11a9b8d6da900b55b0c | Fix memory leak with oneofs and PB_ENABLE_MALLOC (#615)
Nanopb would leak memory when all of the following conditions were true:
- PB_ENABLE_MALLOC is defined at the compile time
- Message definitions contains an oneof field,
the oneof contains a static submessage, and
the static submessage contains a pointer fiel... | 1 | static bool checkreturn decode_static_field(pb_istream_t *stream, pb_wire_type_t wire_type, pb_field_iter_t *iter)
{
pb_type_t type;
pb_decoder_t func;
type = iter->pos->type;
func = PB_DECODERS[PB_LTYPE(type)];
switch (PB_HTYPE(type))
{
case PB_HTYPE_REQUIRED:
return f... | 97,987,516,350,731,130,000,000,000,000,000,000,000 | pb_decode.c | 259,905,948,831,433,880,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2020-26243 | Nanopb is a small code-size Protocol Buffers implementation. In Nanopb before versions 0.4.4 and 0.3.9.7, decoding specifically formed message can leak memory if dynamic allocation is enabled and an oneof field contains a static submessage that contains a dynamic field, and the message being decoded contains the submes... | https://nvd.nist.gov/vuln/detail/CVE-2020-26243 |
398,219 | nanopb | 4fe23595732b6f1254cfc11a9b8d6da900b55b0c | https://github.com/nanopb/nanopb | https://github.com/nanopb/nanopb/commit/4fe23595732b6f1254cfc11a9b8d6da900b55b0c | Fix memory leak with oneofs and PB_ENABLE_MALLOC (#615)
Nanopb would leak memory when all of the following conditions were true:
- PB_ENABLE_MALLOC is defined at the compile time
- Message definitions contains an oneof field,
the oneof contains a static submessage, and
the static submessage contains a pointer fiel... | 0 | static bool checkreturn decode_static_field(pb_istream_t *stream, pb_wire_type_t wire_type, pb_field_iter_t *iter)
{
pb_type_t type;
pb_decoder_t func;
type = iter->pos->type;
func = PB_DECODERS[PB_LTYPE(type)];
switch (PB_HTYPE(type))
{
case PB_HTYPE_REQUIRED:
return f... | 182,754,631,715,074,170,000,000,000,000,000,000,000 | pb_decode.c | 140,871,851,250,121,650,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2020-26243 | Nanopb is a small code-size Protocol Buffers implementation. In Nanopb before versions 0.4.4 and 0.3.9.7, decoding specifically formed message can leak memory if dynamic allocation is enabled and an oneof field contains a static submessage that contains a dynamic field, and the message being decoded contains the submes... | https://nvd.nist.gov/vuln/detail/CVE-2020-26243 |
207,481 | upx | 90279abdfcd235172eab99651043051188938dcc | https://github.com/upx/upx | https://github.com/upx/upx/commit/90279abdfcd235172eab99651043051188938dcc | PackLinuxElf::canUnpack must checkEhdr() for ELF input
https://github.com/upx/upx/issues/485
modified: p_lx_elf.cpp | 1 | int PackLinuxElf64::canUnpack()
{
if (super::canUnpack()) {
return true;
}
if (Elf64_Ehdr::ET_DYN==get_te16(&ehdri.e_type)) {
PackLinuxElf64help1(fi);
Elf64_Phdr const *phdr = phdri, *last_LOAD = nullptr;
for (unsigned j = 0; j < e_phnum; ++phdr, ++j)
if (Elf64_Ph... | 219,935,618,679,455,780,000,000,000,000,000,000,000 | p_lx_elf.cpp | 296,359,139,270,897,460,000,000,000,000,000,000,000 | [
"CWE-415"
] | CVE-2021-30500 | Null pointer dereference was found in upx PackLinuxElf::canUnpack() in p_lx_elf.cpp,in version UPX 4.0.0. That allow attackers to execute arbitrary code and cause a denial of service via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2021-30500 |
398,237 | upx | 90279abdfcd235172eab99651043051188938dcc | https://github.com/upx/upx | https://github.com/upx/upx/commit/90279abdfcd235172eab99651043051188938dcc | PackLinuxElf::canUnpack must checkEhdr() for ELF input
https://github.com/upx/upx/issues/485
modified: p_lx_elf.cpp | 0 | int PackLinuxElf64::canUnpack()
{
if (checkEhdr(&ehdri)) {
return false;
}
if (Elf64_Ehdr::ET_DYN==get_te16(&ehdri.e_type)) {
PackLinuxElf64help1(fi);
Elf64_Phdr const *phdr = phdri, *last_LOAD = nullptr;
for (unsigned j = 0; j < e_phnum; ++phdr, ++j)
if (Elf64_Ph... | 196,551,689,599,588,330,000,000,000,000,000,000,000 | p_lx_elf.cpp | 340,157,686,291,381,940,000,000,000,000,000,000,000 | [
"CWE-415"
] | CVE-2021-30500 | Null pointer dereference was found in upx PackLinuxElf::canUnpack() in p_lx_elf.cpp,in version UPX 4.0.0. That allow attackers to execute arbitrary code and cause a denial of service via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2021-30500 |
207,482 | upx | 90279abdfcd235172eab99651043051188938dcc | https://github.com/upx/upx | https://github.com/upx/upx/commit/90279abdfcd235172eab99651043051188938dcc | PackLinuxElf::canUnpack must checkEhdr() for ELF input
https://github.com/upx/upx/issues/485
modified: p_lx_elf.cpp | 1 | int PackLinuxElf32::canUnpack()
{
if (super::canUnpack()) {
return true;
}
if (Elf32_Ehdr::ET_DYN==get_te16(&ehdri.e_type)) {
PackLinuxElf32help1(fi);
}
return false;
} | 30,905,079,414,765,806,000,000,000,000,000,000,000 | p_lx_elf.cpp | 296,359,139,270,897,460,000,000,000,000,000,000,000 | [
"CWE-415"
] | CVE-2021-30500 | Null pointer dereference was found in upx PackLinuxElf::canUnpack() in p_lx_elf.cpp,in version UPX 4.0.0. That allow attackers to execute arbitrary code and cause a denial of service via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2021-30500 |
398,229 | upx | 90279abdfcd235172eab99651043051188938dcc | https://github.com/upx/upx | https://github.com/upx/upx/commit/90279abdfcd235172eab99651043051188938dcc | PackLinuxElf::canUnpack must checkEhdr() for ELF input
https://github.com/upx/upx/issues/485
modified: p_lx_elf.cpp | 0 | int PackLinuxElf32::canUnpack()
{
if (checkEhdr(&ehdri)) {
return false;
}
// FIXME: ET_DYN same as 64-bit canUnpack ??
if (Elf32_Ehdr::ET_DYN==get_te16(&ehdri.e_type)) {
PackLinuxElf32help1(fi);
}
if (super::canUnpack()) {
return true;
}
return false;
} | 291,852,900,648,094,900,000,000,000,000,000,000,000 | p_lx_elf.cpp | 340,157,686,291,381,940,000,000,000,000,000,000,000 | [
"CWE-415"
] | CVE-2021-30500 | Null pointer dereference was found in upx PackLinuxElf::canUnpack() in p_lx_elf.cpp,in version UPX 4.0.0. That allow attackers to execute arbitrary code and cause a denial of service via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2021-30500 |
207,485 | gimp | 88eccea84aa375197cc04a2a0e2e29debb56bfa5 | https://github.com/GNOME/gimp | http://git.gnome.org/cgit/gimp/commit/?h=gimp-2-6&id=88eccea84aa375197cc04a2a0e2e29debb56bfa5 | Harden the PSD plugin against integer overflows.
Issues discovered by Stefan Cornelius, Secunia Research, advisory SA37232
and CVE identifier CVE-2009-3909. Fixes bug #600741.
(cherry picked from commit 9cc8d78ff33b7a36852b74e64b427489cad44d0e) | 1 | read_channel_data (PSDchannel *channel,
const guint16 bps,
const guint16 compression,
const guint16 *rle_pack_len,
FILE *f,
GError **error)
{
gchar *raw_data;
gchar *src;
gchar *dst;
... | 136,988,084,494,474,630,000,000,000,000,000,000,000 | psd-load.c | 149,826,530,178,813,540,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2009-3909 | Integer overflow in the read_channel_data function in plug-ins/file-psd/psd-load.c in GIMP 2.6.7 might allow remote attackers to execute arbitrary code via a crafted PSD file that triggers a heap-based buffer overflow. | https://nvd.nist.gov/vuln/detail/CVE-2009-3909 |
398,288 | gimp | 88eccea84aa375197cc04a2a0e2e29debb56bfa5 | https://github.com/GNOME/gimp | http://git.gnome.org/cgit/gimp/commit/?h=gimp-2-6&id=88eccea84aa375197cc04a2a0e2e29debb56bfa5 | Harden the PSD plugin against integer overflows.
Issues discovered by Stefan Cornelius, Secunia Research, advisory SA37232
and CVE identifier CVE-2009-3909. Fixes bug #600741.
(cherry picked from commit 9cc8d78ff33b7a36852b74e64b427489cad44d0e) | 0 | read_channel_data (PSDchannel *channel,
const guint16 bps,
const guint16 compression,
const guint16 *rle_pack_len,
FILE *f,
GError **error)
{
gchar *raw_data;
gchar *src;
gchar *dst;
... | 277,032,727,969,152,570,000,000,000,000,000,000,000 | psd-load.c | 145,544,085,230,655,350,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2009-3909 | Integer overflow in the read_channel_data function in plug-ins/file-psd/psd-load.c in GIMP 2.6.7 might allow remote attackers to execute arbitrary code via a crafted PSD file that triggers a heap-based buffer overflow. | https://nvd.nist.gov/vuln/detail/CVE-2009-3909 |
207,494 | oniguruma | ddbf55698b5f7ffdfa737b0b8e0079af1fdd7cb1 | https://github.com/kkos/oniguruma | https://github.com/kkos/oniguruma/commit/ddbf55698b5f7ffdfa737b0b8e0079af1fdd7cb1 | re-fix #60 by check val_type | 1 | parse_char_class(Node** np, OnigToken* tok, UChar** src, UChar* end,
ScanEnv* env)
{
int r, neg, len, fetched, and_start;
OnigCodePoint v, vs;
UChar *p;
Node* node;
CClassNode *cc, *prev_cc;
CClassNode work_cc;
enum CCSTATE state;
enum CCVALTYPE val_type, in_type;
int val_israw, in_israw;
*np =... | 287,714,396,318,495,360,000,000,000,000,000,000,000 | regparse.c | 129,069,855,452,470,340,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2017-9228 | An issue was discovered in Oniguruma 6.2.0, as used in Oniguruma-mod in Ruby through 2.4.1 and mbstring in PHP through 7.1.5. A heap out-of-bounds write occurs in bitset_set_range() during regular expression compilation due to an uninitialized variable from an incorrect state transition. An incorrect state transition i... | https://nvd.nist.gov/vuln/detail/CVE-2017-9228 |
398,404 | oniguruma | ddbf55698b5f7ffdfa737b0b8e0079af1fdd7cb1 | https://github.com/kkos/oniguruma | https://github.com/kkos/oniguruma/commit/ddbf55698b5f7ffdfa737b0b8e0079af1fdd7cb1 | re-fix #60 by check val_type | 0 | parse_char_class(Node** np, OnigToken* tok, UChar** src, UChar* end,
ScanEnv* env)
{
int r, neg, len, fetched, and_start;
OnigCodePoint v, vs;
UChar *p;
Node* node;
CClassNode *cc, *prev_cc;
CClassNode work_cc;
enum CCSTATE state;
enum CCVALTYPE val_type, in_type;
int val_israw, in_israw;
*np =... | 313,964,611,090,230,650,000,000,000,000,000,000,000 | regparse.c | 320,771,163,125,820,440,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2017-9228 | An issue was discovered in Oniguruma 6.2.0, as used in Oniguruma-mod in Ruby through 2.4.1 and mbstring in PHP through 7.1.5. A heap out-of-bounds write occurs in bitset_set_range() during regular expression compilation due to an uninitialized variable from an incorrect state transition. An incorrect state transition i... | https://nvd.nist.gov/vuln/detail/CVE-2017-9228 |
207,496 | re2c | c4603ba5ce229db83a2a4fb93e6d4b4e3ec3776a | https://github.com/skvadrik/re2c | https://github.com/skvadrik/re2c/commit/c4603ba5ce229db83a2a4fb93e6d4b4e3ec3776a | Fix crash in lexer refill (reported by Agostino Sarubbo).
The crash happened in a rare case of a very long lexeme that doen't fit
into the buffer, forcing buffer reallocation.
The crash was caused by an incorrect calculation of the shift offset
(it was smaller than necessary). As a consequence, the data from buffer
s... | 1 | bool Scanner::fill(size_t need)
{
if (eof) return false;
pop_finished_files();
DASSERT(bot <= tok && tok <= lim);
size_t free = static_cast<size_t>(tok - bot);
size_t copy = static_cast<size_t>(lim - tok);
if (free >= need) {
memmove(bot, tok, copy);
shift_ptrs_and_fpos(-stati... | 160,317,948,149,420,250,000,000,000,000,000,000,000 | scanner.cc | 256,816,301,103,786,040,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2020-11958 | re2c 1.3 has a heap-based buffer overflow in Scanner::fill in parse/scanner.cc via a long lexeme. | https://nvd.nist.gov/vuln/detail/CVE-2020-11958 |
398,413 | re2c | c4603ba5ce229db83a2a4fb93e6d4b4e3ec3776a | https://github.com/skvadrik/re2c | https://github.com/skvadrik/re2c/commit/c4603ba5ce229db83a2a4fb93e6d4b4e3ec3776a | Fix crash in lexer refill (reported by Agostino Sarubbo).
The crash happened in a rare case of a very long lexeme that doen't fit
into the buffer, forcing buffer reallocation.
The crash was caused by an incorrect calculation of the shift offset
(it was smaller than necessary). As a consequence, the data from buffer
s... | 0 | bool Scanner::fill(size_t need)
{
if (eof) return false;
pop_finished_files();
DASSERT(bot <= tok && tok <= lim);
size_t free = static_cast<size_t>(tok - bot);
size_t copy = static_cast<size_t>(lim - tok);
if (free >= need) {
memmove(bot, tok, copy);
shift_ptrs_and_fpos(-stati... | 227,188,579,464,338,200,000,000,000,000,000,000,000 | scanner.cc | 161,164,547,988,637,170,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2020-11958 | re2c 1.3 has a heap-based buffer overflow in Scanner::fill in parse/scanner.cc via a long lexeme. | https://nvd.nist.gov/vuln/detail/CVE-2020-11958 |
207,508 | ImageMagick | 74f8b6cb2d31651cd34d2830f570979f7db882e0 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/74f8b6cb2d31651cd34d2830f570979f7db882e0 | https://github.com/ImageMagick/ImageMagick/issues/1050 | 1 | static MagickBooleanType WritePDBImage(const ImageInfo *image_info,Image *image,
ExceptionInfo *exception)
{
const char
*comment;
int
bits;
MagickBooleanType
status;
PDBImage
pdb_image;
PDBInfo
pdb_info;
QuantumInfo
*quantum_info;
register const Quantum
*p;
register ... | 110,671,692,877,981,400,000,000,000,000,000,000,000 | pdb.c | 134,680,943,430,573,040,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2018-17966 | ImageMagick 7.0.7-28 has a memory leak vulnerability in WritePDBImage in coders/pdb.c. | https://nvd.nist.gov/vuln/detail/CVE-2018-17966 |
398,435 | ImageMagick | 74f8b6cb2d31651cd34d2830f570979f7db882e0 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/74f8b6cb2d31651cd34d2830f570979f7db882e0 | https://github.com/ImageMagick/ImageMagick/issues/1050 | 0 | static MagickBooleanType WritePDBImage(const ImageInfo *image_info,Image *image,
ExceptionInfo *exception)
{
const char
*comment;
int
bits;
MagickBooleanType
status;
PDBImage
pdb_image;
PDBInfo
pdb_info;
QuantumInfo
*quantum_info;
register const Quantum
*p;
register ... | 30,309,856,989,213,603,000,000,000,000,000,000,000 | pdb.c | 265,201,857,941,799,900,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2018-17966 | ImageMagick 7.0.7-28 has a memory leak vulnerability in WritePDBImage in coders/pdb.c. | https://nvd.nist.gov/vuln/detail/CVE-2018-17966 |
207,513 | exiv2 | 491c3ebe3b3faa6d8f75fb28146186792c2439da | https://github.com/Exiv2/exiv2 | https://github.com/Exiv2/exiv2/commit/491c3ebe3b3faa6d8f75fb28146186792c2439da | Avoid negative integer overflow when `iccOffset > chunkLength`.
This fixes #790.
(cherry picked from commit 6fa2e31206127bd8bcac0269311f3775a8d6ea21) | 1 | void PngImage::readMetadata()
{
#ifdef DEBUG
std::cerr << "Exiv2::PngImage::readMetadata: Reading PNG file " << io_->path() << std::endl;
#endif
if (io_->open() != 0) {
throw Error(kerDataSourceOpenFailed, io_->path(), strError());
}
IoCloser closer(*io_);
if ... | 5,345,237,172,897,159,000,000,000,000,000,000,000 | pngimage.cpp | 54,016,909,164,860,405,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2019-13109 | An integer overflow in Exiv2 through 0.27.1 allows an attacker to cause a denial of service (SIGSEGV) via a crafted PNG image file, because PngImage::readMetadata mishandles a chunkLength - iccOffset subtraction. | https://nvd.nist.gov/vuln/detail/CVE-2019-13109 |
398,479 | exiv2 | 491c3ebe3b3faa6d8f75fb28146186792c2439da | https://github.com/Exiv2/exiv2 | https://github.com/Exiv2/exiv2/commit/491c3ebe3b3faa6d8f75fb28146186792c2439da | Avoid negative integer overflow when `iccOffset > chunkLength`.
This fixes #790.
(cherry picked from commit 6fa2e31206127bd8bcac0269311f3775a8d6ea21) | 0 | void PngImage::readMetadata()
{
#ifdef DEBUG
std::cerr << "Exiv2::PngImage::readMetadata: Reading PNG file " << io_->path() << std::endl;
#endif
if (io_->open() != 0) {
throw Error(kerDataSourceOpenFailed, io_->path(), strError());
}
IoCloser closer(*io_);
if ... | 93,635,078,137,577,580,000,000,000,000,000,000,000 | pngimage.cpp | 27,270,567,068,678,014,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2019-13109 | An integer overflow in Exiv2 through 0.27.1 allows an attacker to cause a denial of service (SIGSEGV) via a crafted PNG image file, because PngImage::readMetadata mishandles a chunkLength - iccOffset subtraction. | https://nvd.nist.gov/vuln/detail/CVE-2019-13109 |
207,523 | ImageMagick | a81ca9a1b46a96be83682af3389f0a6f3d0d389d | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/a81ca9a1b46a96be83682af3389f0a6f3d0d389d | https://github.com/ImageMagick/ImageMagick/issues/1711 | 1 | static inline void ConvertRGBToCMYK(PixelInfo *pixel)
{
MagickRealType
black,
blue,
cyan,
green,
magenta,
red,
yellow;
if (pixel->colorspace != sRGBColorspace)
{
red=QuantumScale*pixel->red;
green=QuantumScale*pixel->green;
blue=QuantumScale*pixel->blue;
}
el... | 335,463,036,448,358,930,000,000,000,000,000,000,000 | colorspace-private.h | 56,577,435,073,425,320,000,000,000,000,000,000,000 | [
"CWE-369"
] | CVE-2020-27750 | A flaw was found in ImageMagick in MagickCore/colorspace-private.h and MagickCore/quantum.h. An attacker who submits a crafted file that is processed by ImageMagick could trigger undefined behavior in the form of values outside the range of type `unsigned char` and math division by zero. This would most likely lead to ... | https://nvd.nist.gov/vuln/detail/CVE-2020-27750 |
398,562 | ImageMagick | a81ca9a1b46a96be83682af3389f0a6f3d0d389d | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/a81ca9a1b46a96be83682af3389f0a6f3d0d389d | https://github.com/ImageMagick/ImageMagick/issues/1711 | 0 | static inline void ConvertRGBToCMYK(PixelInfo *pixel)
{
MagickRealType
black,
blue,
cyan,
green,
magenta,
red,
yellow;
if (pixel->colorspace != sRGBColorspace)
{
red=QuantumScale*pixel->red;
green=QuantumScale*pixel->green;
blue=QuantumScale*pixel->blue;
}
el... | 236,633,916,104,638,680,000,000,000,000,000,000,000 | colorspace-private.h | 203,246,278,778,652,740,000,000,000,000,000,000,000 | [
"CWE-369"
] | CVE-2020-27750 | A flaw was found in ImageMagick in MagickCore/colorspace-private.h and MagickCore/quantum.h. An attacker who submits a crafted file that is processed by ImageMagick could trigger undefined behavior in the form of values outside the range of type `unsigned char` and math division by zero. This would most likely lead to ... | https://nvd.nist.gov/vuln/detail/CVE-2020-27750 |
207,559 | abcm2ps | dc0372993674d0b50fedfbf7b9fad1239b8efc5f | https://github.com/leesavide/abcm2ps | https://github.com/leesavide/abcm2ps/commit/dc0372993674d0b50fedfbf7b9fad1239b8efc5f | fix: crash when too many accidentals in K: (signature + explicit)
Issue #17. | 1 | static void set_k_acc(struct SYMBOL *s)
{
int i, j, nacc;
char accs[8], pits[8];
static char sharp_tb[8] = {26, 23, 27, 24, 21, 25, 22};
static char flat_tb[8] = {22, 25, 21, 24, 20, 23, 26};
if (s->u.key.sf > 0) {
for (nacc = 0; nacc < s->u.key.sf; nacc++) {
accs[nacc] = A_SH;
pits[nacc] = sharp_tb[nacc]... | 10,672,335,522,720,499,000,000,000,000,000,000,000 | parse.c | 142,811,409,308,722,500,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2018-10771 | Stack-based buffer overflow in the get_key function in parse.c in abcm2ps through 8.13.20 allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact. | https://nvd.nist.gov/vuln/detail/CVE-2018-10771 |
399,015 | abcm2ps | dc0372993674d0b50fedfbf7b9fad1239b8efc5f | https://github.com/leesavide/abcm2ps | https://github.com/leesavide/abcm2ps/commit/dc0372993674d0b50fedfbf7b9fad1239b8efc5f | fix: crash when too many accidentals in K: (signature + explicit)
Issue #17. | 0 | static void set_k_acc(struct SYMBOL *s)
{
int i, j, nacc;
char accs[8], pits[8];
static char sharp_tb[8] = {26, 23, 27, 24, 21, 25, 22};
static char flat_tb[8] = {22, 25, 21, 24, 20, 23, 26};
if (s->u.key.sf > 0) {
for (nacc = 0; nacc < s->u.key.sf; nacc++) {
accs[nacc] = A_SH;
pits[nacc] = sharp_tb[nacc]... | 101,099,105,851,822,770,000,000,000,000,000,000,000 | parse.c | 229,834,367,443,714,700,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2018-10771 | Stack-based buffer overflow in the get_key function in parse.c in abcm2ps through 8.13.20 allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact. | https://nvd.nist.gov/vuln/detail/CVE-2018-10771 |
207,575 | linux | d9d4b1e46d9543a82c23f6df03f4ad697dab361b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d9d4b1e46d9543a82c23f6df03f4ad697dab361b | HID: Fix assumption that devices have inputs
The syzbot fuzzer found a slab-out-of-bounds write bug in the hid-gaff
driver. The problem is caused by the driver's assumption that the
device must have an input report. While this will be true for all
normal HID input devices, a suitably malicious device can violate the... | 1 | int lg2ff_init(struct hid_device *hid)
{
struct lg2ff_device *lg2ff;
struct hid_report *report;
struct hid_input *hidinput = list_entry(hid->inputs.next,
struct hid_input, list);
struct input_dev *dev = hidinput->input;
int error;
/* Check that the report looks ok */
report = hid_validate_values(hid, HID_... | 150,118,936,715,420,640,000,000,000,000,000,000,000 | hid-lg2ff.c | 172,944,395,568,492,120,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19532 | In the Linux kernel before 5.3.9, there are multiple out-of-bounds write bugs that can be caused by a malicious USB device in the Linux kernel HID drivers, aka CID-d9d4b1e46d95. This affects drivers/hid/hid-axff.c, drivers/hid/hid-dr.c, drivers/hid/hid-emsff.c, drivers/hid/hid-gaff.c, drivers/hid/hid-holtekff.c, driver... | https://nvd.nist.gov/vuln/detail/CVE-2019-19532 |
399,348 | linux | d9d4b1e46d9543a82c23f6df03f4ad697dab361b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d9d4b1e46d9543a82c23f6df03f4ad697dab361b | HID: Fix assumption that devices have inputs
The syzbot fuzzer found a slab-out-of-bounds write bug in the hid-gaff
driver. The problem is caused by the driver's assumption that the
device must have an input report. While this will be true for all
normal HID input devices, a suitably malicious device can violate the... | 0 | int lg2ff_init(struct hid_device *hid)
{
struct lg2ff_device *lg2ff;
struct hid_report *report;
struct hid_input *hidinput;
struct input_dev *dev;
int error;
if (list_empty(&hid->inputs)) {
hid_err(hid, "no inputs found\n");
return -ENODEV;
}
hidinput = list_entry(hid->inputs.next, struct hid_input, list);... | 145,565,473,661,944,810,000,000,000,000,000,000,000 | hid-lg2ff.c | 325,077,464,545,451,600,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19532 | In the Linux kernel before 5.3.9, there are multiple out-of-bounds write bugs that can be caused by a malicious USB device in the Linux kernel HID drivers, aka CID-d9d4b1e46d95. This affects drivers/hid/hid-axff.c, drivers/hid/hid-dr.c, drivers/hid/hid-emsff.c, drivers/hid/hid-gaff.c, drivers/hid/hid-holtekff.c, driver... | https://nvd.nist.gov/vuln/detail/CVE-2019-19532 |
207,576 | linux | d9d4b1e46d9543a82c23f6df03f4ad697dab361b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d9d4b1e46d9543a82c23f6df03f4ad697dab361b | HID: Fix assumption that devices have inputs
The syzbot fuzzer found a slab-out-of-bounds write bug in the hid-gaff
driver. The problem is caused by the driver's assumption that the
device must have an input report. While this will be true for all
normal HID input devices, a suitably malicious device can violate the... | 1 | static int sony_init_ff(struct sony_sc *sc)
{
struct hid_input *hidinput = list_entry(sc->hdev->inputs.next,
struct hid_input, list);
struct input_dev *input_dev = hidinput->input;
input_set_capability(input_dev, EV_FF, FF_RUMBLE);
return input_ff_create_memless(input_dev, NULL, sony_play_effect);
} | 97,216,593,480,460,850,000,000,000,000,000,000,000 | hid-sony.c | 313,785,911,430,300,550,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19532 | In the Linux kernel before 5.3.9, there are multiple out-of-bounds write bugs that can be caused by a malicious USB device in the Linux kernel HID drivers, aka CID-d9d4b1e46d95. This affects drivers/hid/hid-axff.c, drivers/hid/hid-dr.c, drivers/hid/hid-emsff.c, drivers/hid/hid-gaff.c, drivers/hid/hid-holtekff.c, driver... | https://nvd.nist.gov/vuln/detail/CVE-2019-19532 |
399,312 | linux | d9d4b1e46d9543a82c23f6df03f4ad697dab361b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d9d4b1e46d9543a82c23f6df03f4ad697dab361b | HID: Fix assumption that devices have inputs
The syzbot fuzzer found a slab-out-of-bounds write bug in the hid-gaff
driver. The problem is caused by the driver's assumption that the
device must have an input report. While this will be true for all
normal HID input devices, a suitably malicious device can violate the... | 0 | static int sony_init_ff(struct sony_sc *sc)
{
struct hid_input *hidinput;
struct input_dev *input_dev;
if (list_empty(&sc->hdev->inputs)) {
hid_err(sc->hdev, "no inputs found\n");
return -ENODEV;
}
hidinput = list_entry(sc->hdev->inputs.next, struct hid_input, list);
input_dev = hidinput->input;
input_set_... | 50,112,979,855,351,370,000,000,000,000,000,000,000 | hid-sony.c | 154,355,804,180,729,100,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19532 | In the Linux kernel before 5.3.9, there are multiple out-of-bounds write bugs that can be caused by a malicious USB device in the Linux kernel HID drivers, aka CID-d9d4b1e46d95. This affects drivers/hid/hid-axff.c, drivers/hid/hid-dr.c, drivers/hid/hid-emsff.c, drivers/hid/hid-gaff.c, drivers/hid/hid-holtekff.c, driver... | https://nvd.nist.gov/vuln/detail/CVE-2019-19532 |
207,578 | linux | d9d4b1e46d9543a82c23f6df03f4ad697dab361b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d9d4b1e46d9543a82c23f6df03f4ad697dab361b | HID: Fix assumption that devices have inputs
The syzbot fuzzer found a slab-out-of-bounds write bug in the hid-gaff
driver. The problem is caused by the driver's assumption that the
device must have an input report. While this will be true for all
normal HID input devices, a suitably malicious device can violate the... | 1 | static int zpff_init(struct hid_device *hid)
{
struct zpff_device *zpff;
struct hid_report *report;
struct hid_input *hidinput = list_entry(hid->inputs.next,
struct hid_input, list);
struct input_dev *dev = hidinput->input;
int i, error;
for (i = 0; i < 4; i++) {
report = hid_validate_values(hid, HID_OUT... | 219,922,862,768,771,750,000,000,000,000,000,000,000 | hid-zpff.c | 38,824,775,435,155,623,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19532 | In the Linux kernel before 5.3.9, there are multiple out-of-bounds write bugs that can be caused by a malicious USB device in the Linux kernel HID drivers, aka CID-d9d4b1e46d95. This affects drivers/hid/hid-axff.c, drivers/hid/hid-dr.c, drivers/hid/hid-emsff.c, drivers/hid/hid-gaff.c, drivers/hid/hid-holtekff.c, driver... | https://nvd.nist.gov/vuln/detail/CVE-2019-19532 |
399,386 | linux | d9d4b1e46d9543a82c23f6df03f4ad697dab361b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d9d4b1e46d9543a82c23f6df03f4ad697dab361b | HID: Fix assumption that devices have inputs
The syzbot fuzzer found a slab-out-of-bounds write bug in the hid-gaff
driver. The problem is caused by the driver's assumption that the
device must have an input report. While this will be true for all
normal HID input devices, a suitably malicious device can violate the... | 0 | static int zpff_init(struct hid_device *hid)
{
struct zpff_device *zpff;
struct hid_report *report;
struct hid_input *hidinput;
struct input_dev *dev;
int i, error;
if (list_empty(&hid->inputs)) {
hid_err(hid, "no inputs found\n");
return -ENODEV;
}
hidinput = list_entry(hid->inputs.next, struct hid_input,... | 171,804,969,116,839,670,000,000,000,000,000,000,000 | hid-zpff.c | 25,516,281,294,915,320,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19532 | In the Linux kernel before 5.3.9, there are multiple out-of-bounds write bugs that can be caused by a malicious USB device in the Linux kernel HID drivers, aka CID-d9d4b1e46d95. This affects drivers/hid/hid-axff.c, drivers/hid/hid-dr.c, drivers/hid/hid-emsff.c, drivers/hid/hid-gaff.c, drivers/hid/hid-holtekff.c, driver... | https://nvd.nist.gov/vuln/detail/CVE-2019-19532 |
207,579 | linux | d9d4b1e46d9543a82c23f6df03f4ad697dab361b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d9d4b1e46d9543a82c23f6df03f4ad697dab361b | HID: Fix assumption that devices have inputs
The syzbot fuzzer found a slab-out-of-bounds write bug in the hid-gaff
driver. The problem is caused by the driver's assumption that the
device must have an input report. While this will be true for all
normal HID input devices, a suitably malicious device can violate the... | 1 | static int tmff_init(struct hid_device *hid, const signed short *ff_bits)
{
struct tmff_device *tmff;
struct hid_report *report;
struct list_head *report_list;
struct hid_input *hidinput = list_entry(hid->inputs.next,
struct hid_input, list);
struct input_dev *input_dev = hidinput->input;
int error;
int i... | 62,885,458,198,387,420,000,000,000,000,000,000,000 | hid-tmff.c | 40,180,274,444,903,573,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19532 | In the Linux kernel before 5.3.9, there are multiple out-of-bounds write bugs that can be caused by a malicious USB device in the Linux kernel HID drivers, aka CID-d9d4b1e46d95. This affects drivers/hid/hid-axff.c, drivers/hid/hid-dr.c, drivers/hid/hid-emsff.c, drivers/hid/hid-gaff.c, drivers/hid/hid-holtekff.c, driver... | https://nvd.nist.gov/vuln/detail/CVE-2019-19532 |
399,481 | linux | d9d4b1e46d9543a82c23f6df03f4ad697dab361b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d9d4b1e46d9543a82c23f6df03f4ad697dab361b | HID: Fix assumption that devices have inputs
The syzbot fuzzer found a slab-out-of-bounds write bug in the hid-gaff
driver. The problem is caused by the driver's assumption that the
device must have an input report. While this will be true for all
normal HID input devices, a suitably malicious device can violate the... | 0 | static int tmff_init(struct hid_device *hid, const signed short *ff_bits)
{
struct tmff_device *tmff;
struct hid_report *report;
struct list_head *report_list;
struct hid_input *hidinput;
struct input_dev *input_dev;
int error;
int i;
if (list_empty(&hid->inputs)) {
hid_err(hid, "no inputs found\n");
retur... | 109,135,974,020,412,900,000,000,000,000,000,000,000 | hid-tmff.c | 158,562,846,529,485,780,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19532 | In the Linux kernel before 5.3.9, there are multiple out-of-bounds write bugs that can be caused by a malicious USB device in the Linux kernel HID drivers, aka CID-d9d4b1e46d95. This affects drivers/hid/hid-axff.c, drivers/hid/hid-dr.c, drivers/hid/hid-emsff.c, drivers/hid/hid-gaff.c, drivers/hid/hid-holtekff.c, driver... | https://nvd.nist.gov/vuln/detail/CVE-2019-19532 |
207,580 | linux | d9d4b1e46d9543a82c23f6df03f4ad697dab361b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d9d4b1e46d9543a82c23f6df03f4ad697dab361b | HID: Fix assumption that devices have inputs
The syzbot fuzzer found a slab-out-of-bounds write bug in the hid-gaff
driver. The problem is caused by the driver's assumption that the
device must have an input report. While this will be true for all
normal HID input devices, a suitably malicious device can violate the... | 1 | static int axff_init(struct hid_device *hid)
{
struct axff_device *axff;
struct hid_report *report;
struct hid_input *hidinput = list_first_entry(&hid->inputs, struct hid_input, list);
struct list_head *report_list =&hid->report_enum[HID_OUTPUT_REPORT].report_list;
struct input_dev *dev = hidinput->input;
int fie... | 321,980,282,110,006,960,000,000,000,000,000,000,000 | hid-axff.c | 308,465,402,983,142,270,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19532 | In the Linux kernel before 5.3.9, there are multiple out-of-bounds write bugs that can be caused by a malicious USB device in the Linux kernel HID drivers, aka CID-d9d4b1e46d95. This affects drivers/hid/hid-axff.c, drivers/hid/hid-dr.c, drivers/hid/hid-emsff.c, drivers/hid/hid-gaff.c, drivers/hid/hid-holtekff.c, driver... | https://nvd.nist.gov/vuln/detail/CVE-2019-19532 |
399,494 | linux | d9d4b1e46d9543a82c23f6df03f4ad697dab361b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d9d4b1e46d9543a82c23f6df03f4ad697dab361b | HID: Fix assumption that devices have inputs
The syzbot fuzzer found a slab-out-of-bounds write bug in the hid-gaff
driver. The problem is caused by the driver's assumption that the
device must have an input report. While this will be true for all
normal HID input devices, a suitably malicious device can violate the... | 0 | static int axff_init(struct hid_device *hid)
{
struct axff_device *axff;
struct hid_report *report;
struct hid_input *hidinput;
struct list_head *report_list =&hid->report_enum[HID_OUTPUT_REPORT].report_list;
struct input_dev *dev;
int field_count = 0;
int i, j;
int error;
if (list_empty(&hid->inputs)) {
hi... | 205,388,641,648,188,700,000,000,000,000,000,000,000 | hid-axff.c | 273,263,220,013,898,500,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19532 | In the Linux kernel before 5.3.9, there are multiple out-of-bounds write bugs that can be caused by a malicious USB device in the Linux kernel HID drivers, aka CID-d9d4b1e46d95. This affects drivers/hid/hid-axff.c, drivers/hid/hid-dr.c, drivers/hid/hid-emsff.c, drivers/hid/hid-gaff.c, drivers/hid/hid-holtekff.c, driver... | https://nvd.nist.gov/vuln/detail/CVE-2019-19532 |
207,582 | linux | d9d4b1e46d9543a82c23f6df03f4ad697dab361b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d9d4b1e46d9543a82c23f6df03f4ad697dab361b | HID: Fix assumption that devices have inputs
The syzbot fuzzer found a slab-out-of-bounds write bug in the hid-gaff
driver. The problem is caused by the driver's assumption that the
device must have an input report. While this will be true for all
normal HID input devices, a suitably malicious device can violate the... | 1 | static int gaff_init(struct hid_device *hid)
{
struct gaff_device *gaff;
struct hid_report *report;
struct hid_input *hidinput = list_entry(hid->inputs.next,
struct hid_input, list);
struct list_head *report_list =
&hid->report_enum[HID_OUTPUT_REPORT].report_list;
struct list_head *report_ptr = report_lis... | 45,308,669,490,471,550,000,000,000,000,000,000,000 | hid-gaff.c | 74,174,609,553,815,440,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19532 | In the Linux kernel before 5.3.9, there are multiple out-of-bounds write bugs that can be caused by a malicious USB device in the Linux kernel HID drivers, aka CID-d9d4b1e46d95. This affects drivers/hid/hid-axff.c, drivers/hid/hid-dr.c, drivers/hid/hid-emsff.c, drivers/hid/hid-gaff.c, drivers/hid/hid-holtekff.c, driver... | https://nvd.nist.gov/vuln/detail/CVE-2019-19532 |
399,369 | linux | d9d4b1e46d9543a82c23f6df03f4ad697dab361b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d9d4b1e46d9543a82c23f6df03f4ad697dab361b | HID: Fix assumption that devices have inputs
The syzbot fuzzer found a slab-out-of-bounds write bug in the hid-gaff
driver. The problem is caused by the driver's assumption that the
device must have an input report. While this will be true for all
normal HID input devices, a suitably malicious device can violate the... | 0 | static int gaff_init(struct hid_device *hid)
{
struct gaff_device *gaff;
struct hid_report *report;
struct hid_input *hidinput;
struct list_head *report_list =
&hid->report_enum[HID_OUTPUT_REPORT].report_list;
struct list_head *report_ptr = report_list;
struct input_dev *dev;
int error;
if (list_empty(&hid-... | 222,758,614,213,222,600,000,000,000,000,000,000,000 | hid-gaff.c | 263,867,582,425,483,550,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19532 | In the Linux kernel before 5.3.9, there are multiple out-of-bounds write bugs that can be caused by a malicious USB device in the Linux kernel HID drivers, aka CID-d9d4b1e46d95. This affects drivers/hid/hid-axff.c, drivers/hid/hid-dr.c, drivers/hid/hid-emsff.c, drivers/hid/hid-gaff.c, drivers/hid/hid-holtekff.c, driver... | https://nvd.nist.gov/vuln/detail/CVE-2019-19532 |
207,583 | linux | d9d4b1e46d9543a82c23f6df03f4ad697dab361b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d9d4b1e46d9543a82c23f6df03f4ad697dab361b | HID: Fix assumption that devices have inputs
The syzbot fuzzer found a slab-out-of-bounds write bug in the hid-gaff
driver. The problem is caused by the driver's assumption that the
device must have an input report. While this will be true for all
normal HID input devices, a suitably malicious device can violate the... | 1 | int lgff_init(struct hid_device* hid)
{
struct hid_input *hidinput = list_entry(hid->inputs.next, struct hid_input, list);
struct input_dev *dev = hidinput->input;
const signed short *ff_bits = ff_joystick;
int error;
int i;
/* Check that the report looks ok */
if (!hid_validate_values(hid, HID_OUTPUT_REPORT, 0... | 210,310,099,119,883,900,000,000,000,000,000,000,000 | hid-lgff.c | 12,522,330,984,594,252,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19532 | In the Linux kernel before 5.3.9, there are multiple out-of-bounds write bugs that can be caused by a malicious USB device in the Linux kernel HID drivers, aka CID-d9d4b1e46d95. This affects drivers/hid/hid-axff.c, drivers/hid/hid-dr.c, drivers/hid/hid-emsff.c, drivers/hid/hid-gaff.c, drivers/hid/hid-holtekff.c, driver... | https://nvd.nist.gov/vuln/detail/CVE-2019-19532 |
399,349 | linux | d9d4b1e46d9543a82c23f6df03f4ad697dab361b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d9d4b1e46d9543a82c23f6df03f4ad697dab361b | HID: Fix assumption that devices have inputs
The syzbot fuzzer found a slab-out-of-bounds write bug in the hid-gaff
driver. The problem is caused by the driver's assumption that the
device must have an input report. While this will be true for all
normal HID input devices, a suitably malicious device can violate the... | 0 | int lgff_init(struct hid_device* hid)
{
struct hid_input *hidinput;
struct input_dev *dev;
const signed short *ff_bits = ff_joystick;
int error;
int i;
if (list_empty(&hid->inputs)) {
hid_err(hid, "no inputs found\n");
return -ENODEV;
}
hidinput = list_entry(hid->inputs.next, struct hid_input, list);
dev ... | 7,385,914,920,016,859,000,000,000,000,000,000,000 | hid-lgff.c | 139,738,316,754,143,360,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19532 | In the Linux kernel before 5.3.9, there are multiple out-of-bounds write bugs that can be caused by a malicious USB device in the Linux kernel HID drivers, aka CID-d9d4b1e46d95. This affects drivers/hid/hid-axff.c, drivers/hid/hid-dr.c, drivers/hid/hid-emsff.c, drivers/hid/hid-gaff.c, drivers/hid/hid-holtekff.c, driver... | https://nvd.nist.gov/vuln/detail/CVE-2019-19532 |
207,585 | linux | d9d4b1e46d9543a82c23f6df03f4ad697dab361b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d9d4b1e46d9543a82c23f6df03f4ad697dab361b | HID: Fix assumption that devices have inputs
The syzbot fuzzer found a slab-out-of-bounds write bug in the hid-gaff
driver. The problem is caused by the driver's assumption that the
device must have an input report. While this will be true for all
normal HID input devices, a suitably malicious device can violate the... | 1 | static int emsff_init(struct hid_device *hid)
{
struct emsff_device *emsff;
struct hid_report *report;
struct hid_input *hidinput = list_first_entry(&hid->inputs,
struct hid_input, list);
struct list_head *report_list =
&hid->report_enum[HID_OUTPUT_REPORT].report_list;
struct input_dev *dev = hidinput->in... | 261,213,450,248,439,000,000,000,000,000,000,000,000 | hid-emsff.c | 231,879,302,581,639,870,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19532 | In the Linux kernel before 5.3.9, there are multiple out-of-bounds write bugs that can be caused by a malicious USB device in the Linux kernel HID drivers, aka CID-d9d4b1e46d95. This affects drivers/hid/hid-axff.c, drivers/hid/hid-dr.c, drivers/hid/hid-emsff.c, drivers/hid/hid-gaff.c, drivers/hid/hid-holtekff.c, driver... | https://nvd.nist.gov/vuln/detail/CVE-2019-19532 |
399,461 | linux | d9d4b1e46d9543a82c23f6df03f4ad697dab361b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d9d4b1e46d9543a82c23f6df03f4ad697dab361b | HID: Fix assumption that devices have inputs
The syzbot fuzzer found a slab-out-of-bounds write bug in the hid-gaff
driver. The problem is caused by the driver's assumption that the
device must have an input report. While this will be true for all
normal HID input devices, a suitably malicious device can violate the... | 0 | static int emsff_init(struct hid_device *hid)
{
struct emsff_device *emsff;
struct hid_report *report;
struct hid_input *hidinput;
struct list_head *report_list =
&hid->report_enum[HID_OUTPUT_REPORT].report_list;
struct input_dev *dev;
int error;
if (list_empty(&hid->inputs)) {
hid_err(hid, "no inputs foun... | 14,038,901,640,544,368,000,000,000,000,000,000,000 | hid-emsff.c | 102,561,510,898,243,900,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19532 | In the Linux kernel before 5.3.9, there are multiple out-of-bounds write bugs that can be caused by a malicious USB device in the Linux kernel HID drivers, aka CID-d9d4b1e46d95. This affects drivers/hid/hid-axff.c, drivers/hid/hid-dr.c, drivers/hid/hid-emsff.c, drivers/hid/hid-gaff.c, drivers/hid/hid-holtekff.c, driver... | https://nvd.nist.gov/vuln/detail/CVE-2019-19532 |
207,586 | linux | d9d4b1e46d9543a82c23f6df03f4ad697dab361b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d9d4b1e46d9543a82c23f6df03f4ad697dab361b | HID: Fix assumption that devices have inputs
The syzbot fuzzer found a slab-out-of-bounds write bug in the hid-gaff
driver. The problem is caused by the driver's assumption that the
device must have an input report. While this will be true for all
normal HID input devices, a suitably malicious device can violate the... | 1 | int lg3ff_init(struct hid_device *hid)
{
struct hid_input *hidinput = list_entry(hid->inputs.next, struct hid_input, list);
struct input_dev *dev = hidinput->input;
const signed short *ff_bits = ff3_joystick_ac;
int error;
int i;
/* Check that the report looks ok */
if (!hid_validate_values(hid, HID_OUTPUT_REPO... | 56,757,149,974,640,710,000,000,000,000,000,000,000 | hid-lg3ff.c | 286,022,525,359,462,170,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19532 | In the Linux kernel before 5.3.9, there are multiple out-of-bounds write bugs that can be caused by a malicious USB device in the Linux kernel HID drivers, aka CID-d9d4b1e46d95. This affects drivers/hid/hid-axff.c, drivers/hid/hid-dr.c, drivers/hid/hid-emsff.c, drivers/hid/hid-gaff.c, drivers/hid/hid-holtekff.c, driver... | https://nvd.nist.gov/vuln/detail/CVE-2019-19532 |
399,309 | linux | d9d4b1e46d9543a82c23f6df03f4ad697dab361b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d9d4b1e46d9543a82c23f6df03f4ad697dab361b | HID: Fix assumption that devices have inputs
The syzbot fuzzer found a slab-out-of-bounds write bug in the hid-gaff
driver. The problem is caused by the driver's assumption that the
device must have an input report. While this will be true for all
normal HID input devices, a suitably malicious device can violate the... | 0 | int lg3ff_init(struct hid_device *hid)
{
struct hid_input *hidinput;
struct input_dev *dev;
const signed short *ff_bits = ff3_joystick_ac;
int error;
int i;
if (list_empty(&hid->inputs)) {
hid_err(hid, "no inputs found\n");
return -ENODEV;
}
hidinput = list_entry(hid->inputs.next, struct hid_input, list);
... | 328,147,073,201,196,300,000,000,000,000,000,000,000 | hid-lg3ff.c | 130,321,361,288,882,140,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19532 | In the Linux kernel before 5.3.9, there are multiple out-of-bounds write bugs that can be caused by a malicious USB device in the Linux kernel HID drivers, aka CID-d9d4b1e46d95. This affects drivers/hid/hid-axff.c, drivers/hid/hid-dr.c, drivers/hid/hid-emsff.c, drivers/hid/hid-gaff.c, drivers/hid/hid-holtekff.c, driver... | https://nvd.nist.gov/vuln/detail/CVE-2019-19532 |
207,587 | linux | d9d4b1e46d9543a82c23f6df03f4ad697dab361b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d9d4b1e46d9543a82c23f6df03f4ad697dab361b | HID: Fix assumption that devices have inputs
The syzbot fuzzer found a slab-out-of-bounds write bug in the hid-gaff
driver. The problem is caused by the driver's assumption that the
device must have an input report. While this will be true for all
normal HID input devices, a suitably malicious device can violate the... | 1 | static int holtekff_init(struct hid_device *hid)
{
struct holtekff_device *holtekff;
struct hid_report *report;
struct hid_input *hidinput = list_entry(hid->inputs.next,
struct hid_input, list);
struct list_head *report_list =
&hid->report_enum[HID_OUTPUT_REPORT].report_list;
struct input_dev *dev = hidin... | 334,014,214,691,276,280,000,000,000,000,000,000,000 | hid-holtekff.c | 27,232,399,215,557,054,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19532 | In the Linux kernel before 5.3.9, there are multiple out-of-bounds write bugs that can be caused by a malicious USB device in the Linux kernel HID drivers, aka CID-d9d4b1e46d95. This affects drivers/hid/hid-axff.c, drivers/hid/hid-dr.c, drivers/hid/hid-emsff.c, drivers/hid/hid-gaff.c, drivers/hid/hid-holtekff.c, driver... | https://nvd.nist.gov/vuln/detail/CVE-2019-19532 |
399,414 | linux | d9d4b1e46d9543a82c23f6df03f4ad697dab361b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d9d4b1e46d9543a82c23f6df03f4ad697dab361b | HID: Fix assumption that devices have inputs
The syzbot fuzzer found a slab-out-of-bounds write bug in the hid-gaff
driver. The problem is caused by the driver's assumption that the
device must have an input report. While this will be true for all
normal HID input devices, a suitably malicious device can violate the... | 0 | static int holtekff_init(struct hid_device *hid)
{
struct holtekff_device *holtekff;
struct hid_report *report;
struct hid_input *hidinput;
struct list_head *report_list =
&hid->report_enum[HID_OUTPUT_REPORT].report_list;
struct input_dev *dev;
int error;
if (list_empty(&hid->inputs)) {
hid_err(hid, "no in... | 79,019,772,351,152,120,000,000,000,000,000,000,000 | hid-holtekff.c | 144,088,745,282,285,760,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19532 | In the Linux kernel before 5.3.9, there are multiple out-of-bounds write bugs that can be caused by a malicious USB device in the Linux kernel HID drivers, aka CID-d9d4b1e46d95. This affects drivers/hid/hid-axff.c, drivers/hid/hid-dr.c, drivers/hid/hid-emsff.c, drivers/hid/hid-gaff.c, drivers/hid/hid-holtekff.c, driver... | https://nvd.nist.gov/vuln/detail/CVE-2019-19532 |
207,589 | linux | d9d4b1e46d9543a82c23f6df03f4ad697dab361b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d9d4b1e46d9543a82c23f6df03f4ad697dab361b | HID: Fix assumption that devices have inputs
The syzbot fuzzer found a slab-out-of-bounds write bug in the hid-gaff
driver. The problem is caused by the driver's assumption that the
device must have an input report. While this will be true for all
normal HID input devices, a suitably malicious device can violate the... | 1 | int lg4ff_init(struct hid_device *hid)
{
struct hid_input *hidinput = list_entry(hid->inputs.next, struct hid_input, list);
struct input_dev *dev = hidinput->input;
struct list_head *report_list = &hid->report_enum[HID_OUTPUT_REPORT].report_list;
struct hid_report *report = list_entry(report_list->next, struct hid_... | 144,511,023,275,817,820,000,000,000,000,000,000,000 | hid-lg4ff.c | 316,630,082,451,873,340,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19532 | In the Linux kernel before 5.3.9, there are multiple out-of-bounds write bugs that can be caused by a malicious USB device in the Linux kernel HID drivers, aka CID-d9d4b1e46d95. This affects drivers/hid/hid-axff.c, drivers/hid/hid-dr.c, drivers/hid/hid-emsff.c, drivers/hid/hid-gaff.c, drivers/hid/hid-holtekff.c, driver... | https://nvd.nist.gov/vuln/detail/CVE-2019-19532 |
399,344 | linux | d9d4b1e46d9543a82c23f6df03f4ad697dab361b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d9d4b1e46d9543a82c23f6df03f4ad697dab361b | HID: Fix assumption that devices have inputs
The syzbot fuzzer found a slab-out-of-bounds write bug in the hid-gaff
driver. The problem is caused by the driver's assumption that the
device must have an input report. While this will be true for all
normal HID input devices, a suitably malicious device can violate the... | 0 | int lg4ff_init(struct hid_device *hid)
{
struct hid_input *hidinput;
struct input_dev *dev;
struct list_head *report_list = &hid->report_enum[HID_OUTPUT_REPORT].report_list;
struct hid_report *report = list_entry(report_list->next, struct hid_report, list);
const struct usb_device_descriptor *udesc = &(hid_to_usb_... | 103,237,355,638,860,160,000,000,000,000,000,000,000 | hid-lg4ff.c | 302,742,441,294,388,480,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19532 | In the Linux kernel before 5.3.9, there are multiple out-of-bounds write bugs that can be caused by a malicious USB device in the Linux kernel HID drivers, aka CID-d9d4b1e46d95. This affects drivers/hid/hid-axff.c, drivers/hid/hid-dr.c, drivers/hid/hid-emsff.c, drivers/hid/hid-gaff.c, drivers/hid/hid-holtekff.c, driver... | https://nvd.nist.gov/vuln/detail/CVE-2019-19532 |
207,590 | linux | d9d4b1e46d9543a82c23f6df03f4ad697dab361b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d9d4b1e46d9543a82c23f6df03f4ad697dab361b | HID: Fix assumption that devices have inputs
The syzbot fuzzer found a slab-out-of-bounds write bug in the hid-gaff
driver. The problem is caused by the driver's assumption that the
device must have an input report. While this will be true for all
normal HID input devices, a suitably malicious device can violate the... | 1 | static int hidpp_ff_init(struct hidpp_device *hidpp, u8 feature_index)
{
struct hid_device *hid = hidpp->hid_dev;
struct hid_input *hidinput = list_entry(hid->inputs.next, struct hid_input, list);
struct input_dev *dev = hidinput->input;
const struct usb_device_descriptor *udesc = &(hid_to_usb_dev(hid)->descriptor)... | 218,471,184,461,478,340,000,000,000,000,000,000,000 | hid-logitech-hidpp.c | 234,033,672,118,896,200,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19532 | In the Linux kernel before 5.3.9, there are multiple out-of-bounds write bugs that can be caused by a malicious USB device in the Linux kernel HID drivers, aka CID-d9d4b1e46d95. This affects drivers/hid/hid-axff.c, drivers/hid/hid-dr.c, drivers/hid/hid-emsff.c, drivers/hid/hid-gaff.c, drivers/hid/hid-holtekff.c, driver... | https://nvd.nist.gov/vuln/detail/CVE-2019-19532 |
399,488 | linux | d9d4b1e46d9543a82c23f6df03f4ad697dab361b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d9d4b1e46d9543a82c23f6df03f4ad697dab361b | HID: Fix assumption that devices have inputs
The syzbot fuzzer found a slab-out-of-bounds write bug in the hid-gaff
driver. The problem is caused by the driver's assumption that the
device must have an input report. While this will be true for all
normal HID input devices, a suitably malicious device can violate the... | 0 | static int hidpp_ff_init(struct hidpp_device *hidpp, u8 feature_index)
{
struct hid_device *hid = hidpp->hid_dev;
struct hid_input *hidinput;
struct input_dev *dev;
const struct usb_device_descriptor *udesc = &(hid_to_usb_dev(hid)->descriptor);
const u16 bcdDevice = le16_to_cpu(udesc->bcdDevice);
struct ff_device... | 107,380,242,006,465,720,000,000,000,000,000,000,000 | hid-logitech-hidpp.c | 107,491,686,593,534,200,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19532 | In the Linux kernel before 5.3.9, there are multiple out-of-bounds write bugs that can be caused by a malicious USB device in the Linux kernel HID drivers, aka CID-d9d4b1e46d95. This affects drivers/hid/hid-axff.c, drivers/hid/hid-dr.c, drivers/hid/hid-emsff.c, drivers/hid/hid-gaff.c, drivers/hid/hid-holtekff.c, driver... | https://nvd.nist.gov/vuln/detail/CVE-2019-19532 |
207,591 | linux | d9d4b1e46d9543a82c23f6df03f4ad697dab361b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d9d4b1e46d9543a82c23f6df03f4ad697dab361b | HID: Fix assumption that devices have inputs
The syzbot fuzzer found a slab-out-of-bounds write bug in the hid-gaff
driver. The problem is caused by the driver's assumption that the
device must have an input report. While this will be true for all
normal HID input devices, a suitably malicious device can violate the... | 1 | static int drff_init(struct hid_device *hid)
{
struct drff_device *drff;
struct hid_report *report;
struct hid_input *hidinput = list_first_entry(&hid->inputs,
struct hid_input, list);
struct list_head *report_list =
&hid->report_enum[HID_OUTPUT_REPORT].report_list;
struct input_dev *dev = hidinput->input... | 29,923,220,476,920,820,000,000,000,000,000,000,000 | hid-dr.c | 244,930,620,405,201,250,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19532 | In the Linux kernel before 5.3.9, there are multiple out-of-bounds write bugs that can be caused by a malicious USB device in the Linux kernel HID drivers, aka CID-d9d4b1e46d95. This affects drivers/hid/hid-axff.c, drivers/hid/hid-dr.c, drivers/hid/hid-emsff.c, drivers/hid/hid-gaff.c, drivers/hid/hid-holtekff.c, driver... | https://nvd.nist.gov/vuln/detail/CVE-2019-19532 |
399,422 | linux | d9d4b1e46d9543a82c23f6df03f4ad697dab361b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d9d4b1e46d9543a82c23f6df03f4ad697dab361b | HID: Fix assumption that devices have inputs
The syzbot fuzzer found a slab-out-of-bounds write bug in the hid-gaff
driver. The problem is caused by the driver's assumption that the
device must have an input report. While this will be true for all
normal HID input devices, a suitably malicious device can violate the... | 0 | static int drff_init(struct hid_device *hid)
{
struct drff_device *drff;
struct hid_report *report;
struct hid_input *hidinput;
struct list_head *report_list =
&hid->report_enum[HID_OUTPUT_REPORT].report_list;
struct input_dev *dev;
int error;
if (list_empty(&hid->inputs)) {
hid_err(hid, "no inputs found\n... | 117,292,566,406,339,780,000,000,000,000,000,000,000 | hid-dr.c | 204,241,937,043,156,450,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19532 | In the Linux kernel before 5.3.9, there are multiple out-of-bounds write bugs that can be caused by a malicious USB device in the Linux kernel HID drivers, aka CID-d9d4b1e46d95. This affects drivers/hid/hid-axff.c, drivers/hid/hid-dr.c, drivers/hid/hid-emsff.c, drivers/hid/hid-gaff.c, drivers/hid/hid-holtekff.c, driver... | https://nvd.nist.gov/vuln/detail/CVE-2019-19532 |
207,592 | linux | d9d4b1e46d9543a82c23f6df03f4ad697dab361b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d9d4b1e46d9543a82c23f6df03f4ad697dab361b | HID: Fix assumption that devices have inputs
The syzbot fuzzer found a slab-out-of-bounds write bug in the hid-gaff
driver. The problem is caused by the driver's assumption that the
device must have an input report. While this will be true for all
normal HID input devices, a suitably malicious device can violate the... | 1 | static int ms_init_ff(struct hid_device *hdev)
{
struct hid_input *hidinput = list_entry(hdev->inputs.next,
struct hid_input, list);
struct input_dev *input_dev = hidinput->input;
struct ms_data *ms = hid_get_drvdata(hdev);
if (!(ms->quirks & MS_QUIRK_FF))
return 0;
ms->hdev = hdev;
INIT_WORK(&ms->ff_wo... | 256,481,378,644,169,720,000,000,000,000,000,000,000 | hid-microsoft.c | 120,379,590,833,699,010,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19532 | In the Linux kernel before 5.3.9, there are multiple out-of-bounds write bugs that can be caused by a malicious USB device in the Linux kernel HID drivers, aka CID-d9d4b1e46d95. This affects drivers/hid/hid-axff.c, drivers/hid/hid-dr.c, drivers/hid/hid-emsff.c, drivers/hid/hid-gaff.c, drivers/hid/hid-holtekff.c, driver... | https://nvd.nist.gov/vuln/detail/CVE-2019-19532 |
399,436 | linux | d9d4b1e46d9543a82c23f6df03f4ad697dab361b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d9d4b1e46d9543a82c23f6df03f4ad697dab361b | HID: Fix assumption that devices have inputs
The syzbot fuzzer found a slab-out-of-bounds write bug in the hid-gaff
driver. The problem is caused by the driver's assumption that the
device must have an input report. While this will be true for all
normal HID input devices, a suitably malicious device can violate the... | 0 | static int ms_init_ff(struct hid_device *hdev)
{
struct hid_input *hidinput;
struct input_dev *input_dev;
struct ms_data *ms = hid_get_drvdata(hdev);
if (list_empty(&hdev->inputs)) {
hid_err(hdev, "no inputs found\n");
return -ENODEV;
}
hidinput = list_entry(hdev->inputs.next, struct hid_input, list);
input... | 283,589,273,396,179,100,000,000,000,000,000,000,000 | hid-microsoft.c | 137,046,196,239,256,340,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19532 | In the Linux kernel before 5.3.9, there are multiple out-of-bounds write bugs that can be caused by a malicious USB device in the Linux kernel HID drivers, aka CID-d9d4b1e46d95. This affects drivers/hid/hid-axff.c, drivers/hid/hid-dr.c, drivers/hid/hid-emsff.c, drivers/hid/hid-gaff.c, drivers/hid/hid-holtekff.c, driver... | https://nvd.nist.gov/vuln/detail/CVE-2019-19532 |
207,600 | ImageMagick | a43f4155ee916fbed080acd534232a9d2396b5b5 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/a43f4155ee916fbed080acd534232a9d2396b5b5 | https://github.com/ImageMagick/ImageMagick/issues/734 | 1 | static Image *ReadMATImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
Image *image, *image2=NULL,
*rotated_image;
register Quantum *q;
unsigned int status;
MATHeader MATLAB_HDR;
size_t size;
size_t CellType;
QuantumInfo *quantum_info;
ImageInfo *clone_info;
int i;
ssize_t ldblk;
u... | 27,603,532,203,589,786,000,000,000,000,000,000,000 | mat.c | 62,045,924,116,333,540,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-18027 | In ImageMagick 7.0.7-1 Q16, a memory leak vulnerability was found in the function ReadMATImage in coders/mat.c, which allow remote attackers to cause a denial of service via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2017-18027 |
399,575 | ImageMagick | a43f4155ee916fbed080acd534232a9d2396b5b5 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/a43f4155ee916fbed080acd534232a9d2396b5b5 | https://github.com/ImageMagick/ImageMagick/issues/734 | 0 | static Image *ReadMATImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
Image *image, *image2=NULL,
*rotated_image;
register Quantum *q;
unsigned int status;
MATHeader MATLAB_HDR;
size_t size;
size_t CellType;
QuantumInfo *quantum_info;
ImageInfo *clone_info;
int i;
ssize_t ldblk;
u... | 188,133,617,004,526,920,000,000,000,000,000,000,000 | mat.c | 197,169,146,420,426,430,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-18027 | In ImageMagick 7.0.7-1 Q16, a memory leak vulnerability was found in the function ReadMATImage in coders/mat.c, which allow remote attackers to cause a denial of service via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2017-18027 |
207,613 | edk2 | 0a0d5296e448fc350de1594c49b9c0deff7fad60 | https://github.com/tianocore/edk2 | https://github.com/tianocore/edk2/commit/0a0d5296e448fc350de1594c49b9c0deff7fad60 | UefiCpuPkg/CpuMpPei: support stack guard feature
This feature is the same as Stack Guard enabled in driver CpuDxe but
applies to PEI phase. Due to the specialty in PEI module dispatching,
this driver is changed to do the actual initialization in notify
callback of event gEfiPeiMemoryDiscoveredPpiGuid. This can let the... | 1 | CpuMpPeimInit (
IN EFI_PEI_FILE_HANDLE FileHandle,
IN CONST EFI_PEI_SERVICES **PeiServices
)
{
EFI_STATUS Status;
EFI_VECTOR_HANDOFF_INFO *VectorInfo;
EFI_PEI_VECTOR_HANDOFF_INFO_PPI *VectorHandoffInfoPpi;
//
// Get Vector Hand-off Info PPI
//
VectorInfo = N... | 234,956,247,865,001,760,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2018-12183 | Stack overflow in DxeCore for EDK II may allow an unauthenticated user to potentially enable escalation of privilege, information disclosure and/or denial of service via local access. | https://nvd.nist.gov/vuln/detail/CVE-2018-12183 |
399,619 | edk2 | 0a0d5296e448fc350de1594c49b9c0deff7fad60 | https://github.com/tianocore/edk2 | https://github.com/tianocore/edk2/commit/0a0d5296e448fc350de1594c49b9c0deff7fad60 | UefiCpuPkg/CpuMpPei: support stack guard feature
This feature is the same as Stack Guard enabled in driver CpuDxe but
applies to PEI phase. Due to the specialty in PEI module dispatching,
this driver is changed to do the actual initialization in notify
callback of event gEfiPeiMemoryDiscoveredPpiGuid. This can let the... | 0 | InitializeCpuMpWorker (
IN CONST EFI_PEI_SERVICES **PeiServices
)
{
EFI_STATUS Status;
EFI_VECTOR_HANDOFF_INFO *VectorInfo;
EFI_PEI_VECTOR_HANDOFF_INFO_PPI *VectorHandoffInfoPpi;
//
// Get Vector Hand-off Info PPI
//
VectorInfo = NULL;
Status = PeiServic... | 244,809,831,469,028,300,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2018-12183 | Stack overflow in DxeCore for EDK II may allow an unauthenticated user to potentially enable escalation of privilege, information disclosure and/or denial of service via local access. | https://nvd.nist.gov/vuln/detail/CVE-2018-12183 |
207,643 | librelp | 2cfe657672636aa5d7d2a14cfcb0a6ab9d1f00cf | https://github.com/rsyslog/librelp | https://github.com/rsyslog/librelp/commit/2cfe657672636aa5d7d2a14cfcb0a6ab9d1f00cf | unify error message generation | 1 | relpTcpChkPeerName(relpTcp_t *pThis, gnutls_x509_crt_t cert)
{
int r = 0;
int ret;
unsigned int status = 0;
char cnBuf[1024]; /* this is sufficient for the DNSNAME... */
char szAltName[1024]; /* this is sufficient for the DNSNAME... */
int iAltName;
char allNames[32*1024]; /* for error-reporting */
int iAllName... | 29,880,058,410,718,510,000,000,000,000,000,000,000 | tcp.c | 123,818,154,568,750,180,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2018-1000140 | rsyslog librelp version 1.2.14 and earlier contains a Buffer Overflow vulnerability in the checking of x509 certificates from a peer that can result in Remote code execution. This attack appear to be exploitable a remote attacker that can connect to rsyslog and trigger a stack buffer overflow by sending a specially cra... | https://nvd.nist.gov/vuln/detail/CVE-2018-1000140 |
399,875 | librelp | 2cfe657672636aa5d7d2a14cfcb0a6ab9d1f00cf | https://github.com/rsyslog/librelp | https://github.com/rsyslog/librelp/commit/2cfe657672636aa5d7d2a14cfcb0a6ab9d1f00cf | unify error message generation | 0 | relpTcpChkPeerName(relpTcp_t *const pThis, gnutls_x509_crt_t cert)
{
int r = 0;
int ret;
unsigned int status = 0;
char cnBuf[1024]; /* this is sufficient for the DNSNAME... */
char szAltName[1024]; /* this is sufficient for the DNSNAME... */
int iAltName;
char allNames[32*1024]; /* for error-reporting */
int iA... | 38,024,531,534,400,620,000,000,000,000,000,000,000 | tcp.c | 12,048,072,939,494,670,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2018-1000140 | rsyslog librelp version 1.2.14 and earlier contains a Buffer Overflow vulnerability in the checking of x509 certificates from a peer that can result in Remote code execution. This attack appear to be exploitable a remote attacker that can connect to rsyslog and trigger a stack buffer overflow by sending a specially cra... | https://nvd.nist.gov/vuln/detail/CVE-2018-1000140 |
207,647 | linux | b70261a288ea4d2f4ac7cd04be08a9f0f2de4f4d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b70261a288ea4d2f4ac7cd04be08a9f0f2de4f4d | mwifiex: Fix possible buffer overflows in mwifiex_cmd_append_vsie_tlv()
mwifiex_cmd_append_vsie_tlv() calls memcpy() without checking
the destination size may trigger a buffer overflower,
which a local user could use to cause denial of service
or the execution of arbitrary code.
Fix it by putting the length check befo... | 1 | mwifiex_cmd_append_vsie_tlv(struct mwifiex_private *priv,
u16 vsie_mask, u8 **buffer)
{
int id, ret_len = 0;
struct mwifiex_ie_types_vendor_param_set *vs_param_set;
if (!buffer)
return 0;
if (!(*buffer))
return 0;
/*
* Traverse through the saved vendor specific IE array and append
* the selected(s... | 258,738,038,729,954,700,000,000,000,000,000,000,000 | scan.c | 280,502,893,863,673,220,000,000,000,000,000,000,000 | [
"CWE-269"
] | CVE-2020-12653 | An issue was found in Linux kernel before 5.5.4. The mwifiex_cmd_append_vsie_tlv() function in drivers/net/wireless/marvell/mwifiex/scan.c allows local users to gain privileges or cause a denial of service because of an incorrect memcpy and buffer overflow, aka CID-b70261a288ea. | https://nvd.nist.gov/vuln/detail/CVE-2020-12653 |
400,004 | linux | b70261a288ea4d2f4ac7cd04be08a9f0f2de4f4d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b70261a288ea4d2f4ac7cd04be08a9f0f2de4f4d | mwifiex: Fix possible buffer overflows in mwifiex_cmd_append_vsie_tlv()
mwifiex_cmd_append_vsie_tlv() calls memcpy() without checking
the destination size may trigger a buffer overflower,
which a local user could use to cause denial of service
or the execution of arbitrary code.
Fix it by putting the length check befo... | 0 | mwifiex_cmd_append_vsie_tlv(struct mwifiex_private *priv,
u16 vsie_mask, u8 **buffer)
{
int id, ret_len = 0;
struct mwifiex_ie_types_vendor_param_set *vs_param_set;
if (!buffer)
return 0;
if (!(*buffer))
return 0;
/*
* Traverse through the saved vendor specific IE array and append
* the selected(s... | 287,985,293,427,958,540,000,000,000,000,000,000,000 | scan.c | 335,510,247,056,150,720,000,000,000,000,000,000,000 | [
"CWE-269"
] | CVE-2020-12653 | An issue was found in Linux kernel before 5.5.4. The mwifiex_cmd_append_vsie_tlv() function in drivers/net/wireless/marvell/mwifiex/scan.c allows local users to gain privileges or cause a denial of service because of an incorrect memcpy and buffer overflow, aka CID-b70261a288ea. | https://nvd.nist.gov/vuln/detail/CVE-2020-12653 |
207,658 | libgd | a11f47475e6443b7f32d21f2271f28f417e2ac04 | https://github.com/libgd/libgd | https://github.com/libgd/libgd/commit/a11f47475e6443b7f32d21f2271f28f417e2ac04 | Fix #420: Potential infinite loop in gdImageCreateFromGifCtx
Due to a signedness confusion in `GetCode_` a corrupt GIF file can
trigger an infinite loop. Furthermore we make sure that a GIF without
any palette entries is treated as invalid *after* open palette entries
have been removed.
CVE-2018-5711
See also https... | 1 | GetCode_(gdIOCtx *fd, CODE_STATIC_DATA *scd, int code_size, int flag, int *ZeroDataBlockP)
{
int i, j, ret;
unsigned char count;
if(flag) {
scd->curbit = 0;
scd->lastbit = 0;
scd->last_byte = 2;
scd->done = FALSE;
return 0;
}
if((scd->curbit + code_size) >= scd->lastbit) {
if(scd->done) {
if(scd->... | 170,050,722,703,016,080,000,000,000,000,000,000,000 | None | null | [
"CWE-681"
] | CVE-2018-5711 | gd_gif_in.c in the GD Graphics Library (aka libgd), as used in PHP before 5.6.33, 7.0.x before 7.0.27, 7.1.x before 7.1.13, and 7.2.x before 7.2.1, has an integer signedness error that leads to an infinite loop via a crafted GIF file, as demonstrated by a call to the imagecreatefromgif or imagecreatefromstring PHP func... | https://nvd.nist.gov/vuln/detail/CVE-2018-5711 |
400,048 | libgd | a11f47475e6443b7f32d21f2271f28f417e2ac04 | https://github.com/libgd/libgd | https://github.com/libgd/libgd/commit/a11f47475e6443b7f32d21f2271f28f417e2ac04 | Fix #420: Potential infinite loop in gdImageCreateFromGifCtx
Due to a signedness confusion in `GetCode_` a corrupt GIF file can
trigger an infinite loop. Furthermore we make sure that a GIF without
any palette entries is treated as invalid *after* open palette entries
have been removed.
CVE-2018-5711
See also https... | 0 | GetCode_(gdIOCtx *fd, CODE_STATIC_DATA *scd, int code_size, int flag, int *ZeroDataBlockP)
{
int i, j, ret;
int count;
if(flag) {
scd->curbit = 0;
scd->lastbit = 0;
scd->last_byte = 2;
scd->done = FALSE;
return 0;
}
if((scd->curbit + code_size) >= scd->lastbit) {
if(scd->done) {
if(scd->curbit >= ... | 62,899,465,460,439,610,000,000,000,000,000,000,000 | None | null | [
"CWE-681"
] | CVE-2018-5711 | gd_gif_in.c in the GD Graphics Library (aka libgd), as used in PHP before 5.6.33, 7.0.x before 7.0.27, 7.1.x before 7.1.13, and 7.2.x before 7.2.1, has an integer signedness error that leads to an infinite loop via a crafted GIF file, as demonstrated by a call to the imagecreatefromgif or imagecreatefromstring PHP func... | https://nvd.nist.gov/vuln/detail/CVE-2018-5711 |
207,659 | libgd | a11f47475e6443b7f32d21f2271f28f417e2ac04 | https://github.com/libgd/libgd | https://github.com/libgd/libgd/commit/a11f47475e6443b7f32d21f2271f28f417e2ac04 | Fix #420: Potential infinite loop in gdImageCreateFromGifCtx
Due to a signedness confusion in `GetCode_` a corrupt GIF file can
trigger an infinite loop. Furthermore we make sure that a GIF without
any palette entries is treated as invalid *after* open palette entries
have been removed.
CVE-2018-5711
See also https... | 1 | BGD_DECLARE(gdImagePtr) gdImageCreateFromGifCtx(gdIOCtxPtr fd)
{
int BitPixel;
#if 0
int ColorResolution;
int Background;
int AspectRatio;
#endif
int Transparent = (-1);
unsigned char buf[16];
unsigned char c;
unsigned char ColorMap[3][MAXCOLORMAPSIZE];
unsigned char localColorMap[3][MAXCOLORMAPSIZE];
int imw... | 144,722,163,819,824,800,000,000,000,000,000,000,000 | None | null | [
"CWE-681"
] | CVE-2018-5711 | gd_gif_in.c in the GD Graphics Library (aka libgd), as used in PHP before 5.6.33, 7.0.x before 7.0.27, 7.1.x before 7.1.13, and 7.2.x before 7.2.1, has an integer signedness error that leads to an infinite loop via a crafted GIF file, as demonstrated by a call to the imagecreatefromgif or imagecreatefromstring PHP func... | https://nvd.nist.gov/vuln/detail/CVE-2018-5711 |
400,047 | libgd | a11f47475e6443b7f32d21f2271f28f417e2ac04 | https://github.com/libgd/libgd | https://github.com/libgd/libgd/commit/a11f47475e6443b7f32d21f2271f28f417e2ac04 | Fix #420: Potential infinite loop in gdImageCreateFromGifCtx
Due to a signedness confusion in `GetCode_` a corrupt GIF file can
trigger an infinite loop. Furthermore we make sure that a GIF without
any palette entries is treated as invalid *after* open palette entries
have been removed.
CVE-2018-5711
See also https... | 0 | BGD_DECLARE(gdImagePtr) gdImageCreateFromGifCtx(gdIOCtxPtr fd)
{
int BitPixel;
#if 0
int ColorResolution;
int Background;
int AspectRatio;
#endif
int Transparent = (-1);
unsigned char buf[16];
unsigned char c;
unsigned char ColorMap[3][MAXCOLORMAPSIZE];
unsigned char localColorMap[3][MAXCOLORMAPSIZE];
int imw... | 178,565,262,351,282,560,000,000,000,000,000,000,000 | None | null | [
"CWE-681"
] | CVE-2018-5711 | gd_gif_in.c in the GD Graphics Library (aka libgd), as used in PHP before 5.6.33, 7.0.x before 7.0.27, 7.1.x before 7.1.13, and 7.2.x before 7.2.1, has an integer signedness error that leads to an infinite loop via a crafted GIF file, as demonstrated by a call to the imagecreatefromgif or imagecreatefromstring PHP func... | https://nvd.nist.gov/vuln/detail/CVE-2018-5711 |
207,712 | wesnoth | f8914468182e8d0a1551b430c0879ba236fe4d6d | https://github.com/wesnoth/wesnoth | https://github.com/wesnoth/wesnoth/commit/f8914468182e8d0a1551b430c0879ba236fe4d6d | Disallow inclusion of .pbl files from WML (bug #23504)
Note that this will also cause Lua wesnoth.have_file() to return false
on .pbl files. | 1 | std::string get_wml_location(const std::string &filename, const std::string ¤t_dir)
{
DBG_FS << "Looking for '" << filename << "'." << std::endl;
assert(game_config::path.empty() == false);
std::string result;
if (filename.empty()) {
LOG_FS << " invalid filename" << std::endl;
return result;
}
if (... | 303,902,118,008,031,580,000,000,000,000,000,000,000 | filesystem.cpp | 237,082,187,925,084,670,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2015-5069 | The (1) filesystem::get_wml_location function in filesystem.cpp and (2) is_legal_file function in filesystem_boost.cpp in Battle for Wesnoth before 1.12.3 and 1.13.x before 1.13.1 allow remote attackers to obtain sensitive information via vectors related to inclusion of .pbl files from WML. | https://nvd.nist.gov/vuln/detail/CVE-2015-5069 |
400,273 | wesnoth | f8914468182e8d0a1551b430c0879ba236fe4d6d | https://github.com/wesnoth/wesnoth | https://github.com/wesnoth/wesnoth/commit/f8914468182e8d0a1551b430c0879ba236fe4d6d | Disallow inclusion of .pbl files from WML (bug #23504)
Note that this will also cause Lua wesnoth.have_file() to return false
on .pbl files. | 0 | std::string get_wml_location(const std::string &filename, const std::string ¤t_dir)
{
if (!is_legal_file(filename))
return std::string();
assert(game_config::path.empty() == false);
path fpath(filename);
path result;
if (filename[0] == '~')
{
result /= get_user_data_path() / "data" / filename.substr(... | 153,240,259,124,864,750,000,000,000,000,000,000,000 | filesystem_boost.cpp | 243,215,982,753,431,320,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2015-5069 | The (1) filesystem::get_wml_location function in filesystem.cpp and (2) is_legal_file function in filesystem_boost.cpp in Battle for Wesnoth before 1.12.3 and 1.13.x before 1.13.1 allow remote attackers to obtain sensitive information via vectors related to inclusion of .pbl files from WML. | https://nvd.nist.gov/vuln/detail/CVE-2015-5069 |
207,716 | libidn2 | e4d1558aa2c1c04a05066ee8600f37603890ba8c | https://github.com/libidn/libidn2 | https://github.com/libidn/libidn2/commit/e4d1558aa2c1c04a05066ee8600f37603890ba8c | idn2_to_ascii_4i(): Restrict output length to 63 | 1 | idn2_to_ascii_4i (const uint32_t * input, size_t inlen, char * output, int flags)
{
uint32_t *input_u32;
uint8_t *input_u8, *output_u8;
size_t length;
int rc;
if (!input)
{
if (output)
*output = 0;
return IDN2_OK;
}
input_u32 = (uint32_t *) malloc ((inlen + 1) * sizeof(uint32_t));
i... | 31,348,825,004,437,350,000,000,000,000,000,000,000 | lookup.c | 58,919,034,669,622,170,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-18224 | idn2_to_ascii_4i in lib/lookup.c in GNU libidn2 before 2.1.1 has a heap-based buffer overflow via a long domain string. | https://nvd.nist.gov/vuln/detail/CVE-2019-18224 |
400,402 | libidn2 | e4d1558aa2c1c04a05066ee8600f37603890ba8c | https://github.com/libidn/libidn2 | https://github.com/libidn/libidn2/commit/e4d1558aa2c1c04a05066ee8600f37603890ba8c | idn2_to_ascii_4i(): Restrict output length to 63 | 0 | idn2_to_ascii_4i (const uint32_t * input, size_t inlen, char * output, int flags)
{
uint32_t *input_u32;
uint8_t *input_u8, *output_u8;
size_t length;
int rc;
if (!input)
{
if (output)
*output = 0;
return IDN2_OK;
}
input_u32 = (uint32_t *) malloc ((inlen + 1) * sizeof(uint32_t));
i... | 273,460,630,927,448,050,000,000,000,000,000,000,000 | lookup.c | 115,678,796,179,300,860,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-18224 | idn2_to_ascii_4i in lib/lookup.c in GNU libidn2 before 2.1.1 has a heap-based buffer overflow via a long domain string. | https://nvd.nist.gov/vuln/detail/CVE-2019-18224 |
207,740 | htcondor | e891cea9970496aac74caf72604475a2b7e6a0ca | https://github.com/htcondor/htcondor | https://github.com/htcondor/htcondor/commit/e891cea9970496aac74caf72604475a2b7e6a0ca.patch | Update command line flags for modern /bin/mail and add option to use sendmail. #4764 | 1 | email_open( const char *email_addr, const char *subject )
{
char *Mailer;
char *SmtpServer = NULL;
char *FromAddress = NULL;
char *FinalSubject;
char *FinalAddr;
char *temp;
int token_boundary;
int num_addresses;
int arg_index;
FILE *mailerstream;
if ( (Mailer = param("MAIL")) == NULL ) {
dprintf(D_FULLDE... | 209,653,000,592,802,060,000,000,000,000,000,000,000 | email.cpp | 272,112,316,938,561,870,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-8126 | The scheduler in HTCondor before 8.2.6 allows remote authenticated users to execute arbitrary code. | https://nvd.nist.gov/vuln/detail/CVE-2014-8126 |
400,646 | htcondor | e891cea9970496aac74caf72604475a2b7e6a0ca | https://github.com/htcondor/htcondor | https://github.com/htcondor/htcondor/commit/e891cea9970496aac74caf72604475a2b7e6a0ca.patch | Update command line flags for modern /bin/mail and add option to use sendmail. #4764 | 0 | email_open( const char *email_addr, const char *subject )
{
char *Sendmail = NULL;
char *Mailer = NULL;
char *SmtpServer = NULL;
char *FromAddress = NULL;
char *FinalSubject;
char *FinalAddr;
char *temp;
int token_boundary;
int num_addresses;
int arg_index;
FILE *mailerstream;
/* Take care of the subject. ... | 128,176,247,313,319,200,000,000,000,000,000,000,000 | email.cpp | 222,262,044,978,444,540,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-8126 | The scheduler in HTCondor before 8.2.6 allows remote authenticated users to execute arbitrary code. | https://nvd.nist.gov/vuln/detail/CVE-2014-8126 |
207,743 | exim | d740d2111f189760593a303124ff6b9b1f83453d | https://github.com/Exim/exim | https://git.exim.org/exim.git/commitdiff/d740d2111f189760593a303124ff6b9b1f83453d | Fix CVE-2019-10149 | 1 | deliver_message(uschar *id, BOOL forced, BOOL give_up)
{
int i, rc;
int final_yield = DELIVER_ATTEMPTED_NORMAL;
time_t now = time(NULL);
address_item *addr_last = NULL;
uschar *filter_message = NULL;
int process_recipients = RECIP_ACCEPT;
open_db dbblock;
open_db *dbm_file;
extern int acl_where;
uschar *info = queue_r... | 279,369,463,353,144,000,000,000,000,000,000,000,000 | deliver.c | 177,628,070,044,532,900,000,000,000,000,000,000,000 | [
"CWE-78"
] | CVE-2019-10149 | A flaw was found in Exim versions 4.87 to 4.91 (inclusive). Improper validation of recipient address in deliver_message() function in /src/deliver.c may lead to remote command execution. | https://nvd.nist.gov/vuln/detail/CVE-2019-10149 |
400,659 | exim | d740d2111f189760593a303124ff6b9b1f83453d | https://github.com/Exim/exim | https://git.exim.org/exim.git/commitdiff/d740d2111f189760593a303124ff6b9b1f83453d | Fix CVE-2019-10149 | 0 | deliver_message(uschar *id, BOOL forced, BOOL give_up)
{
int i, rc;
int final_yield = DELIVER_ATTEMPTED_NORMAL;
time_t now = time(NULL);
address_item *addr_last = NULL;
uschar *filter_message = NULL;
int process_recipients = RECIP_ACCEPT;
open_db dbblock;
open_db *dbm_file;
extern int acl_where;
uschar *info = queue_r... | 58,535,685,879,106,500,000,000,000,000,000,000,000 | deliver.c | 234,992,628,149,154,230,000,000,000,000,000,000,000 | [
"CWE-78"
] | CVE-2019-10149 | A flaw was found in Exim versions 4.87 to 4.91 (inclusive). Improper validation of recipient address in deliver_message() function in /src/deliver.c may lead to remote command execution. | https://nvd.nist.gov/vuln/detail/CVE-2019-10149 |
207,746 | gimp | 06d24a79af94837d615d0024916bb95a01bf3c59 | https://github.com/GNOME/gimp | https://git.gnome.org/browse/gimp/commit/?id=06d24a79af94837d615d0024916bb95a01bf3c59 | Bug 790784 - (CVE-2017-17784) heap overread in gbr parser / load_image.
We were assuming the input name was well formed, hence was
nul-terminated. As any data coming from external input, this has to be
thorougly checked. | 1 | load_image (GFile *file,
GError **error)
{
GInputStream *input;
gchar *name;
BrushHeader bh;
guchar *brush_buf = NULL;
gint32 image_ID;
gint32 layer_ID;
GimpParasite *parasite;
GeglBuffer *buffer;
const Babl *f... | 130,636,640,576,873,260,000,000,000,000,000,000,000 | file-gbr.c | 191,865,808,898,216,200,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-17784 | In GIMP 2.8.22, there is a heap-based buffer over-read in load_image in plug-ins/common/file-gbr.c in the gbr import parser, related to mishandling of UTF-8 data. | https://nvd.nist.gov/vuln/detail/CVE-2017-17784 |
400,665 | gimp | 06d24a79af94837d615d0024916bb95a01bf3c59 | https://github.com/GNOME/gimp | https://git.gnome.org/browse/gimp/commit/?id=06d24a79af94837d615d0024916bb95a01bf3c59 | Bug 790784 - (CVE-2017-17784) heap overread in gbr parser / load_image.
We were assuming the input name was well formed, hence was
nul-terminated. As any data coming from external input, this has to be
thorougly checked. | 0 | load_image (GFile *file,
GError **error)
{
GInputStream *input;
gchar *name;
BrushHeader bh;
guchar *brush_buf = NULL;
gint32 image_ID;
gint32 layer_ID;
GimpParasite *parasite;
GeglBuffer *buffer;
const Babl *f... | 260,220,864,507,317,660,000,000,000,000,000,000,000 | file-gbr.c | 245,408,119,930,978,700,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-17784 | In GIMP 2.8.22, there is a heap-based buffer over-read in load_image in plug-ins/common/file-gbr.c in the gbr import parser, related to mishandling of UTF-8 data. | https://nvd.nist.gov/vuln/detail/CVE-2017-17784 |
207,752 | qemu | dfba99f17feb6d4a129da19d38df1bcd8579d1c3 | https://github.com/bonzini/qemu | https://git.qemu.org/?p=qemu.git;a=commit;h=dfba99f17feb6d4a129da19d38df1bcd8579d1c3 | hw/sd/sdhci: Fix DMA Transfer Block Size field
The 'Transfer Block Size' field is 12-bit wide.
See section '2.2.2. Block Size Register (Offset 004h)' in datasheet.
Two different bug reproducer available:
- https://bugs.launchpad.net/qemu/+bug/1892960
- https://ruhr-uni-bochum.sciebo.de/s/NNWP2GfwzYKeKwE?path=%2Fsdhc... | 1 | sdhci_write(void *opaque, hwaddr offset, uint64_t val, unsigned size)
{
SDHCIState *s = (SDHCIState *)opaque;
unsigned shift = 8 * (offset & 0x3);
uint32_t mask = ~(((1ULL << (size * 8)) - 1) << shift);
uint32_t value = val;
value <<= shift;
switch (offset & ~0x3) {
case SDHC_SYSAD:
... | 242,202,388,178,100,180,000,000,000,000,000,000,000 | sdhci.c | 302,367,590,168,542,050,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2021-3409 | The patch for CVE-2020-17380/CVE-2020-25085 was found to be ineffective, thus making QEMU vulnerable to the out-of-bounds read/write access issues previously found in the SDHCI controller emulation code. This flaw allows a malicious privileged guest to crash the QEMU process on the host, resulting in a denial of servic... | https://nvd.nist.gov/vuln/detail/CVE-2021-3409 |
400,707 | qemu | dfba99f17feb6d4a129da19d38df1bcd8579d1c3 | https://github.com/bonzini/qemu | https://git.qemu.org/?p=qemu.git;a=commit;h=dfba99f17feb6d4a129da19d38df1bcd8579d1c3 | hw/sd/sdhci: Fix DMA Transfer Block Size field
The 'Transfer Block Size' field is 12-bit wide.
See section '2.2.2. Block Size Register (Offset 004h)' in datasheet.
Two different bug reproducer available:
- https://bugs.launchpad.net/qemu/+bug/1892960
- https://ruhr-uni-bochum.sciebo.de/s/NNWP2GfwzYKeKwE?path=%2Fsdhc... | 0 | sdhci_write(void *opaque, hwaddr offset, uint64_t val, unsigned size)
{
SDHCIState *s = (SDHCIState *)opaque;
unsigned shift = 8 * (offset & 0x3);
uint32_t mask = ~(((1ULL << (size * 8)) - 1) << shift);
uint32_t value = val;
value <<= shift;
switch (offset & ~0x3) {
case SDHC_SYSAD:
... | 269,643,271,894,362,500,000,000,000,000,000,000,000 | sdhci.c | 35,439,887,756,246,070,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2021-3409 | The patch for CVE-2020-17380/CVE-2020-25085 was found to be ineffective, thus making QEMU vulnerable to the out-of-bounds read/write access issues previously found in the SDHCI controller emulation code. This flaw allows a malicious privileged guest to crash the QEMU process on the host, resulting in a denial of servic... | https://nvd.nist.gov/vuln/detail/CVE-2021-3409 |
207,758 | ghostpdl | 9f39ed4a92578a020ae10459643e1fe72573d134 | https://github.com/ArtifexSoftware/ghostpdl | https://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=9f39ed4a92578a020ae10459643e1fe72573d134 | Bug 701792: Avoid going beyond buffer in GetNumSameData() and GetNumWrongData().
GetNumSameData() compared buffer contents before checking that we are still
within bounds of buffer, which caused the bug.
Have made similar fix to GetNumWrongData() because it has similar error.
Fixes address sanitizer error in:
./... | 1 | GetNumWrongData(const byte * curPtr, const int maxnum)
{
int count = 0;
if (1 == maxnum) {
return (1);
}
while (*(curPtr + count) != *(curPtr + count + 1) && maxnum > count) {
count++;
}
return (count);
} | 59,025,936,126,994,240,000,000,000,000,000,000,000 | gdevlips.c | 26,356,441,225,771,413,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2020-16296 | A buffer overflow vulnerability in GetNumWrongData() in contrib/lips4/gdevlips.c of Artifex Software GhostScript v9.50 allows a remote attacker to cause a denial of service via a crafted PDF file. This is fixed in v9.51. | https://nvd.nist.gov/vuln/detail/CVE-2020-16296 |
400,783 | ghostpdl | 9f39ed4a92578a020ae10459643e1fe72573d134 | https://github.com/ArtifexSoftware/ghostpdl | https://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=9f39ed4a92578a020ae10459643e1fe72573d134 | Bug 701792: Avoid going beyond buffer in GetNumSameData() and GetNumWrongData().
GetNumSameData() compared buffer contents before checking that we are still
within bounds of buffer, which caused the bug.
Have made similar fix to GetNumWrongData() because it has similar error.
Fixes address sanitizer error in:
./... | 0 | GetNumWrongData(const byte * curPtr, const int maxnum)
{
int count = 0;
if (1 == maxnum) {
return (1);
}
while (maxnum > count+1 && *(curPtr + count) != *(curPtr + count + 1)) {
count++;
}
return (count);
} | 162,571,246,106,752,550,000,000,000,000,000,000,000 | gdevlips.c | 79,281,672,398,030,190,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2020-16296 | A buffer overflow vulnerability in GetNumWrongData() in contrib/lips4/gdevlips.c of Artifex Software GhostScript v9.50 allows a remote attacker to cause a denial of service via a crafted PDF file. This is fixed in v9.51. | https://nvd.nist.gov/vuln/detail/CVE-2020-16296 |
207,759 | vim | dbdd16b62560413abcc3c8e893cc3010ccf31666 | https://github.com/vim/vim | https://github.com/vim/vim/commit/dbdd16b62560413abcc3c8e893cc3010ccf31666 | patch 9.0.0212: invalid memory access when compiling :unlet
Problem: Invalid memory access when compiling :unlet.
Solution: Don't read past the end of the line. | 1 | check_vim9_unlet(char_u *name)
{
if (name[1] != ':' || vim_strchr((char_u *)"gwtb", *name) == NULL)
{
// "unlet s:var" is allowed in legacy script.
if (*name == 's' && !script_is_vim9())
return OK;
semsg(_(e_cannot_unlet_str), name);
return FAIL;
}
return OK;
} | 153,296,571,765,340,130,000,000,000,000,000,000,000 | vim9cmds.c | 97,090,418,665,720,480,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2022-2816 | Out-of-bounds Read in GitHub repository vim/vim prior to 9.0.0212. | https://nvd.nist.gov/vuln/detail/CVE-2022-2816 |
400,812 | vim | dbdd16b62560413abcc3c8e893cc3010ccf31666 | https://github.com/vim/vim | https://github.com/vim/vim/commit/dbdd16b62560413abcc3c8e893cc3010ccf31666 | patch 9.0.0212: invalid memory access when compiling :unlet
Problem: Invalid memory access when compiling :unlet.
Solution: Don't read past the end of the line. | 0 | check_vim9_unlet(char_u *name)
{
if (*name == NUL)
{
semsg(_(e_argument_required_for_str), "unlet");
return FAIL;
}
if (name[1] != ':' || vim_strchr((char_u *)"gwtb", *name) == NULL)
{
// "unlet s:var" is allowed in legacy script.
if (*name == 's' && !script_is_vim9())
return OK;
semsg(_(... | 48,049,525,187,773,250,000,000,000,000,000,000,000 | vim9cmds.c | 154,629,271,053,504,480,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2022-2816 | Out-of-bounds Read in GitHub repository vim/vim prior to 9.0.0212. | https://nvd.nist.gov/vuln/detail/CVE-2022-2816 |
207,761 | linux | a10feaf8c464c3f9cfdd3a8a7ce17e1c0d498da1 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a10feaf8c464c3f9cfdd3a8a7ce17e1c0d498da1 | media: ttusb-dec: Fix info-leak in ttusb_dec_send_command()
The function at issue does not always initialize each byte allocated
for 'b' and can therefore leak uninitialized memory to a USB device in
the call to usb_bulk_msg()
Use kzalloc() instead of kmalloc()
Signed-off-by: Tomas Bortoli <tomasbortoli@gmail.com>
R... | 1 | static int ttusb_dec_send_command(struct ttusb_dec *dec, const u8 command,
int param_length, const u8 params[],
int *result_length, u8 cmd_result[])
{
int result, actual_len;
u8 *b;
dprintk("%s\n", __func__);
b = kmalloc(COMMAND_PACKET_SIZE + 4, GFP_KERNEL);
if (!b)
return -ENOMEM;
if ((result = ... | 43,244,692,200,879,900,000,000,000,000,000,000,000 | ttusb_dec.c | 105,169,635,098,891,760,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2019-19533 | In the Linux kernel before 5.3.4, there is an info-leak bug that can be caused by a malicious USB device in the drivers/media/usb/ttusb-dec/ttusb_dec.c driver, aka CID-a10feaf8c464. | https://nvd.nist.gov/vuln/detail/CVE-2019-19533 |
400,849 | linux | a10feaf8c464c3f9cfdd3a8a7ce17e1c0d498da1 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a10feaf8c464c3f9cfdd3a8a7ce17e1c0d498da1 | media: ttusb-dec: Fix info-leak in ttusb_dec_send_command()
The function at issue does not always initialize each byte allocated
for 'b' and can therefore leak uninitialized memory to a USB device in
the call to usb_bulk_msg()
Use kzalloc() instead of kmalloc()
Signed-off-by: Tomas Bortoli <tomasbortoli@gmail.com>
R... | 0 | static int ttusb_dec_send_command(struct ttusb_dec *dec, const u8 command,
int param_length, const u8 params[],
int *result_length, u8 cmd_result[])
{
int result, actual_len;
u8 *b;
dprintk("%s\n", __func__);
b = kzalloc(COMMAND_PACKET_SIZE + 4, GFP_KERNEL);
if (!b)
return -ENOMEM;
if ((result = ... | 76,077,447,832,076,120,000,000,000,000,000,000,000 | ttusb_dec.c | 295,460,841,900,840,900,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2019-19533 | In the Linux kernel before 5.3.4, there is an info-leak bug that can be caused by a malicious USB device in the drivers/media/usb/ttusb-dec/ttusb_dec.c driver, aka CID-a10feaf8c464. | https://nvd.nist.gov/vuln/detail/CVE-2019-19533 |
207,763 | tty | 0c9acb1af77a3cb8707e43f45b72c95266903cee | https://git.kernel.org/cgit/linux/kernel/git/gregkh/tty | https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-testing&id=0c9acb1af77a3cb8707e43f45b72c95266903cee | vcs: prevent write access to vcsu devices
Commit d21b0be246bf ("vt: introduce unicode mode for /dev/vcs") guarded
against using devices containing attributes as this is not yet
implemented. It however failed to guard against writes to any devices
as this is also unimplemented.
Reported-by: Or Cohen <orcohen@paloalton... | 1 | vcs_write(struct file *file, const char __user *buf, size_t count, loff_t *ppos)
{
struct inode *inode = file_inode(file);
struct vc_data *vc;
long pos;
long attr, size, written;
char *con_buf0;
int col, maxcol, viewed;
u16 *org0 = NULL, *org = NULL;
size_t ret;
char *con_buf;
con_buf = (char *) __get_free_p... | 284,792,318,052,752,770,000,000,000,000,000,000,000 | vc_screen.c | 101,550,278,065,069,850,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2019-19252 | vcs_write in drivers/tty/vt/vc_screen.c in the Linux kernel through 5.3.13 does not prevent write access to vcsu devices, aka CID-0c9acb1af77a. | https://nvd.nist.gov/vuln/detail/CVE-2019-19252 |
400,888 | tty | 0c9acb1af77a3cb8707e43f45b72c95266903cee | https://git.kernel.org/cgit/linux/kernel/git/gregkh/tty | https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-testing&id=0c9acb1af77a3cb8707e43f45b72c95266903cee | vcs: prevent write access to vcsu devices
Commit d21b0be246bf ("vt: introduce unicode mode for /dev/vcs") guarded
against using devices containing attributes as this is not yet
implemented. It however failed to guard against writes to any devices
as this is also unimplemented.
Reported-by: Or Cohen <orcohen@paloalton... | 0 | vcs_write(struct file *file, const char __user *buf, size_t count, loff_t *ppos)
{
struct inode *inode = file_inode(file);
struct vc_data *vc;
long pos;
long attr, size, written;
char *con_buf0;
int col, maxcol, viewed;
u16 *org0 = NULL, *org = NULL;
size_t ret;
char *con_buf;
if (use_unicode(inode))
retur... | 101,155,777,550,216,650,000,000,000,000,000,000,000 | vc_screen.c | 136,503,066,045,647,820,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2019-19252 | vcs_write in drivers/tty/vt/vc_screen.c in the Linux kernel through 5.3.13 does not prevent write access to vcsu devices, aka CID-0c9acb1af77a. | https://nvd.nist.gov/vuln/detail/CVE-2019-19252 |
207,766 | rsync | 9a480deec4d20277d8e20bc55515ef0640ca1e55 | https://github.com/WayneD/rsync | https://git.samba.org/?p=rsync.git;a=commit;h=9a480deec4d20277d8e20bc55515ef0640ca1e55 | Only allow a modern checksum method for passwords. | 1 | char *auth_server(int f_in, int f_out, int module, const char *host,
const char *addr, const char *leader)
{
char *users = lp_auth_users(module);
char challenge[MAX_DIGEST_LEN*2];
char line[BIGPATHBUFLEN];
char **auth_uid_groups = NULL;
int auth_uid_groups_cnt = -1;
const char *err = NULL;
int group_match = ... | 149,926,736,349,678,670,000,000,000,000,000,000,000 | authenticate.c | 288,758,314,673,929,700,000,000,000,000,000,000,000 | [
"CWE-354"
] | CVE-2017-15994 | rsync 3.1.3-development before 2017-10-24 mishandles archaic checksums, which makes it easier for remote attackers to bypass intended access restrictions. NOTE: the rsync development branch has significant use beyond the rsync developers, e.g., the code has been copied for use in various GitHub projects. | https://nvd.nist.gov/vuln/detail/CVE-2017-15994 |
400,893 | rsync | 9a480deec4d20277d8e20bc55515ef0640ca1e55 | https://github.com/WayneD/rsync | https://git.samba.org/?p=rsync.git;a=commit;h=9a480deec4d20277d8e20bc55515ef0640ca1e55 | Only allow a modern checksum method for passwords. | 0 | char *auth_server(int f_in, int f_out, int module, const char *host,
const char *addr, const char *leader)
{
char *users = lp_auth_users(module);
char challenge[MAX_DIGEST_LEN*2];
char line[BIGPATHBUFLEN];
char **auth_uid_groups = NULL;
int auth_uid_groups_cnt = -1;
const char *err = NULL;
int group_match = ... | 297,773,950,722,013,820,000,000,000,000,000,000,000 | authenticate.c | 87,296,578,568,276,710,000,000,000,000,000,000,000 | [
"CWE-354"
] | CVE-2017-15994 | rsync 3.1.3-development before 2017-10-24 mishandles archaic checksums, which makes it easier for remote attackers to bypass intended access restrictions. NOTE: the rsync development branch has significant use beyond the rsync developers, e.g., the code has been copied for use in various GitHub projects. | https://nvd.nist.gov/vuln/detail/CVE-2017-15994 |
207,767 | ImageMagick | 916d7bbd2c66a286d379dbd94bc6035c8fab937c | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/916d7bbd2c66a286d379dbd94bc6035c8fab937c | Removed invalid free reported in #1791. | 1 | static Image *ReadOneMNGImage(MngInfo* mng_info, const ImageInfo *image_info,
ExceptionInfo *exception)
{
char
page_geometry[MagickPathExtent];
Image
*image;
MagickBooleanType
logging;
volatile int
first_mng_object,
object_id,
term_chunk_found,
skip_to_iend;
volatile ssize... | 140,704,116,713,123,720,000,000,000,000,000,000,000 | png.c | 254,607,083,701,360,550,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2019-19952 | In ImageMagick 7.0.9-7 Q16, there is a use-after-free in the function MngInfoDiscardObject of coders/png.c, related to ReadOneMNGImage. | https://nvd.nist.gov/vuln/detail/CVE-2019-19952 |
400,895 | ImageMagick | 916d7bbd2c66a286d379dbd94bc6035c8fab937c | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/916d7bbd2c66a286d379dbd94bc6035c8fab937c | Removed invalid free reported in #1791. | 0 | static Image *ReadOneMNGImage(MngInfo* mng_info, const ImageInfo *image_info,
ExceptionInfo *exception)
{
char
page_geometry[MagickPathExtent];
Image
*image;
MagickBooleanType
logging;
volatile int
first_mng_object,
object_id,
term_chunk_found,
skip_to_iend;
volatile ssize... | 93,789,117,898,514,220,000,000,000,000,000,000,000 | png.c | 283,297,615,328,770,500,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2019-19952 | In ImageMagick 7.0.9-7 Q16, there is a use-after-free in the function MngInfoDiscardObject of coders/png.c, related to ReadOneMNGImage. | https://nvd.nist.gov/vuln/detail/CVE-2019-19952 |
207,771 | xserver | 8a59e3b7dbb30532a7c3769c555e00d7c4301170 | http://gitweb.freedesktop.org/?p=xorg/xserver | https://gitlab.freedesktop.org/xorg/xserver/commit/8a59e3b7dbb30532a7c3769c555e00d7c4301170 | Disable -logfile and -modulepath when running with elevated privileges
Could cause privilege elevation and/or arbitrary files overwrite, when
the X server is running with elevated privileges (ie when Xorg is
installed with the setuid bit set and started by a non-root user).
CVE-2018-14665
Issue reported by Narendra ... | 1 | ddxProcessArgument(int argc, char **argv, int i)
{
#define CHECK_FOR_REQUIRED_ARGUMENT() \
if (((i + 1) >= argc) || (!argv[i + 1])) { \
ErrorF("Required argument to %s not specified\n", argv[i]); \
UseMsg(); \
FatalError("Required argument to %s not specified\n", argv[i]); \
}
... | 335,276,027,688,759,860,000,000,000,000,000,000,000 | xf86Init.c | 232,707,080,156,735,940,000,000,000,000,000,000,000 | [
"CWE-863"
] | CVE-2018-14665 | A flaw was found in xorg-x11-server before 1.20.3. An incorrect permission check for -modulepath and -logfile options when starting Xorg. X server allows unprivileged users with the ability to log in to the system via physical console to escalate their privileges and run arbitrary code under root privileges. | https://nvd.nist.gov/vuln/detail/CVE-2018-14665 |
400,935 | xserver | 8a59e3b7dbb30532a7c3769c555e00d7c4301170 | http://gitweb.freedesktop.org/?p=xorg/xserver | https://gitlab.freedesktop.org/xorg/xserver/commit/8a59e3b7dbb30532a7c3769c555e00d7c4301170 | Disable -logfile and -modulepath when running with elevated privileges
Could cause privilege elevation and/or arbitrary files overwrite, when
the X server is running with elevated privileges (ie when Xorg is
installed with the setuid bit set and started by a non-root user).
CVE-2018-14665
Issue reported by Narendra ... | 0 | ddxProcessArgument(int argc, char **argv, int i)
{
#define CHECK_FOR_REQUIRED_ARGUMENT() \
if (((i + 1) >= argc) || (!argv[i + 1])) { \
ErrorF("Required argument to %s not specified\n", argv[i]); \
UseMsg(); \
FatalError("Required argument to %s not specified\n", argv[i]); \
}
... | 4,853,382,525,035,145,000,000,000,000,000,000,000 | xf86Init.c | 291,379,981,573,730,100,000,000,000,000,000,000,000 | [
"CWE-863"
] | CVE-2018-14665 | A flaw was found in xorg-x11-server before 1.20.3. An incorrect permission check for -modulepath and -logfile options when starting Xorg. X server allows unprivileged users with the ability to log in to the system via physical console to escalate their privileges and run arbitrary code under root privileges. | https://nvd.nist.gov/vuln/detail/CVE-2018-14665 |
207,779 | gnutls | 3db352734472d851318944db13be73da61300568 | http://git.savannah.gnu.org/cgit/gnutls | https://gitlab.com/gnutls/gnutls/-/commit/3db352734472d851318944db13be73da61300568 | wrap_nettle_hash_fast: avoid calling _update with zero-length input
As Nettle's hash update functions internally call memcpy, providing
zero-length input may cause undefined behavior.
Signed-off-by: Daiki Ueno <ueno@gnu.org> | 1 | static int wrap_nettle_hash_fast(gnutls_digest_algorithm_t algo,
const void *text, size_t text_size,
void *digest)
{
struct nettle_hash_ctx ctx;
int ret;
ret = _ctx_init(algo, &ctx);
if (ret < 0)
return gnutls_assert_val(ret);
ctx.update(&ctx, text_size, text);
ctx.digest(&ctx, ctx.length, digest);
... | 53,412,847,317,425,750,000,000,000,000,000,000,000 | mac.c | 293,516,344,940,906,740,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2021-4209 | A NULL pointer dereference flaw was found in GnuTLS. As Nettle's hash update functions internally call memcpy, providing zero-length input may cause undefined behavior. This flaw leads to a denial of service after authentication in rare circumstances. | https://nvd.nist.gov/vuln/detail/CVE-2021-4209 |
401,023 | gnutls | 3db352734472d851318944db13be73da61300568 | http://git.savannah.gnu.org/cgit/gnutls | https://gitlab.com/gnutls/gnutls/-/commit/3db352734472d851318944db13be73da61300568 | wrap_nettle_hash_fast: avoid calling _update with zero-length input
As Nettle's hash update functions internally call memcpy, providing
zero-length input may cause undefined behavior.
Signed-off-by: Daiki Ueno <ueno@gnu.org> | 0 | static int wrap_nettle_hash_fast(gnutls_digest_algorithm_t algo,
const void *text, size_t text_size,
void *digest)
{
struct nettle_hash_ctx ctx;
int ret;
ret = _ctx_init(algo, &ctx);
if (ret < 0)
return gnutls_assert_val(ret);
if (text_size > 0) {
ctx.update(&ctx, text_size, text);
}
ctx.digest(&... | 196,631,902,292,224,000,000,000,000,000,000,000,000 | mac.c | 144,550,425,274,546,240,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2021-4209 | A NULL pointer dereference flaw was found in GnuTLS. As Nettle's hash update functions internally call memcpy, providing zero-length input may cause undefined behavior. This flaw leads to a denial of service after authentication in rare circumstances. | https://nvd.nist.gov/vuln/detail/CVE-2021-4209 |
207,781 | cups | 07428f6a640ff93aa0b4cc69ca372e2cf8490e41 | https://github.com/apple/cups | https://github.com/apple/cups/commit/07428f6a640ff93aa0b4cc69ca372e2cf8490e41 | Only list supported PDLs (Issue #4923) | 1 | _ppdCreateFromIPP(char *buffer, /* I - Filename buffer */
size_t bufsize, /* I - Size of filename buffer */
ipp_t *response) /* I - Get-Printer-Attributes response */
{
cups_file_t *fp; /* PPD file */
cups_array_t *sizes; /* Media sizes we've added */
ipp_attribute_t *attr, /* xxx-su... | 164,184,577,227,430,030,000,000,000,000,000,000,000 | ppd-cache.c | 130,900,504,754,344,590,000,000,000,000,000,000,000 | [
"CWE-93"
] | CVE-2017-15400 | Insufficient restriction of IPP filters in CUPS in Google Chrome OS prior to 62.0.3202.74 allowed a remote attacker to execute a command with the same privileges as the cups daemon via a crafted PPD file, aka a printer zeroconfig CRLF issue. | https://nvd.nist.gov/vuln/detail/CVE-2017-15400 |
401,058 | cups | 07428f6a640ff93aa0b4cc69ca372e2cf8490e41 | https://github.com/apple/cups | https://github.com/apple/cups/commit/07428f6a640ff93aa0b4cc69ca372e2cf8490e41 | Only list supported PDLs (Issue #4923) | 0 | _ppdCreateFromIPP(char *buffer, /* I - Filename buffer */
size_t bufsize, /* I - Size of filename buffer */
ipp_t *response) /* I - Get-Printer-Attributes response */
{
cups_file_t *fp; /* PPD file */
cups_array_t *sizes; /* Media sizes we've added */
ipp_attribute_t *attr, /* xxx-su... | 249,097,572,563,071,850,000,000,000,000,000,000,000 | ppd-cache.c | 120,838,589,295,219,470,000,000,000,000,000,000,000 | [
"CWE-93"
] | CVE-2017-15400 | Insufficient restriction of IPP filters in CUPS in Google Chrome OS prior to 62.0.3202.74 allowed a remote attacker to execute a command with the same privileges as the cups daemon via a crafted PPD file, aka a printer zeroconfig CRLF issue. | https://nvd.nist.gov/vuln/detail/CVE-2017-15400 |
207,782 | linux | 6f3ef5c25cc762687a7341c18cbea5af54461407 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6f3ef5c25cc762687a7341c18cbea5af54461407 | wimax: i2400: Fix memory leak in i2400m_op_rfkill_sw_toggle
In the implementation of i2400m_op_rfkill_sw_toggle() the allocated
buffer for cmd should be released before returning. The
documentation for i2400m_msg_to_dev() says when it returns the buffer
can be reused. Meaning cmd should be released in either case. Mov... | 1 | int i2400m_op_rfkill_sw_toggle(struct wimax_dev *wimax_dev,
enum wimax_rf_state state)
{
int result;
struct i2400m *i2400m = wimax_dev_to_i2400m(wimax_dev);
struct device *dev = i2400m_dev(i2400m);
struct sk_buff *ack_skb;
struct {
struct i2400m_l3l4_hdr hdr;
struct i2400m_tlv_rf_operation sw_rf;
} ... | 185,109,671,119,641,700,000,000,000,000,000,000,000 | op-rfkill.c | 119,362,973,161,223,000,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2019-19051 | A memory leak in the i2400m_op_rfkill_sw_toggle() function in drivers/net/wimax/i2400m/op-rfkill.c in the Linux kernel before 5.3.11 allows attackers to cause a denial of service (memory consumption), aka CID-6f3ef5c25cc7. | https://nvd.nist.gov/vuln/detail/CVE-2019-19051 |
401,062 | linux | 6f3ef5c25cc762687a7341c18cbea5af54461407 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6f3ef5c25cc762687a7341c18cbea5af54461407 | wimax: i2400: Fix memory leak in i2400m_op_rfkill_sw_toggle
In the implementation of i2400m_op_rfkill_sw_toggle() the allocated
buffer for cmd should be released before returning. The
documentation for i2400m_msg_to_dev() says when it returns the buffer
can be reused. Meaning cmd should be released in either case. Mov... | 0 | int i2400m_op_rfkill_sw_toggle(struct wimax_dev *wimax_dev,
enum wimax_rf_state state)
{
int result;
struct i2400m *i2400m = wimax_dev_to_i2400m(wimax_dev);
struct device *dev = i2400m_dev(i2400m);
struct sk_buff *ack_skb;
struct {
struct i2400m_l3l4_hdr hdr;
struct i2400m_tlv_rf_operation sw_rf;
} ... | 156,746,425,556,083,460,000,000,000,000,000,000,000 | op-rfkill.c | 115,760,626,497,223,650,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2019-19051 | A memory leak in the i2400m_op_rfkill_sw_toggle() function in drivers/net/wimax/i2400m/op-rfkill.c in the Linux kernel before 5.3.11 allows attackers to cause a denial of service (memory consumption), aka CID-6f3ef5c25cc7. | https://nvd.nist.gov/vuln/detail/CVE-2019-19051 |
207,808 | exiv2 | 74cb5bab132ed76adf15df172c5e8b58cddaa96c | https://github.com/Exiv2/exiv2 | https://github.com/Exiv2/exiv2/commit/74cb5bab132ed76adf15df172c5e8b58cddaa96c | Fixed wrong brackets: size*count + pad can overflow before the cast
=> Should fix #76 (most of the work has been done by Robin Mills in
6e3855aed7ba8bb4731fc4087ca7f9078b2f3d97)
The problem with #76 is the contents of the 26th IFD, with the
following contents:
tag: 0x8649
type: 0x1
count: 0xffff ffff
offset: 0x497... | 1 | void Image::printIFDStructure(BasicIo& io, std::ostream& out, Exiv2::PrintStructureOption option,uint32_t start,bool bSwap,char c,int depth)
{
depth++;
bool bFirst = true ;
// buffer
const size_t dirSize = 32;
DataBuf dir(dirSize);
bool bPrint = option == kpsB... | 312,839,316,983,498,800,000,000,000,000,000,000,000 | image.cpp | 287,081,946,078,799,000,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-17723 | In Exiv2 0.26, there is a heap-based buffer over-read in the Exiv2::Image::byteSwap4 function in image.cpp. Remote attackers can exploit this vulnerability to disclose memory data or cause a denial of service via a crafted TIFF file. | https://nvd.nist.gov/vuln/detail/CVE-2017-17723 |
401,640 | exiv2 | 74cb5bab132ed76adf15df172c5e8b58cddaa96c | https://github.com/Exiv2/exiv2 | https://github.com/Exiv2/exiv2/commit/74cb5bab132ed76adf15df172c5e8b58cddaa96c | Fixed wrong brackets: size*count + pad can overflow before the cast
=> Should fix #76 (most of the work has been done by Robin Mills in
6e3855aed7ba8bb4731fc4087ca7f9078b2f3d97)
The problem with #76 is the contents of the 26th IFD, with the
following contents:
tag: 0x8649
type: 0x1
count: 0xffff ffff
offset: 0x497... | 0 | void Image::printIFDStructure(BasicIo& io, std::ostream& out, Exiv2::PrintStructureOption option,uint32_t start,bool bSwap,char c,int depth)
{
depth++;
bool bFirst = true ;
// buffer
const size_t dirSize = 32;
DataBuf dir(dirSize);
bool bPrint = option == kpsB... | 123,620,731,507,173,180,000,000,000,000,000,000,000 | image.cpp | 247,637,633,740,130,500,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-17723 | In Exiv2 0.26, there is a heap-based buffer over-read in the Exiv2::Image::byteSwap4 function in image.cpp. Remote attackers can exploit this vulnerability to disclose memory data or cause a denial of service via a crafted TIFF file. | https://nvd.nist.gov/vuln/detail/CVE-2017-17723 |
207,827 | libsoup | f8a54ac85eec2008c85393f331cdd251af8266ad | https://git.gnome.org/browse/libsoup | https://gitlab.gnome.org/GNOME/libsoup/commit/f8a54ac85eec2008c85393f331cdd251af8266ad | NTLM: Avoid a potential heap buffer overflow in v2 authentication
Check the length of the decoded v2 challenge before attempting to
parse it, to avoid reading past it.
Fixes #173 | 1 | soup_ntlm_parse_challenge (const char *challenge,
char **nonce,
char **default_domain,
gboolean *ntlmv2_session,
gboolean *negotiate_target,
char **target_info,
size_t *target_info_sz)
{
gsize clen;
NTLMString domain;
NTLMString target;
guchar *chall;
guint32 flag... | 320,512,014,728,184,920,000,000,000,000,000,000,000 | soup-auth-ntlm.c | 15,940,960,510,749,928,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2019-17266 | libsoup from versions 2.65.1 until 2.68.1 have a heap-based buffer over-read because soup_ntlm_parse_challenge() in soup-auth-ntlm.c does not properly check an NTLM message's length before proceeding with a memcpy. | https://nvd.nist.gov/vuln/detail/CVE-2019-17266 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.