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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
363,847 | linux | 56cd26b618855c9af48c8301aa6754ced8dd0beb | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=56cd26b618855c9af48c8301aa6754ced8dd0beb | media: serial_ir: Fix use-after-free in serial_ir_init_module
Syzkaller report this:
BUG: KASAN: use-after-free in sysfs_remove_file_ns+0x5f/0x70 fs/sysfs/file.c:468
Read of size 8 at addr ffff8881dc7ae030 by task syz-executor.0/6249
CPU: 1 PID: 6249 Comm: syz-executor.0 Not tainted 5.0.0-rc8+ #3
Hardware name: QEMU... | 0 | static int __init serial_ir_init_module(void)
{
switch (type) {
case IR_HOMEBREW:
case IR_IRDEO:
case IR_IRDEO_REMOTE:
case IR_ANIMAX:
case IR_IGOR:
/* if nothing specified, use ttyS0/com1 and irq 4 */
io = io ? io : 0x3f8;
irq = irq ? irq : 4;
break;
default:
return -EINVAL;
}
if (!softcarrier) {
... | 140,512,031,743,349,640,000,000,000,000,000,000,000 | serial_ir.c | 133,447,381,504,448,630,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2019-19543 | In the Linux kernel before 5.1.6, there is a use-after-free in serial_ir_init_module() in drivers/media/rc/serial_ir.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-19543 |
204,710 | ImageMagick | 787f9dc99c8d186ae26ed53ddec54bd0a6f90852 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/787f9dc99c8d186ae26ed53ddec54bd0a6f90852 | https://github.com/ImageMagick/ImageMagick/issues/539 | 1 | MagickExport void GetNextToken(const char *start,const char **end,
const size_t extent,char *token)
{
double
value;
register const char
*p;
register ssize_t
i;
assert(start != (const char *) NULL);
assert(token != (char *) NULL);
i=0;
p=start;
while ((isspace((int) ((unsigned char) *p))... | 254,400,509,639,460,370,000,000,000,000,000,000,000 | token.c | 151,576,362,775,183,240,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-10928 | In ImageMagick 7.0.6-0, a heap-based buffer over-read in the GetNextToken function in token.c allows remote attackers to obtain sensitive information from process memory or possibly have unspecified other impact via a crafted SVG document that is mishandled in the GetUserSpaceCoordinateValue function in coders/svg.c. | https://nvd.nist.gov/vuln/detail/CVE-2017-10928 |
363,880 | ImageMagick | 787f9dc99c8d186ae26ed53ddec54bd0a6f90852 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/787f9dc99c8d186ae26ed53ddec54bd0a6f90852 | https://github.com/ImageMagick/ImageMagick/issues/539 | 0 | MagickExport void GetNextToken(const char *start,const char **end,
const size_t extent,char *token)
{
double
value;
register const char
*p;
register ssize_t
i;
size_t
length;
assert(start != (const char *) NULL);
assert(token != (char *) NULL);
i=0;
length=strlen(start);
p=start;... | 323,769,358,705,897,930,000,000,000,000,000,000,000 | token.c | 177,748,973,877,629,400,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-10928 | In ImageMagick 7.0.6-0, a heap-based buffer over-read in the GetNextToken function in token.c allows remote attackers to obtain sensitive information from process memory or possibly have unspecified other impact via a crafted SVG document that is mishandled in the GetUserSpaceCoordinateValue function in coders/svg.c. | https://nvd.nist.gov/vuln/detail/CVE-2017-10928 |
204,726 | curl | d41dcba4e9b69d6b761e3460cc6ae7e8fd8f621f | https://github.com/curl/curl | https://github.com/curl/curl/commit/d41dcba4e9b69d6b761e3460cc6ae7e8fd8f621f | NTLM: Fix ConnectionExists to compare Proxy credentials
Proxy NTLM authentication should compare credentials when
re-using a connection similar to host authentication, as it
authenticate the connection.
Example:
curl -v -x http://proxy:port http://host/ -U good_user:good_pwd
--proxy-ntlm --next -x http://proxy:port... | 1 | ConnectionExists(struct SessionHandle *data,
struct connectdata *needle,
struct connectdata **usethis,
bool *force_reuse,
bool *waitpipe)
{
struct connectdata *check;
struct connectdata *chosen = 0;
bool foundPendingCandidate = FALSE;
bool canP... | 335,706,115,566,858,940,000,000,000,000,000,000,000 | url.c | 194,081,227,937,011,320,000,000,000,000,000,000,000 | [
"CWE-287"
] | CVE-2016-0755 | The ConnectionExists function in lib/url.c in libcurl before 7.47.0 does not properly re-use NTLM-authenticated proxy connections, which might allow remote attackers to authenticate as other users via a request, a similar issue to CVE-2014-0015. | https://nvd.nist.gov/vuln/detail/CVE-2016-0755 |
364,212 | curl | d41dcba4e9b69d6b761e3460cc6ae7e8fd8f621f | https://github.com/curl/curl | https://github.com/curl/curl/commit/d41dcba4e9b69d6b761e3460cc6ae7e8fd8f621f | NTLM: Fix ConnectionExists to compare Proxy credentials
Proxy NTLM authentication should compare credentials when
re-using a connection similar to host authentication, as it
authenticate the connection.
Example:
curl -v -x http://proxy:port http://host/ -U good_user:good_pwd
--proxy-ntlm --next -x http://proxy:port... | 0 | ConnectionExists(struct SessionHandle *data,
struct connectdata *needle,
struct connectdata **usethis,
bool *force_reuse,
bool *waitpipe)
{
struct connectdata *check;
struct connectdata *chosen = 0;
bool foundPendingCandidate = FALSE;
bool canP... | 153,504,608,759,038,770,000,000,000,000,000,000,000 | url.c | 321,410,225,031,724,350,000,000,000,000,000,000,000 | [
"CWE-287"
] | CVE-2016-0755 | The ConnectionExists function in lib/url.c in libcurl before 7.47.0 does not properly re-use NTLM-authenticated proxy connections, which might allow remote attackers to authenticate as other users via a request, a similar issue to CVE-2014-0015. | https://nvd.nist.gov/vuln/detail/CVE-2016-0755 |
204,730 | linux | 4edbe1d7bcffcd6269f3b5eb63f710393ff2ec7a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4edbe1d7bcffcd6269f3b5eb63f710393ff2ec7a | dm ioctl: fix out of bounds array access when no devices
If there are not any dm devices, we need to zero the "dev" argument in
the first structure dm_name_list. However, this can cause out of
bounds write, because the "needed" variable is zero and len may be
less than eight.
Fix this bug by reporting DM_BUFFER_FULL_... | 1 | static int list_devices(struct file *filp, struct dm_ioctl *param, size_t param_size)
{
unsigned int i;
struct hash_cell *hc;
size_t len, needed = 0;
struct gendisk *disk;
struct dm_name_list *orig_nl, *nl, *old_nl = NULL;
uint32_t *event_nr;
down_write(&_hash_lock);
/*
* Loop through all the devices workin... | 148,333,388,479,535,550,000,000,000,000,000,000,000 | dm-ioctl.c | 31,998,968,692,962,680,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-31916 | An out-of-bounds (OOB) memory write flaw was found in list_devices in drivers/md/dm-ioctl.c in the Multi-device driver module in the Linux kernel before 5.12. A bound check failure allows an attacker with special user (CAP_SYS_ADMIN) privilege to gain access to out-of-bounds memory leading to a system crash or a leak o... | https://nvd.nist.gov/vuln/detail/CVE-2021-31916 |
364,275 | linux | 4edbe1d7bcffcd6269f3b5eb63f710393ff2ec7a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4edbe1d7bcffcd6269f3b5eb63f710393ff2ec7a | dm ioctl: fix out of bounds array access when no devices
If there are not any dm devices, we need to zero the "dev" argument in
the first structure dm_name_list. However, this can cause out of
bounds write, because the "needed" variable is zero and len may be
less than eight.
Fix this bug by reporting DM_BUFFER_FULL_... | 0 | static int list_devices(struct file *filp, struct dm_ioctl *param, size_t param_size)
{
unsigned int i;
struct hash_cell *hc;
size_t len, needed = 0;
struct gendisk *disk;
struct dm_name_list *orig_nl, *nl, *old_nl = NULL;
uint32_t *event_nr;
down_write(&_hash_lock);
/*
* Loop through all the devices workin... | 274,921,427,580,533,570,000,000,000,000,000,000,000 | dm-ioctl.c | 257,413,058,497,764,050,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-31916 | An out-of-bounds (OOB) memory write flaw was found in list_devices in drivers/md/dm-ioctl.c in the Multi-device driver module in the Linux kernel before 5.12. A bound check failure allows an attacker with special user (CAP_SYS_ADMIN) privilege to gain access to out-of-bounds memory leading to a system crash or a leak o... | https://nvd.nist.gov/vuln/detail/CVE-2021-31916 |
204,737 | libslirp | c59279437eda91841b9d26079c70b8a540d41204 | https://gitlab.freedesktop.org/slirp/libslirp | https://gitlab.freedesktop.org/slirp/libslirp/commit/c59279437eda91841b9d26079c70b8a540d41204 | ip_reass: Fix use after free
Using ip_deq after m_free might read pointers from an allocation reuse.
This would be difficult to exploit, but that is still related with
CVE-2019-14378 which generates fragmented IP packets that would trigger this
issue and at least produce a DoS.
Signed-off-by: Samuel Thibault <samuel... | 1 | static struct ip *ip_reass(Slirp *slirp, struct ip *ip, struct ipq *fp)
{
register struct mbuf *m = dtom(slirp, ip);
register struct ipasfrag *q;
int hlen = ip->ip_hl << 2;
int i, next;
DEBUG_CALL("ip_reass");
DEBUG_ARG("ip = %p", ip);
DEBUG_ARG("fp = %p", fp);
DEBUG_ARG("m = %p", m);
... | 12,275,899,998,196,474,000,000,000,000,000,000,000 | ip_input.c | 55,735,069,880,064,440,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2019-15890 | libslirp 4.0.0, as used in QEMU 4.1.0, has a use-after-free in ip_reass in ip_input.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-15890 |
364,494 | libslirp | c59279437eda91841b9d26079c70b8a540d41204 | https://gitlab.freedesktop.org/slirp/libslirp | https://gitlab.freedesktop.org/slirp/libslirp/commit/c59279437eda91841b9d26079c70b8a540d41204 | ip_reass: Fix use after free
Using ip_deq after m_free might read pointers from an allocation reuse.
This would be difficult to exploit, but that is still related with
CVE-2019-14378 which generates fragmented IP packets that would trigger this
issue and at least produce a DoS.
Signed-off-by: Samuel Thibault <samuel... | 0 | static struct ip *ip_reass(Slirp *slirp, struct ip *ip, struct ipq *fp)
{
register struct mbuf *m = dtom(slirp, ip);
register struct ipasfrag *q;
int hlen = ip->ip_hl << 2;
int i, next;
DEBUG_CALL("ip_reass");
DEBUG_ARG("ip = %p", ip);
DEBUG_ARG("fp = %p", fp);
DEBUG_ARG("m = %p", m);
... | 16,085,044,458,890,204,000,000,000,000,000,000,000 | ip_input.c | 176,357,467,889,952,460,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2019-15890 | libslirp 4.0.0, as used in QEMU 4.1.0, has a use-after-free in ip_reass in ip_input.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-15890 |
204,741 | qemu | 449e8171f96a6a944d1f3b7d3627ae059eae21ca | https://github.com/bonzini/qemu | https://gitlab.com/qemu-project/qemu/-/commit/449e8171f96a6a944d1f3b7d3627ae059eae21ca | virtiofsd: Drop membership of all supplementary groups (CVE-2022-0358)
At the start, drop membership of all supplementary groups. This is
not required.
If we have membership of "root" supplementary group and when we switch
uid/gid using setresuid/setsgid, we still retain membership of existing
supplemntary groups. An... | 1 | int main(int argc, char *argv[])
{
struct fuse_args args = FUSE_ARGS_INIT(argc, argv);
struct fuse_session *se;
struct fuse_cmdline_opts opts;
struct lo_data lo = {
.sandbox = SANDBOX_NAMESPACE,
.debug = 0,
.writeback = 0,
.posix_lock = 0,
.allow_direct_io = 0,
... | 29,837,294,008,545,864,000,000,000,000,000,000,000 | passthrough_ll.c | 215,195,499,999,254,900,000,000,000,000,000,000,000 | [
"CWE-273"
] | CVE-2022-0358 | A flaw was found in the QEMU virtio-fs shared file system daemon (virtiofsd) implementation. This flaw is strictly related to CVE-2018-13405. A local guest user can create files in the directories shared by virtio-fs with unintended group ownership in a scenario where a directory is SGID to a certain group and is writa... | https://nvd.nist.gov/vuln/detail/CVE-2022-0358 |
364,532 | qemu | 449e8171f96a6a944d1f3b7d3627ae059eae21ca | https://github.com/bonzini/qemu | https://gitlab.com/qemu-project/qemu/-/commit/449e8171f96a6a944d1f3b7d3627ae059eae21ca | virtiofsd: Drop membership of all supplementary groups (CVE-2022-0358)
At the start, drop membership of all supplementary groups. This is
not required.
If we have membership of "root" supplementary group and when we switch
uid/gid using setresuid/setsgid, we still retain membership of existing
supplemntary groups. An... | 0 | int main(int argc, char *argv[])
{
struct fuse_args args = FUSE_ARGS_INIT(argc, argv);
struct fuse_session *se;
struct fuse_cmdline_opts opts;
struct lo_data lo = {
.sandbox = SANDBOX_NAMESPACE,
.debug = 0,
.writeback = 0,
.posix_lock = 0,
.allow_direct_io = 0,
... | 178,573,494,322,144,870,000,000,000,000,000,000,000 | passthrough_ll.c | 184,303,727,564,008,100,000,000,000,000,000,000,000 | [
"CWE-273"
] | CVE-2022-0358 | A flaw was found in the QEMU virtio-fs shared file system daemon (virtiofsd) implementation. This flaw is strictly related to CVE-2018-13405. A local guest user can create files in the directories shared by virtio-fs with unintended group ownership in a scenario where a directory is SGID to a certain group and is writa... | https://nvd.nist.gov/vuln/detail/CVE-2022-0358 |
204,750 | linux | 189b0ddc245139af81198d1a3637cac74f96e13a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/189b0ddc245139af81198d1a3637cac74f96e13a | pipe: Fix missing lock in pipe_resize_ring()
pipe_resize_ring() needs to take the pipe->rd_wait.lock spinlock to
prevent post_one_notification() from trying to insert into the ring
whilst the ring is being replaced.
The occupancy check must be done after the lock is taken, and the lock
must be taken after the new rin... | 1 | int pipe_resize_ring(struct pipe_inode_info *pipe, unsigned int nr_slots)
{
struct pipe_buffer *bufs;
unsigned int head, tail, mask, n;
/*
* We can shrink the pipe, if arg is greater than the ring occupancy.
* Since we don't expect a lot of shrink+grow operations, just free and
* allocate again like we would ... | 275,935,744,647,639,200,000,000,000,000,000,000,000 | pipe.c | 143,718,026,170,015,160,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2022-2959 | A race condition was found in the Linux kernel's watch queue due to a missing lock in pipe_resize_ring(). The specific flaw exists within the handling of pipe buffers. The issue results from the lack of proper locking when performing operations on an object. This flaw allows a local user to crash the system or escalate... | https://nvd.nist.gov/vuln/detail/CVE-2022-2959 |
364,725 | linux | 189b0ddc245139af81198d1a3637cac74f96e13a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/189b0ddc245139af81198d1a3637cac74f96e13a | pipe: Fix missing lock in pipe_resize_ring()
pipe_resize_ring() needs to take the pipe->rd_wait.lock spinlock to
prevent post_one_notification() from trying to insert into the ring
whilst the ring is being replaced.
The occupancy check must be done after the lock is taken, and the lock
must be taken after the new rin... | 0 | int pipe_resize_ring(struct pipe_inode_info *pipe, unsigned int nr_slots)
{
struct pipe_buffer *bufs;
unsigned int head, tail, mask, n;
bufs = kcalloc(nr_slots, sizeof(*bufs),
GFP_KERNEL_ACCOUNT | __GFP_NOWARN);
if (unlikely(!bufs))
return -ENOMEM;
spin_lock_irq(&pipe->rd_wait.lock);
mask = pipe->rin... | 167,442,208,997,875,210,000,000,000,000,000,000,000 | pipe.c | 36,028,737,810,219,195,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2022-2959 | A race condition was found in the Linux kernel's watch queue due to a missing lock in pipe_resize_ring(). The specific flaw exists within the handling of pipe buffers. The issue results from the lack of proper locking when performing operations on an object. This flaw allows a local user to crash the system or escalate... | https://nvd.nist.gov/vuln/detail/CVE-2022-2959 |
204,763 | php-src | 70523ce41ff400ea00343a03f297332cb1f1b77b | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commit;h=70523ce41ff400ea00343a03f297332cb1f1b77b | Fix bug #78069 - Out-of-bounds read in iconv.c:_php_iconv_mime_decode() due to integer overflow
(cherry picked from commit 7cf7148a8f8f4f55fb04de2a517d740bb6253eac) | 1 | static php_iconv_err_t _php_iconv_mime_decode(smart_str *pretval, const char *str, size_t str_nbytes, const char *enc, const char **next_pos, int mode)
{
php_iconv_err_t err = PHP_ICONV_ERR_SUCCESS;
iconv_t cd = (iconv_t)(-1), cd_pl = (iconv_t)(-1);
const char *p1;
size_t str_left;
unsigned int scan_stat = 0;
c... | 13,911,939,298,294,340,000,000,000,000,000,000,000 | iconv.c | 59,501,852,036,608,100,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2019-11039 | Function iconv_mime_decode_headers() in PHP versions 7.1.x below 7.1.30, 7.2.x below 7.2.19 and 7.3.x below 7.3.6 may perform out-of-buffer read due to integer overflow when parsing MIME headers. This may lead to information disclosure or crash. | https://nvd.nist.gov/vuln/detail/CVE-2019-11039 |
364,858 | php-src | 70523ce41ff400ea00343a03f297332cb1f1b77b | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commit;h=70523ce41ff400ea00343a03f297332cb1f1b77b | Fix bug #78069 - Out-of-bounds read in iconv.c:_php_iconv_mime_decode() due to integer overflow
(cherry picked from commit 7cf7148a8f8f4f55fb04de2a517d740bb6253eac) | 0 | static php_iconv_err_t _php_iconv_mime_decode(smart_str *pretval, const char *str, size_t str_nbytes, const char *enc, const char **next_pos, int mode)
{
php_iconv_err_t err = PHP_ICONV_ERR_SUCCESS;
iconv_t cd = (iconv_t)(-1), cd_pl = (iconv_t)(-1);
const char *p1;
size_t str_left;
unsigned int scan_stat = 0;
c... | 323,126,973,245,952,770,000,000,000,000,000,000,000 | iconv.c | 101,196,545,313,511,940,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2019-11039 | Function iconv_mime_decode_headers() in PHP versions 7.1.x below 7.1.30, 7.2.x below 7.2.19 and 7.3.x below 7.3.6 may perform out-of-buffer read due to integer overflow when parsing MIME headers. This may lead to information disclosure or crash. | https://nvd.nist.gov/vuln/detail/CVE-2019-11039 |
204,765 | linux | 161f873b89136eb1e69477c847d5a5033239d9ba | https://github.com/torvalds/linux | https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=161f873b89136eb1e69477c847d5a5033239d9ba | vfs: read file_handle only once in handle_to_path
We used to read file_handle twice. Once to get the amount of extra
bytes, and once to fetch the entire structure.
This may be problematic since we do size verifications only after the
first read, so if the number of extra bytes changes in userspace between
the first ... | 1 | static int handle_to_path(int mountdirfd, struct file_handle __user *ufh,
struct path *path)
{
int retval = 0;
struct file_handle f_handle;
struct file_handle *handle = NULL;
/*
* With handle we don't look at the execute bit on the
* the directory. Ideally we would like CAP_DAC_SEARCH.
* But we don't ha... | 206,564,101,007,058,570,000,000,000,000,000,000,000 | fhandle.c | 298,586,193,721,159,750,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2015-1420 | Race condition in the handle_to_path function in fs/fhandle.c in the Linux kernel through 3.19.1 allows local users to bypass intended size restrictions and trigger read operations on additional memory locations by changing the handle_bytes value of a file handle during the execution of this function. | https://nvd.nist.gov/vuln/detail/CVE-2015-1420 |
364,984 | linux | 161f873b89136eb1e69477c847d5a5033239d9ba | https://github.com/torvalds/linux | https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=161f873b89136eb1e69477c847d5a5033239d9ba | vfs: read file_handle only once in handle_to_path
We used to read file_handle twice. Once to get the amount of extra
bytes, and once to fetch the entire structure.
This may be problematic since we do size verifications only after the
first read, so if the number of extra bytes changes in userspace between
the first ... | 0 | static int handle_to_path(int mountdirfd, struct file_handle __user *ufh,
struct path *path)
{
int retval = 0;
struct file_handle f_handle;
struct file_handle *handle = NULL;
/*
* With handle we don't look at the execute bit on the
* the directory. Ideally we would like CAP_DAC_SEARCH.
* But we don't ha... | 321,136,248,391,844,960,000,000,000,000,000,000,000 | fhandle.c | 262,618,824,538,277,220,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2015-1420 | Race condition in the handle_to_path function in fs/fhandle.c in the Linux kernel through 3.19.1 allows local users to bypass intended size restrictions and trigger read operations on additional memory locations by changing the handle_bytes value of a file handle during the execution of this function. | https://nvd.nist.gov/vuln/detail/CVE-2015-1420 |
204,769 | linux | 8c55dedb795be8ec0cf488f98c03a1c2176f7fb1 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8c55dedb795be8ec0cf488f98c03a1c2176f7fb1 | rtlwifi: Fix potential overflow on P2P code
Nicolas Waisman noticed that even though noa_len is checked for
a compatible length it's still possible to overrun the buffers
of p2pinfo since there's no check on the upper bound of noa_num.
Bound noa_num against P2P_MAX_NOA_NUM.
Reported-by: Nicolas Waisman <nico@semmle.c... | 1 | static void rtl_p2p_noa_ie(struct ieee80211_hw *hw, void *data,
unsigned int len)
{
struct rtl_priv *rtlpriv = rtl_priv(hw);
struct ieee80211_mgmt *mgmt = data;
struct rtl_p2p_ps_info *p2pinfo = &(rtlpriv->psc.p2p_ps_info);
u8 *pos, *end, *ie;
u16 noa_len;
static u8 p2p_oui_ie_type[4] = {0x50, 0x6f, 0x9a, 0... | 194,402,860,665,596,760,000,000,000,000,000,000,000 | ps.c | 31,575,109,750,425,710,000,000,000,000,000,000,000 | [
"CWE-120"
] | CVE-2019-17666 | rtl_p2p_noa_ie in drivers/net/wireless/realtek/rtlwifi/ps.c in the Linux kernel through 5.3.6 lacks a certain upper-bound check, leading to a buffer overflow. | https://nvd.nist.gov/vuln/detail/CVE-2019-17666 |
365,006 | linux | 8c55dedb795be8ec0cf488f98c03a1c2176f7fb1 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8c55dedb795be8ec0cf488f98c03a1c2176f7fb1 | rtlwifi: Fix potential overflow on P2P code
Nicolas Waisman noticed that even though noa_len is checked for
a compatible length it's still possible to overrun the buffers
of p2pinfo since there's no check on the upper bound of noa_num.
Bound noa_num against P2P_MAX_NOA_NUM.
Reported-by: Nicolas Waisman <nico@semmle.c... | 0 | static void rtl_p2p_noa_ie(struct ieee80211_hw *hw, void *data,
unsigned int len)
{
struct rtl_priv *rtlpriv = rtl_priv(hw);
struct ieee80211_mgmt *mgmt = data;
struct rtl_p2p_ps_info *p2pinfo = &(rtlpriv->psc.p2p_ps_info);
u8 *pos, *end, *ie;
u16 noa_len;
static u8 p2p_oui_ie_type[4] = {0x50, 0x6f, 0x9a, 0... | 1,997,491,080,762,112,700,000,000,000,000,000,000 | ps.c | 81,730,111,700,832,440,000,000,000,000,000,000,000 | [
"CWE-120"
] | CVE-2019-17666 | rtl_p2p_noa_ie in drivers/net/wireless/realtek/rtlwifi/ps.c in the Linux kernel through 5.3.6 lacks a certain upper-bound check, leading to a buffer overflow. | https://nvd.nist.gov/vuln/detail/CVE-2019-17666 |
204,794 | ImageMagick | 90c4afcde1bf3ad5aead4477716161c350b049f8 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/90c4afcde1bf3ad5aead4477716161c350b049f8 | https://github.com/ImageMagick/ImageMagick/issues/1518 | 1 | static MagickBooleanType WriteJP2Image(const ImageInfo *image_info,Image *image,
ExceptionInfo *exception)
{
const char
*option,
*property;
int
jp2_status;
MagickBooleanType
status;
opj_codec_t
*jp2_codec;
OPJ_COLOR_SPACE
jp2_colorspace;
opj_cparameters_t
parameters;
op... | 69,738,302,850,407,880,000,000,000,000,000,000,000 | jp2.c | 94,559,439,941,308,770,000,000,000,000,000,000,000 | [
"CWE-665"
] | CVE-2019-12977 | ImageMagick 7.0.8-34 has a "use of uninitialized value" vulnerability in the WriteJP2Image function in coders/jp2.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-12977 |
365,055 | ImageMagick | 90c4afcde1bf3ad5aead4477716161c350b049f8 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/90c4afcde1bf3ad5aead4477716161c350b049f8 | https://github.com/ImageMagick/ImageMagick/issues/1518 | 0 | static MagickBooleanType WriteJP2Image(const ImageInfo *image_info,Image *image,
ExceptionInfo *exception)
{
const char
*option,
*property;
int
jp2_status;
MagickBooleanType
status;
opj_codec_t
*jp2_codec;
OPJ_COLOR_SPACE
jp2_colorspace;
opj_cparameters_t
parameters;
op... | 274,739,476,139,335,420,000,000,000,000,000,000,000 | jp2.c | 242,449,575,315,524,830,000,000,000,000,000,000,000 | [
"CWE-665"
] | CVE-2019-12977 | ImageMagick 7.0.8-34 has a "use of uninitialized value" vulnerability in the WriteJP2Image function in coders/jp2.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-12977 |
204,813 | gnutls | 96e07075e8f105b13e76b11e493d5aa2dd937226 | http://git.savannah.gnu.org/cgit/gnutls | https://gitlab.com/gnutls/gnutls/commit/96e07075e8f105b13e76b11e493d5aa2dd937226 | handshake: add missing initialization of local variable
Resolves: #704
Signed-off-by: Daiki Ueno <dueno@redhat.com>
Signed-off-by: Nikos Mavrogiannopoulos <nmav@redhat.com> | 1 | _gnutls13_recv_async_handshake(gnutls_session_t session)
{
int ret;
handshake_buffer_st hsk;
recv_state_t next_state = RECV_STATE_0;
/* The following messages are expected asynchronously after
* the handshake process is complete */
if (unlikely(session->internals.handshake_in_progress))
return gnutls_assert_v... | 307,739,429,144,177,700,000,000,000,000,000,000,000 | handshake-tls13.c | 271,232,727,093,081,920,000,000,000,000,000,000,000 | [
"CWE-824"
] | CVE-2019-3836 | It was discovered in gnutls before version 3.6.7 upstream that there is an uninitialized pointer access in gnutls versions 3.6.3 or later which can be triggered by certain post-handshake messages. | https://nvd.nist.gov/vuln/detail/CVE-2019-3836 |
365,753 | gnutls | 96e07075e8f105b13e76b11e493d5aa2dd937226 | http://git.savannah.gnu.org/cgit/gnutls | https://gitlab.com/gnutls/gnutls/commit/96e07075e8f105b13e76b11e493d5aa2dd937226 | handshake: add missing initialization of local variable
Resolves: #704
Signed-off-by: Daiki Ueno <dueno@redhat.com>
Signed-off-by: Nikos Mavrogiannopoulos <nmav@redhat.com> | 0 | _gnutls13_recv_async_handshake(gnutls_session_t session)
{
int ret;
handshake_buffer_st hsk;
recv_state_t next_state = RECV_STATE_0;
/* The following messages are expected asynchronously after
* the handshake process is complete */
if (unlikely(session->internals.handshake_in_progress))
return gnutls_assert_v... | 251,681,357,697,346,660,000,000,000,000,000,000,000 | handshake-tls13.c | 178,771,334,496,075,160,000,000,000,000,000,000,000 | [
"CWE-824"
] | CVE-2019-3836 | It was discovered in gnutls before version 3.6.7 upstream that there is an uninitialized pointer access in gnutls versions 3.6.3 or later which can be triggered by certain post-handshake messages. | https://nvd.nist.gov/vuln/detail/CVE-2019-3836 |
204,815 | linux | f5a4941aa6d190e676065e8f4ed35999f52a01c3 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f5a4941aa6d190e676065e8f4ed35999f52a01c3 | vhost_net: flush batched heads before trying to busy polling
After commit e2b3b35eb989 ("vhost_net: batch used ring update in rx"),
we tend to batch updating used heads. But it doesn't flush batched
heads before trying to do busy polling, this will cause vhost to wait
for guest TX which waits for the used RX. Fixing b... | 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... | 306,869,401,622,050,400,000,000,000,000,000,000,000 | net.c | 180,394,262,854,657,830,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 |
365,769 | linux | f5a4941aa6d190e676065e8f4ed35999f52a01c3 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f5a4941aa6d190e676065e8f4ed35999f52a01c3 | vhost_net: flush batched heads before trying to busy polling
After commit e2b3b35eb989 ("vhost_net: batch used ring update in rx"),
we tend to batch updating used heads. But it doesn't flush batched
heads before trying to do busy polling, this will cause vhost to wait
for guest TX which waits for the used RX. Fixing b... | 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... | 37,243,310,794,247,895,000,000,000,000,000,000,000 | net.c | 237,616,249,675,738,460,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,819 | bpf | 5b029a32cfe4600f5e10e36b41778506b90fd4de | https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf | https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git/commit/?id=5b029a32cfe4600f5e10e36b41778506b90fd4de | bpf: Fix ringbuf helper function compatibility
Commit 457f44363a88 ("bpf: Implement BPF ring buffer and verifier support
for it") extended check_map_func_compatibility() by enforcing map -> helper
function match, but not helper -> map type match.
Due to this all of the bpf_ringbuf_*() helper functions could be used w... | 1 | static int check_map_func_compatibility(struct bpf_verifier_env *env,
struct bpf_map *map, int func_id)
{
if (!map)
return 0;
/* We need a two way check, first is from map perspective ... */
switch (map->map_type) {
case BPF_MAP_TYPE_PROG_ARRAY:
if (func_id != BPF_FUNC_tail_call)
goto error;
break;
... | 283,665,478,338,390,060,000,000,000,000,000,000,000 | verifier.c | 18,907,162,923,364,713,000,000,000,000,000,000,000 | [
"CWE-843"
] | CVE-2021-34866 | This vulnerability allows local attackers to escalate privileges on affected installations of Linux Kernel 5.14-rc3. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. The specific flaw exists within the handling of eBPF programs. The is... | https://nvd.nist.gov/vuln/detail/CVE-2021-34866 |
365,850 | bpf | 5b029a32cfe4600f5e10e36b41778506b90fd4de | https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf | https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git/commit/?id=5b029a32cfe4600f5e10e36b41778506b90fd4de | bpf: Fix ringbuf helper function compatibility
Commit 457f44363a88 ("bpf: Implement BPF ring buffer and verifier support
for it") extended check_map_func_compatibility() by enforcing map -> helper
function match, but not helper -> map type match.
Due to this all of the bpf_ringbuf_*() helper functions could be used w... | 0 | static int check_map_func_compatibility(struct bpf_verifier_env *env,
struct bpf_map *map, int func_id)
{
if (!map)
return 0;
/* We need a two way check, first is from map perspective ... */
switch (map->map_type) {
case BPF_MAP_TYPE_PROG_ARRAY:
if (func_id != BPF_FUNC_tail_call)
goto error;
break;
... | 166,073,041,212,020,300,000,000,000,000,000,000,000 | verifier.c | 55,631,823,624,727,930,000,000,000,000,000,000,000 | [
"CWE-843"
] | CVE-2021-34866 | This vulnerability allows local attackers to escalate privileges on affected installations of Linux Kernel 5.14-rc3. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. The specific flaw exists within the handling of eBPF programs. The is... | https://nvd.nist.gov/vuln/detail/CVE-2021-34866 |
204,820 | sqlite | 926f796e8feec15f3836aa0a060ed906f8ae04d3 | https://github.com/sqlite/sqlite | https://github.com/sqlite/sqlite/commit/926f796e8feec15f3836aa0a060ed906f8ae04d3 | Ensure that the SrcList_item.colUsed field is set correctly (set to have a
1 for all columns of the table) when a generated column appears in the USING
clause of a join.
FossilOrigin-Name: 1923efb283e8840fa7436eb20b9d2174ef7cace1690d3b97b572a0db2048b8e3 | 1 | Expr *sqlite3CreateColumnExpr(sqlite3 *db, SrcList *pSrc, int iSrc, int iCol){
Expr *p = sqlite3ExprAlloc(db, TK_COLUMN, 0, 0);
if( p ){
struct SrcList_item *pItem = &pSrc->a[iSrc];
p->y.pTab = pItem->pTab;
p->iTable = pItem->iCursor;
if( p->y.pTab->iPKey==iCol ){
p->iColumn = -1;
}else{
... | 8,463,624,512,899,698,000,000,000,000,000,000,000 | resolve.c | 289,041,534,745,656,160,000,000,000,000,000,000,000 | [
"CWE-754"
] | CVE-2019-19646 | pragma.c in SQLite through 3.30.1 mishandles NOT NULL in an integrity_check PRAGMA command in certain cases of generated columns. | https://nvd.nist.gov/vuln/detail/CVE-2019-19646 |
365,871 | sqlite | 926f796e8feec15f3836aa0a060ed906f8ae04d3 | https://github.com/sqlite/sqlite | https://github.com/sqlite/sqlite/commit/926f796e8feec15f3836aa0a060ed906f8ae04d3 | Ensure that the SrcList_item.colUsed field is set correctly (set to have a
1 for all columns of the table) when a generated column appears in the USING
clause of a join.
FossilOrigin-Name: 1923efb283e8840fa7436eb20b9d2174ef7cace1690d3b97b572a0db2048b8e3 | 0 | Expr *sqlite3CreateColumnExpr(sqlite3 *db, SrcList *pSrc, int iSrc, int iCol){
Expr *p = sqlite3ExprAlloc(db, TK_COLUMN, 0, 0);
if( p ){
struct SrcList_item *pItem = &pSrc->a[iSrc];
Table *pTab = p->y.pTab = pItem->pTab;
p->iTable = pItem->iCursor;
if( p->y.pTab->iPKey==iCol ){
p->iColumn = -1... | 235,199,681,514,685,870,000,000,000,000,000,000,000 | resolve.c | 168,507,211,454,570,730,000,000,000,000,000,000,000 | [
"CWE-754"
] | CVE-2019-19646 | pragma.c in SQLite through 3.30.1 mishandles NOT NULL in an integrity_check PRAGMA command in certain cases of generated columns. | https://nvd.nist.gov/vuln/detail/CVE-2019-19646 |
204,823 | php-src | c4cca4c20e75359c9a13a1f9a36cb7b4e9601d29 | https://github.com/php/php-src | https://github.com/php/php-src/commit/c4cca4c20e75359c9a13a1f9a36cb7b4e9601d29?w=1 | Fix bug #73065: Out-Of-Bounds Read in php_wddx_push_element of wddx.c | 1 | */
static void php_wddx_push_element(void *user_data, const XML_Char *name, const XML_Char **atts)
{
st_entry ent;
wddx_stack *stack = (wddx_stack *)user_data;
if (!strcmp(name, EL_PACKET)) {
int i;
if (atts) for (i=0; atts[i]; i++) {
if (!strcmp(atts[i], EL_VERSION)) {
/* nothing for now */
}
}
... | 14,414,359,733,919,540,000,000,000,000,000,000,000 | wddx.c | 280,305,920,871,161,900,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-7418 | The php_wddx_push_element function in ext/wddx/wddx.c in PHP before 5.6.26 and 7.x before 7.0.11 allows remote attackers to cause a denial of service (invalid pointer access and out-of-bounds read) or possibly have unspecified other impact via an incorrect boolean element in a wddxPacket XML document, leading to mishan... | https://nvd.nist.gov/vuln/detail/CVE-2016-7418 |
365,987 | php-src | c4cca4c20e75359c9a13a1f9a36cb7b4e9601d29 | https://github.com/php/php-src | https://github.com/php/php-src/commit/c4cca4c20e75359c9a13a1f9a36cb7b4e9601d29?w=1 | Fix bug #73065: Out-Of-Bounds Read in php_wddx_push_element of wddx.c | 0 | */
static void php_wddx_push_element(void *user_data, const XML_Char *name, const XML_Char **atts)
{
st_entry ent;
wddx_stack *stack = (wddx_stack *)user_data;
if (!strcmp(name, EL_PACKET)) {
int i;
if (atts) for (i=0; atts[i]; i++) {
if (!strcmp(atts[i], EL_VERSION)) {
/* nothing for now */
}
}
... | 108,110,755,708,891,850,000,000,000,000,000,000,000 | wddx.c | 283,855,878,967,745,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-7418 | The php_wddx_push_element function in ext/wddx/wddx.c in PHP before 5.6.26 and 7.x before 7.0.11 allows remote attackers to cause a denial of service (invalid pointer access and out-of-bounds read) or possibly have unspecified other impact via an incorrect boolean element in a wddxPacket XML document, leading to mishan... | https://nvd.nist.gov/vuln/detail/CVE-2016-7418 |
204,824 | clamav-devel | 3cbd8b5668bd0f262a8c00b1fd57eb03c117b00a | https://github.com/vrtadmin/clamav-devel | https://github.com/vrtadmin/clamav-devel/commit/3cbd8b5668bd0f262a8c00b1fd57eb03c117b00a | libclamav/pe_icons.c: introduce LOGPARSEICONDETAILS define to reduce parseicon logging in default build | 1 | static int parseicon(icon_groupset *set, uint32_t rva, cli_ctx *ctx, struct cli_exe_section *exe_sections, uint16_t nsections, uint32_t hdr_size) {
struct {
unsigned int sz;
unsigned int w;
unsigned int h;
unsigned short planes;
unsigned short depth;
unsigned int comp;
unsigned int imagesize;
unsigned int... | 161,990,166,972,340,210,000,000,000,000,000,000,000 | pe_icons.c | 100,529,783,985,956,870,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2020 | Integer underflow in the cli_scanpe function in pe.c in ClamAV before 0.97.8 allows remote attackers to cause a denial of service (crash) via a skewed offset larger than the size of the PE section in a UPX packed executable, which triggers an out-of-bounds read. | https://nvd.nist.gov/vuln/detail/CVE-2013-2020 |
365,990 | clamav-devel | 3cbd8b5668bd0f262a8c00b1fd57eb03c117b00a | https://github.com/vrtadmin/clamav-devel | https://github.com/vrtadmin/clamav-devel/commit/3cbd8b5668bd0f262a8c00b1fd57eb03c117b00a | libclamav/pe_icons.c: introduce LOGPARSEICONDETAILS define to reduce parseicon logging in default build | 0 | static int parseicon(icon_groupset *set, uint32_t rva, cli_ctx *ctx, struct cli_exe_section *exe_sections, uint16_t nsections, uint32_t hdr_size) {
struct {
unsigned int sz;
unsigned int w;
unsigned int h;
unsigned short planes;
unsigned short depth;
unsigned int comp;
unsigned int imagesize;
unsigned int... | 40,765,558,056,279,880,000,000,000,000,000,000,000 | pe_icons.c | 268,890,378,613,524,870,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2020 | Integer underflow in the cli_scanpe function in pe.c in ClamAV before 0.97.8 allows remote attackers to cause a denial of service (crash) via a skewed offset larger than the size of the PE section in a UPX packed executable, which triggers an out-of-bounds read. | https://nvd.nist.gov/vuln/detail/CVE-2013-2020 |
204,827 | php-src | a5a15965da23c8e97657278fc8dfbf1dfb20c016 | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commit;h=a5a15965da23c8e97657278fc8dfbf1dfb20c016 | Fix #78863: DirectoryIterator class silently truncates after a null byte
Since the constructor of DirectoryIterator and friends is supposed to
accepts paths (i.e. strings without NUL bytes), we must not accept
arbitrary strings. | 1 | void spl_filesystem_object_construct(INTERNAL_FUNCTION_PARAMETERS, zend_long ctor_flags) /* {{{ */
{
spl_filesystem_object *intern;
char *path;
int parsed;
size_t len;
zend_long flags;
zend_error_handling error_handling;
zend_replace_error_handling(EH_THROW, spl_ce_UnexpectedValueException, &error_handling);
... | 70,184,727,776,418,730,000,000,000,000,000,000,000 | spl_directory.c | 296,730,226,747,378,420,000,000,000,000,000,000,000 | [
"CWE-74"
] | CVE-2019-11045 | In PHP versions 7.2.x below 7.2.26, 7.3.x below 7.3.13 and 7.4.0, PHP DirectoryIterator class accepts filenames with embedded \0 byte and treats them as terminating at that byte. This could lead to security vulnerabilities, e.g. in applications checking paths that the code is allowed to access. | https://nvd.nist.gov/vuln/detail/CVE-2019-11045 |
366,058 | php-src | a5a15965da23c8e97657278fc8dfbf1dfb20c016 | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commit;h=a5a15965da23c8e97657278fc8dfbf1dfb20c016 | Fix #78863: DirectoryIterator class silently truncates after a null byte
Since the constructor of DirectoryIterator and friends is supposed to
accepts paths (i.e. strings without NUL bytes), we must not accept
arbitrary strings. | 0 | void spl_filesystem_object_construct(INTERNAL_FUNCTION_PARAMETERS, zend_long ctor_flags) /* {{{ */
{
spl_filesystem_object *intern;
char *path;
int parsed;
size_t len;
zend_long flags;
zend_error_handling error_handling;
zend_replace_error_handling(EH_THROW, spl_ce_UnexpectedValueException, &error_handling);
... | 286,065,656,458,005,500,000,000,000,000,000,000,000 | spl_directory.c | 324,377,992,069,963,460,000,000,000,000,000,000,000 | [
"CWE-74"
] | CVE-2019-11045 | In PHP versions 7.2.x below 7.2.26, 7.3.x below 7.3.13 and 7.4.0, PHP DirectoryIterator class accepts filenames with embedded \0 byte and treats them as terminating at that byte. This could lead to security vulnerabilities, e.g. in applications checking paths that the code is allowed to access. | https://nvd.nist.gov/vuln/detail/CVE-2019-11045 |
204,828 | polkit | a04d13affe0fa53ff618e07aa8f57f4c0e3b9b81 | https://gitlab.freedesktop.org/polkit/polkit | https://gitlab.freedesktop.org/polkit/polkit/-/commit/a04d13affe0fa53ff618e07aa8f57f4c0e3b9b81 | GHSL-2021-074: authentication bypass vulnerability in polkit
initial values returned if error caught | 1 | polkit_system_bus_name_get_creds_sync (PolkitSystemBusName *system_bus_name,
guint32 *out_uid,
guint32 *out_pid,
GCancellable *cancellable,
GError **error)
{
gboolean ret = FALSE;
... | 101,148,048,157,964,300,000,000,000,000,000,000,000 | None | null | [
"CWE-754"
] | CVE-2021-3560 | It was found that polkit could be tricked into bypassing the credential checks for D-Bus requests, elevating the privileges of the requestor to the root user. This flaw could be used by an unprivileged local attacker to, for example, create a new local administrator. The highest threat from this vulnerability is to dat... | https://nvd.nist.gov/vuln/detail/CVE-2021-3560 |
366,159 | polkit | a04d13affe0fa53ff618e07aa8f57f4c0e3b9b81 | https://gitlab.freedesktop.org/polkit/polkit | https://gitlab.freedesktop.org/polkit/polkit/-/commit/a04d13affe0fa53ff618e07aa8f57f4c0e3b9b81 | GHSL-2021-074: authentication bypass vulnerability in polkit
initial values returned if error caught | 0 | polkit_system_bus_name_get_creds_sync (PolkitSystemBusName *system_bus_name,
guint32 *out_uid,
guint32 *out_pid,
GCancellable *cancellable,
GError **error)
{
gboolean ret = FALSE;
... | 260,734,700,528,986,700,000,000,000,000,000,000,000 | None | null | [
"CWE-754"
] | CVE-2021-3560 | It was found that polkit could be tricked into bypassing the credential checks for D-Bus requests, elevating the privileges of the requestor to the root user. This flaw could be used by an unprivileged local attacker to, for example, create a new local administrator. The highest threat from this vulnerability is to dat... | https://nvd.nist.gov/vuln/detail/CVE-2021-3560 |
204,831 | linux | 1399c59fa92984836db90538cf92397fe7caaa57 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1399c59fa92984836db90538cf92397fe7caaa57 | nl80211: fix memory leak in nl80211_get_ftm_responder_stats
In nl80211_get_ftm_responder_stats, a new skb is created via nlmsg_new
named msg. If nl80211hdr_put() fails, then msg should be released. The
return statement should be replace by goto to error handling code.
Fixes: 81e54d08d9d8 ("cfg80211: support FTM respo... | 1 | static int nl80211_get_ftm_responder_stats(struct sk_buff *skb,
struct genl_info *info)
{
struct cfg80211_registered_device *rdev = info->user_ptr[0];
struct net_device *dev = info->user_ptr[1];
struct wireless_dev *wdev = dev->ieee80211_ptr;
struct cfg80211_ftm_responder_stats ftm_stats = {};
struct sk_bu... | 196,291,267,499,025,540,000,000,000,000,000,000,000 | nl80211.c | 91,850,922,559,660,000,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2019-19055 | A memory leak in the nl80211_get_ftm_responder_stats() function in net/wireless/nl80211.c in the Linux kernel through 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering nl80211hdr_put() failures, aka CID-1399c59fa929. NOTE: third parties dispute the relevance of this because it occu... | https://nvd.nist.gov/vuln/detail/CVE-2019-19055 |
366,344 | linux | 1399c59fa92984836db90538cf92397fe7caaa57 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1399c59fa92984836db90538cf92397fe7caaa57 | nl80211: fix memory leak in nl80211_get_ftm_responder_stats
In nl80211_get_ftm_responder_stats, a new skb is created via nlmsg_new
named msg. If nl80211hdr_put() fails, then msg should be released. The
return statement should be replace by goto to error handling code.
Fixes: 81e54d08d9d8 ("cfg80211: support FTM respo... | 0 | static int nl80211_get_ftm_responder_stats(struct sk_buff *skb,
struct genl_info *info)
{
struct cfg80211_registered_device *rdev = info->user_ptr[0];
struct net_device *dev = info->user_ptr[1];
struct wireless_dev *wdev = dev->ieee80211_ptr;
struct cfg80211_ftm_responder_stats ftm_stats = {};
struct sk_bu... | 43,077,159,841,037,280,000,000,000,000,000,000,000 | nl80211.c | 142,896,446,383,646,170,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2019-19055 | A memory leak in the nl80211_get_ftm_responder_stats() function in net/wireless/nl80211.c in the Linux kernel through 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering nl80211hdr_put() failures, aka CID-1399c59fa929. NOTE: third parties dispute the relevance of this because it occu... | https://nvd.nist.gov/vuln/detail/CVE-2019-19055 |
204,841 | qemu | d4862a87e31a51de9eb260f25c9e99a75efe3235 | https://github.com/bonzini/qemu | http://git.qemu.org/?p=qemu.git;a=commit;h=d4862a87e31a51de9eb260f25c9e99a75efe3235 | i8254: fix out-of-bounds memory access in pit_ioport_read()
Due converting PIO to the new memory read/write api we no longer provide
separate I/O region lenghts for read and write operations. As a result,
reading from PIT Mode/Command register will end with accessing
pit->channels with invalid index.
Fix this by igno... | 1 | static uint64_t pit_ioport_read(void *opaque, hwaddr addr,
unsigned size)
{
PITCommonState *pit = opaque;
int ret, count;
PITChannelState *s;
addr &= 3;
s = &pit->channels[addr];
if (s->status_latched) {
s->status_latched = 0;
ret = s->status;
... | 249,151,357,581,003,230,000,000,000,000,000,000,000 | i8254.c | 231,579,447,042,081,650,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-3214 | The pit_ioport_read in i8254.c in the Linux kernel before 2.6.33 and QEMU before 2.3.1 does not distinguish between read lengths and write lengths, which might allow guest OS users to execute arbitrary code on the host OS by triggering use of an invalid index. | https://nvd.nist.gov/vuln/detail/CVE-2015-3214 |
366,561 | qemu | d4862a87e31a51de9eb260f25c9e99a75efe3235 | https://github.com/bonzini/qemu | http://git.qemu.org/?p=qemu.git;a=commit;h=d4862a87e31a51de9eb260f25c9e99a75efe3235 | i8254: fix out-of-bounds memory access in pit_ioport_read()
Due converting PIO to the new memory read/write api we no longer provide
separate I/O region lenghts for read and write operations. As a result,
reading from PIT Mode/Command register will end with accessing
pit->channels with invalid index.
Fix this by igno... | 0 | static uint64_t pit_ioport_read(void *opaque, hwaddr addr,
unsigned size)
{
PITCommonState *pit = opaque;
int ret, count;
PITChannelState *s;
addr &= 3;
if (addr == 3) {
/* Mode/Command register is write only, read is ignored */
return 0;
}
... | 103,207,940,373,319,180,000,000,000,000,000,000,000 | i8254.c | 7,755,840,818,486,709,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-3214 | The pit_ioport_read in i8254.c in the Linux kernel before 2.6.33 and QEMU before 2.3.1 does not distinguish between read lengths and write lengths, which might allow guest OS users to execute arbitrary code on the host OS by triggering use of an invalid index. | https://nvd.nist.gov/vuln/detail/CVE-2015-3214 |
204,846 | vim | 35a9a00afcb20897d462a766793ff45534810dc3 | https://github.com/vim/vim | https://github.com/vim/vim/commit/35a9a00afcb20897d462a766793ff45534810dc3 | patch 8.2.3428: using freed memory when replacing
Problem: Using freed memory when replacing. (Dhiraj Mishra)
Solution: Get the line pointer after calling ins_copychar(). | 1 | nv_replace(cmdarg_T *cap)
{
char_u *ptr;
int had_ctrl_v;
long n;
if (checkclearop(cap->oap))
return;
#ifdef FEAT_JOB_CHANNEL
if (bt_prompt(curbuf) && !prompt_curpos_editable())
{
clearopbeep(cap->oap);
return;
}
#endif
// get another character
if (cap->nchar == Ctrl_V)
{
h... | 75,579,518,303,629,215,000,000,000,000,000,000,000 | normal.c | 334,025,220,412,253,050,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2021-3796 | vim is vulnerable to Use After Free | https://nvd.nist.gov/vuln/detail/CVE-2021-3796 |
366,644 | vim | 35a9a00afcb20897d462a766793ff45534810dc3 | https://github.com/vim/vim | https://github.com/vim/vim/commit/35a9a00afcb20897d462a766793ff45534810dc3 | patch 8.2.3428: using freed memory when replacing
Problem: Using freed memory when replacing. (Dhiraj Mishra)
Solution: Get the line pointer after calling ins_copychar(). | 0 | nv_replace(cmdarg_T *cap)
{
char_u *ptr;
int had_ctrl_v;
long n;
if (checkclearop(cap->oap))
return;
#ifdef FEAT_JOB_CHANNEL
if (bt_prompt(curbuf) && !prompt_curpos_editable())
{
clearopbeep(cap->oap);
return;
}
#endif
// get another character
if (cap->nchar == Ctrl_V)
{
h... | 244,793,032,090,661,770,000,000,000,000,000,000,000 | normal.c | 72,583,640,376,175,970,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2021-3796 | vim is vulnerable to Use After Free | https://nvd.nist.gov/vuln/detail/CVE-2021-3796 |
204,847 | ImageMagick | f050a9b18ba537952abf20db2e18d62f07b4956e | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/f050a9b18ba537952abf20db2e18d62f07b4956e | Fixed memory leak reported in #1558 and fixed other leak. | 1 | static Image *ReadDOTImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
char
command[MagickPathExtent];
const char
*option;
graph_t
*graph;
Image
*image;
ImageInfo
*read_info;
MagickBooleanType
status;
/*
Open image file.
*/
assert(image_info != (const Imag... | 260,569,544,807,593,300,000,000,000,000,000,000,000 | dot.c | 227,160,092,507,807,520,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2019-16713 | ImageMagick 7.0.8-43 has a memory leak in coders/dot.c, as demonstrated by PingImage in MagickCore/constitute.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-16713 |
366,654 | ImageMagick | f050a9b18ba537952abf20db2e18d62f07b4956e | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/f050a9b18ba537952abf20db2e18d62f07b4956e | Fixed memory leak reported in #1558 and fixed other leak. | 0 | static Image *ReadDOTImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
char
command[MagickPathExtent];
const char
*option;
graph_t
*graph;
Image
*image;
ImageInfo
*read_info;
MagickBooleanType
status;
/*
Open image file.
*/
assert(image_info != (const Imag... | 193,481,519,760,652,520,000,000,000,000,000,000,000 | dot.c | 65,871,818,416,105,160,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2019-16713 | ImageMagick 7.0.8-43 has a memory leak in coders/dot.c, as demonstrated by PingImage in MagickCore/constitute.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-16713 |
204,848 | libyang | 6cc51b1757dfbb7cff92de074ada65e8523289a6 | https://github.com/CESNET/libyang | https://github.com/CESNET/libyang/commit/6cc51b1757dfbb7cff92de074ada65e8523289a6 | yang parser BUGFIX double free
Fixes #769 | 1 | int
yyparse (void *scanner, struct yang_parameter *param)
{
/* The lookahead symbol. */
int yychar;
char *s = NULL, *tmp_s = NULL, *ext_name = NULL;
struct lys_module *trg = NULL;
struct lys_node *tpdf_parent = NULL, *data_node = NULL;
struct lys_ext_instance_complex *ext_instance = NULL;
int is_ext_instance;
void *ac... | 246,246,709,336,386,860,000,000,000,000,000,000,000 | parser_yang_bis.c | 334,107,674,555,853,970,000,000,000,000,000,000,000 | [
"CWE-415"
] | CVE-2019-20394 | A double-free is present in libyang before v1.0-r3 in the function yyparse() when a type statement in used in a notification statement. Applications that use libyang to parse untrusted input yang files may be vulnerable to this flaw, which would cause a crash or potentially code execution. | https://nvd.nist.gov/vuln/detail/CVE-2019-20394 |
366,657 | libyang | 6cc51b1757dfbb7cff92de074ada65e8523289a6 | https://github.com/CESNET/libyang | https://github.com/CESNET/libyang/commit/6cc51b1757dfbb7cff92de074ada65e8523289a6 | yang parser BUGFIX double free
Fixes #769 | 0 | int
yyparse (void *scanner, struct yang_parameter *param)
{
/* The lookahead symbol. */
int yychar;
char *s = NULL, *tmp_s = NULL, *ext_name = NULL;
struct lys_module *trg = NULL;
struct lys_node *tpdf_parent = NULL, *data_node = NULL;
struct lys_ext_instance_complex *ext_instance = NULL;
int is_ext_instance;
void *ac... | 237,431,378,676,718,000,000,000,000,000,000,000,000 | parser_yang_bis.c | 258,076,237,716,557,340,000,000,000,000,000,000,000 | [
"CWE-415"
] | CVE-2019-20394 | A double-free is present in libyang before v1.0-r3 in the function yyparse() when a type statement in used in a notification statement. Applications that use libyang to parse untrusted input yang files may be vulnerable to this flaw, which would cause a crash or potentially code execution. | https://nvd.nist.gov/vuln/detail/CVE-2019-20394 |
204,857 | php-src | 58006537fc5f133ae8549efe5118cde418b3ace9 | https://github.com/php/php-src | https://github.com/php/php-src/commit/58006537fc5f133ae8549efe5118cde418b3ace9 | Fix bug #81719: mysqlnd/pdo password buffer overflow | 1 | static size_t
php_mysqlnd_change_auth_response_write(MYSQLND_CONN_DATA * conn, void * _packet)
{
MYSQLND_PACKET_CHANGE_AUTH_RESPONSE *packet= (MYSQLND_PACKET_CHANGE_AUTH_RESPONSE *) _packet;
MYSQLND_ERROR_INFO * error_info = conn->error_info;
MYSQLND_PFC * pfc = conn->protocol_frame_codec;
MYSQLND_VIO * vio = conn-... | 107,314,003,748,433,360,000,000,000,000,000,000,000 | mysqlnd_wireprotocol.c | 36,575,036,206,325,386,000,000,000,000,000,000,000 | [
"CWE-120"
] | CVE-2022-31626 | In PHP versions 7.4.x below 7.4.30, 8.0.x below 8.0.20, and 8.1.x below 8.1.7, when pdo_mysql extension with mysqlnd driver, if the third party is allowed to supply host to connect to and the password for the connection, password of excessive length can trigger a buffer overflow in PHP, which can lead to a remote code ... | https://nvd.nist.gov/vuln/detail/CVE-2022-31626 |
366,838 | php-src | 58006537fc5f133ae8549efe5118cde418b3ace9 | https://github.com/php/php-src | https://github.com/php/php-src/commit/58006537fc5f133ae8549efe5118cde418b3ace9 | Fix bug #81719: mysqlnd/pdo password buffer overflow | 0 | static size_t
php_mysqlnd_change_auth_response_write(MYSQLND_CONN_DATA * conn, void * _packet)
{
MYSQLND_PACKET_CHANGE_AUTH_RESPONSE *packet= (MYSQLND_PACKET_CHANGE_AUTH_RESPONSE *) _packet;
MYSQLND_ERROR_INFO * error_info = conn->error_info;
MYSQLND_PFC * pfc = conn->protocol_frame_codec;
MYSQLND_VIO * vio = conn-... | 218,054,549,298,811,480,000,000,000,000,000,000,000 | mysqlnd_wireprotocol.c | 144,728,643,896,346,290,000,000,000,000,000,000,000 | [
"CWE-120"
] | CVE-2022-31626 | In PHP versions 7.4.x below 7.4.30, 8.0.x below 8.0.20, and 8.1.x below 8.1.7, when pdo_mysql extension with mysqlnd driver, if the third party is allowed to supply host to connect to and the password for the connection, password of excessive length can trigger a buffer overflow in PHP, which can lead to a remote code ... | https://nvd.nist.gov/vuln/detail/CVE-2022-31626 |
204,864 | libcaca | 84bd155087b93ab2d8d7cb5b1ac94ecd4cf4f93c | https://github.com/cacalabs/libcaca | https://github.com/cacalabs/libcaca/commit/84bd155087b93ab2d8d7cb5b1ac94ecd4cf4f93c | dither: fix integer overflows that were causing a division by zero.
Fixes: #36 (CVE-2018-20544) | 1 | int caca_dither_bitmap(caca_canvas_t *cv, int x, int y, int w, int h,
caca_dither_t const *d, void const *pixels)
{
int *floyd_steinberg, *fs_r, *fs_g, *fs_b;
uint32_t savedattr;
int fs_length;
int x1, y1, x2, y2, pitch, deltax, deltay, dchmax;
if(!d || !pixels)
retu... | 222,182,658,956,075,870,000,000,000,000,000,000,000 | dither.c | 75,964,262,565,125,770,000,000,000,000,000,000,000 | [
"CWE-369"
] | CVE-2018-20544 | There is floating point exception at caca/dither.c (function caca_dither_bitmap) in libcaca 0.99.beta19. | https://nvd.nist.gov/vuln/detail/CVE-2018-20544 |
366,999 | libcaca | 84bd155087b93ab2d8d7cb5b1ac94ecd4cf4f93c | https://github.com/cacalabs/libcaca | https://github.com/cacalabs/libcaca/commit/84bd155087b93ab2d8d7cb5b1ac94ecd4cf4f93c | dither: fix integer overflows that were causing a division by zero.
Fixes: #36 (CVE-2018-20544) | 0 | int caca_dither_bitmap(caca_canvas_t *cv, int x, int y, int w, int h,
caca_dither_t const *d, void const *pixels)
{
int *floyd_steinberg, *fs_r, *fs_g, *fs_b;
uint32_t savedattr;
int fs_length;
int x1, y1, x2, y2, pitch, deltax, deltay, dchmax;
if(!d || !pixels)
retu... | 326,407,322,839,035,470,000,000,000,000,000,000,000 | dither.c | 90,459,157,697,461,890,000,000,000,000,000,000,000 | [
"CWE-369"
] | CVE-2018-20544 | There is floating point exception at caca/dither.c (function caca_dither_bitmap) in libcaca 0.99.beta19. | https://nvd.nist.gov/vuln/detail/CVE-2018-20544 |
204,869 | bluez | 1cd644db8c23a2f530ddb93cebed7dacc5f5721a | https://github.com/bluez/bluez | https://github.com/bluez/bluez/commit/1cd644db8c23a2f530ddb93cebed7dacc5f5721a | shared/att: Fix possible crash on disconnect
If there are pending request while disconnecting they would be notified
but clients may endup being freed in the proccess which will then be
calling bt_att_cancel to cancal its requests causing the following
trace:
Invalid read of size 4
at 0x1D894C: enable_ccc_callback... | 1 | static bool disconnect_cb(struct io *io, void *user_data)
{
struct bt_att_chan *chan = user_data;
struct bt_att *att = chan->att;
int err;
socklen_t len;
len = sizeof(err);
if (getsockopt(chan->fd, SOL_SOCKET, SO_ERROR, &err, &len) < 0) {
util_debug(chan->att->debug_callback, chan->att->debug_data,
"(cha... | 40,730,305,161,339,517,000,000,000,000,000,000,000 | att.c | 287,198,484,261,187,900,000,000,000,000,000,000,000 | [
"CWE-415"
] | CVE-2020-27153 | In BlueZ before 5.55, a double free was found in the gatttool disconnect_cb() routine from shared/att.c. A remote attacker could potentially cause a denial of service or code execution, during service discovery, due to a redundant disconnect MGMT event. | https://nvd.nist.gov/vuln/detail/CVE-2020-27153 |
367,118 | bluez | 1cd644db8c23a2f530ddb93cebed7dacc5f5721a | https://github.com/bluez/bluez | https://github.com/bluez/bluez/commit/1cd644db8c23a2f530ddb93cebed7dacc5f5721a | shared/att: Fix possible crash on disconnect
If there are pending request while disconnecting they would be notified
but clients may endup being freed in the proccess which will then be
calling bt_att_cancel to cancal its requests causing the following
trace:
Invalid read of size 4
at 0x1D894C: enable_ccc_callback... | 0 | static bool disconnect_cb(struct io *io, void *user_data)
{
struct bt_att_chan *chan = user_data;
struct bt_att *att = chan->att;
int err;
socklen_t len;
len = sizeof(err);
if (getsockopt(chan->fd, SOL_SOCKET, SO_ERROR, &err, &len) < 0) {
util_debug(chan->att->debug_callback, chan->att->debug_data,
"(cha... | 116,817,315,527,218,330,000,000,000,000,000,000,000 | att.c | 97,920,202,388,798,680,000,000,000,000,000,000,000 | [
"CWE-415"
] | CVE-2020-27153 | In BlueZ before 5.55, a double free was found in the gatttool disconnect_cb() routine from shared/att.c. A remote attacker could potentially cause a denial of service or code execution, during service discovery, due to a redundant disconnect MGMT event. | https://nvd.nist.gov/vuln/detail/CVE-2020-27153 |
204,879 | libslirp | c7ede54cbd2e2b25385325600958ba0124e31cc0 | https://gitlab.freedesktop.org/slirp/libslirp | https://gitlab.freedesktop.org/slirp/libslirp/-/commit/c7ede54cbd2e2b25385325600958ba0124e31cc0 | Drop bogus IPv6 messages
Drop IPv6 message shorter than what's mentioned in the payload
length header (+ the size of the IPv6 header). They're invalid an could
lead to data leakage in icmp6_send_echoreply(). | 1 | void ip6_input(struct mbuf *m)
{
struct ip6 *ip6;
Slirp *slirp = m->slirp;
if (!slirp->in6_enabled) {
goto bad;
}
DEBUG_CALL("ip6_input");
DEBUG_ARG("m = %p", m);
DEBUG_ARG("m_len = %d", m->m_len);
if (m->m_len < sizeof(struct ip6)) {
goto bad;
}
ip6 = mtod(m,... | 240,340,833,440,501,700,000,000,000,000,000,000,000 | ip6_input.c | 183,976,981,809,510,540,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2020-10756 | An out-of-bounds read vulnerability was found in the SLiRP networking implementation of the QEMU emulator. This flaw occurs in the icmp6_send_echoreply() routine while replying to an ICMP echo request, also known as ping. This flaw allows a malicious guest to leak the contents of the host memory, resulting in possible ... | https://nvd.nist.gov/vuln/detail/CVE-2020-10756 |
367,175 | libslirp | c7ede54cbd2e2b25385325600958ba0124e31cc0 | https://gitlab.freedesktop.org/slirp/libslirp | https://gitlab.freedesktop.org/slirp/libslirp/-/commit/c7ede54cbd2e2b25385325600958ba0124e31cc0 | Drop bogus IPv6 messages
Drop IPv6 message shorter than what's mentioned in the payload
length header (+ the size of the IPv6 header). They're invalid an could
lead to data leakage in icmp6_send_echoreply(). | 0 | void ip6_input(struct mbuf *m)
{
struct ip6 *ip6;
Slirp *slirp = m->slirp;
if (!slirp->in6_enabled) {
goto bad;
}
DEBUG_CALL("ip6_input");
DEBUG_ARG("m = %p", m);
DEBUG_ARG("m_len = %d", m->m_len);
if (m->m_len < sizeof(struct ip6)) {
goto bad;
}
ip6 = mtod(m,... | 88,039,214,949,440,510,000,000,000,000,000,000,000 | ip6_input.c | 125,892,682,135,406,330,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2020-10756 | An out-of-bounds read vulnerability was found in the SLiRP networking implementation of the QEMU emulator. This flaw occurs in the icmp6_send_echoreply() routine while replying to an ICMP echo request, also known as ping. This flaw allows a malicious guest to leak the contents of the host memory, resulting in possible ... | https://nvd.nist.gov/vuln/detail/CVE-2020-10756 |
204,883 | php-src | 49782c54994ecca2ef2a061063bd5a7079c43527 | https://github.com/php/php-src | https://git.php.net/?p=php-src.git;a=commit;h=49782c54994ecca2ef2a061063bd5a7079c43527 | Fix bug #76248 - Malicious LDAP-Server Response causes Crash | 1 | PHP_FUNCTION(ldap_get_entries)
{
zval *link, *result;
LDAPMessage *ldap_result, *ldap_result_entry;
zval *tmp1, *tmp2;
ldap_linkdata *ld;
LDAP *ldap;
int num_entries, num_attrib, num_values, i;
BerElement *ber;
char *attribute;
size_t attr_len;
struct berval **ldap_value;
char *dn;
if (zend_parse_parameter... | 206,527,534,868,897,700,000,000,000,000,000,000,000 | ldap.c | 16,100,690,716,253,703,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2018-10548 | An issue was discovered in PHP before 5.6.36, 7.0.x before 7.0.30, 7.1.x before 7.1.17, and 7.2.x before 7.2.5. ext/ldap/ldap.c allows remote LDAP servers to cause a denial of service (NULL pointer dereference and application crash) because of mishandling of the ldap_get_dn return value. | https://nvd.nist.gov/vuln/detail/CVE-2018-10548 |
367,372 | php-src | 49782c54994ecca2ef2a061063bd5a7079c43527 | https://github.com/php/php-src | https://git.php.net/?p=php-src.git;a=commit;h=49782c54994ecca2ef2a061063bd5a7079c43527 | Fix bug #76248 - Malicious LDAP-Server Response causes Crash | 0 | PHP_FUNCTION(ldap_get_entries)
{
zval *link, *result;
LDAPMessage *ldap_result, *ldap_result_entry;
zval *tmp1, *tmp2;
ldap_linkdata *ld;
LDAP *ldap;
int num_entries, num_attrib, num_values, i;
BerElement *ber;
char *attribute;
size_t attr_len;
struct berval **ldap_value;
char *dn;
if (zend_parse_parameter... | 284,115,107,865,349,700,000,000,000,000,000,000,000 | ldap.c | 15,172,069,511,262,146,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2018-10548 | An issue was discovered in PHP before 5.6.36, 7.0.x before 7.0.30, 7.1.x before 7.1.17, and 7.2.x before 7.2.5. ext/ldap/ldap.c allows remote LDAP servers to cause a denial of service (NULL pointer dereference and application crash) because of mishandling of the ldap_get_dn return value. | https://nvd.nist.gov/vuln/detail/CVE-2018-10548 |
205,515 | oniguruma | 778a43dd56925ed58bbe26e3a7bb8202d72c3f3f | https://github.com/kkos/oniguruma | https://github.com/kkos/oniguruma/commit/778a43dd56925ed58bbe26e3a7bb8202d72c3f3f | fix #164: Integer overflow related to reg->dmax in search_in_range() | 1 | search_in_range(regex_t* reg, const UChar* str, const UChar* end,
const UChar* start, const UChar* range, /* match start range */
const UChar* data_range, /* subject string range */
OnigRegion* region,
OnigOptionType option, OnigMatchParam* mp)
{
int r;
... | 162,970,409,423,573,550,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2019-19012 | An integer overflow in the search_in_range function in regexec.c in Oniguruma 6.x before 6.9.4_rc2 leads to an out-of-bounds read, in which the offset of this read is under the control of an attacker. (This only affects the 32-bit compiled version). Remote attackers can cause a denial-of-service or information disclosu... | https://nvd.nist.gov/vuln/detail/CVE-2019-19012 |
368,012 | oniguruma | 778a43dd56925ed58bbe26e3a7bb8202d72c3f3f | https://github.com/kkos/oniguruma | https://github.com/kkos/oniguruma/commit/778a43dd56925ed58bbe26e3a7bb8202d72c3f3f | fix #164: Integer overflow related to reg->dmax in search_in_range() | 0 | search_in_range(regex_t* reg, const UChar* str, const UChar* end,
const UChar* start, const UChar* range, /* match start range */
const UChar* data_range, /* subject string range */
OnigRegion* region,
OnigOptionType option, OnigMatchParam* mp)
{
int r;
... | 300,379,729,317,854,580,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2019-19012 | An integer overflow in the search_in_range function in regexec.c in Oniguruma 6.x before 6.9.4_rc2 leads to an out-of-bounds read, in which the offset of this read is under the control of an attacker. (This only affects the 32-bit compiled version). Remote attackers can cause a denial-of-service or information disclosu... | https://nvd.nist.gov/vuln/detail/CVE-2019-19012 |
205,569 | samba | 94295b7aa22d2544af5323bca70d3dcb97fd7c64 | https://github.com/samba-team/samba | https://git.samba.org/?p=samba.git;a=commitdiff;h=94295b7aa22d2544af5323bca70d3dcb97fd7c64 | CVE-2016-2019: s3:libsmb: add comment regarding smbXcli_session_is_guest() with mandatory signing
BUG: https://bugzilla.samba.org/show_bug.cgi?id=11860
Signed-off-by: Stefan Metzmacher <metze@samba.org> | 1 | static void cli_session_setup_gensec_remote_done(struct tevent_req *subreq)
{
struct tevent_req *req =
tevent_req_callback_data(subreq,
struct tevent_req);
struct cli_session_setup_gensec_state *state =
tevent_req_data(req,
struct cli_session_setup_gensec_state);
NTSTATUS status;
TALLOC_FREE(state->inbuf);... | 74,551,486,247,016,670,000,000,000,000,000,000,000 | cliconnect.c | 186,525,302,681,237,900,000,000,000,000,000,000,000 | [
"CWE-94"
] | CVE-2016-2119 | libcli/smb/smbXcli_base.c in Samba 4.x before 4.2.14, 4.3.x before 4.3.11, and 4.4.x before 4.4.5 allows man-in-the-middle attackers to bypass a client-signing protection mechanism, and consequently spoof SMB2 and SMB3 servers, via the (1) SMB2_SESSION_FLAG_IS_GUEST or (2) SMB2_SESSION_FLAG_IS_NULL flag. | https://nvd.nist.gov/vuln/detail/CVE-2016-2119 |
368,214 | samba | 94295b7aa22d2544af5323bca70d3dcb97fd7c64 | https://github.com/samba-team/samba | https://git.samba.org/?p=samba.git;a=commitdiff;h=94295b7aa22d2544af5323bca70d3dcb97fd7c64 | CVE-2016-2019: s3:libsmb: add comment regarding smbXcli_session_is_guest() with mandatory signing
BUG: https://bugzilla.samba.org/show_bug.cgi?id=11860
Signed-off-by: Stefan Metzmacher <metze@samba.org> | 0 | static void cli_session_setup_gensec_remote_done(struct tevent_req *subreq)
{
struct tevent_req *req =
tevent_req_callback_data(subreq,
struct tevent_req);
struct cli_session_setup_gensec_state *state =
tevent_req_data(req,
struct cli_session_setup_gensec_state);
NTSTATUS status;
TALLOC_FREE(state->inbuf);... | 38,549,631,979,881,870,000,000,000,000,000,000,000 | cliconnect.c | 221,907,680,471,963,130,000,000,000,000,000,000,000 | [
"CWE-94"
] | CVE-2016-2119 | libcli/smb/smbXcli_base.c in Samba 4.x before 4.2.14, 4.3.x before 4.3.11, and 4.4.x before 4.4.5 allows man-in-the-middle attackers to bypass a client-signing protection mechanism, and consequently spoof SMB2 and SMB3 servers, via the (1) SMB2_SESSION_FLAG_IS_GUEST or (2) SMB2_SESSION_FLAG_IS_NULL flag. | https://nvd.nist.gov/vuln/detail/CVE-2016-2119 |
205,571 | linux | e69dbd4619e7674c1679cba49afd9dd9ac347eef | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e69dbd4619e7674c1679cba49afd9dd9ac347eef | ieee802154: enforce CAP_NET_RAW for raw sockets
When creating a raw AF_IEEE802154 socket, CAP_NET_RAW needs to be
checked first.
Signed-off-by: Ori Nimron <orinimron123@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Acked-by: Stefan Schmidt <stefan@datenfreihafen.org>
Signed-off-by: David S... | 1 | static int ieee802154_create(struct net *net, struct socket *sock,
int protocol, int kern)
{
struct sock *sk;
int rc;
struct proto *proto;
const struct proto_ops *ops;
if (!net_eq(net, &init_net))
return -EAFNOSUPPORT;
switch (sock->type) {
case SOCK_RAW:
proto = &ieee802154_raw_prot;
ops = &ieee... | 139,915,128,781,295,710,000,000,000,000,000,000,000 | socket.c | 229,868,972,394,345,420,000,000,000,000,000,000,000 | [
"CWE-276"
] | CVE-2019-17053 | ieee802154_create in net/ieee802154/socket.c in the AF_IEEE802154 network module in the Linux kernel through 5.3.2 does not enforce CAP_NET_RAW, which means that unprivileged users can create a raw socket, aka CID-e69dbd4619e7. | https://nvd.nist.gov/vuln/detail/CVE-2019-17053 |
368,280 | linux | e69dbd4619e7674c1679cba49afd9dd9ac347eef | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e69dbd4619e7674c1679cba49afd9dd9ac347eef | ieee802154: enforce CAP_NET_RAW for raw sockets
When creating a raw AF_IEEE802154 socket, CAP_NET_RAW needs to be
checked first.
Signed-off-by: Ori Nimron <orinimron123@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Acked-by: Stefan Schmidt <stefan@datenfreihafen.org>
Signed-off-by: David S... | 0 | static int ieee802154_create(struct net *net, struct socket *sock,
int protocol, int kern)
{
struct sock *sk;
int rc;
struct proto *proto;
const struct proto_ops *ops;
if (!net_eq(net, &init_net))
return -EAFNOSUPPORT;
switch (sock->type) {
case SOCK_RAW:
rc = -EPERM;
if (!capable(CAP_NET_RAW))
... | 111,374,327,814,135,630,000,000,000,000,000,000,000 | socket.c | 307,884,334,270,640,340,000,000,000,000,000,000,000 | [
"CWE-276"
] | CVE-2019-17053 | ieee802154_create in net/ieee802154/socket.c in the AF_IEEE802154 network module in the Linux kernel through 5.3.2 does not enforce CAP_NET_RAW, which means that unprivileged users can create a raw socket, aka CID-e69dbd4619e7. | https://nvd.nist.gov/vuln/detail/CVE-2019-17053 |
205,572 | poppler | d2f5d424ba8752f9a9e9dad410546ec1b46caa0a | https://github.com/freedesktop/poppler | https://gitlab.freedesktop.org/poppler/poppler/commit/d2f5d424ba8752f9a9e9dad410546ec1b46caa0a | pdfdetach: Check for valid file name of embedded file before using it to determine save path.
Closes #660 | 1 | int main(int argc, char *argv[]) {
GooString *fileName;
UnicodeMap *uMap;
GooString *ownerPW, *userPW;
PDFDoc *doc;
char uBuf[8];
char path[1024];
char *p;
bool ok;
int exitCode;
GooList *embeddedFiles = nullptr;
int nFiles, nPages, n, i, j;
FileSpec *fileSpec;
Page *page;
Annots *annots;
... | 16,580,154,496,579,372,000,000,000,000,000,000,000 | pdfdetach.cc | 248,280,362,835,072,330,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2018-19060 | An issue was discovered in Poppler 0.71.0. There is a NULL pointer dereference in goo/GooString.h, will lead to denial of service, as demonstrated by utils/pdfdetach.cc not validating a filename of an embedded file before constructing a save path. | https://nvd.nist.gov/vuln/detail/CVE-2018-19060 |
368,294 | poppler | d2f5d424ba8752f9a9e9dad410546ec1b46caa0a | https://github.com/freedesktop/poppler | https://gitlab.freedesktop.org/poppler/poppler/commit/d2f5d424ba8752f9a9e9dad410546ec1b46caa0a | pdfdetach: Check for valid file name of embedded file before using it to determine save path.
Closes #660 | 0 | int main(int argc, char *argv[]) {
GooString *fileName;
UnicodeMap *uMap;
GooString *ownerPW, *userPW;
PDFDoc *doc;
char uBuf[8];
char path[1024];
char *p;
bool ok;
int exitCode;
GooList *embeddedFiles = nullptr;
int nFiles, nPages, n, i, j;
FileSpec *fileSpec;
Page *page;
Annots *annots;
... | 266,531,793,746,289,000,000,000,000,000,000,000,000 | pdfdetach.cc | 151,008,064,577,835,150,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2018-19060 | An issue was discovered in Poppler 0.71.0. There is a NULL pointer dereference in goo/GooString.h, will lead to denial of service, as demonstrated by utils/pdfdetach.cc not validating a filename of an embedded file before constructing a save path. | https://nvd.nist.gov/vuln/detail/CVE-2018-19060 |
205,574 | libgit2 | 64c612cc3e25eff5fb02c59ef5a66ba7a14751e4 | https://github.com/libgit2/libgit2 | https://github.com/libgit2/libgit2/commit/64c612cc3e25eff5fb02c59ef5a66ba7a14751e4 | Protect against 8.3 "short name" attacks also on Linux/macOS
The Windows Subsystem for Linux (WSL) is getting increasingly popular,
in particular because it makes it _so_ easy to run Linux software on
Windows' files, via the auto-mounted Windows drives (`C:\` is mapped to
`/mnt/c/`, no need to set that up manually).
... | 1 | static int checkout_verify_paths(
git_repository *repo,
int action,
git_diff_delta *delta)
{
unsigned int flags = GIT_PATH_REJECT_WORKDIR_DEFAULTS;
if (action & CHECKOUT_ACTION__REMOVE) {
if (!git_path_isvalid(repo, delta->old_file.path, delta->old_file.mode, flags)) {
git_error_set(GIT_ERROR_CHECKOUT, "cann... | 250,212,561,924,659,960,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2020-12279 | An issue was discovered in libgit2 before 0.28.4 and 0.9x before 0.99.0. checkout.c mishandles equivalent filenames that exist because of NTFS short names. This may allow remote code execution when cloning a repository. This issue is similar to CVE-2019-1353. | https://nvd.nist.gov/vuln/detail/CVE-2020-12279 |
368,376 | libgit2 | 64c612cc3e25eff5fb02c59ef5a66ba7a14751e4 | https://github.com/libgit2/libgit2 | https://github.com/libgit2/libgit2/commit/64c612cc3e25eff5fb02c59ef5a66ba7a14751e4 | Protect against 8.3 "short name" attacks also on Linux/macOS
The Windows Subsystem for Linux (WSL) is getting increasingly popular,
in particular because it makes it _so_ easy to run Linux software on
Windows' files, via the auto-mounted Windows drives (`C:\` is mapped to
`/mnt/c/`, no need to set that up manually).
... | 0 | static int checkout_verify_paths(
git_repository *repo,
int action,
git_diff_delta *delta)
{
unsigned int flags = GIT_PATH_REJECT_WORKDIR_DEFAULTS | GIT_PATH_REJECT_DOT_GIT_NTFS;
if (action & CHECKOUT_ACTION__REMOVE) {
if (!git_path_isvalid(repo, delta->old_file.path, delta->old_file.mode, flags)) {
git_erro... | 199,111,540,326,248,070,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2020-12279 | An issue was discovered in libgit2 before 0.28.4 and 0.9x before 0.99.0. checkout.c mishandles equivalent filenames that exist because of NTFS short names. This may allow remote code execution when cloning a repository. This issue is similar to CVE-2019-1353. | https://nvd.nist.gov/vuln/detail/CVE-2020-12279 |
205,575 | optee_os | 30d13250c390c4f56adefdcd3b64b7cc672f9fe2 | https://github.com/OP-TEE/optee_os | https://github.com/OP-TEE/optee_os/commit/30d13250c390c4f56adefdcd3b64b7cc672f9fe2 | rsa_verify_hash: fix possible bleichenbacher signature attack
Fixes CVE-2016-6129
cherry-picked from:
https://github.com/libtom/libtomcrypt/commit/5eb9743410ce4657e9d54fef26a2ee31a1b5dd09
Acked-by: Jerome Forissier <jerome.forissier@linaro.org>
Tested-by: Jens Wiklander <jens.wiklander@linaro.org> (QEMU)
Signed-off-... | 1 | int rsa_verify_hash_ex(const unsigned char *sig, unsigned long siglen,
const unsigned char *hash, unsigned long hashlen,
int padding,
int hash_idx, unsigned long saltlen,
int ... | 19,224,811,408,210,450,000,000,000,000,000,000,000 | rsa_verify_hash.c | 180,732,859,638,298,840,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-6129 | The rsa_verify_hash_ex function in rsa_verify_hash.c in LibTomCrypt, as used in OP-TEE before 2.2.0, does not validate that the message length is equal to the ASN.1 encoded data length, which makes it easier for remote attackers to forge RSA signatures or public certificates by leveraging a Bleichenbacher signature for... | https://nvd.nist.gov/vuln/detail/CVE-2016-6129 |
368,408 | optee_os | 30d13250c390c4f56adefdcd3b64b7cc672f9fe2 | https://github.com/OP-TEE/optee_os | https://github.com/OP-TEE/optee_os/commit/30d13250c390c4f56adefdcd3b64b7cc672f9fe2 | rsa_verify_hash: fix possible bleichenbacher signature attack
Fixes CVE-2016-6129
cherry-picked from:
https://github.com/libtom/libtomcrypt/commit/5eb9743410ce4657e9d54fef26a2ee31a1b5dd09
Acked-by: Jerome Forissier <jerome.forissier@linaro.org>
Tested-by: Jens Wiklander <jens.wiklander@linaro.org> (QEMU)
Signed-off-... | 0 | int rsa_verify_hash_ex(const unsigned char *sig, unsigned long siglen,
const unsigned char *hash, unsigned long hashlen,
int padding,
int hash_idx, unsigned long saltlen,
int ... | 92,942,365,125,606,670,000,000,000,000,000,000,000 | rsa_verify_hash.c | 210,652,562,281,140,970,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-6129 | The rsa_verify_hash_ex function in rsa_verify_hash.c in LibTomCrypt, as used in OP-TEE before 2.2.0, does not validate that the message length is equal to the ASN.1 encoded data length, which makes it easier for remote attackers to forge RSA signatures or public certificates by leveraging a Bleichenbacher signature for... | https://nvd.nist.gov/vuln/detail/CVE-2016-6129 |
205,580 | gnupg | c6dbfe89903d0c8191cf50ecf1abb3c8458b427a | http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg | http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commitdiff;h=c6dbfe89903d0c8191cf50ecf1abb3c8458b427a | random: Hash continuous areas in the csprng pool.
* cipher/random.c (mix_pool): Store the first hash at the end of the
pool.
--
This fixes a long standing bug (since 1998) in Libgcrypt and GnuPG.
An attacker who obtains 580 bytes of the random number from the
standard RNG can trivially predict the next 20 bytes of ou... | 1 | mix_pool(byte *pool)
{
char *hashbuf = pool + POOLSIZE;
char *p, *pend;
int i, n;
RMD160_CONTEXT md;
rmd160_init( &md );
#if DIGESTLEN != 20
#error must have a digest length of 20 for ripe-md-160
#endif
/* loop over the pool */
pend = pool + POOLSIZE;
memcpy(hashbuf, pend - DIGESTLEN, D... | 131,570,372,674,305,390,000,000,000,000,000,000,000 | random.c | 247,284,420,734,872,000,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2016-6313 | The mixing functions in the random number generator in Libgcrypt before 1.5.6, 1.6.x before 1.6.6, and 1.7.x before 1.7.3 and GnuPG before 1.4.21 make it easier for attackers to obtain the values of 160 bits by leveraging knowledge of the previous 4640 bits. | https://nvd.nist.gov/vuln/detail/CVE-2016-6313 |
368,490 | gnupg | c6dbfe89903d0c8191cf50ecf1abb3c8458b427a | http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg | http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commitdiff;h=c6dbfe89903d0c8191cf50ecf1abb3c8458b427a | random: Hash continuous areas in the csprng pool.
* cipher/random.c (mix_pool): Store the first hash at the end of the
pool.
--
This fixes a long standing bug (since 1998) in Libgcrypt and GnuPG.
An attacker who obtains 580 bytes of the random number from the
standard RNG can trivially predict the next 20 bytes of ou... | 0 | mix_pool(byte *pool)
{
char *hashbuf = pool + POOLSIZE;
char *p, *pend;
int i, n;
RMD160_CONTEXT md;
rmd160_init( &md );
#if DIGESTLEN != 20
#error must have a digest length of 20 for ripe-md-160
#endif
/* pool -> pool' */
pend = pool + POOLSIZE;
memcpy(hashbuf, pend - DIGESTLEN, DIGEST... | 129,283,300,313,097,470,000,000,000,000,000,000,000 | random.c | 161,193,903,877,116,560,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2016-6313 | The mixing functions in the random number generator in Libgcrypt before 1.5.6, 1.6.x before 1.6.6, and 1.7.x before 1.7.3 and GnuPG before 1.4.21 make it easier for attackers to obtain the values of 160 bits by leveraging knowledge of the previous 4640 bits. | https://nvd.nist.gov/vuln/detail/CVE-2016-6313 |
205,581 | aircrack-ng | 091b153f294b9b695b0b2831e65936438b550d7b | https://github.com/aircrack-ng/aircrack-ng | https://github.com/aircrack-ng/aircrack-ng/commit/091b153f294b9b695b0b2831e65936438b550d7b | Aireplay-ng: Fixed tcp_test stack overflow (Closes #14 on GitHub).
git-svn-id: http://svn.aircrack-ng.org/trunk@2417 28c6078b-6c39-48e3-add9-af49d547ecab | 1 | int tcp_test(const char* ip_str, const short port)
{
int sock, i;
struct sockaddr_in s_in;
int packetsize = 1024;
unsigned char packet[packetsize];
struct timeval tv, tv2, tv3;
int caplen = 0;
int times[REQUESTS];
int min, avg, max, len;
struct net_hdr nh;
tv3.tv_sec=0;
tv3.... | 4,358,153,153,698,486,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2014-8321 | Stack-based buffer overflow in the gps_tracker function in airodump-ng.c in Aircrack-ng before 1.2 RC 1 allows local users to execute arbitrary code or gain privileges via unspecified vectors. | https://nvd.nist.gov/vuln/detail/CVE-2014-8321 |
368,532 | aircrack-ng | 091b153f294b9b695b0b2831e65936438b550d7b | https://github.com/aircrack-ng/aircrack-ng | https://github.com/aircrack-ng/aircrack-ng/commit/091b153f294b9b695b0b2831e65936438b550d7b | Aireplay-ng: Fixed tcp_test stack overflow (Closes #14 on GitHub).
git-svn-id: http://svn.aircrack-ng.org/trunk@2417 28c6078b-6c39-48e3-add9-af49d547ecab | 0 | int tcp_test(const char* ip_str, const short port)
{
int sock, i;
struct sockaddr_in s_in;
int packetsize = 1024;
unsigned char packet[packetsize];
struct timeval tv, tv2, tv3;
int caplen = 0;
int times[REQUESTS];
int min, avg, max, len;
struct net_hdr nh;
tv3.tv_sec=0;
tv3.... | 118,686,941,596,852,830,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2014-8321 | Stack-based buffer overflow in the gps_tracker function in airodump-ng.c in Aircrack-ng before 1.2 RC 1 allows local users to execute arbitrary code or gain privileges via unspecified vectors. | https://nvd.nist.gov/vuln/detail/CVE-2014-8321 |
205,598 | linux | eff73de2b1600ad8230692f00bc0ab49b166512a | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eff73de2b1600ad8230692f00bc0ab49b166512a | media: cpia2_usb: first wake up, then free in disconnect
Kasan reported a use after free in cpia2_usb_disconnect()
It first freed everything and then woke up those waiting.
The reverse order is correct.
Fixes: 6c493f8b28c67 ("[media] cpia2: major overhaul to get it in a working state again")
Signed-off-by: Oliver Ne... | 1 | static void cpia2_usb_disconnect(struct usb_interface *intf)
{
struct camera_data *cam = usb_get_intfdata(intf);
usb_set_intfdata(intf, NULL);
DBG("Stopping stream\n");
cpia2_usb_stream_stop(cam);
mutex_lock(&cam->v4l2_lock);
DBG("Unregistering camera\n");
cpia2_unregister_camera(cam);
v4l2_device_disconnect(... | 281,012,788,068,544,380,000,000,000,000,000,000,000 | cpia2_usb.c | 175,776,458,711,920,950,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2019-15215 | An issue was discovered in the Linux kernel before 5.2.6. There is a use-after-free caused by a malicious USB device in the drivers/media/usb/cpia2/cpia2_usb.c driver. | https://nvd.nist.gov/vuln/detail/CVE-2019-15215 |
368,635 | linux | eff73de2b1600ad8230692f00bc0ab49b166512a | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eff73de2b1600ad8230692f00bc0ab49b166512a | media: cpia2_usb: first wake up, then free in disconnect
Kasan reported a use after free in cpia2_usb_disconnect()
It first freed everything and then woke up those waiting.
The reverse order is correct.
Fixes: 6c493f8b28c67 ("[media] cpia2: major overhaul to get it in a working state again")
Signed-off-by: Oliver Ne... | 0 | static void cpia2_usb_disconnect(struct usb_interface *intf)
{
struct camera_data *cam = usb_get_intfdata(intf);
usb_set_intfdata(intf, NULL);
DBG("Stopping stream\n");
cpia2_usb_stream_stop(cam);
mutex_lock(&cam->v4l2_lock);
DBG("Unregistering camera\n");
cpia2_unregister_camera(cam);
v4l2_device_disconnect(... | 102,278,847,064,300,450,000,000,000,000,000,000,000 | cpia2_usb.c | 169,886,625,542,153,660,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2019-15215 | An issue was discovered in the Linux kernel before 5.2.6. There is a use-after-free caused by a malicious USB device in the drivers/media/usb/cpia2/cpia2_usb.c driver. | https://nvd.nist.gov/vuln/detail/CVE-2019-15215 |
205,604 | libxml2 | c97750d11bb8b6f3303e7131fe526a61ac65bcfd | https://github.com/GNOME/libxml2 | https://git.gnome.org/browse/libxml2/commit/?h=CVE-2016-4483&id=c97750d11bb8b6f3303e7131fe526a61ac65bcfd | Avoid an out of bound access when serializing malformed strings
For https://bugzilla.gnome.org/show_bug.cgi?id=766414
* xmlsave.c: xmlBufAttrSerializeTxtContent() if an attribute value
is not UTF-8 be more careful when serializing it as we may do an
out of bound access as a result. | 1 | xmlBufAttrSerializeTxtContent(xmlBufPtr buf, xmlDocPtr doc,
xmlAttrPtr attr, const xmlChar * string)
{
xmlChar *base, *cur;
if (string == NULL)
return;
base = cur = (xmlChar *) string;
while (*cur != 0) {
if (*cur == '\n') {
if (base != cur)
... | 138,667,295,950,559,270,000,000,000,000,000,000,000 | xmlsave.c | 184,687,595,939,346,930,000,000,000,000,000,000,000 | [
"CWE-502"
] | CVE-2016-4483 | The xmlBufAttrSerializeTxtContent function in xmlsave.c in libxml2 allows context-dependent attackers to cause a denial of service (out-of-bounds read and application crash) via a non-UTF-8 attribute value, related to serialization. NOTE: this vulnerability may be a duplicate of CVE-2016-3627. | https://nvd.nist.gov/vuln/detail/CVE-2016-4483 |
368,699 | libxml2 | c97750d11bb8b6f3303e7131fe526a61ac65bcfd | https://github.com/GNOME/libxml2 | https://git.gnome.org/browse/libxml2/commit/?h=CVE-2016-4483&id=c97750d11bb8b6f3303e7131fe526a61ac65bcfd | Avoid an out of bound access when serializing malformed strings
For https://bugzilla.gnome.org/show_bug.cgi?id=766414
* xmlsave.c: xmlBufAttrSerializeTxtContent() if an attribute value
is not UTF-8 be more careful when serializing it as we may do an
out of bound access as a result. | 0 | xmlBufAttrSerializeTxtContent(xmlBufPtr buf, xmlDocPtr doc,
xmlAttrPtr attr, const xmlChar * string)
{
xmlChar *base, *cur;
if (string == NULL)
return;
base = cur = (xmlChar *) string;
while (*cur != 0) {
if (*cur == '\n') {
if (base != cur)
... | 333,191,119,854,146,870,000,000,000,000,000,000,000 | xmlsave.c | 15,936,751,178,262,834,000,000,000,000,000,000,000 | [
"CWE-502"
] | CVE-2016-4483 | The xmlBufAttrSerializeTxtContent function in xmlsave.c in libxml2 allows context-dependent attackers to cause a denial of service (out-of-bounds read and application crash) via a non-UTF-8 attribute value, related to serialization. NOTE: this vulnerability may be a duplicate of CVE-2016-3627. | https://nvd.nist.gov/vuln/detail/CVE-2016-4483 |
205,605 | ipmitool | 9452be87181a6e83cfcc768b3ed8321763db50e4 | https://github.com/ipmitool/ipmitool | https://github.com/ipmitool/ipmitool/commit/9452be87181a6e83cfcc768b3ed8321763db50e4 | channel: Fix buffer overflow
Partial fix for CVE-2020-5208, see
https://github.com/ipmitool/ipmitool/security/advisories/GHSA-g659-9qxw-p7cp
The `ipmi_get_channel_cipher_suites` function does not properly check
the final response’s `data_len`, which can lead to stack buffer overflow
on the final copy. | 1 | ipmi_get_channel_cipher_suites(struct ipmi_intf *intf,
const char *payload_type,
uint8_t channel,
struct cipher_suite_info *suites,
size_t *count)
{
struct ipmi_rs *rsp;
struct ipmi_rq req;
ui... | 35,711,658,876,121,163,000,000,000,000,000,000,000 | ipmi_channel.c | 139,564,790,566,854,130,000,000,000,000,000,000,000 | [
"CWE-120"
] | CVE-2020-5208 | It's been found that multiple functions in ipmitool before 1.8.19 neglect proper checking of the data received from a remote LAN party, which may lead to buffer overflows and potentially to remote code execution on the ipmitool side. This is especially dangerous if ipmitool is run as a privileged user. This problem is ... | https://nvd.nist.gov/vuln/detail/CVE-2020-5208 |
368,739 | ipmitool | 9452be87181a6e83cfcc768b3ed8321763db50e4 | https://github.com/ipmitool/ipmitool | https://github.com/ipmitool/ipmitool/commit/9452be87181a6e83cfcc768b3ed8321763db50e4 | channel: Fix buffer overflow
Partial fix for CVE-2020-5208, see
https://github.com/ipmitool/ipmitool/security/advisories/GHSA-g659-9qxw-p7cp
The `ipmi_get_channel_cipher_suites` function does not properly check
the final response’s `data_len`, which can lead to stack buffer overflow
on the final copy. | 0 | ipmi_get_channel_cipher_suites(struct ipmi_intf *intf,
const char *payload_type,
uint8_t channel,
struct cipher_suite_info *suites,
size_t *count)
{
struct ipmi_rs *rsp;
struct ipmi_rq req;
ui... | 110,934,357,561,927,470,000,000,000,000,000,000,000 | ipmi_channel.c | 200,629,554,803,324,070,000,000,000,000,000,000,000 | [
"CWE-120"
] | CVE-2020-5208 | It's been found that multiple functions in ipmitool before 1.8.19 neglect proper checking of the data received from a remote LAN party, which may lead to buffer overflows and potentially to remote code execution on the ipmitool side. This is especially dangerous if ipmitool is run as a privileged user. This problem is ... | https://nvd.nist.gov/vuln/detail/CVE-2020-5208 |
205,606 | qemu | 8e53abbc20d08ae3ec30c2054e1161314ad9501d | https://github.com/bonzini/qemu | http://git.qemu.org/?p=qemu.git;a=commit;h=8e53abbc20d08ae3ec30c2054e1161314ad9501d | bochs: Check extent_size header field (CVE-2014-0142)
This fixes two possible division by zero crashes: In bochs_open() and in
seek_to_sector().
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Max Reitz <mreitz@redhat.com>
Signed-off-by: Stefan Hajnoczi <st... | 1 | static int bochs_open(BlockDriverState *bs, QDict *options, int flags,
Error **errp)
{
BDRVBochsState *s = bs->opaque;
uint32_t i;
struct bochs_header bochs;
int ret;
bs->read_only = 1; // no write support yet
ret = bdrv_pread(bs->file, 0, &bochs, sizeof(bochs));
if (... | 333,939,999,322,483,100,000,000,000,000,000,000,000 | bochs.c | 323,328,224,716,878,980,000,000,000,000,000,000,000 | [
"CWE-369"
] | CVE-2014-0142 | QEMU, possibly before 2.0.0, allows local users to cause a denial of service (divide-by-zero error and crash) via a zero value in the (1) tracks field to the seek_to_sector function in block/parallels.c or (2) extent_size field in the bochs function in block/bochs.c. | https://nvd.nist.gov/vuln/detail/CVE-2014-0142 |
368,741 | qemu | 8e53abbc20d08ae3ec30c2054e1161314ad9501d | https://github.com/bonzini/qemu | http://git.qemu.org/?p=qemu.git;a=commit;h=8e53abbc20d08ae3ec30c2054e1161314ad9501d | bochs: Check extent_size header field (CVE-2014-0142)
This fixes two possible division by zero crashes: In bochs_open() and in
seek_to_sector().
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Max Reitz <mreitz@redhat.com>
Signed-off-by: Stefan Hajnoczi <st... | 0 | static int bochs_open(BlockDriverState *bs, QDict *options, int flags,
Error **errp)
{
BDRVBochsState *s = bs->opaque;
uint32_t i;
struct bochs_header bochs;
int ret;
bs->read_only = 1; // no write support yet
ret = bdrv_pread(bs->file, 0, &bochs, sizeof(bochs));
if (... | 88,607,858,515,138,600,000,000,000,000,000,000,000 | bochs.c | 218,733,395,737,016,500,000,000,000,000,000,000,000 | [
"CWE-369"
] | CVE-2014-0142 | QEMU, possibly before 2.0.0, allows local users to cause a denial of service (divide-by-zero error and crash) via a zero value in the (1) tracks field to the seek_to_sector function in block/parallels.c or (2) extent_size field in the bochs function in block/bochs.c. | https://nvd.nist.gov/vuln/detail/CVE-2014-0142 |
205,643 | php-src | ede59c8feb4b80e1b94e4abdaa0711051e2912ab | https://github.com/php/php-src | https://github.com/php/php-src/commit/ede59c8feb4b80e1b94e4abdaa0711051e2912ab | Fixed bug #68735 fileinfo out-of-bounds memory access | 1 | */
private int
mconvert(struct magic_set *ms, struct magic *m, int flip)
{
union VALUETYPE *p = &ms->ms_value;
switch (cvt_flip(m->type, flip)) {
case FILE_BYTE:
cvt_8(p, m);
return 1;
case FILE_SHORT:
cvt_16(p, m);
return 1;
case FILE_LONG:
case FILE_DATE:
case FILE_LDATE:
cvt_32(p, m);
return 1;
... | 325,191,839,000,770,300,000,000,000,000,000,000,000 | softmagic.c | 199,148,446,244,725,740,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-9652 | The mconvert function in softmagic.c in file before 5.21, as used in the Fileinfo component in PHP before 5.4.37, 5.5.x before 5.5.21, and 5.6.x before 5.6.5, does not properly handle a certain string-length field during a copy of a truncated version of a Pascal string, which might allow remote attackers to cause a den... | https://nvd.nist.gov/vuln/detail/CVE-2014-9652 |
369,629 | php-src | ede59c8feb4b80e1b94e4abdaa0711051e2912ab | https://github.com/php/php-src | https://github.com/php/php-src/commit/ede59c8feb4b80e1b94e4abdaa0711051e2912ab | Fixed bug #68735 fileinfo out-of-bounds memory access | 0 | */
private int
mconvert(struct magic_set *ms, struct magic *m, int flip)
{
union VALUETYPE *p = &ms->ms_value;
switch (cvt_flip(m->type, flip)) {
case FILE_BYTE:
cvt_8(p, m);
return 1;
case FILE_SHORT:
cvt_16(p, m);
return 1;
case FILE_LONG:
case FILE_DATE:
case FILE_LDATE:
cvt_32(p, m);
return 1;
... | 340,206,963,824,480,380,000,000,000,000,000,000,000 | softmagic.c | 259,075,460,094,977,160,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-9652 | The mconvert function in softmagic.c in file before 5.21, as used in the Fileinfo component in PHP before 5.4.37, 5.5.x before 5.5.21, and 5.6.x before 5.6.5, does not properly handle a certain string-length field during a copy of a truncated version of a Pascal string, which might allow remote attackers to cause a den... | https://nvd.nist.gov/vuln/detail/CVE-2014-9652 |
205,668 | libspiro | 35233450c922787dad42321e359e5229ff470a1e | https://github.com/fontforge/libspiro | https://github.com/fontforge/libspiro/commit/35233450c922787dad42321e359e5229ff470a1e | CVE-2019-19847, Stack-based buffer overflow in the spiro_to_bpath0()
Frederic Cambus (@fcambus) discovered a bug in call-test.c using:
./configure CFLAGS="-fsanitize=address"
make
./tests/call-test[14,15,16,17,18,19]
Fredrick Brennan (@ctrlcctrlv) provided bugfix. See issue #21 | 1 | int test_curve(int c) {
spiro_cp spiro[16];
int nextknot[17];
double d[5];
spiro_seg *segs = NULL;
bezctx *bc;
rs_check_vals *rsp;
int i,j,done;
/* Load sample data so that we can see if library is callable */
load_test_curve(spiro,nextknot,c);
d[0] = 1.; d[1] = d[1] = 0.;
#if ... | 155,357,845,017,441,480,000,000,000,000,000,000,000 | call-test.c | 216,332,299,233,271,920,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19847 | Libspiro through 20190731 has a stack-based buffer overflow in the spiro_to_bpath0() function in spiro.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-19847 |
369,998 | libspiro | 35233450c922787dad42321e359e5229ff470a1e | https://github.com/fontforge/libspiro | https://github.com/fontforge/libspiro/commit/35233450c922787dad42321e359e5229ff470a1e | CVE-2019-19847, Stack-based buffer overflow in the spiro_to_bpath0()
Frederic Cambus (@fcambus) discovered a bug in call-test.c using:
./configure CFLAGS="-fsanitize=address"
make
./tests/call-test[14,15,16,17,18,19]
Fredrick Brennan (@ctrlcctrlv) provided bugfix. See issue #21 | 0 | int test_curve(int c) {
spiro_cp spiro[16];
int nextknot[17];
double d[6];
spiro_seg *segs = NULL;
bezctx *bc;
rs_check_vals *rsp;
int i,j,done;
/* Load sample data so that we can see if library is callable */
load_test_curve(spiro,nextknot,c);
d[0] = 1.; d[1] = d[2] = 0.;
#if ... | 215,894,115,355,795,120,000,000,000,000,000,000,000 | call-test.c | 302,033,070,773,640,650,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19847 | Libspiro through 20190731 has a stack-based buffer overflow in the spiro_to_bpath0() function in spiro.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-19847 |
205,670 | gdm | 4e6e5335d29c039bed820c43bfd1c19cb62539ff | http://git.gnome.org/browse/gdm | https://gitlab.gnome.org/GNOME/gdm/-/commit/4e6e5335d29c039bed820c43bfd1c19cb62539ff | display: Use autoptr to handle errors in look for existing users
It will make things just cleaner | 1 | look_for_existing_users_sync (GdmDisplay *self)
{
GdmDisplayPrivate *priv;
GError *error = NULL;
GVariant *call_result;
GVariant *user_list;
priv = gdm_display_get_instance_private (self);
priv->accountsservice_proxy = g_dbus_proxy_new_sync (priv->connection,
... | 14,607,101,596,807,789,000,000,000,000,000,000,000 | gdm-display.c | 889,018,594,180,917,400,000,000,000,000,000,000 | [
"CWE-754"
] | CVE-2020-16125 | gdm3 versions before 3.36.2 or 3.38.2 would start gnome-initial-setup if gdm3 can't contact the accountservice service via dbus in a timely manner; on Ubuntu (and potentially derivatives) this could be be chained with an additional issue that could allow a local user to create a new privileged account. | https://nvd.nist.gov/vuln/detail/CVE-2020-16125 |
370,124 | gdm | 4e6e5335d29c039bed820c43bfd1c19cb62539ff | http://git.gnome.org/browse/gdm | https://gitlab.gnome.org/GNOME/gdm/-/commit/4e6e5335d29c039bed820c43bfd1c19cb62539ff | display: Use autoptr to handle errors in look for existing users
It will make things just cleaner | 0 | look_for_existing_users_sync (GdmDisplay *self)
{
GdmDisplayPrivate *priv;
g_autoptr(GError) error = NULL;
g_autoptr(GVariant) call_result = NULL;
g_autoptr(GVariant) user_list = NULL;
priv = gdm_display_get_instance_private (self);
priv->accountsservice_proxy = g_dbus_p... | 94,728,912,362,686,840,000,000,000,000,000,000,000 | gdm-display.c | 300,710,704,620,036,930,000,000,000,000,000,000,000 | [
"CWE-754"
] | CVE-2020-16125 | gdm3 versions before 3.36.2 or 3.38.2 would start gnome-initial-setup if gdm3 can't contact the accountservice service via dbus in a timely manner; on Ubuntu (and potentially derivatives) this could be be chained with an additional issue that could allow a local user to create a new privileged account. | https://nvd.nist.gov/vuln/detail/CVE-2020-16125 |
205,672 | php-src | 9649ca1630433473a307d015ba1a79a4a7a779f5 | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commitdiff;h=9649ca1630433473a307d015ba1a79a4a7a779f5 | Fixed bug #71331 - Uninitialized pointer in phar_make_dirstream() | 1 | static php_stream *phar_make_dirstream(char *dir, HashTable *manifest TSRMLS_DC) /* {{{ */
{
HashTable *data;
int dirlen = strlen(dir);
phar_zstr key;
char *entry, *found, *save, *str_key;
uint keylen;
ulong unused;
ALLOC_HASHTABLE(data);
zend_hash_init(data, 64, zend_get_hash_value, NULL, 0);
if ((*dir == '... | 282,317,724,622,478,730,000,000,000,000,000,000,000 | dirstream.c | 170,203,414,882,543,500,000,000,000,000,000,000,000 | [
"CWE-824"
] | CVE-2016-4343 | The phar_make_dirstream function in ext/phar/dirstream.c in PHP before 5.6.18 and 7.x before 7.0.3 mishandles zero-size ././@LongLink files, which allows remote attackers to cause a denial of service (uninitialized pointer dereference) or possibly have unspecified other impact via a crafted TAR archive. | https://nvd.nist.gov/vuln/detail/CVE-2016-4343 |
370,210 | php-src | 9649ca1630433473a307d015ba1a79a4a7a779f5 | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commitdiff;h=9649ca1630433473a307d015ba1a79a4a7a779f5 | Fixed bug #71331 - Uninitialized pointer in phar_make_dirstream() | 0 | static php_stream *phar_make_dirstream(char *dir, HashTable *manifest TSRMLS_DC) /* {{{ */
{
HashTable *data;
int dirlen = strlen(dir);
phar_zstr key;
char *entry, *found, *save, *str_key;
uint keylen;
ulong unused;
ALLOC_HASHTABLE(data);
zend_hash_init(data, 64, zend_get_hash_value, NULL, 0);
if ((*dir == '... | 318,888,471,110,657,440,000,000,000,000,000,000,000 | dirstream.c | 67,562,469,529,076,230,000,000,000,000,000,000,000 | [
"CWE-824"
] | CVE-2016-4343 | The phar_make_dirstream function in ext/phar/dirstream.c in PHP before 5.6.18 and 7.x before 7.0.3 mishandles zero-size ././@LongLink files, which allows remote attackers to cause a denial of service (uninitialized pointer dereference) or possibly have unspecified other impact via a crafted TAR archive. | https://nvd.nist.gov/vuln/detail/CVE-2016-4343 |
205,689 | tip | dfb4357da6ddbdf57d583ba64361c9d792b0e0b1 | http://git.kernel.org/cgit/linux/kernel/git/tip/tip | http://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?id=dfb4357da6ddbdf57d583ba64361c9d792b0e0b1 | time: Remove CONFIG_TIMER_STATS
Currently CONFIG_TIMER_STATS exposes process information across namespaces:
kernel/time/timer_list.c print_timer():
SEQ_printf(m, ", %s/%d", tmp, timer->start_pid);
/proc/timer_list:
#11: <0000000000000000>, hrtimer_wakeup, S:01, do_nanosleep, cron/2570
Given that the trac... | 1 | print_timer(struct seq_file *m, struct hrtimer *taddr, struct hrtimer *timer,
int idx, u64 now)
{
#ifdef CONFIG_TIMER_STATS
char tmp[TASK_COMM_LEN + 1];
#endif
SEQ_printf(m, " #%d: ", idx);
print_name_offset(m, taddr);
SEQ_printf(m, ", ");
print_name_offset(m, timer->function);
SEQ_printf(m, ", S:%02x", time... | 977,240,536,533,433,300,000,000,000,000,000,000 | None | null | [
"CWE-200"
] | CVE-2017-5967 | The time subsystem in the Linux kernel through 4.9.9, when CONFIG_TIMER_STATS is enabled, allows local users to discover real PID values (as distinguished from PID values inside a PID namespace) by reading the /proc/timer_list file, related to the print_timer function in kernel/time/timer_list.c and the __timer_stats_t... | https://nvd.nist.gov/vuln/detail/CVE-2017-5967 |
370,618 | tip | dfb4357da6ddbdf57d583ba64361c9d792b0e0b1 | http://git.kernel.org/cgit/linux/kernel/git/tip/tip | http://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?id=dfb4357da6ddbdf57d583ba64361c9d792b0e0b1 | time: Remove CONFIG_TIMER_STATS
Currently CONFIG_TIMER_STATS exposes process information across namespaces:
kernel/time/timer_list.c print_timer():
SEQ_printf(m, ", %s/%d", tmp, timer->start_pid);
/proc/timer_list:
#11: <0000000000000000>, hrtimer_wakeup, S:01, do_nanosleep, cron/2570
Given that the trac... | 0 | print_timer(struct seq_file *m, struct hrtimer *taddr, struct hrtimer *timer,
int idx, u64 now)
{
SEQ_printf(m, " #%d: ", idx);
print_name_offset(m, taddr);
SEQ_printf(m, ", ");
print_name_offset(m, timer->function);
SEQ_printf(m, ", S:%02x", timer->state);
SEQ_printf(m, "\n");
SEQ_printf(m, " # expires at ... | 181,813,224,093,462,520,000,000,000,000,000,000,000 | None | null | [
"CWE-200"
] | CVE-2017-5967 | The time subsystem in the Linux kernel through 4.9.9, when CONFIG_TIMER_STATS is enabled, allows local users to discover real PID values (as distinguished from PID values inside a PID namespace) by reading the /proc/timer_list file, related to the print_timer function in kernel/time/timer_list.c and the __timer_stats_t... | https://nvd.nist.gov/vuln/detail/CVE-2017-5967 |
205,711 | linux | 7b0d0b40cd78cadb525df760ee4cac151533c2b5 | https://github.com/torvalds/linux | http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=7b0d0b40cd78cadb525df760ee4cac151533c2b5 | selinux: Permit bounded transitions under NO_NEW_PRIVS or NOSUID.
If the callee SID is bounded by the caller SID, then allowing
the transition to occur poses no risk of privilege escalation and we can
therefore safely allow the transition to occur. Add this exemption
for both the case where a transition was explicitl... | 1 | static int selinux_bprm_set_creds(struct linux_binprm *bprm)
{
const struct task_security_struct *old_tsec;
struct task_security_struct *new_tsec;
struct inode_security_struct *isec;
struct common_audit_data ad;
struct inode *inode = file_inode(bprm->file);
int rc;
rc = cap_bprm_set_creds(bprm);
if (rc)
retu... | 299,955,029,395,722,040,000,000,000,000,000,000,000 | hooks.c | 111,951,058,843,613,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3215 | seunshare in policycoreutils 2.2.5 is owned by root with 4755 permissions, and executes programs in a way that changes the relationship between the setuid system call and the getresuid saved set-user-ID value, which makes it easier for local users to gain privileges by leveraging a program that mistakenly expected that... | https://nvd.nist.gov/vuln/detail/CVE-2014-3215 |
370,680 | linux | 7b0d0b40cd78cadb525df760ee4cac151533c2b5 | https://github.com/torvalds/linux | http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=7b0d0b40cd78cadb525df760ee4cac151533c2b5 | selinux: Permit bounded transitions under NO_NEW_PRIVS or NOSUID.
If the callee SID is bounded by the caller SID, then allowing
the transition to occur poses no risk of privilege escalation and we can
therefore safely allow the transition to occur. Add this exemption
for both the case where a transition was explicitl... | 0 | static int selinux_bprm_set_creds(struct linux_binprm *bprm)
{
const struct task_security_struct *old_tsec;
struct task_security_struct *new_tsec;
struct inode_security_struct *isec;
struct common_audit_data ad;
struct inode *inode = file_inode(bprm->file);
int rc;
rc = cap_bprm_set_creds(bprm);
if (rc)
retu... | 7,866,086,313,761,822,000,000,000,000,000,000,000 | hooks.c | 85,702,854,252,003,090,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3215 | seunshare in policycoreutils 2.2.5 is owned by root with 4755 permissions, and executes programs in a way that changes the relationship between the setuid system call and the getresuid saved set-user-ID value, which makes it easier for local users to gain privileges by leveraging a program that mistakenly expected that... | https://nvd.nist.gov/vuln/detail/CVE-2014-3215 |
205,714 | exiv2 | c73d1e27198a389ce7caf52ac30f8e2120acdafd | https://github.com/Exiv2/exiv2 | https://github.com/Exiv2/exiv2/commit/c73d1e27198a389ce7caf52ac30f8e2120acdafd | Avoid negative integer overflow when `filesize < io_->tell()`.
This fixes #791. | 1 | void WebPImage::decodeChunks(uint64_t filesize)
{
DataBuf chunkId(5);
byte size_buff[WEBP_TAG_SIZE];
bool has_canvas_data = false;
#ifdef DEBUG
std::cout << "Reading metadata" << std::endl;
#endif
chunkId.pData_[4] = '\0' ;
while ( !io_->eof() && (ui... | 327,391,411,616,211,700,000,000,000,000,000,000,000 | webpimage.cpp | 135,911,644,179,918,430,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2019-13111 | A WebPImage::decodeChunks integer overflow in Exiv2 through 0.27.1 allows an attacker to cause a denial of service (large heap allocation followed by a very long running loop) via a crafted WEBP image file. | https://nvd.nist.gov/vuln/detail/CVE-2019-13111 |
370,709 | exiv2 | c73d1e27198a389ce7caf52ac30f8e2120acdafd | https://github.com/Exiv2/exiv2 | https://github.com/Exiv2/exiv2/commit/c73d1e27198a389ce7caf52ac30f8e2120acdafd | Avoid negative integer overflow when `filesize < io_->tell()`.
This fixes #791. | 0 | void WebPImage::decodeChunks(uint32_t filesize)
{
DataBuf chunkId(5);
byte size_buff[WEBP_TAG_SIZE];
bool has_canvas_data = false;
#ifdef DEBUG
std::cout << "Reading metadata" << std::endl;
#endif
chunkId.pData_[4] = '\0' ;
while ( !io_->eof() && (ui... | 325,344,023,026,128,800,000,000,000,000,000,000,000 | webpimage.cpp | 188,228,762,631,251,350,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2019-13111 | A WebPImage::decodeChunks integer overflow in Exiv2 through 0.27.1 allows an attacker to cause a denial of service (large heap allocation followed by a very long running loop) via a crafted WEBP image file. | https://nvd.nist.gov/vuln/detail/CVE-2019-13111 |
205,716 | ImageMagick6 | 9e7db22f8c374301db3f968757f0d08070fd4e54 | https://github.com/ImageMagick/ImageMagick6 | https://github.com/ImageMagick/ImageMagick6/commit/9e7db22f8c374301db3f968757f0d08070fd4e54 | https://github.com/ImageMagick/ImageMagick/issues/1562 | 1 | static MagickBooleanType WriteSGIImage(const ImageInfo *image_info,Image *image)
{
CompressionType
compression;
const char
*value;
MagickBooleanType
status;
MagickOffsetType
scene;
MagickSizeType
number_pixels;
MemoryInfo
*pixel_info;
SGIInfo
iris_info;
register const ... | 198,645,521,295,199,230,000,000,000,000,000,000,000 | sgi.c | 13,873,368,556,669,940,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19948 | In ImageMagick 7.0.8-43 Q16, there is a heap-based buffer overflow in the function WriteSGIImage of coders/sgi.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-19948 |
370,711 | ImageMagick6 | 9e7db22f8c374301db3f968757f0d08070fd4e54 | https://github.com/ImageMagick/ImageMagick6 | https://github.com/ImageMagick/ImageMagick6/commit/9e7db22f8c374301db3f968757f0d08070fd4e54 | https://github.com/ImageMagick/ImageMagick/issues/1562 | 0 | static MagickBooleanType WriteSGIImage(const ImageInfo *image_info,Image *image)
{
CompressionType
compression;
const char
*value;
MagickBooleanType
status;
MagickOffsetType
scene;
MagickSizeType
number_pixels;
MemoryInfo
*pixel_info;
SGIInfo
iris_info;
register const ... | 58,680,261,541,416,900,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2019-19948 | In ImageMagick 7.0.8-43 Q16, there is a heap-based buffer overflow in the function WriteSGIImage of coders/sgi.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-19948 |
205,717 | tip | 4e78921ba4dd0aca1cc89168f45039add4183f8e | http://git.kernel.org/cgit/linux/kernel/git/tip/tip | https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=4e78921ba4dd0aca1cc89168f45039add4183f8e | efi/x86/Add missing error handling to old_memmap 1:1 mapping code
The old_memmap flow in efi_call_phys_prolog() performs numerous memory
allocations, and either does not check for failure at all, or it does
but fails to propagate it back to the caller, which may end up calling
into the firmware with an incomplete 1:1 ... | 1 | static efi_status_t __init phys_efi_set_virtual_address_map(
unsigned long memory_map_size,
unsigned long descriptor_size,
u32 descriptor_version,
efi_memory_desc_t *virtual_map)
{
efi_status_t status;
unsigned long flags;
pgd_t *save_pgd;
save_pgd = efi_call_phys_prolog();
/* Disable interrupts around EFI c... | 228,364,983,707,793,160,000,000,000,000,000,000,000 | None | null | [
"CWE-388"
] | CVE-2019-12380 | **DISPUTED** An issue was discovered in the efi subsystem in the Linux kernel through 5.1.5. phys_efi_set_virtual_address_map in arch/x86/platform/efi/efi.c and efi_call_phys_prolog in arch/x86/platform/efi/efi_64.c mishandle memory allocation failures. NOTE: This id is disputed as not being an issue because “All the c... | https://nvd.nist.gov/vuln/detail/CVE-2019-12380 |
370,761 | tip | 4e78921ba4dd0aca1cc89168f45039add4183f8e | http://git.kernel.org/cgit/linux/kernel/git/tip/tip | https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=4e78921ba4dd0aca1cc89168f45039add4183f8e | efi/x86/Add missing error handling to old_memmap 1:1 mapping code
The old_memmap flow in efi_call_phys_prolog() performs numerous memory
allocations, and either does not check for failure at all, or it does
but fails to propagate it back to the caller, which may end up calling
into the firmware with an incomplete 1:1 ... | 0 | static efi_status_t __init phys_efi_set_virtual_address_map(
unsigned long memory_map_size,
unsigned long descriptor_size,
u32 descriptor_version,
efi_memory_desc_t *virtual_map)
{
efi_status_t status;
unsigned long flags;
pgd_t *save_pgd;
save_pgd = efi_call_phys_prolog();
if (!save_pgd)
return EFI_ABORTED... | 144,802,768,739,214,400,000,000,000,000,000,000,000 | None | null | [
"CWE-388"
] | CVE-2019-12380 | **DISPUTED** An issue was discovered in the efi subsystem in the Linux kernel through 5.1.5. phys_efi_set_virtual_address_map in arch/x86/platform/efi/efi.c and efi_call_phys_prolog in arch/x86/platform/efi/efi_64.c mishandle memory allocation failures. NOTE: This id is disputed as not being an issue because “All the c... | https://nvd.nist.gov/vuln/detail/CVE-2019-12380 |
205,718 | tip | 4e78921ba4dd0aca1cc89168f45039add4183f8e | http://git.kernel.org/cgit/linux/kernel/git/tip/tip | https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=4e78921ba4dd0aca1cc89168f45039add4183f8e | efi/x86/Add missing error handling to old_memmap 1:1 mapping code
The old_memmap flow in efi_call_phys_prolog() performs numerous memory
allocations, and either does not check for failure at all, or it does
but fails to propagate it back to the caller, which may end up calling
into the firmware with an incomplete 1:1 ... | 1 | pgd_t * __init efi_call_phys_prolog(void)
{
unsigned long vaddr, addr_pgd, addr_p4d, addr_pud;
pgd_t *save_pgd, *pgd_k, *pgd_efi;
p4d_t *p4d, *p4d_k, *p4d_efi;
pud_t *pud;
int pgd;
int n_pgds, i, j;
if (!efi_enabled(EFI_OLD_MEMMAP)) {
efi_switch_mm(&efi_mm);
return NULL;
}
early_code_mapping_set_exec(1)... | 200,771,155,311,142,300,000,000,000,000,000,000,000 | None | null | [
"CWE-388"
] | CVE-2019-12380 | **DISPUTED** An issue was discovered in the efi subsystem in the Linux kernel through 5.1.5. phys_efi_set_virtual_address_map in arch/x86/platform/efi/efi.c and efi_call_phys_prolog in arch/x86/platform/efi/efi_64.c mishandle memory allocation failures. NOTE: This id is disputed as not being an issue because “All the c... | https://nvd.nist.gov/vuln/detail/CVE-2019-12380 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.