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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
343,197 | ImageMagick6 | 4745eb1047617330141e9abfd5ae01236a71ae12 | https://github.com/ImageMagick/ImageMagick6 | https://github.com/ImageMagick/ImageMagick6/commit/4745eb1047617330141e9abfd5ae01236a71ae12 | https://github.com/ImageMagick/ImageMagick/issues/1249 | 0 | static StringInfo *ParseImageResourceBlocks(Image *image,
const unsigned char *blocks,size_t length,
MagickBooleanType *has_merged_image)
{
const unsigned char
*p;
StringInfo
*profile;
unsigned char
name_length;
unsigned int
count;
unsigned short
id,
short_sans;
if (length <... | 230,263,082,353,828,060,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2018-16412 | ImageMagick 7.0.8-11 Q16 has a heap-based buffer over-read in the coders/psd.c ParseImageResourceBlocks function. | https://nvd.nist.gov/vuln/detail/CVE-2018-16412 |
202,895 | php-src | 4605d536d23b00813d11cc906bb48d39bdcf5f25 | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commitdiff;h=4605d536d23b00813d11cc906bb48d39bdcf5f25 | Fixed bug #69364 - use smart_str to assemble strings | 1 | static int multipart_buffer_headers(multipart_buffer *self, zend_llist *header TSRMLS_DC)
{
char *line;
mime_header_entry prev_entry = {0}, entry;
int prev_len, cur_len;
/* didn't find boundary, abort */
if (!find_boundary(self, self->boundary TSRMLS_CC)) {
return 0;
}
/* get lines of text, or CRLF_CRLF */
... | 141,798,922,069,046,700,000,000,000,000,000,000,000 | rfc1867.c | 303,714,083,219,982,150,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2015-4024 | Algorithmic complexity vulnerability in the multipart_buffer_headers function in main/rfc1867.c in PHP before 5.4.41, 5.5.x before 5.5.25, and 5.6.x before 5.6.9 allows remote attackers to cause a denial of service (CPU consumption) via crafted form data that triggers an improper order-of-growth outcome. | https://nvd.nist.gov/vuln/detail/CVE-2015-4024 |
343,421 | php-src | 4605d536d23b00813d11cc906bb48d39bdcf5f25 | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commitdiff;h=4605d536d23b00813d11cc906bb48d39bdcf5f25 | Fixed bug #69364 - use smart_str to assemble strings | 0 | static int multipart_buffer_headers(multipart_buffer *self, zend_llist *header TSRMLS_DC)
{
char *line;
mime_header_entry entry = {0};
smart_str buf_value = {0};
char *key = NULL;
/* didn't find boundary, abort */
if (!find_boundary(self, self->boundary TSRMLS_CC)) {
return 0;
}
/* get lines of text, or CRL... | 328,523,675,582,182,100,000,000,000,000,000,000,000 | rfc1867.c | 70,699,713,515,909,640,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2015-4024 | Algorithmic complexity vulnerability in the multipart_buffer_headers function in main/rfc1867.c in PHP before 5.4.41, 5.5.x before 5.5.25, and 5.6.x before 5.6.9 allows remote attackers to cause a denial of service (CPU consumption) via crafted form data that triggers an improper order-of-growth outcome. | https://nvd.nist.gov/vuln/detail/CVE-2015-4024 |
202,899 | avahi | e111def44a7df4624a4aa3f85fe98054bffb6b4f | http://git.0pointer.de/?p=avahi | https://github.com/lathiat/avahi/commit/e111def44a7df4624a4aa3f85fe98054bffb6b4f | Drop legacy unicast queries from address not on local link
When handling legacy unicast queries, ensure that the source IP is
inside a subnet on the local link, otherwise drop the packet.
Fixes #145
Fixes #203
CVE-2017-6519
CVE-2018-100084 | 1 | static void dispatch_packet(AvahiServer *s, AvahiDnsPacket *p, const AvahiAddress *src_address, uint16_t port, const AvahiAddress *dst_address, AvahiIfIndex iface, int ttl) {
AvahiInterface *i;
int from_local_iface = 0;
assert(s);
assert(p);
assert(src_address);
assert(dst_address);
assert(... | 30,074,756,553,344,203,000,000,000,000,000,000,000 | server.c | 294,258,670,284,742,820,000,000,000,000,000,000,000 | [
"CWE-346"
] | CVE-2017-6519 | avahi-daemon in Avahi through 0.6.32 and 0.7 inadvertently responds to IPv6 unicast queries with source addresses that are not on-link, which allows remote attackers to cause a denial of service (traffic amplification) and may cause information leakage by obtaining potentially sensitive information from the responding... | https://nvd.nist.gov/vuln/detail/CVE-2017-6519 |
343,600 | avahi | e111def44a7df4624a4aa3f85fe98054bffb6b4f | http://git.0pointer.de/?p=avahi | https://github.com/lathiat/avahi/commit/e111def44a7df4624a4aa3f85fe98054bffb6b4f | Drop legacy unicast queries from address not on local link
When handling legacy unicast queries, ensure that the source IP is
inside a subnet on the local link, otherwise drop the packet.
Fixes #145
Fixes #203
CVE-2017-6519
CVE-2018-100084 | 0 | static void dispatch_packet(AvahiServer *s, AvahiDnsPacket *p, const AvahiAddress *src_address, uint16_t port, const AvahiAddress *dst_address, AvahiIfIndex iface, int ttl) {
AvahiInterface *i;
int from_local_iface = 0;
assert(s);
assert(p);
assert(src_address);
assert(dst_address);
assert(... | 204,526,678,845,123,900,000,000,000,000,000,000,000 | server.c | 23,909,170,392,287,565,000,000,000,000,000,000,000 | [
"CWE-346"
] | CVE-2017-6519 | avahi-daemon in Avahi through 0.6.32 and 0.7 inadvertently responds to IPv6 unicast queries with source addresses that are not on-link, which allows remote attackers to cause a denial of service (traffic amplification) and may cause information leakage by obtaining potentially sensitive information from the responding... | https://nvd.nist.gov/vuln/detail/CVE-2017-6519 |
202,931 | ghostpdl | 98f6da60b9d463c617e631fc254cf6d66f2e8e3c | https://github.com/ArtifexSoftware/ghostpdl | http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=98f6da60b9d463c617e631fc254cf6d66f2e8e3c | Bug 698026: bounds check zone pointers in Ins_IP() | 1 | static void Ins_IP( INS_ARG )
{
TT_F26Dot6 org_a, org_b, org_x,
cur_a, cur_b, cur_x,
distance;
Int point;
(void)args;
if ( CUR.top < CUR.GS.loop )
{
CUR.error = TT_Err_Invalid_Reference;
return;
}
org_a = CUR_Func_dualproj( CUR.zp0.... | 32,883,715,114,853,980,000,000,000,000,000,000,000 | ttinterp.c | 326,370,461,196,501,800,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2017-9612 | The Ins_IP function in base/ttinterp.c in Artifex Ghostscript GhostXPS 9.21 allows remote attackers to cause a denial of service (use-after-free and application crash) or possibly have unspecified other impact via a crafted document. | https://nvd.nist.gov/vuln/detail/CVE-2017-9612 |
14,448 | ghostscript | c501a58f8d5650c8ba21d447c0d6f07eafcb0f15 | http://git.ghostscript.com/?p=mupdf | http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=c501a58f8d5650c8ba21d447c0d6f07eafcb0f15 | None | 0 | static void Ins_IP( INS_ARG )
{
TT_F26Dot6 org_a, org_b, org_x,
cur_a, cur_b, cur_x,
distance;
Int point;
(void)args;
if ( CUR.top < CUR.GS.loop ||
BOUNDS(CUR.GS.rp1, CUR.zp0.n_points) ||
BOUNDS(CUR.GS.rp2, CUR.zp1.n_points))
{
C... | 182,601,607,540,285,200,000,000,000,000,000,000,000 | ttinterp.c | 3,055,912,626,797,426,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-9739 | The Ins_JMPR function in base/ttinterp.c in Artifex Ghostscript GhostXPS 9.21 allows remote attackers to cause a denial of service (heap-based buffer over-read and application crash) or possibly have unspecified other impact via a crafted document. | https://nvd.nist.gov/vuln/detail/CVE-2017-9739 |
202,933 | qpdf | 701b518d5c56a1449825a3a37a716c58e05e1c3e | https://github.com/qpdf/qpdf | https://github.com/qpdf/qpdf/commit/701b518d5c56a1449825a3a37a716c58e05e1c3e | Detect recursion loops resolving objects (fixes #51)
During parsing of an object, sometimes parts of the object have to be
resolved. An example is stream lengths. If such an object directly or
indirectly points to the object being parsed, it can cause an infinite
loop. Guard against all cases of re-entrant resolution ... | 1 | QPDF::resolve(int objid, int generation)
{
// Check object cache before checking xref table. This allows us
// to insert things into the object cache that don't actually
// exist in the file.
QPDFObjGen og(objid, generation);
if (! this->obj_cache.count(og))
{
if (! this->xref_table.count(og))... | 282,206,738,362,846,570,000,000,000,000,000,000,000 | QPDF.cc | 11,991,360,527,579,300,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2017-11624 | A stack-consumption vulnerability was found in libqpdf in QPDF 6.0.0, which allows attackers to cause a denial of service via a crafted file, related to the QPDFTokenizer::resolveLiteral function in QPDFTokenizer.cc after two consecutive calls to QPDFObjectHandle::parseInternal, aka an "infinite loop." | https://nvd.nist.gov/vuln/detail/CVE-2017-11624 |
344,062 | qpdf | 701b518d5c56a1449825a3a37a716c58e05e1c3e | https://github.com/qpdf/qpdf | https://github.com/qpdf/qpdf/commit/701b518d5c56a1449825a3a37a716c58e05e1c3e | Detect recursion loops resolving objects (fixes #51)
During parsing of an object, sometimes parts of the object have to be
resolved. An example is stream lengths. If such an object directly or
indirectly points to the object being parsed, it can cause an infinite
loop. Guard against all cases of re-entrant resolution ... | 0 | QPDF::resolve(int objid, int generation)
{
// Check object cache before checking xref table. This allows us
// to insert things into the object cache that don't actually
// exist in the file.
QPDFObjGen og(objid, generation);
if (this->resolving.count(og))
{
// This can happen if an obj... | 66,241,811,359,446,270,000,000,000,000,000,000,000 | QPDF.cc | 239,319,240,737,068,400,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2017-11624 | A stack-consumption vulnerability was found in libqpdf in QPDF 6.0.0, which allows attackers to cause a denial of service via a crafted file, related to the QPDFTokenizer::resolveLiteral function in QPDFTokenizer.cc after two consecutive calls to QPDFObjectHandle::parseInternal, aka an "infinite loop." | https://nvd.nist.gov/vuln/detail/CVE-2017-11624 |
202,937 | LibRaw | 89d065424f09b788f443734d44857289489ca9e2 | https://github.com/LibRaw/LibRaw | https://github.com/LibRaw/LibRaw/commit/89d065424f09b788f443734d44857289489ca9e2 | fixed two more problems found by fuzzer | 1 | void CLASS smal_decode_segment (unsigned seg[2][2], int holes)
{
uchar hist[3][13] = {
{ 7, 7, 0, 0, 63, 55, 47, 39, 31, 23, 15, 7, 0 },
{ 7, 7, 0, 0, 63, 55, 47, 39, 31, 23, 15, 7, 0 },
{ 3, 3, 0, 0, 63, 47, 31, 15, 0 } };
int low, high=0xff, carry=0, nbits=8;
int pix, s, count, bin, n... | 135,309,279,465,091,660,000,000,000,000,000,000,000 | dcraw.c | 16,246,307,575,535,150,000,000,000,000,000,000,000 | [
"CWE-129"
] | CVE-2015-8366 | Array index error in smal_decode_segment function in LibRaw before 0.17.1 allows context-dependent attackers to cause memory errors and possibly execute arbitrary code via vectors related to indexes. | https://nvd.nist.gov/vuln/detail/CVE-2015-8366 |
344,087 | LibRaw | 89d065424f09b788f443734d44857289489ca9e2 | https://github.com/LibRaw/LibRaw | https://github.com/LibRaw/LibRaw/commit/89d065424f09b788f443734d44857289489ca9e2 | fixed two more problems found by fuzzer | 0 | void CLASS smal_decode_segment (unsigned seg[2][2], int holes)
{
uchar hist[3][13] = {
{ 7, 7, 0, 0, 63, 55, 47, 39, 31, 23, 15, 7, 0 },
{ 7, 7, 0, 0, 63, 55, 47, 39, 31, 23, 15, 7, 0 },
{ 3, 3, 0, 0, 63, 47, 31, 15, 0 } };
int low, high=0xff, carry=0, nbits=8;
int pix, s, count, bin, n... | 317,460,317,061,733,270,000,000,000,000,000,000,000 | dcraw.c | 136,801,594,126,834,490,000,000,000,000,000,000,000 | [
"CWE-129"
] | CVE-2015-8366 | Array index error in smal_decode_segment function in LibRaw before 0.17.1 allows context-dependent attackers to cause memory errors and possibly execute arbitrary code via vectors related to indexes. | https://nvd.nist.gov/vuln/detail/CVE-2015-8366 |
202,941 | openexr | 6bb36714528a9563dd3b92720c5063a1284b86f8 | https://github.com/AcademySoftwareFoundation/openexr | https://github.com/AcademySoftwareFoundation/openexr/commit/6bb36714528a9563dd3b92720c5063a1284b86f8 | Fix for #494: validate tile coordinates when doing copyPixels | 1 | TiledInputFile::rawTileData (int &dx, int &dy,
int &lx, int &ly,
const char *&pixelData,
int &pixelDataSize)
{
try
{
Lock lock (*_data->_streamData);
if (!isValidTile (dx, dy, lx, ly))
throw IEX_NAMESPACE::ArgExc ("Tried to read a tile ou... | 224,799,836,926,634,080,000,000,000,000,000,000,000 | ImfTiledInputFile.cpp | 34,001,987,699,428,620,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2020-16589 | A head-based buffer overflow exists in Academy Software Foundation OpenEXR 2.3.0 in writeTileData in ImfTiledOutputFile.cpp that can cause a denial of service via a crafted EXR file. | https://nvd.nist.gov/vuln/detail/CVE-2020-16589 |
344,182 | openexr | 6bb36714528a9563dd3b92720c5063a1284b86f8 | https://github.com/AcademySoftwareFoundation/openexr | https://github.com/AcademySoftwareFoundation/openexr/commit/6bb36714528a9563dd3b92720c5063a1284b86f8 | Fix for #494: validate tile coordinates when doing copyPixels | 0 | TiledInputFile::rawTileData (int &dx, int &dy,
int &lx, int &ly,
const char *&pixelData,
int &pixelDataSize)
{
try
{
Lock lock (*_data->_streamData);
if (!isValidTile (dx, dy, lx, ly))
throw IEX_NAMESPACE::ArgExc ("Tried to read a tile ou... | 14,284,281,747,924,887,000,000,000,000,000,000,000 | ImfTiledInputFile.cpp | 239,750,803,676,068,660,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2020-16589 | A head-based buffer overflow exists in Academy Software Foundation OpenEXR 2.3.0 in writeTileData in ImfTiledOutputFile.cpp that can cause a denial of service via a crafted EXR file. | https://nvd.nist.gov/vuln/detail/CVE-2020-16589 |
202,948 | libexif | 5ae5973bed1947f4d447dc80b76d5cefadd90133 | https://github.com/libexif/libexif | https://github.com/libexif/libexif/commit/5ae5973bed1947f4d447dc80b76d5cefadd90133 | libexif: Fix read buffer overflow (CVE-2020-0093)
Make sure the number of bytes being copied from doesn't exceed the
source buffer size.
From Android repo:
https://android.googlesource.com/platform/external/libexif/+/0335ffc17f9b9a4831c242bb08ea92f605fde7a6%5E%21/#F0
Test: testPocBug_148705132
Bug: 148705132
fixes ... | 1 | exif_data_save_data_entry (ExifData *data, ExifEntry *e,
unsigned char **d, unsigned int *ds,
unsigned int offset)
{
unsigned int doff, s;
unsigned int ts;
if (!data || !data->priv)
return;
/*
* Each entry is 12 bytes long. The memory for the entry has
* already been allocated.
*/
exif_set_s... | 333,073,273,447,400,780,000,000,000,000,000,000,000 | exif-data.c | 151,058,703,672,803,600,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2020-0093 | In exif_data_save_data_entry of exif-data.c, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-8.0 Android-8.1 Android-9 Andro... | https://nvd.nist.gov/vuln/detail/CVE-2020-0093 |
344,370 | libexif | 5ae5973bed1947f4d447dc80b76d5cefadd90133 | https://github.com/libexif/libexif | https://github.com/libexif/libexif/commit/5ae5973bed1947f4d447dc80b76d5cefadd90133 | libexif: Fix read buffer overflow (CVE-2020-0093)
Make sure the number of bytes being copied from doesn't exceed the
source buffer size.
From Android repo:
https://android.googlesource.com/platform/external/libexif/+/0335ffc17f9b9a4831c242bb08ea92f605fde7a6%5E%21/#F0
Test: testPocBug_148705132
Bug: 148705132
fixes ... | 0 | exif_data_save_data_entry (ExifData *data, ExifEntry *e,
unsigned char **d, unsigned int *ds,
unsigned int offset)
{
unsigned int doff, s;
unsigned int ts;
if (!data || !data->priv)
return;
/*
* Each entry is 12 bytes long. The memory for the entry has
* already been allocated.
*/
exif_set_s... | 181,566,981,621,556,440,000,000,000,000,000,000,000 | exif-data.c | 75,155,830,072,442,550,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2020-0093 | In exif_data_save_data_entry of exif-data.c, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-8.0 Android-8.1 Android-9 Andro... | https://nvd.nist.gov/vuln/detail/CVE-2020-0093 |
202,949 | postgres | 1dc75515868454c645ded22d38054ec693e23ec6 | https://github.com/postgres/postgres | https://github.com/postgres/postgres/commit/1dc75515868454c645ded22d38054ec693e23ec6 | Fix buffer overrun after incomplete read in pullf_read_max().
Most callers pass a stack buffer. The ensuing stack smash can crash the
server, and we have not ruled out the viability of attacks that lead to
privilege escalation. Back-patch to 9.0 (all supported versions).
Marko Tiikkaja
Security: CVE-2015-0243 | 1 | pullf_read_max(PullFilter *pf, int len, uint8 **data_p, uint8 *tmpbuf)
{
int res,
total;
uint8 *tmp;
res = pullf_read(pf, len, data_p);
if (res <= 0 || res == len)
return res;
/* read was shorter, use tmpbuf */
memcpy(tmpbuf, *data_p, res);
*data_p = tmpbuf;
len -= res;
total = res;
while (len >... | 245,804,215,287,102,860,000,000,000,000,000,000,000 | None | null | [
"CWE-120"
] | CVE-2015-0243 | Multiple buffer overflows in contrib/pgcrypto in PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 allow remote authenticated users to cause a denial of service (crash) and possibly execute arbitrary code via unspecified vectors. | https://nvd.nist.gov/vuln/detail/CVE-2015-0243 |
344,418 | postgres | 1dc75515868454c645ded22d38054ec693e23ec6 | https://github.com/postgres/postgres | https://github.com/postgres/postgres/commit/1dc75515868454c645ded22d38054ec693e23ec6 | Fix buffer overrun after incomplete read in pullf_read_max().
Most callers pass a stack buffer. The ensuing stack smash can crash the
server, and we have not ruled out the viability of attacks that lead to
privilege escalation. Back-patch to 9.0 (all supported versions).
Marko Tiikkaja
Security: CVE-2015-0243 | 0 | pullf_read_max(PullFilter *pf, int len, uint8 **data_p, uint8 *tmpbuf)
{
int res,
total;
uint8 *tmp;
res = pullf_read(pf, len, data_p);
if (res <= 0 || res == len)
return res;
/* read was shorter, use tmpbuf */
memcpy(tmpbuf, *data_p, res);
*data_p = tmpbuf;
len -= res;
total = res;
while (len >... | 297,999,672,645,319,750,000,000,000,000,000,000,000 | None | null | [
"CWE-120"
] | CVE-2015-0243 | Multiple buffer overflows in contrib/pgcrypto in PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 allow remote authenticated users to cause a denial of service (crash) and possibly execute arbitrary code via unspecified vectors. | https://nvd.nist.gov/vuln/detail/CVE-2015-0243 |
202,950 | sysstat | fbc691eaaa10d0bcea6741d5a223dc3906106548 | https://github.com/sysstat/sysstat | https://github.com/sysstat/sysstat/commit/fbc691eaaa10d0bcea6741d5a223dc3906106548 | Fix #196 and #199: Out of bound reads security issues
Check args before calling memmove() and memset() in remap_struct()
function to avoid out of bound reads which would possibly lead to
unknown code execution and/or sadf command crash.
Signed-off-by: Sebastien GODARD <sysstat@users.noreply.github.com> | 1 | void remap_struct(unsigned int gtypes_nr[], unsigned int ftypes_nr[],
void *ps, unsigned int f_size, unsigned int g_size)
{
int d;
/* Sanity check */
if (MAP_SIZE(ftypes_nr) > f_size)
return;
/* Remap [unsigned] long fields */
d = gtypes_nr[0] - ftypes_nr[0];
if (d) {
memmove(((char *) ps) + gtypes_nr[0... | 71,716,990,822,083,200,000,000,000,000,000,000,000 | sa_common.c | 127,919,254,308,057,980,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2018-19416 | An issue was discovered in sysstat 12.1.1. The remap_struct function in sa_common.c has an out-of-bounds read during a memmove call, as demonstrated by sadf. | https://nvd.nist.gov/vuln/detail/CVE-2018-19416 |
344,456 | sysstat | fbc691eaaa10d0bcea6741d5a223dc3906106548 | https://github.com/sysstat/sysstat | https://github.com/sysstat/sysstat/commit/fbc691eaaa10d0bcea6741d5a223dc3906106548 | Fix #196 and #199: Out of bound reads security issues
Check args before calling memmove() and memset() in remap_struct()
function to avoid out of bound reads which would possibly lead to
unknown code execution and/or sadf command crash.
Signed-off-by: Sebastien GODARD <sysstat@users.noreply.github.com> | 0 | void remap_struct(unsigned int gtypes_nr[], unsigned int ftypes_nr[],
void *ps, unsigned int f_size, unsigned int g_size, size_t b_size)
{
int d;
size_t n;
/* Sanity check */
if (MAP_SIZE(ftypes_nr) > f_size)
return;
/* Remap [unsigned] long fields */
d = gtypes_nr[0] - ftypes_nr[0];
if (d) {
n = MINIM... | 317,806,385,157,476,530,000,000,000,000,000,000,000 | sa_common.c | 131,976,512,262,609,360,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2018-19416 | An issue was discovered in sysstat 12.1.1. The remap_struct function in sa_common.c has an out-of-bounds read during a memmove call, as demonstrated by sadf. | https://nvd.nist.gov/vuln/detail/CVE-2018-19416 |
203,417 | typed_ast | 156afcb26c198e162504a57caddfe0acd9ed7dce | https://github.com/python/typed_ast | https://github.com/python/typed_ast/commit/156afcb26c198e162504a57caddfe0acd9ed7dce | Fully incorporate the code from Python 3.7.2 (#78)
This is a full port, following the recipe in update_process.md. I've also tried to keep the recipe up to date and improved the automation (see tools/script). I haven't cleaned up the commits. As of #77 there are a few tests that sanity-check this (though it's far from... | 1 | handle_keywordonly_args(struct compiling *c, const node *n, int start,
asdl_seq *kwonlyargs, asdl_seq *kwdefaults)
{
PyObject *argname;
node *ch;
expr_ty expression, annotation;
arg_ty arg;
int i = start;
int j = 0; /* index for kwdefaults and kwonlyargs */
if (kwonl... | 272,330,688,373,414,220,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2019-19275 | typed_ast 1.3.0 and 1.3.1 has an ast_for_arguments out-of-bounds read. An attacker with the ability to cause a Python interpreter to parse Python source (but not necessarily execute it) may be able to crash the interpreter process. This could be a concern, for example, in a web-based service that parses (but does not e... | https://nvd.nist.gov/vuln/detail/CVE-2019-19275 |
344,994 | typed_ast | 156afcb26c198e162504a57caddfe0acd9ed7dce | https://github.com/python/typed_ast | https://github.com/python/typed_ast/commit/156afcb26c198e162504a57caddfe0acd9ed7dce | Fully incorporate the code from Python 3.7.2 (#78)
This is a full port, following the recipe in update_process.md. I've also tried to keep the recipe up to date and improved the automation (see tools/script). I haven't cleaned up the commits. As of #77 there are a few tests that sanity-check this (though it's far from... | 0 | handle_keywordonly_args(struct compiling *c, const node *n, int start,
asdl_seq *kwonlyargs, asdl_seq *kwdefaults)
{
PyObject *argname;
node *ch;
expr_ty expression, annotation;
arg_ty arg;
int i = start;
int j = 0; /* index for kwdefaults and kwonlyargs */
if (kwonl... | 137,042,752,727,253,000,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2019-19275 | typed_ast 1.3.0 and 1.3.1 has an ast_for_arguments out-of-bounds read. An attacker with the ability to cause a Python interpreter to parse Python source (but not necessarily execute it) may be able to crash the interpreter process. This could be a concern, for example, in a web-based service that parses (but does not e... | https://nvd.nist.gov/vuln/detail/CVE-2019-19275 |
203,537 | typed_ast | 156afcb26c198e162504a57caddfe0acd9ed7dce | https://github.com/python/typed_ast | https://github.com/python/typed_ast/commit/156afcb26c198e162504a57caddfe0acd9ed7dce | Fully incorporate the code from Python 3.7.2 (#78)
This is a full port, following the recipe in update_process.md. I've also tried to keep the recipe up to date and improved the automation (see tools/script). I haven't cleaned up the commits. As of #77 there are a few tests that sanity-check this (though it's far from... | 1 | ast_for_arguments(struct compiling *c, const node *n)
{
/* This function handles both typedargslist (function definition)
and varargslist (lambda definition).
parameters: '(' [typedargslist] ')'
typedargslist: (tfpdef ['=' test] (',' tfpdef ['=' test])* [',' [
'*' [tfpdef] (',' ... | 216,219,023,813,721,750,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2019-19275 | typed_ast 1.3.0 and 1.3.1 has an ast_for_arguments out-of-bounds read. An attacker with the ability to cause a Python interpreter to parse Python source (but not necessarily execute it) may be able to crash the interpreter process. This could be a concern, for example, in a web-based service that parses (but does not e... | https://nvd.nist.gov/vuln/detail/CVE-2019-19275 |
344,893 | typed_ast | 156afcb26c198e162504a57caddfe0acd9ed7dce | https://github.com/python/typed_ast | https://github.com/python/typed_ast/commit/156afcb26c198e162504a57caddfe0acd9ed7dce | Fully incorporate the code from Python 3.7.2 (#78)
This is a full port, following the recipe in update_process.md. I've also tried to keep the recipe up to date and improved the automation (see tools/script). I haven't cleaned up the commits. As of #77 there are a few tests that sanity-check this (though it's far from... | 0 | ast_for_arguments(struct compiling *c, const node *n)
{
/* This function handles both typedargslist (function definition)
and varargslist (lambda definition).
parameters: '(' [typedargslist] ')'
typedargslist: (tfpdef ['=' test] (',' tfpdef ['=' test])* [',' [
'*' [tfpdef] (',' ... | 123,405,336,780,686,900,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2019-19275 | typed_ast 1.3.0 and 1.3.1 has an ast_for_arguments out-of-bounds read. An attacker with the ability to cause a Python interpreter to parse Python source (but not necessarily execute it) may be able to crash the interpreter process. This could be a concern, for example, in a web-based service that parses (but does not e... | https://nvd.nist.gov/vuln/detail/CVE-2019-19275 |
203,613 | gdal | 148115fcc40f1651a5d15fa34c9a8c528e7147bb | https://github.com/OSGeo/gdal | https://github.com/OSGeo/gdal/commit/148115fcc40f1651a5d15fa34c9a8c528e7147bb | OGRExpatRealloc(): fix double-free when size to allocate is above the default 10MB threshold. Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=16178. Credit to OSS Fuzz | 1 | static void* OGRExpatRealloc( void *ptr, size_t size )
{
if( CanAlloc(size) )
return realloc(ptr, size);
free(ptr);
return nullptr;
} | 292,039,366,937,885,630,000,000,000,000,000,000,000 | ogr_expat.cpp | 52,538,270,045,536,830,000,000,000,000,000,000,000 | [
"CWE-415"
] | CVE-2019-17545 | GDAL through 3.0.1 has a poolDestroy double free in OGRExpatRealloc in ogr/ogr_expat.cpp when the 10MB threshold is exceeded. | https://nvd.nist.gov/vuln/detail/CVE-2019-17545 |
345,120 | gdal | 148115fcc40f1651a5d15fa34c9a8c528e7147bb | https://github.com/OSGeo/gdal | https://github.com/OSGeo/gdal/commit/148115fcc40f1651a5d15fa34c9a8c528e7147bb | OGRExpatRealloc(): fix double-free when size to allocate is above the default 10MB threshold. Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=16178. Credit to OSS Fuzz | 0 | static void* OGRExpatRealloc( void *ptr, size_t size )
{
if( CanAlloc(size) )
return realloc(ptr, size);
return nullptr;
} | 294,555,905,023,825,260,000,000,000,000,000,000,000 | ogr_expat.cpp | 236,288,052,023,632,100,000,000,000,000,000,000,000 | [
"CWE-415"
] | CVE-2019-17545 | GDAL through 3.0.1 has a poolDestroy double free in OGRExpatRealloc in ogr/ogr_expat.cpp when the 10MB threshold is exceeded. | https://nvd.nist.gov/vuln/detail/CVE-2019-17545 |
203,623 | linux | c278c253f3d992c6994d08aa0efb2b6806ca396f | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c278c253f3d992c6994d08aa0efb2b6806ca396f | net: arc_emac: fix koops caused by sk_buff free
There is a race between arc_emac_tx() and arc_emac_tx_clean().
sk_buff got freed by arc_emac_tx_clean() while arc_emac_tx()
submitting sk_buff.
In order to free sk_buff arc_emac_tx_clean() checks:
if ((info & FOR_EMAC) || !txbd->data)
break;
...
dev_... | 1 | static void arc_emac_tx_clean(struct net_device *ndev)
{
struct arc_emac_priv *priv = netdev_priv(ndev);
struct net_device_stats *stats = &ndev->stats;
unsigned int i;
for (i = 0; i < TX_BD_NUM; i++) {
unsigned int *txbd_dirty = &priv->txbd_dirty;
struct arc_emac_bd *txbd = &priv->txbd[*txbd_dirty];
struct b... | 150,569,664,597,589,110,000,000,000,000,000,000,000 | emac_main.c | 128,785,670,229,970,200,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2016-10906 | An issue was discovered in drivers/net/ethernet/arc/emac_main.c in the Linux kernel before 4.5. A use-after-free is caused by a race condition between the functions arc_emac_tx and arc_emac_tx_clean. | https://nvd.nist.gov/vuln/detail/CVE-2016-10906 |
345,237 | linux | c278c253f3d992c6994d08aa0efb2b6806ca396f | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c278c253f3d992c6994d08aa0efb2b6806ca396f | net: arc_emac: fix koops caused by sk_buff free
There is a race between arc_emac_tx() and arc_emac_tx_clean().
sk_buff got freed by arc_emac_tx_clean() while arc_emac_tx()
submitting sk_buff.
In order to free sk_buff arc_emac_tx_clean() checks:
if ((info & FOR_EMAC) || !txbd->data)
break;
...
dev_... | 0 | static void arc_emac_tx_clean(struct net_device *ndev)
{
struct arc_emac_priv *priv = netdev_priv(ndev);
struct net_device_stats *stats = &ndev->stats;
unsigned int i;
for (i = 0; i < TX_BD_NUM; i++) {
unsigned int *txbd_dirty = &priv->txbd_dirty;
struct arc_emac_bd *txbd = &priv->txbd[*txbd_dirty];
struct b... | 203,884,859,878,983,600,000,000,000,000,000,000,000 | emac_main.c | 170,585,828,806,776,740,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2016-10906 | An issue was discovered in drivers/net/ethernet/arc/emac_main.c in the Linux kernel before 4.5. A use-after-free is caused by a race condition between the functions arc_emac_tx and arc_emac_tx_clean. | https://nvd.nist.gov/vuln/detail/CVE-2016-10906 |
203,624 | linux | c278c253f3d992c6994d08aa0efb2b6806ca396f | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c278c253f3d992c6994d08aa0efb2b6806ca396f | net: arc_emac: fix koops caused by sk_buff free
There is a race between arc_emac_tx() and arc_emac_tx_clean().
sk_buff got freed by arc_emac_tx_clean() while arc_emac_tx()
submitting sk_buff.
In order to free sk_buff arc_emac_tx_clean() checks:
if ((info & FOR_EMAC) || !txbd->data)
break;
...
dev_... | 1 | static int arc_emac_tx(struct sk_buff *skb, struct net_device *ndev)
{
struct arc_emac_priv *priv = netdev_priv(ndev);
unsigned int len, *txbd_curr = &priv->txbd_curr;
struct net_device_stats *stats = &ndev->stats;
__le32 *info = &priv->txbd[*txbd_curr].info;
dma_addr_t addr;
if (skb_padto(skb, ETH_ZLEN))
retu... | 209,596,075,106,628,820,000,000,000,000,000,000,000 | emac_main.c | 128,785,670,229,970,200,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2016-10906 | An issue was discovered in drivers/net/ethernet/arc/emac_main.c in the Linux kernel before 4.5. A use-after-free is caused by a race condition between the functions arc_emac_tx and arc_emac_tx_clean. | https://nvd.nist.gov/vuln/detail/CVE-2016-10906 |
345,230 | linux | c278c253f3d992c6994d08aa0efb2b6806ca396f | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c278c253f3d992c6994d08aa0efb2b6806ca396f | net: arc_emac: fix koops caused by sk_buff free
There is a race between arc_emac_tx() and arc_emac_tx_clean().
sk_buff got freed by arc_emac_tx_clean() while arc_emac_tx()
submitting sk_buff.
In order to free sk_buff arc_emac_tx_clean() checks:
if ((info & FOR_EMAC) || !txbd->data)
break;
...
dev_... | 0 | static int arc_emac_tx(struct sk_buff *skb, struct net_device *ndev)
{
struct arc_emac_priv *priv = netdev_priv(ndev);
unsigned int len, *txbd_curr = &priv->txbd_curr;
struct net_device_stats *stats = &ndev->stats;
__le32 *info = &priv->txbd[*txbd_curr].info;
dma_addr_t addr;
if (skb_padto(skb, ETH_ZLEN))
retu... | 163,851,604,475,322,780,000,000,000,000,000,000,000 | emac_main.c | 170,585,828,806,776,740,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2016-10906 | An issue was discovered in drivers/net/ethernet/arc/emac_main.c in the Linux kernel before 4.5. A use-after-free is caused by a race condition between the functions arc_emac_tx and arc_emac_tx_clean. | https://nvd.nist.gov/vuln/detail/CVE-2016-10906 |
203,811 | evince | 234f034a4d15cd46dd556f4945f99fbd57ef5f15 | https://github.com/GNOME/evince | https://gitlab.gnome.org/GNOME/evince/commit/234f034a4d15cd46dd556f4945f99fbd57ef5f15 | tiff: Handle failure from TIFFReadRGBAImageOriented
The TIFFReadRGBAImageOriented function returns zero if it was unable to
read the image. Return NULL in this case instead of displaying
uninitialized memory.
Fixes #1129 | 1 | tiff_document_render (EvDocument *document,
EvRenderContext *rc)
{
TiffDocument *tiff_document = TIFF_DOCUMENT (document);
int width, height;
int scaled_width, scaled_height;
float x_res, y_res;
gint rowstride, bytes;
guchar *pixels = NULL;
guchar *p;
int orientation;
cairo_surface_t *surface;
ca... | 52,463,076,965,098,220,000,000,000,000,000,000,000 | tiff-document.c | 27,835,589,638,085,300,000,000,000,000,000,000,000 | [
"CWE-754"
] | CVE-2019-11459 | The tiff_document_render() and tiff_document_get_thumbnail() functions in the TIFF document backend in GNOME Evince through 3.32.0 did not handle errors from TIFFReadRGBAImageOriented(), leading to uninitialized memory use when processing certain TIFF image files. | https://nvd.nist.gov/vuln/detail/CVE-2019-11459 |
345,946 | evince | 234f034a4d15cd46dd556f4945f99fbd57ef5f15 | https://github.com/GNOME/evince | https://gitlab.gnome.org/GNOME/evince/commit/234f034a4d15cd46dd556f4945f99fbd57ef5f15 | tiff: Handle failure from TIFFReadRGBAImageOriented
The TIFFReadRGBAImageOriented function returns zero if it was unable to
read the image. Return NULL in this case instead of displaying
uninitialized memory.
Fixes #1129 | 0 | tiff_document_render (EvDocument *document,
EvRenderContext *rc)
{
TiffDocument *tiff_document = TIFF_DOCUMENT (document);
int width, height;
int scaled_width, scaled_height;
float x_res, y_res;
gint rowstride, bytes;
guchar *pixels = NULL;
guchar *p;
int orientation;
cairo_surface_t *surface;
ca... | 272,163,112,520,658,780,000,000,000,000,000,000,000 | tiff-document.c | 42,179,381,584,053,470,000,000,000,000,000,000,000 | [
"CWE-754"
] | CVE-2019-11459 | The tiff_document_render() and tiff_document_get_thumbnail() functions in the TIFF document backend in GNOME Evince through 3.32.0 did not handle errors from TIFFReadRGBAImageOriented(), leading to uninitialized memory use when processing certain TIFF image files. | https://nvd.nist.gov/vuln/detail/CVE-2019-11459 |
203,812 | evince | 234f034a4d15cd46dd556f4945f99fbd57ef5f15 | https://github.com/GNOME/evince | https://gitlab.gnome.org/GNOME/evince/commit/234f034a4d15cd46dd556f4945f99fbd57ef5f15 | tiff: Handle failure from TIFFReadRGBAImageOriented
The TIFFReadRGBAImageOriented function returns zero if it was unable to
read the image. Return NULL in this case instead of displaying
uninitialized memory.
Fixes #1129 | 1 | tiff_document_get_thumbnail (EvDocument *document,
EvRenderContext *rc)
{
TiffDocument *tiff_document = TIFF_DOCUMENT (document);
int width, height;
int scaled_width, scaled_height;
float x_res, y_res;
gint rowstride, bytes;
guchar *pixels = NULL;
GdkPixbuf *pixbuf;
GdkPixbuf *scaled_pixbuf;
GdkPi... | 232,030,955,257,414,950,000,000,000,000,000,000,000 | tiff-document.c | 27,835,589,638,085,300,000,000,000,000,000,000,000 | [
"CWE-754"
] | CVE-2019-11459 | The tiff_document_render() and tiff_document_get_thumbnail() functions in the TIFF document backend in GNOME Evince through 3.32.0 did not handle errors from TIFFReadRGBAImageOriented(), leading to uninitialized memory use when processing certain TIFF image files. | https://nvd.nist.gov/vuln/detail/CVE-2019-11459 |
345,947 | evince | 234f034a4d15cd46dd556f4945f99fbd57ef5f15 | https://github.com/GNOME/evince | https://gitlab.gnome.org/GNOME/evince/commit/234f034a4d15cd46dd556f4945f99fbd57ef5f15 | tiff: Handle failure from TIFFReadRGBAImageOriented
The TIFFReadRGBAImageOriented function returns zero if it was unable to
read the image. Return NULL in this case instead of displaying
uninitialized memory.
Fixes #1129 | 0 | tiff_document_get_thumbnail (EvDocument *document,
EvRenderContext *rc)
{
TiffDocument *tiff_document = TIFF_DOCUMENT (document);
int width, height;
int scaled_width, scaled_height;
float x_res, y_res;
gint rowstride, bytes;
guchar *pixels = NULL;
GdkPixbuf *pixbuf;
GdkPixbuf *scaled_pixbuf;
GdkPi... | 319,561,925,173,337,860,000,000,000,000,000,000,000 | tiff-document.c | 42,179,381,584,053,470,000,000,000,000,000,000,000 | [
"CWE-754"
] | CVE-2019-11459 | The tiff_document_render() and tiff_document_get_thumbnail() functions in the TIFF document backend in GNOME Evince through 3.32.0 did not handle errors from TIFFReadRGBAImageOriented(), leading to uninitialized memory use when processing certain TIFF image files. | https://nvd.nist.gov/vuln/detail/CVE-2019-11459 |
203,903 | ImageMagick | f28e9e56e1b56d4e1f09d2a56d70892ae295d6a4 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/f28e9e56e1b56d4e1f09d2a56d70892ae295d6a4 | https://github.com/ImageMagick/ImageMagick/issues/1756 | 1 | MagickExport MagickBooleanType SetImageExtent(Image *image,const size_t columns,
const size_t rows,ExceptionInfo *exception)
{
if ((columns == 0) || (rows == 0))
ThrowBinaryException(ImageError,"NegativeOrZeroImageSize",image->filename);
image->columns=columns;
image->rows=rows;
if ((image->depth == 0) ||... | 102,946,401,776,037,100,000,000,000,000,000,000,000 | image.c | 141,446,298,785,891,320,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2020-27755 | in SetImageExtent() of /MagickCore/image.c, an incorrect image depth size can cause a memory leak because the code which checks for the proper image depth size does not reset the size in the event there is an invalid size. The patch resets the depth to a proper size before throwing an exception. The memory leak can be ... | https://nvd.nist.gov/vuln/detail/CVE-2020-27755 |
346,477 | ImageMagick | f28e9e56e1b56d4e1f09d2a56d70892ae295d6a4 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/f28e9e56e1b56d4e1f09d2a56d70892ae295d6a4 | https://github.com/ImageMagick/ImageMagick/issues/1756 | 0 | MagickExport MagickBooleanType SetImageExtent(Image *image,const size_t columns,
const size_t rows,ExceptionInfo *exception)
{
if ((columns == 0) || (rows == 0))
ThrowBinaryException(ImageError,"NegativeOrZeroImageSize",image->filename);
image->columns=columns;
image->rows=rows;
if (image->depth == 0)
... | 272,749,559,762,139,000,000,000,000,000,000,000,000 | image.c | 29,733,140,564,459,163,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2020-27755 | in SetImageExtent() of /MagickCore/image.c, an incorrect image depth size can cause a memory leak because the code which checks for the proper image depth size does not reset the size in the event there is an invalid size. The patch resets the depth to a proper size before throwing an exception. The memory leak can be ... | https://nvd.nist.gov/vuln/detail/CVE-2020-27755 |
203,904 | spice-common | bb15d4815ab586b4c4a20f4a565970a44824c42c | https://gitlab.freedesktop.org/spice/spice-common | https://gitlab.freedesktop.org/spice/spice-common/commit/bb15d4815ab586b4c4a20f4a565970a44824c42c | Fix flexible array buffer overflow
This is kind of a DoS, possibly flexible array in the protocol
causes the network size check to be ignored due to integer overflows.
The size of flexible array is computed as (message_end - position),
then this size is added to the number of bytes before the array and
this number is... | 1 | int main(int argc G_GNUC_UNUSED, char **argv G_GNUC_UNUSED)
{
SpiceMarshaller *marshaller;
SpiceMsgMainShortDataSubMarshall *msg;
size_t len, msg_len;
int free_res;
uint8_t *data;
message_destructor_t free_message;
msg = g_new0(SpiceMsgMainShortDataSubMarshall, 1);
msg->data = g_new(uin... | 98,807,849,529,275,900,000,000,000,000,000,000,000 | test-marshallers.c | 233,413,353,654,043,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2018-10873 | A vulnerability was discovered in SPICE before version 0.14.1 where the generated code used for demarshalling messages lacked sufficient bounds checks. A malicious client or server, after authentication, could send specially crafted messages to its peer which would result in a crash or, potentially, other impacts. | https://nvd.nist.gov/vuln/detail/CVE-2018-10873 |
346,479 | spice-common | bb15d4815ab586b4c4a20f4a565970a44824c42c | https://gitlab.freedesktop.org/spice/spice-common | https://gitlab.freedesktop.org/spice/spice-common/commit/bb15d4815ab586b4c4a20f4a565970a44824c42c | Fix flexible array buffer overflow
This is kind of a DoS, possibly flexible array in the protocol
causes the network size check to be ignored due to integer overflows.
The size of flexible array is computed as (message_end - position),
then this size is added to the number of bytes before the array and
this number is... | 0 | int main(int argc G_GNUC_UNUSED, char **argv G_GNUC_UNUSED)
{
SpiceMarshaller *marshaller;
SpiceMsgMainShortDataSubMarshall *msg;
size_t len, msg_len;
int free_res;
uint8_t *data;
message_destructor_t free_message;
msg = g_new0(SpiceMsgMainShortDataSubMarshall, 1);
msg->data = g_new(uin... | 120,881,196,676,812,850,000,000,000,000,000,000,000 | test-marshallers.c | 77,558,600,188,555,360,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2018-10873 | A vulnerability was discovered in SPICE before version 0.14.1 where the generated code used for demarshalling messages lacked sufficient bounds checks. A malicious client or server, after authentication, could send specially crafted messages to its peer which would result in a crash or, potentially, other impacts. | https://nvd.nist.gov/vuln/detail/CVE-2018-10873 |
203,908 | dpdk | 6442c329b9d2ded0f44b27d2016aaba8ba5844c5 | https://github.com/DPDK/dpdk | https://github.com/DPDK/dpdk/commit/6442c329b9d2ded0f44b27d2016aaba8ba5844c5 | vhost: fix queue number check when setting inflight FD
In function vhost_user_set_inflight_fd, queue number in inflight
message is used to access virtqueue. However, queue number could
be larger than VHOST_MAX_VRING and cause write OOB as this number
will be used to write inflight info in virtqueue structure. This
pat... | 1 | vhost_user_check_and_alloc_queue_pair(struct virtio_net *dev,
struct vhu_msg_context *ctx)
{
uint32_t vring_idx;
switch (ctx->msg.request.master) {
case VHOST_USER_SET_VRING_KICK:
case VHOST_USER_SET_VRING_CALL:
case VHOST_USER_SET_VRING_ERR:
vring_idx = ctx->msg.payload.u64 & VHOST_USER_VRING_IDX_MASK;
br... | 272,192,373,818,864,540,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2021-3839 | A flaw was found in the vhost library in DPDK. Function vhost_user_set_inflight_fd() does not validate `msg->payload.inflight.num_queues`, possibly causing out-of-bounds memory read/write. Any software using DPDK vhost library may crash as a result of this vulnerability. | https://nvd.nist.gov/vuln/detail/CVE-2021-3839 |
346,597 | dpdk | 6442c329b9d2ded0f44b27d2016aaba8ba5844c5 | https://github.com/DPDK/dpdk | https://github.com/DPDK/dpdk/commit/6442c329b9d2ded0f44b27d2016aaba8ba5844c5 | vhost: fix queue number check when setting inflight FD
In function vhost_user_set_inflight_fd, queue number in inflight
message is used to access virtqueue. However, queue number could
be larger than VHOST_MAX_VRING and cause write OOB as this number
will be used to write inflight info in virtqueue structure. This
pat... | 0 | vhost_user_check_and_alloc_queue_pair(struct virtio_net *dev,
struct vhu_msg_context *ctx)
{
uint32_t vring_idx;
switch (ctx->msg.request.master) {
case VHOST_USER_SET_VRING_KICK:
case VHOST_USER_SET_VRING_CALL:
case VHOST_USER_SET_VRING_ERR:
vring_idx = ctx->msg.payload.u64 & VHOST_USER_VRING_IDX_MASK;
br... | 75,785,573,116,999,760,000,000,000,000,000,000,000 | vhost_user.c | 99,784,894,649,346,630,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-3839 | A flaw was found in the vhost library in DPDK. Function vhost_user_set_inflight_fd() does not validate `msg->payload.inflight.num_queues`, possibly causing out-of-bounds memory read/write. Any software using DPDK vhost library may crash as a result of this vulnerability. | https://nvd.nist.gov/vuln/detail/CVE-2021-3839 |
203,970 | krb5 | d775c95af7606a51bf79547a94fa52ddd1cb7f49 | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/d775c95af7606a51bf79547a94fa52ddd1cb7f49 | Fix KDC null deref on TGS inner body null server
After the KDC decodes a FAST inner body, it does not check for a null
server. Prior to commit 39548a5b17bbda9eeb63625a201cfd19b9de1c5b this
would typically result in an error from krb5_unparse_name(), but with
the addition of get_local_tgt() it results in a null derefe... | 1 | process_tgs_req(krb5_kdc_req *request, krb5_data *pkt,
const krb5_fulladdr *from, kdc_realm_t *kdc_active_realm,
krb5_data **response)
{
krb5_keyblock * subkey = 0;
krb5_keyblock *header_key = NULL;
krb5_keyblock *stkt_server_key = NULL;
krb5_keyblock *subject_key;
kr... | 314,418,701,667,240,270,000,000,000,000,000,000,000 | do_tgs_req.c | 229,204,698,431,064,940,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2021-37750 | The Key Distribution Center (KDC) in MIT Kerberos 5 (aka krb5) before 1.18.5 and 1.19.x before 1.19.3 has a NULL pointer dereference in kdc/do_tgs_req.c via a FAST inner body that lacks a server field. | https://nvd.nist.gov/vuln/detail/CVE-2021-37750 |
347,922 | krb5 | d775c95af7606a51bf79547a94fa52ddd1cb7f49 | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/d775c95af7606a51bf79547a94fa52ddd1cb7f49 | Fix KDC null deref on TGS inner body null server
After the KDC decodes a FAST inner body, it does not check for a null
server. Prior to commit 39548a5b17bbda9eeb63625a201cfd19b9de1c5b this
would typically result in an error from krb5_unparse_name(), but with
the addition of get_local_tgt() it results in a null derefe... | 0 | process_tgs_req(krb5_kdc_req *request, krb5_data *pkt,
const krb5_fulladdr *from, kdc_realm_t *kdc_active_realm,
krb5_data **response)
{
krb5_keyblock * subkey = 0;
krb5_keyblock *header_key = NULL;
krb5_keyblock *stkt_server_key = NULL;
krb5_keyblock *subject_key;
kr... | 2,163,243,578,792,509,000,000,000,000,000,000,000 | do_tgs_req.c | 151,688,542,635,645,600,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2021-37750 | The Key Distribution Center (KDC) in MIT Kerberos 5 (aka krb5) before 1.18.5 and 1.19.x before 1.19.3 has a NULL pointer dereference in kdc/do_tgs_req.c via a FAST inner body that lacks a server field. | https://nvd.nist.gov/vuln/detail/CVE-2021-37750 |
203,971 | gst-plugins-base | 2fdccfd64fc609e44e9c4b8eed5bfdc0ab9c9095 | https://github.com/GStreamer/gst-plugins-base | https://github.com/GStreamer/gst-plugins-base/commit/2fdccfd64fc609e44e9c4b8eed5bfdc0ab9c9095 | typefind: bounds check windows ico detection
Fixes out of bounds read
https://bugzilla.gnome.org/show_bug.cgi?id=774902 | 1 | windows_icon_typefind (GstTypeFind * find, gpointer user_data)
{
const guint8 *data;
gint64 datalen;
guint16 type, nimages;
gint32 size, offset;
datalen = gst_type_find_get_length (find);
if ((data = gst_type_find_peek (find, 0, 6)) == NULL)
return;
/* header - simple and not enough to rely on it al... | 243,585,266,860,916,050,000,000,000,000,000,000,000 | gsttypefindfunctions.c | 40,115,388,986,360,230,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2016-9811 | The windows_icon_typefind function in gst-plugins-base in GStreamer before 1.10.2, when G_SLICE is set to always-malloc, allows remote attackers to cause a denial of service (out-of-bounds read) via a crafted ico file. | https://nvd.nist.gov/vuln/detail/CVE-2016-9811 |
348,017 | gst-plugins-base | 2fdccfd64fc609e44e9c4b8eed5bfdc0ab9c9095 | https://github.com/GStreamer/gst-plugins-base | https://github.com/GStreamer/gst-plugins-base/commit/2fdccfd64fc609e44e9c4b8eed5bfdc0ab9c9095 | typefind: bounds check windows ico detection
Fixes out of bounds read
https://bugzilla.gnome.org/show_bug.cgi?id=774902 | 0 | windows_icon_typefind (GstTypeFind * find, gpointer user_data)
{
const guint8 *data;
gint64 datalen;
guint16 type, nimages;
gint32 size, offset;
datalen = gst_type_find_get_length (find);
if (datalen < 18)
return;
if ((data = gst_type_find_peek (find, 0, 6)) == NULL)
return;
/* header - simple... | 155,231,360,524,088,500,000,000,000,000,000,000,000 | gsttypefindfunctions.c | 212,994,739,353,016,570,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2016-9811 | The windows_icon_typefind function in gst-plugins-base in GStreamer before 1.10.2, when G_SLICE is set to always-malloc, allows remote attackers to cause a denial of service (out-of-bounds read) via a crafted ico file. | https://nvd.nist.gov/vuln/detail/CVE-2016-9811 |
203,975 | bind9 | 6ed167ad0a647dff20c8cb08c944a7967df2d415 | https://github.com/isc-projects/bind9 | https://gitlab.isc.org/isc-projects/bind9/-/commit/6ed167ad0a647dff20c8cb08c944a7967df2d415 | Always keep a copy of the message
this allows it to be available even when dns_message_parse()
returns a error. | 1 | dns_message_parse(dns_message_t *msg, isc_buffer_t *source,
unsigned int options)
{
isc_region_t r;
dns_decompress_t dctx;
isc_result_t ret;
uint16_t tmpflags;
isc_buffer_t origsource;
bool seen_problem;
bool ignore_tc;
REQUIRE(DNS_MESSAGE_VALID(msg));
REQUIRE(source != NULL);
REQUIRE(msg->from_to_wire =... | 247,925,502,280,138,240,000,000,000,000,000,000,000 | message.c | 67,336,047,159,629,040,000,000,000,000,000,000,000 | [
"CWE-617"
] | CVE-2020-8622 | In BIND 9.0.0 -> 9.11.21, 9.12.0 -> 9.16.5, 9.17.0 -> 9.17.3, also affects 9.9.3-S1 -> 9.11.21-S1 of the BIND 9 Supported Preview Edition, An attacker on the network path for a TSIG-signed request, or operating the server receiving the TSIG-signed request, could send a truncated response to that request, triggering an ... | https://nvd.nist.gov/vuln/detail/CVE-2020-8622 |
348,162 | bind9 | 6ed167ad0a647dff20c8cb08c944a7967df2d415 | https://github.com/isc-projects/bind9 | https://gitlab.isc.org/isc-projects/bind9/-/commit/6ed167ad0a647dff20c8cb08c944a7967df2d415 | Always keep a copy of the message
this allows it to be available even when dns_message_parse()
returns a error. | 0 | dns_message_parse(dns_message_t *msg, isc_buffer_t *source,
unsigned int options)
{
isc_region_t r;
dns_decompress_t dctx;
isc_result_t ret;
uint16_t tmpflags;
isc_buffer_t origsource;
bool seen_problem;
bool ignore_tc;
REQUIRE(DNS_MESSAGE_VALID(msg));
REQUIRE(source != NULL);
REQUIRE(msg->from_to_wire =... | 106,654,624,665,304,360,000,000,000,000,000,000,000 | message.c | 228,259,023,266,091,330,000,000,000,000,000,000,000 | [
"CWE-617"
] | CVE-2020-8622 | In BIND 9.0.0 -> 9.11.21, 9.12.0 -> 9.16.5, 9.17.0 -> 9.17.3, also affects 9.9.3-S1 -> 9.11.21-S1 of the BIND 9 Supported Preview Edition, An attacker on the network path for a TSIG-signed request, or operating the server receiving the TSIG-signed request, could send a truncated response to that request, triggering an ... | https://nvd.nist.gov/vuln/detail/CVE-2020-8622 |
203,977 | oniguruma | 6eb4aca6a7f2f60f473580576d86686ed6a6ebec | https://github.com/kkos/oniguruma | https://github.com/kkos/oniguruma/commit/6eb4aca6a7f2f60f473580576d86686ed6a6ebec | fix #162: heap-buffer-overflow in fetch_interval_quantifier due to double PFETCH | 1 | fetch_interval_quantifier(UChar** src, UChar* end, PToken* tok, ScanEnv* env)
{
int low, up, syn_allow, non_low = 0;
int r = 0;
OnigCodePoint c;
OnigEncoding enc = env->enc;
UChar* p = *src;
PFETCH_READY;
syn_allow = IS_SYNTAX_BV(env->syntax, ONIG_SYN_ALLOW_INVALID_INTERVAL);
if (PEND) {
if (syn_a... | 231,445,382,448,830,800,000,000,000,000,000,000,000 | regparse.c | 82,538,838,162,306,370,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2019-19204 | An issue was discovered in Oniguruma 6.x before 6.9.4_rc2. In the function fetch_interval_quantifier (formerly known as fetch_range_quantifier) in regparse.c, PFETCH is called without checking PEND. This leads to a heap-based buffer over-read. | https://nvd.nist.gov/vuln/detail/CVE-2019-19204 |
348,238 | oniguruma | 6eb4aca6a7f2f60f473580576d86686ed6a6ebec | https://github.com/kkos/oniguruma | https://github.com/kkos/oniguruma/commit/6eb4aca6a7f2f60f473580576d86686ed6a6ebec | fix #162: heap-buffer-overflow in fetch_interval_quantifier due to double PFETCH | 0 | fetch_interval_quantifier(UChar** src, UChar* end, PToken* tok, ScanEnv* env)
{
int low, up, syn_allow, non_low = 0;
int r = 0;
OnigCodePoint c;
OnigEncoding enc = env->enc;
UChar* p = *src;
PFETCH_READY;
syn_allow = IS_SYNTAX_BV(env->syntax, ONIG_SYN_ALLOW_INVALID_INTERVAL);
if (PEND) {
if (syn_a... | 151,248,511,285,907,730,000,000,000,000,000,000,000 | regparse.c | 337,509,209,670,944,100,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2019-19204 | An issue was discovered in Oniguruma 6.x before 6.9.4_rc2. In the function fetch_interval_quantifier (formerly known as fetch_range_quantifier) in regparse.c, PFETCH is called without checking PEND. This leads to a heap-based buffer over-read. | https://nvd.nist.gov/vuln/detail/CVE-2019-19204 |
203,981 | linux | 0f4f199443faca715523b0659aa536251d8b978f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0f4f199443faca715523b0659aa536251d8b978f | iwlwifi: pcie: fix memory leaks in iwl_pcie_ctxt_info_gen3_init
In iwl_pcie_ctxt_info_gen3_init there are cases that the allocated dma
memory is leaked in case of error.
DMA memories prph_scratch, prph_info, and ctxt_info_gen3 are allocated
and initialized to be later assigned to trans_pcie. But in any error case
bef... | 1 | int iwl_pcie_ctxt_info_gen3_init(struct iwl_trans *trans,
const struct fw_img *fw)
{
struct iwl_trans_pcie *trans_pcie = IWL_TRANS_GET_PCIE_TRANS(trans);
struct iwl_context_info_gen3 *ctxt_info_gen3;
struct iwl_prph_scratch *prph_scratch;
struct iwl_prph_scratch_ctrl_cfg *prph_sc_ctrl;
struct iwl_prph_info *p... | 242,185,707,525,481,870,000,000,000,000,000,000,000 | ctxt-info-gen3.c | 31,598,176,394,673,764,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2019-19059 | Multiple memory leaks in the iwl_pcie_ctxt_info_gen3_init() function in drivers/net/wireless/intel/iwlwifi/pcie/ctxt-info-gen3.c in the Linux kernel through 5.3.11 allow attackers to cause a denial of service (memory consumption) by triggering iwl_pcie_init_fw_sec() or dma_alloc_coherent() failures, aka CID-0f4f199443f... | https://nvd.nist.gov/vuln/detail/CVE-2019-19059 |
348,448 | linux | 0f4f199443faca715523b0659aa536251d8b978f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0f4f199443faca715523b0659aa536251d8b978f | iwlwifi: pcie: fix memory leaks in iwl_pcie_ctxt_info_gen3_init
In iwl_pcie_ctxt_info_gen3_init there are cases that the allocated dma
memory is leaked in case of error.
DMA memories prph_scratch, prph_info, and ctxt_info_gen3 are allocated
and initialized to be later assigned to trans_pcie. But in any error case
bef... | 0 | int iwl_pcie_ctxt_info_gen3_init(struct iwl_trans *trans,
const struct fw_img *fw)
{
struct iwl_trans_pcie *trans_pcie = IWL_TRANS_GET_PCIE_TRANS(trans);
struct iwl_context_info_gen3 *ctxt_info_gen3;
struct iwl_prph_scratch *prph_scratch;
struct iwl_prph_scratch_ctrl_cfg *prph_sc_ctrl;
struct iwl_prph_info *p... | 198,712,361,890,178,070,000,000,000,000,000,000,000 | ctxt-info-gen3.c | 232,341,986,234,407,300,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2019-19059 | Multiple memory leaks in the iwl_pcie_ctxt_info_gen3_init() function in drivers/net/wireless/intel/iwlwifi/pcie/ctxt-info-gen3.c in the Linux kernel through 5.3.11 allow attackers to cause a denial of service (memory consumption) by triggering iwl_pcie_init_fw_sec() or dma_alloc_coherent() failures, aka CID-0f4f199443f... | https://nvd.nist.gov/vuln/detail/CVE-2019-19059 |
203,984 | linux | 13054abbaa4f1fd4e6f3b4b63439ec033b4c8035 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=13054abbaa4f1fd4e6f3b4b63439ec033b4c8035 | HID: debug: fix the ring buffer implementation
Ring buffer implementation in hid_debug_event() and hid_debug_events_read()
is strange allowing lost or corrupted data. After commit 717adfdaf147
("HID: debug: check length before copy_to_user()") it is possible to enter
an infinite loop in hid_debug_events_read() by prov... | 1 | static ssize_t hid_debug_events_read(struct file *file, char __user *buffer,
size_t count, loff_t *ppos)
{
struct hid_debug_list *list = file->private_data;
int ret = 0, len;
DECLARE_WAITQUEUE(wait, current);
mutex_lock(&list->read_mutex);
while (ret == 0) {
if (list->head == list->tail) {
add_wait_queue(&... | 29,731,328,370,802,475,000,000,000,000,000,000,000 | hid-debug.c | 53,188,215,045,641,990,000,000,000,000,000,000,000 | [
"CWE-835"
] | CVE-2019-3819 | A flaw was found in the Linux kernel in the function hid_debug_events_read() in drivers/hid/hid-debug.c file which may enter an infinite loop with certain parameters passed from a userspace. A local privileged user ("root") can cause a system lock up and a denial of service. Versions from v4.18 and newer are vulnerable... | https://nvd.nist.gov/vuln/detail/CVE-2019-3819 |
348,462 | linux | 13054abbaa4f1fd4e6f3b4b63439ec033b4c8035 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=13054abbaa4f1fd4e6f3b4b63439ec033b4c8035 | HID: debug: fix the ring buffer implementation
Ring buffer implementation in hid_debug_event() and hid_debug_events_read()
is strange allowing lost or corrupted data. After commit 717adfdaf147
("HID: debug: check length before copy_to_user()") it is possible to enter
an infinite loop in hid_debug_events_read() by prov... | 0 | static ssize_t hid_debug_events_read(struct file *file, char __user *buffer,
size_t count, loff_t *ppos)
{
struct hid_debug_list *list = file->private_data;
int ret = 0, copied;
DECLARE_WAITQUEUE(wait, current);
mutex_lock(&list->read_mutex);
if (kfifo_is_empty(&list->hid_debug_fifo)) {
add_wait_queue(&list->... | 34,766,508,214,412,970,000,000,000,000,000,000,000 | hid-debug.c | 70,384,487,501,794,070,000,000,000,000,000,000,000 | [
"CWE-835"
] | CVE-2019-3819 | A flaw was found in the Linux kernel in the function hid_debug_events_read() in drivers/hid/hid-debug.c file which may enter an infinite loop with certain parameters passed from a userspace. A local privileged user ("root") can cause a system lock up and a denial of service. Versions from v4.18 and newer are vulnerable... | https://nvd.nist.gov/vuln/detail/CVE-2019-3819 |
203,989 | stb | 5ba0baaa269b3fd681828e0e3b3ac0f1472eaf40 | https://github.com/nothings/stb | https://github.com/nothings/stb/commit/5ba0baaa269b3fd681828e0e3b3ac0f1472eaf40 | stb_image: Reject fractional JPEG component subsampling ratios
The component resamplers are not written to support this and I've
never seen it happen in a real (non-crafted) JPEG file so I'm
fine rejecting this as outright corrupt.
Fixes issue #1178. | 1 | static int stbi__process_frame_header(stbi__jpeg *z, int scan)
{
stbi__context *s = z->s;
int Lf,p,i,q, h_max=1,v_max=1,c;
Lf = stbi__get16be(s); if (Lf < 11) return stbi__err("bad SOF len","Corrupt JPEG"); // JPEG
p = stbi__get8(s); if (p != 8) return stbi__err("only 8-bit","JPEG format... | 324,944,188,515,566,600,000,000,000,000,000,000,000 | stb_image.h | 259,314,994,306,211,340,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-28021 | Buffer overflow vulnerability in function stbi__extend_receive in stb_image.h in stb 2.26 via a crafted JPEG file. | https://nvd.nist.gov/vuln/detail/CVE-2021-28021 |
349,036 | stb | 5ba0baaa269b3fd681828e0e3b3ac0f1472eaf40 | https://github.com/nothings/stb | https://github.com/nothings/stb/commit/5ba0baaa269b3fd681828e0e3b3ac0f1472eaf40 | stb_image: Reject fractional JPEG component subsampling ratios
The component resamplers are not written to support this and I've
never seen it happen in a real (non-crafted) JPEG file so I'm
fine rejecting this as outright corrupt.
Fixes issue #1178. | 0 | static int stbi__process_frame_header(stbi__jpeg *z, int scan)
{
stbi__context *s = z->s;
int Lf,p,i,q, h_max=1,v_max=1,c;
Lf = stbi__get16be(s); if (Lf < 11) return stbi__err("bad SOF len","Corrupt JPEG"); // JPEG
p = stbi__get8(s); if (p != 8) return stbi__err("only 8-bit","JPEG format... | 126,089,494,958,718,940,000,000,000,000,000,000,000 | stb_image.h | 101,931,493,667,071,330,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-28021 | Buffer overflow vulnerability in function stbi__extend_receive in stb_image.h in stb 2.26 via a crafted JPEG file. | https://nvd.nist.gov/vuln/detail/CVE-2021-28021 |
203,991 | sqlite | 57f7ece78410a8aae86aa4625fb7556897db384c | https://github.com/sqlite/sqlite | https://github.com/sqlite/sqlite/commit/57f7ece78410a8aae86aa4625fb7556897db384c | Fix a problem that comes up when using generated columns that evaluate to a
constant in an index and then making use of that index in a join.
FossilOrigin-Name: 8b12e95fec7ce6e0de82a04ca3dfcf1a8e62e233b7382aa28a8a9be6e862b1af | 1 | int sqlite3ExprCodeTarget(Parse *pParse, Expr *pExpr, int target){
Vdbe *v = pParse->pVdbe; /* The VM under construction */
int op; /* The opcode being coded */
int inReg = target; /* Results stored in register inReg */
int regFree1 = 0; /* If non-zero free this temporary regist... | 310,483,172,761,266,080,000,000,000,000,000,000,000 | expr.c | 192,167,213,098,004,530,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2019-19242 | SQLite 3.30.1 mishandles pExpr->y.pTab, as demonstrated by the TK_COLUMN case in sqlite3ExprCodeTarget in expr.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-19242 |
349,206 | sqlite | 57f7ece78410a8aae86aa4625fb7556897db384c | https://github.com/sqlite/sqlite | https://github.com/sqlite/sqlite/commit/57f7ece78410a8aae86aa4625fb7556897db384c | Fix a problem that comes up when using generated columns that evaluate to a
constant in an index and then making use of that index in a join.
FossilOrigin-Name: 8b12e95fec7ce6e0de82a04ca3dfcf1a8e62e233b7382aa28a8a9be6e862b1af | 0 | int sqlite3ExprCodeTarget(Parse *pParse, Expr *pExpr, int target){
Vdbe *v = pParse->pVdbe; /* The VM under construction */
int op; /* The opcode being coded */
int inReg = target; /* Results stored in register inReg */
int regFree1 = 0; /* If non-zero free this temporary regist... | 296,250,149,918,875,240,000,000,000,000,000,000,000 | expr.c | 286,600,823,016,277,520,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2019-19242 | SQLite 3.30.1 mishandles pExpr->y.pTab, as demonstrated by the TK_COLUMN case in sqlite3ExprCodeTarget in expr.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-19242 |
204,015 | libpng | 83f4c735c88e7f451541c1528d8043c31ba3b466 | https://github.com/glennrp/libpng | https://github.com/glennrp/libpng/commit/83f4c735c88e7f451541c1528d8043c31ba3b466 | [libpng16] Clean up coding style in png_handle_PLTE() | 1 | png_handle_PLTE(png_structrp png_ptr, png_inforp info_ptr, png_uint_32 length)
{
png_color palette[PNG_MAX_PALETTE_LENGTH];
int max_palette_length, num, i;
#ifdef PNG_POINTER_INDEXING_SUPPORTED
png_colorp pal_ptr;
#endif
png_debug(1, "in png_handle_PLTE");
if ((png_ptr->mode & PNG_HAVE_IHDR) == 0)
... | 113,696,798,552,189,080,000,000,000,000,000,000,000 | pngrutil.c | 266,793,719,447,046,300,000,000,000,000,000,000,000 | [
"CWE-120"
] | CVE-2015-8126 | Multiple buffer overflows in the (1) png_set_PLTE and (2) png_get_PLTE functions in libpng before 1.0.64, 1.1.x and 1.2.x before 1.2.54, 1.3.x and 1.4.x before 1.4.17, 1.5.x before 1.5.24, and 1.6.x before 1.6.19 allow remote attackers to cause a denial of service (application crash) or possibly have unspecified other ... | https://nvd.nist.gov/vuln/detail/CVE-2015-8126 |
349,245 | libpng | 83f4c735c88e7f451541c1528d8043c31ba3b466 | https://github.com/glennrp/libpng | https://github.com/glennrp/libpng/commit/83f4c735c88e7f451541c1528d8043c31ba3b466 | [libpng16] Clean up coding style in png_handle_PLTE() | 0 | png_handle_PLTE(png_structrp png_ptr, png_inforp info_ptr, png_uint_32 length)
{
png_color palette[PNG_MAX_PALETTE_LENGTH];
int max_palette_length, num, i;
#ifdef PNG_POINTER_INDEXING_SUPPORTED
png_colorp pal_ptr;
#endif
png_debug(1, "in png_handle_PLTE");
if ((png_ptr->mode & PNG_HAVE_IHDR) == 0)
... | 59,387,195,221,952,160,000,000,000,000,000,000,000 | pngrutil.c | 112,004,499,013,330,480,000,000,000,000,000,000,000 | [
"CWE-120"
] | CVE-2015-8126 | Multiple buffer overflows in the (1) png_set_PLTE and (2) png_get_PLTE functions in libpng before 1.0.64, 1.1.x and 1.2.x before 1.2.54, 1.3.x and 1.4.x before 1.4.17, 1.5.x before 1.5.24, and 1.6.x before 1.6.19 allow remote attackers to cause a denial of service (application crash) or possibly have unspecified other ... | https://nvd.nist.gov/vuln/detail/CVE-2015-8126 |
204,020 | w3m | a6257663824c63abb3c62c4dd62455fe6f63d958 | https://github.com/tats/w3m | https://github.com/tats/w3m/commit/a6257663824c63abb3c62c4dd62455fe6f63d958 | Prevent segfault with malformed table_alt
Bug-Debian: https://github.com/tats/w3m/issues/24 | 1 | do_refill(struct table *tbl, int row, int col, int maxlimit)
{
TextList *orgdata;
TextListItem *l;
struct readbuffer obuf;
struct html_feed_environ h_env;
struct environment envs[MAX_ENV_LEVEL];
int colspan, icell;
if (tbl->tabdata[row] == NULL || tbl->tabdata[row][col] == NULL)
return;
... | 44,013,139,628,165,925,000,000,000,000,000,000,000 | table.c | 249,522,111,250,133,320,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2016-9441 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31. w3m allows remote attackers to cause a denial of service (segmentation fault and crash) via a crafted HTML page. | https://nvd.nist.gov/vuln/detail/CVE-2016-9441 |
174,145 | w3m | 8354763b90490d4105695df52674d0fcef823e92 | https://github.com/tats/w3m | https://github.com/tats/w3m/commit/8354763b90490d4105695df52674d0fcef823e92 | Prevent negative indent value in feed_table_block_tag()
Bug-Debian: https://github.com/tats/w3m/issues/88 | 0 | do_refill(struct table *tbl, int row, int col, int maxlimit)
{
TextList *orgdata;
TextListItem *l;
struct readbuffer obuf;
struct html_feed_environ h_env;
struct environment envs[MAX_ENV_LEVEL];
int colspan, icell;
if (tbl->tabdata[row] == NULL || tbl->tabdata[row][col] == NULL)
return;
... | 79,285,233,680,286,760,000,000,000,000,000,000,000 | table.c | 48,265,608,758,374,150,000,000,000,000,000,000,000 | [
"CWE-835"
] | CVE-2018-6196 | w3m through 0.5.3 is prone to an infinite recursion flaw in HTMLlineproc0 because the feed_table_block_tag function in table.c does not prevent a negative indent value. | https://nvd.nist.gov/vuln/detail/CVE-2018-6196 |
204,061 | linux | 04c4f2ee3f68c9a4bf1653d15f1a9a435ae33f7a | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=04c4f2ee3f68c9a4bf1653d15f1a9a435ae33f7a | KVM: VMX: Don't use vcpu->run->internal.ndata as an array index
__vmx_handle_exit() uses vcpu->run->internal.ndata as an index for
an array access. Since vcpu->run is (can be) mapped to a user address
space with a writer permission, the 'ndata' could be updated by the
user process at anytime (the user process can set... | 1 | static int __vmx_handle_exit(struct kvm_vcpu *vcpu, fastpath_t exit_fastpath)
{
struct vcpu_vmx *vmx = to_vmx(vcpu);
union vmx_exit_reason exit_reason = vmx->exit_reason;
u32 vectoring_info = vmx->idt_vectoring_info;
u16 exit_handler_index;
/*
* Flush logged GPAs PML buffer, this will make dirty_bitmap more
*... | 186,624,720,975,592,150,000,000,000,000,000,000,000 | vmx.c | 269,564,098,713,093,160,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-3501 | A flaw was found in the Linux kernel in versions before 5.12. The value of internal.ndata, in the KVM API, is mapped to an array index, which can be updated by a user process at anytime which could lead to an out-of-bounds write. The highest threat from this vulnerability is to data integrity and system availability. | https://nvd.nist.gov/vuln/detail/CVE-2021-3501 |
350,420 | linux | 04c4f2ee3f68c9a4bf1653d15f1a9a435ae33f7a | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=04c4f2ee3f68c9a4bf1653d15f1a9a435ae33f7a | KVM: VMX: Don't use vcpu->run->internal.ndata as an array index
__vmx_handle_exit() uses vcpu->run->internal.ndata as an index for
an array access. Since vcpu->run is (can be) mapped to a user address
space with a writer permission, the 'ndata' could be updated by the
user process at anytime (the user process can set... | 0 | static int __vmx_handle_exit(struct kvm_vcpu *vcpu, fastpath_t exit_fastpath)
{
struct vcpu_vmx *vmx = to_vmx(vcpu);
union vmx_exit_reason exit_reason = vmx->exit_reason;
u32 vectoring_info = vmx->idt_vectoring_info;
u16 exit_handler_index;
/*
* Flush logged GPAs PML buffer, this will make dirty_bitmap more
*... | 37,941,075,957,131,433,000,000,000,000,000,000,000 | vmx.c | 220,173,518,058,065,270,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-3501 | A flaw was found in the Linux kernel in versions before 5.12. The value of internal.ndata, in the KVM API, is mapped to an array index, which can be updated by a user process at anytime which could lead to an out-of-bounds write. The highest threat from this vulnerability is to data integrity and system availability. | https://nvd.nist.gov/vuln/detail/CVE-2021-3501 |
204,064 | php-src | 344ff5dd4c538eaebea075f7705321f8b86d0b47 | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commitdiff;h=344ff5dd4c538eaebea075f7705321f8b86d0b47 | fixed fix #69975 wrt. ODBCVER < 0x0300 | 1 | int odbc_bindcols(odbc_result *result TSRMLS_DC)
{
RETCODE rc;
int i;
SQLSMALLINT colnamelen; /* Not used */
SQLLEN displaysize;
SQLUSMALLINT colfieldid;
int charextraalloc;
result->values = (odbc_result_value *) safe_emalloc(sizeof(odbc_result_value), result->numcols, 0);
result->longreadlen = ODBCG(... | 255,412,909,189,957,100,000,000,000,000,000,000,000 | php_odbc.c | 306,196,941,890,402,170,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2015-8879 | The odbc_bindcols function in ext/odbc/php_odbc.c in PHP before 5.6.12 mishandles driver behavior for SQL_WVARCHAR columns, which allows remote attackers to cause a denial of service (application crash) in opportunistic circumstances by leveraging use of the odbc_fetch_array function to access a certain type of Microso... | https://nvd.nist.gov/vuln/detail/CVE-2015-8879 |
350,703 | php-src | 344ff5dd4c538eaebea075f7705321f8b86d0b47 | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commitdiff;h=344ff5dd4c538eaebea075f7705321f8b86d0b47 | fixed fix #69975 wrt. ODBCVER < 0x0300 | 0 | int odbc_bindcols(odbc_result *result TSRMLS_DC)
{
RETCODE rc;
int i;
SQLSMALLINT colnamelen; /* Not used */
SQLLEN displaysize;
SQLUSMALLINT colfieldid;
int charextraalloc;
result->values = (odbc_result_value *) safe_emalloc(sizeof(odbc_result_value), result->numcols, 0);
result->longreadlen = ODBCG(... | 28,261,833,746,118,350,000,000,000,000,000,000,000 | php_odbc.c | 261,726,595,409,977,720,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2015-8879 | The odbc_bindcols function in ext/odbc/php_odbc.c in PHP before 5.6.12 mishandles driver behavior for SQL_WVARCHAR columns, which allows remote attackers to cause a denial of service (application crash) in opportunistic circumstances by leveraging use of the odbc_fetch_array function to access a certain type of Microso... | https://nvd.nist.gov/vuln/detail/CVE-2015-8879 |
204,067 | libvpx | 34d54b04e98dd0bac32e9aab0fbda0bf501bc742 | https://github.com/webmproject/libvpx | https://github.com/webmproject/libvpx/commit/34d54b04e98dd0bac32e9aab0fbda0bf501bc742 | update libwebm to libwebm-1.0.0.27-358-gdbf1d10
changelog:
https://chromium.googlesource.com/webm/libwebm/+log/libwebm-1.0.0.27-351-g9f23fbc..libwebm-1.0.0.27-358-gdbf1d10
Change-Id: I28a6b3ae02a53fb1f2029eee11e9449afb94c8e3 | 1 | long VideoTrack::Parse(Segment* pSegment, const Info& info,
long long element_start, long long element_size,
VideoTrack*& pResult) {
if (pResult)
return -1;
if (info.type != Track::kVideo)
return -1;
long long width = 0;
long long height = 0;
long long d... | 21,176,750,482,246,079,000,000,000,000,000,000,000 | mkvparser.cc | 11,418,977,260,316,773,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2019-9371 | In libvpx, there is a possible resource exhaustion due to improper input validation. This could lead to remote denial of service with no additional execution privileges needed. User interaction is needed for exploitation. Product: AndroidVersions: Android-10Android ID: A-132783254 | https://nvd.nist.gov/vuln/detail/CVE-2019-9371 |
350,893 | libvpx | 34d54b04e98dd0bac32e9aab0fbda0bf501bc742 | https://github.com/webmproject/libvpx | https://github.com/webmproject/libvpx/commit/34d54b04e98dd0bac32e9aab0fbda0bf501bc742 | update libwebm to libwebm-1.0.0.27-358-gdbf1d10
changelog:
https://chromium.googlesource.com/webm/libwebm/+log/libwebm-1.0.0.27-351-g9f23fbc..libwebm-1.0.0.27-358-gdbf1d10
Change-Id: I28a6b3ae02a53fb1f2029eee11e9449afb94c8e3 | 0 | long VideoTrack::Parse(Segment* pSegment, const Info& info,
long long element_start, long long element_size,
VideoTrack*& pResult) {
if (pResult)
return -1;
if (info.type != Track::kVideo)
return -1;
long long width = 0;
long long height = 0;
long long d... | 225,577,098,959,292,220,000,000,000,000,000,000,000 | mkvparser.cc | 120,349,953,275,244,100,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2019-9371 | In libvpx, there is a possible resource exhaustion due to improper input validation. This could lead to remote denial of service with no additional execution privileges needed. User interaction is needed for exploitation. Product: AndroidVersions: Android-10Android ID: A-132783254 | https://nvd.nist.gov/vuln/detail/CVE-2019-9371 |
204,068 | libxml2 | 0bcd05c5cd83dec3406c8f68b769b1d610c72f76 | https://github.com/GNOME/libxml2 | https://git.gnome.org/browse/libxml2/commit/?id=0bcd05c5cd83dec3406c8f68b769b1d610c72f76 | Heap-based buffer overread in htmlCurrentChar
For https://bugzilla.gnome.org/show_bug.cgi?id=758606
* parserInternals.c:
(xmlNextChar): Add an test to catch other issues on ctxt->input
corruption proactively.
For non-UTF-8 charsets, xmlNextChar() failed to check for the end
of the input buffer and would continuing re... | 1 | xmlNextChar(xmlParserCtxtPtr ctxt)
{
if ((ctxt == NULL) || (ctxt->instate == XML_PARSER_EOF) ||
(ctxt->input == NULL))
return;
if (ctxt->charset == XML_CHAR_ENCODING_UTF8) {
if ((*ctxt->input->cur == 0) &&
(xmlParserInputGrow(ctxt->input, INPUT_CHUNK) <= 0) &&
(c... | 18,885,006,305,171,136,000,000,000,000,000,000,000 | parserInternals.c | 165,320,828,923,553,500,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2016-1833 | The htmlCurrentChar function in libxml2 before 2.9.4, as used in Apple iOS before 9.3.2, OS X before 10.11.5, tvOS before 9.2.1, and watchOS before 2.2.1, allows remote attackers to cause a denial of service (heap-based buffer over-read) via a crafted XML document. | https://nvd.nist.gov/vuln/detail/CVE-2016-1833 |
351,044 | libxml2 | 0bcd05c5cd83dec3406c8f68b769b1d610c72f76 | https://github.com/GNOME/libxml2 | https://git.gnome.org/browse/libxml2/commit/?id=0bcd05c5cd83dec3406c8f68b769b1d610c72f76 | Heap-based buffer overread in htmlCurrentChar
For https://bugzilla.gnome.org/show_bug.cgi?id=758606
* parserInternals.c:
(xmlNextChar): Add an test to catch other issues on ctxt->input
corruption proactively.
For non-UTF-8 charsets, xmlNextChar() failed to check for the end
of the input buffer and would continuing re... | 0 | xmlNextChar(xmlParserCtxtPtr ctxt)
{
if ((ctxt == NULL) || (ctxt->instate == XML_PARSER_EOF) ||
(ctxt->input == NULL))
return;
if (!(VALID_CTXT(ctxt))) {
xmlErrInternal(ctxt, "Parser input data memory error\n", NULL);
ctxt->errNo = XML_ERR_INTERNAL_ERROR;
xmlStopParser(ctxt);
... | 301,052,085,686,848,400,000,000,000,000,000,000,000 | parserInternals.c | 58,981,992,463,121,090,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2016-1833 | The htmlCurrentChar function in libxml2 before 2.9.4, as used in Apple iOS before 9.3.2, OS X before 10.11.5, tvOS before 9.2.1, and watchOS before 2.2.1, allows remote attackers to cause a denial of service (heap-based buffer over-read) via a crafted XML document. | https://nvd.nist.gov/vuln/detail/CVE-2016-1833 |
204,078 | tidy-html5 | c18f27a58792f7fbd0b30a0ff50d6b40a82f940d | https://github.com/htacg/tidy-html5 | https://github.com/htacg/tidy-html5/commit/c18f27a58792f7fbd0b30a0ff50d6b40a82f940d | Issue #217 - avoid len going negative, ever... | 1 | static tmbstr ParseValue( TidyDocImpl* doc, ctmbstr name,
Bool foldCase, Bool *isempty, int *pdelim)
{
Lexer* lexer = doc->lexer;
int len = 0, start;
Bool seen_gt = no;
Bool munge = yes;
uint c, lastc, delim, quotewarning;
tmbstr value;
delim = (tmbchar) 0;
*pd... | 271,695,580,377,329,840,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2015-5522 | Heap-based buffer overflow in the ParseValue function in lexer.c in tidy before 4.9.31 allows remote attackers to cause a denial of service (crash) via vectors involving a command character in an href. | https://nvd.nist.gov/vuln/detail/CVE-2015-5522 |
351,498 | tidy-html5 | c18f27a58792f7fbd0b30a0ff50d6b40a82f940d | https://github.com/htacg/tidy-html5 | https://github.com/htacg/tidy-html5/commit/c18f27a58792f7fbd0b30a0ff50d6b40a82f940d | Issue #217 - avoid len going negative, ever... | 0 | static tmbstr ParseValue( TidyDocImpl* doc, ctmbstr name,
Bool foldCase, Bool *isempty, int *pdelim)
{
Lexer* lexer = doc->lexer;
int len = 0, start;
Bool seen_gt = no;
Bool munge = yes;
uint c, lastc, delim, quotewarning;
tmbstr value;
delim = (tmbchar) 0;
*pd... | 155,466,502,948,646,490,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2015-5522 | Heap-based buffer overflow in the ParseValue function in lexer.c in tidy before 4.9.31 allows remote attackers to cause a denial of service (crash) via vectors involving a command character in an href. | https://nvd.nist.gov/vuln/detail/CVE-2015-5522 |
204,099 | spice-vd_agent | 91caa9223857708475d29df1768208fed1675340 | https://github.com/freedesktop/spice-vd_agent | https://github.com/freedesktop/spice-vd_agent/commit/91caa9223857708475d29df1768208fed1675340 | Avoids unlimited agent connections
Limit the number of agents that can be connected.
Avoids reaching the maximum number of files in a process.
Beside one file descriptor per agent the daemon open just some
other fixed number of files.
This issue was reported by SUSE security team.
Signed-off-by: Frediano Ziglio <fre... | 1 | static gboolean udscs_server_accept_cb(GSocketService *service,
GSocketConnection *socket_conn,
GObject *source_object,
gpointer user_data)
{
struct udscs_server *server = user... | 42,260,523,929,278,800,000,000,000,000,000,000,000 | udscs.c | 23,082,790,634,740,113,000,000,000,000,000,000,000 | [
"CWE-770"
] | CVE-2020-25652 | A flaw was found in the spice-vdagentd daemon, where it did not properly handle client connections that can be established via the UNIX domain socket in `/run/spice-vdagentd/spice-vdagent-sock`. Any unprivileged local guest user could use this flaw to prevent legitimate agents from connecting to the spice-vdagentd daem... | https://nvd.nist.gov/vuln/detail/CVE-2020-25652 |
352,797 | spice-vd_agent | 91caa9223857708475d29df1768208fed1675340 | https://github.com/freedesktop/spice-vd_agent | https://github.com/freedesktop/spice-vd_agent/commit/91caa9223857708475d29df1768208fed1675340 | Avoids unlimited agent connections
Limit the number of agents that can be connected.
Avoids reaching the maximum number of files in a process.
Beside one file descriptor per agent the daemon open just some
other fixed number of files.
This issue was reported by SUSE security team.
Signed-off-by: Frediano Ziglio <fre... | 0 | static gboolean udscs_server_accept_cb(GSocketService *service,
GSocketConnection *socket_conn,
GObject *source_object,
gpointer user_data)
{
struct udscs_server *server = user... | 29,883,919,431,646,643,000,000,000,000,000,000,000 | udscs.c | 283,322,592,806,689,700,000,000,000,000,000,000,000 | [
"CWE-770"
] | CVE-2020-25652 | A flaw was found in the spice-vdagentd daemon, where it did not properly handle client connections that can be established via the UNIX domain socket in `/run/spice-vdagentd/spice-vdagent-sock`. Any unprivileged local guest user could use this flaw to prevent legitimate agents from connecting to the spice-vdagentd daem... | https://nvd.nist.gov/vuln/detail/CVE-2020-25652 |
204,100 | net | 66d42ed8b25b64eb63111a2b8582c5afc8bf1105 | https://git.kernel.org/cgit/linux/kernel/git/davem/net | https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=66d42ed8b25b64eb63111a2b8582c5afc8bf1105 | hdlc_ppp: add range checks in ppp_cp_parse_cr()
There are a couple bugs here:
1) If opt[1] is zero then this results in a forever loop. If the value
is less than 2 then it is invalid.
2) It assumes that "len" is more than sizeof(valid_accm) or 6 which can
result in memory corruption.
In the case of LCP_OPTION_... | 1 | static void ppp_cp_parse_cr(struct net_device *dev, u16 pid, u8 id,
unsigned int req_len, const u8 *data)
{
static u8 const valid_accm[6] = { LCP_OPTION_ACCM, 6, 0, 0, 0, 0 };
const u8 *opt;
u8 *out;
unsigned int len = req_len, nak_len = 0, rej_len = 0;
if (!(out = kmalloc(len, GFP_ATOMIC))) {
dev->stats... | 123,873,851,670,231,450,000,000,000,000,000,000,000 | hdlc_ppp.c | 98,840,581,769,596,840,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2020-25643 | A flaw was found in the HDLC_PPP module of the Linux kernel in versions before 5.9-rc7. Memory corruption and a read overflow is caused by improper input validation in the ppp_cp_parse_cr function which can cause the system to crash or cause a denial of service. The highest threat from this vulnerability is to data con... | https://nvd.nist.gov/vuln/detail/CVE-2020-25643 |
352,799 | net | 66d42ed8b25b64eb63111a2b8582c5afc8bf1105 | https://git.kernel.org/cgit/linux/kernel/git/davem/net | https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=66d42ed8b25b64eb63111a2b8582c5afc8bf1105 | hdlc_ppp: add range checks in ppp_cp_parse_cr()
There are a couple bugs here:
1) If opt[1] is zero then this results in a forever loop. If the value
is less than 2 then it is invalid.
2) It assumes that "len" is more than sizeof(valid_accm) or 6 which can
result in memory corruption.
In the case of LCP_OPTION_... | 0 | static void ppp_cp_parse_cr(struct net_device *dev, u16 pid, u8 id,
unsigned int req_len, const u8 *data)
{
static u8 const valid_accm[6] = { LCP_OPTION_ACCM, 6, 0, 0, 0, 0 };
const u8 *opt;
u8 *out;
unsigned int len = req_len, nak_len = 0, rej_len = 0;
if (!(out = kmalloc(len, GFP_ATOMIC))) {
dev->stats... | 327,189,183,482,540,720,000,000,000,000,000,000,000 | hdlc_ppp.c | 19,680,262,565,472,288,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2020-25643 | A flaw was found in the HDLC_PPP module of the Linux kernel in versions before 5.9-rc7. Memory corruption and a read overflow is caused by improper input validation in the ppp_cp_parse_cr function which can cause the system to crash or cause a denial of service. The highest threat from this vulnerability is to data con... | https://nvd.nist.gov/vuln/detail/CVE-2020-25643 |
204,111 | tip | 3b56496865f9f7d9bcb2f93b44c63f274f08e3b6 | http://git.kernel.org/cgit/linux/kernel/git/tip/tip | http://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?id=3b56496865f9f7d9bcb2f93b44c63f274f08e3b6 | x86, cpu, amd: Add workaround for family 16h, erratum 793
This adds the workaround for erratum 793 as a precaution in case not
every BIOS implements it. This addresses CVE-2013-6885.
Erratum text:
[Revision Guide for AMD Family 16h Models 00h-0Fh Processors,
document 51810 Rev. 3.04 November 2013]
793 Specific Com... | 1 | static void early_init_amd(struct cpuinfo_x86 *c)
{
early_init_amd_mc(c);
/*
* c->x86_power is 8000_0007 edx. Bit 8 is TSC runs at constant rate
* with P/T states and does not stop in deep C-states
*/
if (c->x86_power & (1 << 8)) {
set_cpu_cap(c, X86_FEATURE_CONSTANT_TSC);
set_cpu_cap(c, X86_FEATURE_NONST... | 308,879,407,253,909,300,000,000,000,000,000,000,000 | amd.c | 197,052,207,439,006,860,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-6885 | The microcode on AMD 16h 00h through 0Fh processors does not properly handle the interaction between locked instructions and write-combined memory types, which allows local users to cause a denial of service (system hang) via a crafted application, aka the errata 793 issue. | https://nvd.nist.gov/vuln/detail/CVE-2013-6885 |
352,894 | tip | 3b56496865f9f7d9bcb2f93b44c63f274f08e3b6 | http://git.kernel.org/cgit/linux/kernel/git/tip/tip | http://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?id=3b56496865f9f7d9bcb2f93b44c63f274f08e3b6 | x86, cpu, amd: Add workaround for family 16h, erratum 793
This adds the workaround for erratum 793 as a precaution in case not
every BIOS implements it. This addresses CVE-2013-6885.
Erratum text:
[Revision Guide for AMD Family 16h Models 00h-0Fh Processors,
document 51810 Rev. 3.04 November 2013]
793 Specific Com... | 0 | static void early_init_amd(struct cpuinfo_x86 *c)
{
early_init_amd_mc(c);
/*
* c->x86_power is 8000_0007 edx. Bit 8 is TSC runs at constant rate
* with P/T states and does not stop in deep C-states
*/
if (c->x86_power & (1 << 8)) {
set_cpu_cap(c, X86_FEATURE_CONSTANT_TSC);
set_cpu_cap(c, X86_FEATURE_NONST... | 57,769,976,202,792,890,000,000,000,000,000,000,000 | amd.c | 318,555,958,238,995,950,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-6885 | The microcode on AMD 16h 00h through 0Fh processors does not properly handle the interaction between locked instructions and write-combined memory types, which allows local users to cause a denial of service (system hang) via a crafted application, aka the errata 793 issue. | https://nvd.nist.gov/vuln/detail/CVE-2013-6885 |
204,142 | linux | e2b3b35eb9896f26c98b9a2c047d9111638059a2 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e2b3b35eb9896f26c98b9a2c047d9111638059a2 | vhost_net: batch used ring update in rx
This patch tries to batched used ring update during RX. This is pretty
fit for the case when guest is much faster (e.g dpdk based
backend). In this case, used ring is almost empty:
- we may get serious cache line misses/contending on both used ring
and used idx.
- at most 1 p... | 1 | static void handle_rx(struct vhost_net *net)
{
struct vhost_net_virtqueue *nvq = &net->vqs[VHOST_NET_VQ_RX];
struct vhost_virtqueue *vq = &nvq->vq;
unsigned uninitialized_var(in), log;
struct vhost_log *vq_log;
struct msghdr msg = {
.msg_name = NULL,
.msg_namelen = 0,
.msg_control = NULL, /* FIXME: get and h... | 47,994,188,619,583,740,000,000,000,000,000,000,000 | net.c | 126,653,565,525,054,730,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2018-16880 | A flaw was found in the Linux kernel's handle_rx() function in the [vhost_net] driver. A malicious virtual guest, under specific conditions, can trigger an out-of-bounds write in a kmalloc-8 slab on a virtual host which may lead to a kernel memory corruption and a system panic. Due to the nature of the flaw, privilege ... | https://nvd.nist.gov/vuln/detail/CVE-2018-16880 |
353,295 | linux | e2b3b35eb9896f26c98b9a2c047d9111638059a2 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e2b3b35eb9896f26c98b9a2c047d9111638059a2 | vhost_net: batch used ring update in rx
This patch tries to batched used ring update during RX. This is pretty
fit for the case when guest is much faster (e.g dpdk based
backend). In this case, used ring is almost empty:
- we may get serious cache line misses/contending on both used ring
and used idx.
- at most 1 p... | 0 | static void handle_rx(struct vhost_net *net)
{
struct vhost_net_virtqueue *nvq = &net->vqs[VHOST_NET_VQ_RX];
struct vhost_virtqueue *vq = &nvq->vq;
unsigned uninitialized_var(in), log;
struct vhost_log *vq_log;
struct msghdr msg = {
.msg_name = NULL,
.msg_namelen = 0,
.msg_control = NULL, /* FIXME: get and h... | 226,523,722,833,166,170,000,000,000,000,000,000,000 | net.c | 315,275,781,317,721,480,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2018-16880 | A flaw was found in the Linux kernel's handle_rx() function in the [vhost_net] driver. A malicious virtual guest, under specific conditions, can trigger an out-of-bounds write in a kmalloc-8 slab on a virtual host which may lead to a kernel memory corruption and a system panic. Due to the nature of the flaw, privilege ... | https://nvd.nist.gov/vuln/detail/CVE-2018-16880 |
204,143 | ceph | 8f396cf35a3826044b089141667a196454c0a587 | https://github.com/ceph/ceph | https://github.com/ceph/ceph/commit/8f396cf35a3826044b089141667a196454c0a587 | auth/cephx/CephxSessionHandler: implement CEPHX_V2 calculation mode
Derive the signature from the entire buffer (both cipher blocks).
Signed-off-by: Sage Weil <sage@redhat.com> | 1 | int CephxSessionHandler::_calc_signature(Message *m, uint64_t *psig)
{
const ceph_msg_header& header = m->get_header();
const ceph_msg_footer& footer = m->get_footer();
// optimized signature calculation
// - avoid temporary allocated buffers from encode_encrypt[_enc_bl]
// - skip the leading 4 byte wrapper ... | 300,296,398,024,781,870,000,000,000,000,000,000,000 | CephxSessionHandler.cc | 299,534,379,172,937,750,000,000,000,000,000,000,000 | [
"CWE-284"
] | CVE-2018-1129 | A flaw was found in the way signature calculation was handled by cephx authentication protocol. An attacker having access to ceph cluster network who is able to alter the message payload was able to bypass signature checks done by cephx protocol. Ceph branches master, mimic, luminous and jewel are believed to be vulner... | https://nvd.nist.gov/vuln/detail/CVE-2018-1129 |
353,304 | ceph | 8f396cf35a3826044b089141667a196454c0a587 | https://github.com/ceph/ceph | https://github.com/ceph/ceph/commit/8f396cf35a3826044b089141667a196454c0a587 | auth/cephx/CephxSessionHandler: implement CEPHX_V2 calculation mode
Derive the signature from the entire buffer (both cipher blocks).
Signed-off-by: Sage Weil <sage@redhat.com> | 0 | int CephxSessionHandler::_calc_signature(Message *m, uint64_t *psig)
{
const ceph_msg_header& header = m->get_header();
const ceph_msg_footer& footer = m->get_footer();
if (!HAVE_FEATURE(features, CEPHX_V2)) {
// legacy pre-mimic behavior for compatibility
// optimized signature calculation
// - avo... | 64,056,571,121,101,660,000,000,000,000,000,000,000 | CephxSessionHandler.cc | 240,234,451,205,823,360,000,000,000,000,000,000,000 | [
"CWE-284"
] | CVE-2018-1129 | A flaw was found in the way signature calculation was handled by cephx authentication protocol. An attacker having access to ceph cluster network who is able to alter the message payload was able to bypass signature checks done by cephx protocol. Ceph branches master, mimic, luminous and jewel are believed to be vulner... | https://nvd.nist.gov/vuln/detail/CVE-2018-1129 |
204,157 | qemu | 51dbea77a29ea46173373a6dad4ebd95d4661f42 | https://github.com/bonzini/qemu | https://github.com/qemu/qemu/commit/51dbea77a29ea46173373a6dad4ebd95d4661f42 | hid: Reset kbd modifiers on reset
When resetting the keyboard, we need to reset not just the pending keystrokes,
but also any pending modifiers. Otherwise there's a race when we're getting
reset while running an escape sequence (modifier 0x100).
Cc: qemu-stable@nongnu.org
Signed-off-by: Alexander Graf <agraf@suse.de>... | 1 | void hid_reset(HIDState *hs)
{
switch (hs->kind) {
case HID_KEYBOARD:
memset(hs->kbd.keycodes, 0, sizeof(hs->kbd.keycodes));
memset(hs->kbd.key, 0, sizeof(hs->kbd.key));
hs->kbd.keys = 0;
break;
case HID_MOUSE:
case HID_TABLET:
memset(hs->ptr.queue, 0, sizeof(hs->... | 175,482,920,648,144,300,000,000,000,000,000,000,000 | hid.c | 319,904,606,669,871,700,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-8379 | Memory leak in the keyboard input event handlers support in QEMU (aka Quick Emulator) allows local guest OS privileged users to cause a denial of service (host memory consumption) by rapidly generating large keyboard events. | https://nvd.nist.gov/vuln/detail/CVE-2017-8379 |
353,537 | qemu | 51dbea77a29ea46173373a6dad4ebd95d4661f42 | https://github.com/bonzini/qemu | https://github.com/qemu/qemu/commit/51dbea77a29ea46173373a6dad4ebd95d4661f42 | hid: Reset kbd modifiers on reset
When resetting the keyboard, we need to reset not just the pending keystrokes,
but also any pending modifiers. Otherwise there's a race when we're getting
reset while running an escape sequence (modifier 0x100).
Cc: qemu-stable@nongnu.org
Signed-off-by: Alexander Graf <agraf@suse.de>... | 0 | void hid_reset(HIDState *hs)
{
switch (hs->kind) {
case HID_KEYBOARD:
memset(hs->kbd.keycodes, 0, sizeof(hs->kbd.keycodes));
memset(hs->kbd.key, 0, sizeof(hs->kbd.key));
hs->kbd.keys = 0;
hs->kbd.modifiers = 0;
break;
case HID_MOUSE:
case HID_TABLET:
memse... | 16,983,307,463,722,767,000,000,000,000,000,000,000 | hid.c | 19,701,082,240,069,023,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-8379 | Memory leak in the keyboard input event handlers support in QEMU (aka Quick Emulator) allows local guest OS privileged users to cause a denial of service (host memory consumption) by rapidly generating large keyboard events. | https://nvd.nist.gov/vuln/detail/CVE-2017-8379 |
204,158 | ntp | ba716a464ecb20618560075f2e4e1051e5b6f24f | https://github.com/ntp-project/ntp | https://github.com/ntp-project/ntp/commit/ba716a464ecb20618560075f2e4e1051e5b6f24f | [Sec 2922] decodenetnum() will ASSERT botch instead of returning FAIL on some bogus values. Harlan Stenn. | 1 | decodenetnum(
const char *num,
sockaddr_u *netnum
)
{
struct addrinfo hints, *ai = NULL;
int err;
u_short port;
const char *cp;
const char *port_str;
char *pp;
char *np;
char name[80];
REQUIRE(num != NULL);
REQUIRE(strlen(num) < sizeof(name));
port_str = NULL;
if ('[' != num[0]) {
/*
* to distingu... | 99,428,777,598,024,660,000,000,000,000,000,000,000 | decodenetnum.c | 330,212,176,223,597,500,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2015-7855 | The decodenetnum function in ntpd in NTP 4.2.x before 4.2.8p4, and 4.3.x before 4.3.77 allows remote attackers to cause a denial of service (assertion failure) via a 6 or mode 7 packet containing a long data value. | https://nvd.nist.gov/vuln/detail/CVE-2015-7855 |
353,545 | ntp | ba716a464ecb20618560075f2e4e1051e5b6f24f | https://github.com/ntp-project/ntp | https://github.com/ntp-project/ntp/commit/ba716a464ecb20618560075f2e4e1051e5b6f24f | [Sec 2922] decodenetnum() will ASSERT botch instead of returning FAIL on some bogus values. Harlan Stenn. | 0 | decodenetnum(
const char *num,
sockaddr_u *netnum
)
{
struct addrinfo hints, *ai = NULL;
int err;
u_short port;
const char *cp;
const char *port_str;
char *pp;
char *np;
char name[80];
REQUIRE(num != NULL);
if (strlen(num) >= sizeof(name)) {
return 0;
}
port_str = NULL;
if ('[' != num[0]) {
/*
... | 209,178,506,920,371,500,000,000,000,000,000,000,000 | decodenetnum.c | 99,309,422,797,296,180,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2015-7855 | The decodenetnum function in ntpd in NTP 4.2.x before 4.2.8p4, and 4.3.x before 4.3.77 allows remote attackers to cause a denial of service (assertion failure) via a 6 or mode 7 packet containing a long data value. | https://nvd.nist.gov/vuln/detail/CVE-2015-7855 |
204,159 | oniguruma | f015fbdd95f76438cd86366467bb2b39870dd7c6 | https://github.com/kkos/oniguruma | https://github.com/kkos/oniguruma/commit/f015fbdd95f76438cd86366467bb2b39870dd7c6 | fix #55 : Byte value expressed in octal must be smaller than 256 | 1 | fetch_token(OnigToken* tok, UChar** src, UChar* end, ScanEnv* env)
{
int r, num;
OnigCodePoint c;
OnigEncoding enc = env->enc;
OnigSyntaxType* syn = env->syntax;
UChar* prev;
UChar* p = *src;
PFETCH_READY;
start:
if (PEND) {
tok->type = TK_EOT;
return tok->type;
}
tok->type = TK_STRING;
... | 13,883,846,990,322,395,000,000,000,000,000,000,000 | regparse.c | 31,891,282,150,523,286,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2017-9226 | 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 or read occurs in next_state_val() during regular expression compilation. Octal numbers larger than 0xff are not handled correctly in fetch_token() and fetch_token_in_... | https://nvd.nist.gov/vuln/detail/CVE-2017-9226 |
353,546 | oniguruma | f015fbdd95f76438cd86366467bb2b39870dd7c6 | https://github.com/kkos/oniguruma | https://github.com/kkos/oniguruma/commit/f015fbdd95f76438cd86366467bb2b39870dd7c6 | fix #55 : Byte value expressed in octal must be smaller than 256 | 0 | fetch_token(OnigToken* tok, UChar** src, UChar* end, ScanEnv* env)
{
int r, num;
OnigCodePoint c;
OnigEncoding enc = env->enc;
OnigSyntaxType* syn = env->syntax;
UChar* prev;
UChar* p = *src;
PFETCH_READY;
start:
if (PEND) {
tok->type = TK_EOT;
return tok->type;
}
tok->type = TK_STRING;
... | 173,003,136,726,200,980,000,000,000,000,000,000,000 | regparse.c | 205,767,443,219,914,600,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2017-9226 | 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 or read occurs in next_state_val() during regular expression compilation. Octal numbers larger than 0xff are not handled correctly in fetch_token() and fetch_token_in_... | https://nvd.nist.gov/vuln/detail/CVE-2017-9226 |
204,160 | oniguruma | f015fbdd95f76438cd86366467bb2b39870dd7c6 | https://github.com/kkos/oniguruma | https://github.com/kkos/oniguruma/commit/f015fbdd95f76438cd86366467bb2b39870dd7c6 | fix #55 : Byte value expressed in octal must be smaller than 256 | 1 | fetch_token_in_cc(OnigToken* tok, UChar** src, UChar* end, ScanEnv* env)
{
int num;
OnigCodePoint c, c2;
OnigSyntaxType* syn = env->syntax;
OnigEncoding enc = env->enc;
UChar* prev;
UChar* p = *src;
PFETCH_READY;
if (PEND) {
tok->type = TK_EOT;
return tok->type;
}
PFETCH(c);
tok->type = ... | 95,497,899,004,455,920,000,000,000,000,000,000,000 | regparse.c | 31,891,282,150,523,286,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2017-9226 | 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 or read occurs in next_state_val() during regular expression compilation. Octal numbers larger than 0xff are not handled correctly in fetch_token() and fetch_token_in_... | https://nvd.nist.gov/vuln/detail/CVE-2017-9226 |
353,547 | oniguruma | f015fbdd95f76438cd86366467bb2b39870dd7c6 | https://github.com/kkos/oniguruma | https://github.com/kkos/oniguruma/commit/f015fbdd95f76438cd86366467bb2b39870dd7c6 | fix #55 : Byte value expressed in octal must be smaller than 256 | 0 | fetch_token_in_cc(OnigToken* tok, UChar** src, UChar* end, ScanEnv* env)
{
int num;
OnigCodePoint c, c2;
OnigSyntaxType* syn = env->syntax;
OnigEncoding enc = env->enc;
UChar* prev;
UChar* p = *src;
PFETCH_READY;
if (PEND) {
tok->type = TK_EOT;
return tok->type;
}
PFETCH(c);
tok->type = ... | 143,536,488,914,025,170,000,000,000,000,000,000,000 | regparse.c | 205,767,443,219,914,600,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2017-9226 | 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 or read occurs in next_state_val() during regular expression compilation. Octal numbers larger than 0xff are not handled correctly in fetch_token() and fetch_token_in_... | https://nvd.nist.gov/vuln/detail/CVE-2017-9226 |
204,183 | curl | 0583e87ada7a3cfb10904ae4ab61b339582c5bd3 | https://github.com/curl/curl | https://github.com/bagder/curl/commit/0583e87ada7a3cfb10904ae4ab61b339582c5bd3 | fix_hostname: zero length host name caused -1 index offset
If a URL is given with a zero-length host name, like in "http://:80" or
just ":80", `fix_hostname()` will index the host name pointer with a -1
offset (as it blindly assumes a non-zero length) and both read and
assign that address.
CVE-2015-3144
Bug: http://... | 1 | static void fix_hostname(struct SessionHandle *data,
struct connectdata *conn, struct hostname *host)
{
size_t len;
#ifndef USE_LIBIDN
(void)data;
(void)conn;
#elif defined(CURL_DISABLE_VERBOSE_STRINGS)
(void)conn;
#endif
/* set the name we use to display the host name */
host->di... | 123,910,420,958,773,860,000,000,000,000,000,000,000 | url.c | 89,772,642,171,184,000,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-3144 | The fix_hostname function in cURL and libcurl 7.37.0 through 7.41.0 does not properly calculate an index, which allows remote attackers to cause a denial of service (out-of-bounds read or write and crash) or possibly have other unspecified impact via a zero-length host name, as demonstrated by "http://:80" and ":80." | https://nvd.nist.gov/vuln/detail/CVE-2015-3144 |
354,080 | curl | 0583e87ada7a3cfb10904ae4ab61b339582c5bd3 | https://github.com/curl/curl | https://github.com/bagder/curl/commit/0583e87ada7a3cfb10904ae4ab61b339582c5bd3 | fix_hostname: zero length host name caused -1 index offset
If a URL is given with a zero-length host name, like in "http://:80" or
just ":80", `fix_hostname()` will index the host name pointer with a -1
offset (as it blindly assumes a non-zero length) and both read and
assign that address.
CVE-2015-3144
Bug: http://... | 0 | static void fix_hostname(struct SessionHandle *data,
struct connectdata *conn, struct hostname *host)
{
size_t len;
#ifndef USE_LIBIDN
(void)data;
(void)conn;
#elif defined(CURL_DISABLE_VERBOSE_STRINGS)
(void)conn;
#endif
/* set the name we use to display the host name */
host->di... | 182,500,492,057,105,630,000,000,000,000,000,000,000 | url.c | 321,410,225,031,724,350,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-3144 | The fix_hostname function in cURL and libcurl 7.37.0 through 7.41.0 does not properly calculate an index, which allows remote attackers to cause a denial of service (out-of-bounds read or write and crash) or possibly have other unspecified impact via a zero-length host name, as demonstrated by "http://:80" and ":80." | https://nvd.nist.gov/vuln/detail/CVE-2015-3144 |
204,186 | linux | d2ffed5185df9d8d9ccd150e4340e3b6f96a8381 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d2ffed5185df9d8d9ccd150e4340e3b6f96a8381 | ARM: amba: Don't read past the end of sysfs "driver_override" buffer
When printing the driver_override parameter when it is 4095 and 4094
bytes long, the printing code would access invalid memory because we
need count + 1 bytes for printing.
Cfr. commits 4efe874aace57dba ("PCI: Don't read past the end of sysfs
"drive... | 1 | static ssize_t driver_override_store(struct device *_dev,
struct device_attribute *attr,
const char *buf, size_t count)
{
struct amba_device *dev = to_amba_device(_dev);
char *driver_override, *old, *cp;
if (count > PATH_MAX)
return -EINVAL;
driver_override = kstrndup(buf, count, GFP_KERNEL);
... | 47,725,458,212,385,760,000,000,000,000,000,000,000 | bus.c | 337,508,225,327,085,880,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2018-9385 | In driver_override_store of bus.c, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Product: Android Versions: Android kernel Android ID: A-74128061 Referen... | https://nvd.nist.gov/vuln/detail/CVE-2018-9385 |
354,397 | linux | d2ffed5185df9d8d9ccd150e4340e3b6f96a8381 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d2ffed5185df9d8d9ccd150e4340e3b6f96a8381 | ARM: amba: Don't read past the end of sysfs "driver_override" buffer
When printing the driver_override parameter when it is 4095 and 4094
bytes long, the printing code would access invalid memory because we
need count + 1 bytes for printing.
Cfr. commits 4efe874aace57dba ("PCI: Don't read past the end of sysfs
"drive... | 0 | static ssize_t driver_override_store(struct device *_dev,
struct device_attribute *attr,
const char *buf, size_t count)
{
struct amba_device *dev = to_amba_device(_dev);
char *driver_override, *old, *cp;
/* We need to keep extra room for a newline */
if (count >= (PAGE_SIZE - 1))
return -EINVAL... | 328,487,934,157,185,750,000,000,000,000,000,000,000 | bus.c | 320,847,968,428,667,340,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2018-9385 | In driver_override_store of bus.c, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Product: Android Versions: Android kernel Android ID: A-74128061 Referen... | https://nvd.nist.gov/vuln/detail/CVE-2018-9385 |
204,194 | bind9 | 15996f0cb15631b95a801e3e88928494a69ad6ee | https://github.com/isc-projects/bind9 | https://gitlab.isc.org/isc-projects/bind9/commit/15996f0cb15631b95a801e3e88928494a69ad6ee | ns_client_error() could assert if rcode was overridden to NOERROR
The client->rcode_override was originally created to force the server
to send SERVFAIL in some cases when it would normally have sent FORMERR.
More recently, it was used in a3ba95116ed04594ea59a8124bf781b30367a7a2
commit (part of GL #2790) to force the... | 1 | ns_client_error(ns_client_t *client, isc_result_t result) {
dns_message_t *message = NULL;
dns_rcode_t rcode;
bool trunc = false;
REQUIRE(NS_CLIENT_VALID(client));
CTRACE("error");
message = client->message;
if (client->rcode_override == -1) {
rcode = dns_result_torcode(result);
} else {
rcode = (dns_rc... | 315,766,005,616,556,300,000,000,000,000,000,000,000 | client.c | 230,516,845,582,537,730,000,000,000,000,000,000,000 | [
"CWE-617"
] | CVE-2021-25218 | In BIND 9.16.19, 9.17.16. Also, version 9.16.19-S1 of BIND Supported Preview Edition When a vulnerable version of named receives a query under the circumstances described above, the named process will terminate due to a failed assertion check. The vulnerability affects only BIND 9 releases 9.16.19, 9.17.16, and release... | https://nvd.nist.gov/vuln/detail/CVE-2021-25218 |
355,007 | bind9 | 15996f0cb15631b95a801e3e88928494a69ad6ee | https://github.com/isc-projects/bind9 | https://gitlab.isc.org/isc-projects/bind9/commit/15996f0cb15631b95a801e3e88928494a69ad6ee | ns_client_error() could assert if rcode was overridden to NOERROR
The client->rcode_override was originally created to force the server
to send SERVFAIL in some cases when it would normally have sent FORMERR.
More recently, it was used in a3ba95116ed04594ea59a8124bf781b30367a7a2
commit (part of GL #2790) to force the... | 0 | ns_client_error(ns_client_t *client, isc_result_t result) {
dns_message_t *message = NULL;
dns_rcode_t rcode;
bool trunc = false;
REQUIRE(NS_CLIENT_VALID(client));
CTRACE("error");
message = client->message;
if (client->rcode_override == -1) {
rcode = dns_result_torcode(result);
} else {
rcode = (dns_rc... | 60,866,367,629,948,720,000,000,000,000,000,000,000 | client.c | 198,358,306,488,490,240,000,000,000,000,000,000,000 | [
"CWE-617"
] | CVE-2021-25218 | In BIND 9.16.19, 9.17.16. Also, version 9.16.19-S1 of BIND Supported Preview Edition When a vulnerable version of named receives a query under the circumstances described above, the named process will terminate due to a failed assertion check. The vulnerability affects only BIND 9 releases 9.16.19, 9.17.16, and release... | https://nvd.nist.gov/vuln/detail/CVE-2021-25218 |
204,198 | openjpeg | c22cbd8bdf8ff2ae372f94391a4be2d322b36b41 | https://github.com/uclouvain/openjpeg | https://github.com/uclouvain/openjpeg/commit/c22cbd8bdf8ff2ae372f94391a4be2d322b36b41 | Avoid heap buffer overflow in function pnmtoimage of convert.c, and unsigned integer overflow in opj_image_create() (CVE-2016-9118, #861) | 1 | opj_image_t* pnmtoimage(const char *filename, opj_cparameters_t *parameters)
{
int subsampling_dx = parameters->subsampling_dx;
int subsampling_dy = parameters->subsampling_dy;
FILE *fp = NULL;
int i, compno, numcomps, w, h, prec, format;
OPJ_COLOR_SPACE color_space;
opj_image_cmptparm_t cmptpa... | 214,108,702,453,048,700,000,000,000,000,000,000,000 | convert.c | 84,080,489,302,192,770,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2018-16375 | An issue was discovered in OpenJPEG 2.3.0. Missing checks for header_info.height and header_info.width in the function pnmtoimage in bin/jpwl/convert.c can lead to a heap-based buffer overflow. | https://nvd.nist.gov/vuln/detail/CVE-2018-16375 |
58,747 | openjpeg | e5285319229a5d77bf316bb0d3a6cbd3cb8666d9 | https://github.com/uclouvain/openjpeg | https://github.com/uclouvain/openjpeg/commit/e5285319229a5d77bf316bb0d3a6cbd3cb8666d9 | pgxtoimage(): fix write stack buffer overflow (#997) | 0 | opj_image_t* pnmtoimage(const char *filename, opj_cparameters_t *parameters)
{
int subsampling_dx = parameters->subsampling_dx;
int subsampling_dy = parameters->subsampling_dy;
FILE *fp = NULL;
int i, compno, numcomps, w, h, prec, format;
OPJ_COLOR_SPACE color_space;
opj_image_cmptparm_t cmptpa... | 38,051,196,207,686,665,000,000,000,000,000,000,000 | convert.c | 218,087,604,944,335,500,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2017-14041 | A stack-based buffer overflow was discovered in the pgxtoimage function in bin/jp2/convert.c in OpenJPEG 2.2.0. The vulnerability causes an out-of-bounds write, which may lead to remote denial of service or possibly remote code execution. | https://nvd.nist.gov/vuln/detail/CVE-2017-14041 |
204,200 | git | 7c3745fc6185495d5765628b4dfe1bd2c25a2981 | https://github.com/git/git | https://github.com/git/git/commit/7c3745fc6185495d5765628b4dfe1bd2c25a2981 | path: safeguard `.git` against NTFS Alternate Streams Accesses
Probably inspired by HFS' resource streams, NTFS supports "Alternate
Data Streams": by appending `:<stream-name>` to the file name,
information in addition to the file contents can be written and read,
information that is copied together with the file (unl... | 1 | int is_ntfs_dotgit(const char *name)
{
size_t len;
for (len = 0; ; len++)
if (!name[len] || name[len] == '\\' || is_dir_sep(name[len])) {
if (only_spaces_and_periods(name, len, 4) &&
!strncasecmp(name, ".git", 4))
return 1;
if (only_spaces_and_periods(name, len, 5) &&
!strncasecmp(name, "git~1"... | 234,693,646,680,167,440,000,000,000,000,000,000,000 | path.c | 118,391,683,935,009,300,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2019-1352 | A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-1349, CVE-2019-1350, CVE-2019-1354, CVE-2019-1387. | https://nvd.nist.gov/vuln/detail/CVE-2019-1352 |
355,239 | git | 7c3745fc6185495d5765628b4dfe1bd2c25a2981 | https://github.com/git/git | https://github.com/git/git/commit/7c3745fc6185495d5765628b4dfe1bd2c25a2981 | path: safeguard `.git` against NTFS Alternate Streams Accesses
Probably inspired by HFS' resource streams, NTFS supports "Alternate
Data Streams": by appending `:<stream-name>` to the file name,
information in addition to the file contents can be written and read,
information that is copied together with the file (unl... | 0 | int is_ntfs_dotgit(const char *name)
{
size_t len;
for (len = 0; ; len++)
if (!name[len] || name[len] == '\\' || is_dir_sep(name[len]) ||
name[len] == ':') {
if (only_spaces_and_periods(name, len, 4) &&
!strncasecmp(name, ".git", 4))
return 1;
if (only_spaces_and_periods(name, len, 5) &&
... | 170,572,245,304,108,440,000,000,000,000,000,000,000 | path.c | 158,986,474,118,137,490,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2019-1352 | A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-1349, CVE-2019-1350, CVE-2019-1354, CVE-2019-1387. | https://nvd.nist.gov/vuln/detail/CVE-2019-1352 |
204,201 | php-src | f80ad18afae2230c2c1802c7d829100af646874e | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commit;h=f80ad18afae2230c2c1802c7d829100af646874e | Fix bug #77950 - Heap-buffer-overflow in _estrndup via exif_process_IFD_TAG
I do not completely understand what is going on there, but I am pretty
sure dir_entry <= offset_base if not a normal situation, so we better not
to rely on such dir_entry. | 1 | static int exif_process_IFD_TAG(image_info_type *ImageInfo, char *dir_entry, char *offset_base, size_t IFDlength, size_t displacement, int section_index, int ReadNextIFD, tag_table_type tag_table)
{
size_t length;
unsigned int tag, format, components;
char *value_ptr, tagname[64], cbuf[32], *outside=NULL;
size_t by... | 249,561,136,594,462,930,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2019-11036 | When processing certain files, PHP EXIF extension in versions 7.1.x below 7.1.29, 7.2.x below 7.2.18 and 7.3.x below 7.3.5 can be caused to read past allocated buffer in exif_process_IFD_TAG function. This may lead to information disclosure or crash. | https://nvd.nist.gov/vuln/detail/CVE-2019-11036 |
355,294 | php-src | f80ad18afae2230c2c1802c7d829100af646874e | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commit;h=f80ad18afae2230c2c1802c7d829100af646874e | Fix bug #77950 - Heap-buffer-overflow in _estrndup via exif_process_IFD_TAG
I do not completely understand what is going on there, but I am pretty
sure dir_entry <= offset_base if not a normal situation, so we better not
to rely on such dir_entry. | 0 | static int exif_process_IFD_TAG(image_info_type *ImageInfo, char *dir_entry, char *offset_base, size_t IFDlength, size_t displacement, int section_index, int ReadNextIFD, tag_table_type tag_table)
{
size_t length;
unsigned int tag, format, components;
char *value_ptr, tagname[64], cbuf[32], *outside=NULL;
size_t by... | 121,920,826,638,986,400,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2019-11036 | When processing certain files, PHP EXIF extension in versions 7.1.x below 7.1.29, 7.2.x below 7.2.18 and 7.3.x below 7.3.5 can be caused to read past allocated buffer in exif_process_IFD_TAG function. This may lead to information disclosure or crash. | https://nvd.nist.gov/vuln/detail/CVE-2019-11036 |
204,241 | php-src | 4e3f55c36272a5f29b50e1924b78e9db1b23f214 | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commit;h=4e3f55c36272a5f29b50e1924b78e9db1b23f214 | Fix bug #74782: remove file name from output to avoid XSS
(cherry picked from commit 73ca9b37731dd9690ffd9706333b17eaf90ea091) | 1 | static inline zend_string* phar_get_stub(const char *index_php, const char *web, const int name_len, const int web_len)
{
static const char newstub0[] = "<?php\n\n$web = '";
static const char newstub1_0[] = "';\n\nif (in_array('phar', stream_get_wrappers()) && class_exists('Phar', 0)) {\nPhar::interceptFileFuncs();\n... | 8,003,331,714,422,307,000,000,000,000,000,000,000 | stub.h | 314,837,471,676,620,700,000,000,000,000,000,000,000 | [
"CWE-79"
] | CVE-2018-5712 | An issue was discovered 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. There is Reflected XSS on the PHAR 404 error page via the URI of a request for a .phar file. | https://nvd.nist.gov/vuln/detail/CVE-2018-5712 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.