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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
161,042 | linux | fbe0e839d1e22d88810f3ee3e2f1479be4c0aa4a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fbe0e839d1e22d88810f3ee3e2f1479be4c0aa4a | futex: Prevent overflow by strengthen input validation
UBSAN reports signed integer overflow in kernel/futex.c:
UBSAN: Undefined behaviour in kernel/futex.c:2041:18
signed integer overflow:
0 - -2147483648 cannot be represented in type 'int'
Add a sanity check to catch negative values of nr_wake and nr_requeue.
... | 0 | static int futex_requeue(u32 __user *uaddr1, unsigned int flags,
u32 __user *uaddr2, int nr_wake, int nr_requeue,
u32 *cmpval, int requeue_pi)
{
union futex_key key1 = FUTEX_KEY_INIT, key2 = FUTEX_KEY_INIT;
int drop_count = 0, task_count = 0, ret;
struct futex_pi_state *pi_state = NULL;
struct futex_hash_bu... | 172,839,210,836,346,600,000,000,000,000,000,000,000 | None | null | [
"CWE-190"
] | CVE-2018-6927 | The futex_requeue function in kernel/futex.c in the Linux kernel before 4.14.15 might allow attackers to cause a denial of service (integer overflow) or possibly have unspecified other impact by triggering a negative wake or requeue value. | https://nvd.nist.gov/vuln/detail/CVE-2018-6927 |
3,786 | WavPack | d5bf76b5a88d044a1be1d5656698e3ba737167e5 | https://github.com/dbry/WavPack | https://github.com/dbry/WavPack/commit/d5bf76b5a88d044a1be1d5656698e3ba737167e5 | issue #27, do not overwrite stack on corrupt RF64 file | 1 | int ParseRiffHeaderConfig (FILE *infile, char *infilename, char *fourcc, WavpackContext *wpc, WavpackConfig *config)
{
int is_rf64 = !strncmp (fourcc, "RF64", 4), got_ds64 = 0;
int64_t total_samples = 0, infilesize;
RiffChunkHeader riff_chunk_header;
ChunkHeader chunk_header;
WaveHeader WaveHeader;
... | 266,946,299,595,107,760,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2018-6767 | A stack-based buffer over-read in the ParseRiffHeaderConfig function of cli/riff.c file of WavPack 5.1.0 allows a remote attacker to cause a denial-of-service attack or possibly have unspecified other impact via a maliciously crafted RF64 file. | https://nvd.nist.gov/vuln/detail/CVE-2018-6767 |
161,043 | WavPack | d5bf76b5a88d044a1be1d5656698e3ba737167e5 | https://github.com/dbry/WavPack | https://github.com/dbry/WavPack/commit/d5bf76b5a88d044a1be1d5656698e3ba737167e5 | issue #27, do not overwrite stack on corrupt RF64 file | 0 | int ParseRiffHeaderConfig (FILE *infile, char *infilename, char *fourcc, WavpackContext *wpc, WavpackConfig *config)
{
int is_rf64 = !strncmp (fourcc, "RF64", 4), got_ds64 = 0;
int64_t total_samples = 0, infilesize;
RiffChunkHeader riff_chunk_header;
ChunkHeader chunk_header;
WaveHeader WaveHeader;
... | 80,629,958,392,025,220,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2018-6767 | A stack-based buffer over-read in the ParseRiffHeaderConfig function of cli/riff.c file of WavPack 5.1.0 allows a remote attacker to cause a denial-of-service attack or possibly have unspecified other impact via a maliciously crafted RF64 file. | https://nvd.nist.gov/vuln/detail/CVE-2018-6767 |
3,787 | uncurl | 448cd13e7b18c83855d706c564341ddd1e38e769 | https://github.com/chrisd1100/uncurl | https://github.com/chrisd1100/uncurl/commit/448cd13e7b18c83855d706c564341ddd1e38e769 | None | 1 | UNCURL_EXPORT int32_t uncurl_ws_accept(struct uncurl_conn *ucc, char **origins, int32_t n_origins)
{
int32_t e;
e = uncurl_read_header(ucc);
if (e != UNCURL_OK) return e;
uncurl_set_header_str(ucc, "Upgrade", "websocket");
uncurl_set_header_str(ucc, "Connection", "Upgrade");
char *origin = NULL;
e = uncurl_g... | 185,832,743,048,029,200,000,000,000,000,000,000,000 | None | null | [
"CWE-352"
] | CVE-2018-6651 | In the uncurl_ws_accept function in uncurl.c in uncurl before 0.07, as used in Parsec before 140-3, insufficient Origin header validation (accepting an arbitrary substring match) for WebSocket API requests allows remote attackers to bypass intended access restrictions. In Parsec, this means full control over the victim... | https://nvd.nist.gov/vuln/detail/CVE-2018-6651 |
161,044 | uncurl | 448cd13e7b18c83855d706c564341ddd1e38e769 | https://github.com/chrisd1100/uncurl | https://github.com/chrisd1100/uncurl/commit/448cd13e7b18c83855d706c564341ddd1e38e769 | None | 0 | UNCURL_EXPORT int32_t uncurl_ws_accept(struct uncurl_conn *ucc, char **origins, int32_t n_origins)
{
int32_t e;
e = uncurl_read_header(ucc);
if (e != UNCURL_OK) return e;
uncurl_set_header_str(ucc, "Upgrade", "websocket");
uncurl_set_header_str(ucc, "Connection", "Upgrade");
char *origin = NULL;
e = uncurl_g... | 263,789,975,002,183,800,000,000,000,000,000,000,000 | None | null | [
"CWE-352"
] | CVE-2018-6651 | In the uncurl_ws_accept function in uncurl.c in uncurl before 0.07, as used in Parsec before 140-3, insufficient Origin header validation (accepting an arbitrary substring match) for WebSocket API requests allows remote attackers to bypass intended access restrictions. In Parsec, this means full control over the victim... | https://nvd.nist.gov/vuln/detail/CVE-2018-6651 |
3,790 | w3m | 7fdc83b0364005a0b5ed869230dd81752ba022e8 | https://github.com/tats/w3m | https://github.com/tats/w3m/commit/7fdc83b0364005a0b5ed869230dd81752ba022e8 | Prevent invalid columnPos() call in formUpdateBuffer()
Bug-Debian: https://github.com/tats/w3m/issues/89 | 1 | formUpdateBuffer(Anchor *a, Buffer *buf, FormItemList *form)
{
Buffer save;
char *p;
int spos, epos, rows, c_rows, pos, col = 0;
Line *l;
copyBuffer(&save, buf);
gotoLine(buf, a->start.line);
switch (form->type) {
case FORM_TEXTAREA:
case FORM_INPUT_TEXT:
case FORM_INPUT_FILE:
... | 90,699,627,261,407,880,000,000,000,000,000,000,000 | form.c | 290,331,077,565,996,070,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2018-6197 | w3m through 0.5.3 is prone to a NULL pointer dereference flaw in formUpdateBuffer in form.c. | https://nvd.nist.gov/vuln/detail/CVE-2018-6197 |
161,047 | w3m | 7fdc83b0364005a0b5ed869230dd81752ba022e8 | https://github.com/tats/w3m | https://github.com/tats/w3m/commit/7fdc83b0364005a0b5ed869230dd81752ba022e8 | Prevent invalid columnPos() call in formUpdateBuffer()
Bug-Debian: https://github.com/tats/w3m/issues/89 | 0 | formUpdateBuffer(Anchor *a, Buffer *buf, FormItemList *form)
{
Buffer save;
char *p;
int spos, epos, rows, c_rows, pos, col = 0;
Line *l;
copyBuffer(&save, buf);
gotoLine(buf, a->start.line);
switch (form->type) {
case FORM_TEXTAREA:
case FORM_INPUT_TEXT:
case FORM_INPUT_FILE:
... | 147,055,894,434,931,500,000,000,000,000,000,000,000 | form.c | 280,081,430,134,045,950,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2018-6197 | w3m through 0.5.3 is prone to a NULL pointer dereference flaw in formUpdateBuffer in form.c. | https://nvd.nist.gov/vuln/detail/CVE-2018-6197 |
3,791 | w3m | 8354763b90490d4105695df52674d0fcef823e92 | https://github.com/tats/w3m | https://github.com/tats/w3m/commit/8354763b90490d4105695df52674d0fcef823e92 | Prevent negative indent value in feed_table_block_tag()
Bug-Debian: https://github.com/tats/w3m/issues/88 | 1 | feed_table_block_tag(struct table *tbl,
char *line, struct table_mode *mode, int indent, int cmd)
{
int offset;
if (mode->indent_level <= 0 && indent == -1)
return;
if (mode->indent_level >= CHAR_MAX && indent == 1)
return;
setwidth(tbl, mode);
feed_table_inline_tag(tbl, line, mode, -1);
... | 95,430,748,719,998,940,000,000,000,000,000,000,000 | table.c | 48,265,608,758,374,150,000,000,000,000,000,000,000 | [
"CWE-835"
] | CVE-2018-6196 | w3m through 0.5.3 is prone to an infinite recursion flaw in HTMLlineproc0 because the feed_table_block_tag function in table.c does not prevent a negative indent value. | https://nvd.nist.gov/vuln/detail/CVE-2018-6196 |
161,048 | w3m | 8354763b90490d4105695df52674d0fcef823e92 | https://github.com/tats/w3m | https://github.com/tats/w3m/commit/8354763b90490d4105695df52674d0fcef823e92 | Prevent negative indent value in feed_table_block_tag()
Bug-Debian: https://github.com/tats/w3m/issues/88 | 0 | feed_table_block_tag(struct table *tbl,
char *line, struct table_mode *mode, int indent, int cmd)
{
int offset;
if (mode->indent_level <= 0 && indent == -1)
return;
if (mode->indent_level >= CHAR_MAX && indent == 1)
return;
setwidth(tbl, mode);
feed_table_inline_tag(tbl, line, mode, -1);
... | 181,646,912,890,994,800,000,000,000,000,000,000,000 | table.c | 245,558,100,729,634,500,000,000,000,000,000,000,000 | [
"CWE-835"
] | CVE-2018-6196 | w3m through 0.5.3 is prone to an infinite recursion flaw in HTMLlineproc0 because the feed_table_block_tag function in table.c does not prevent a negative indent value. | https://nvd.nist.gov/vuln/detail/CVE-2018-6196 |
3,792 | linux | 073c516ff73557a8f7315066856c04b50383ac34 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/073c516ff73557a8f7315066856c04b50383ac34 | nsfs: mark dentry with DCACHE_RCUACCESS
Andrey reported a use-after-free in __ns_get_path():
spin_lock include/linux/spinlock.h:299 [inline]
lockref_get_not_dead+0x19/0x80 lib/lockref.c:179
__ns_get_path+0x197/0x860 fs/nsfs.c:66
open_related_ns+0xda/0x200 fs/nsfs.c:143
sock_ioctl+0x39d/0x440 net/socket.c:10... | 1 | static void *__ns_get_path(struct path *path, struct ns_common *ns)
{
struct vfsmount *mnt = nsfs_mnt;
struct qstr qname = { .name = "", };
struct dentry *dentry;
struct inode *inode;
unsigned long d;
rcu_read_lock();
d = atomic_long_read(&ns->stashed);
if (!d)
goto slow;
dentry = (struct dentry *)d;
if (!... | 283,164,269,815,372,800,000,000,000,000,000,000,000 | nsfs.c | 255,868,983,414,598,720,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2018-5873 | An issue was discovered in the __ns_get_path function in fs/nsfs.c in the Linux kernel before 4.11. Due to a race condition when accessing files, a Use After Free condition can occur. This also affects all Android releases from CAF using the Linux kernel (Android for MSM, Firefox OS for MSM, QRD Android) before securit... | https://nvd.nist.gov/vuln/detail/CVE-2018-5873 |
161,049 | linux | 073c516ff73557a8f7315066856c04b50383ac34 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/073c516ff73557a8f7315066856c04b50383ac34 | nsfs: mark dentry with DCACHE_RCUACCESS
Andrey reported a use-after-free in __ns_get_path():
spin_lock include/linux/spinlock.h:299 [inline]
lockref_get_not_dead+0x19/0x80 lib/lockref.c:179
__ns_get_path+0x197/0x860 fs/nsfs.c:66
open_related_ns+0xda/0x200 fs/nsfs.c:143
sock_ioctl+0x39d/0x440 net/socket.c:10... | 0 | static void *__ns_get_path(struct path *path, struct ns_common *ns)
{
struct vfsmount *mnt = nsfs_mnt;
struct qstr qname = { .name = "", };
struct dentry *dentry;
struct inode *inode;
unsigned long d;
rcu_read_lock();
d = atomic_long_read(&ns->stashed);
if (!d)
goto slow;
dentry = (struct dentry *)d;
if (!... | 241,101,837,584,245,400,000,000,000,000,000,000,000 | nsfs.c | 205,323,731,216,993,800,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2018-5873 | An issue was discovered in the __ns_get_path function in fs/nsfs.c in the Linux kernel before 4.11. Due to a race condition when accessing files, a Use After Free condition can occur. This also affects all Android releases from CAF using the Linux kernel (Android for MSM, Firefox OS for MSM, QRD Android) before securit... | https://nvd.nist.gov/vuln/detail/CVE-2018-5873 |
3,795 | linux | ae6650163c66a7eff1acd6eb8b0f752dcfa8eba5 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ae6650163c66a7eff1acd6eb8b0f752dcfa8eba5 | loop: fix concurrent lo_open/lo_release
范龙飞 reports that KASAN can report a use-after-free in __lock_acquire.
The reason is due to insufficient serialization in lo_release(), which
will continue to use the loop device even after it has decremented the
lo_refcnt to zero.
In the meantime, another process can come in, o... | 1 | static void lo_release(struct gendisk *disk, fmode_t mode)
{
struct loop_device *lo = disk->private_data;
int err;
if (atomic_dec_return(&lo->lo_refcnt))
return;
mutex_lock(&lo->lo_ctl_mutex);
if (lo->lo_flags & LO_FLAGS_AUTOCLEAR) {
/*
* In autoclear mode, stop the loop thread
* and remove configu... | 92,709,335,376,815,670,000,000,000,000,000,000,000 | loop.c | 15,664,066,985,517,498,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2018-5344 | In the Linux kernel through 4.14.13, drivers/block/loop.c mishandles lo_release serialization, which allows attackers to cause a denial of service (__lock_acquire use-after-free) or possibly have unspecified other impact. | https://nvd.nist.gov/vuln/detail/CVE-2018-5344 |
161,052 | linux | ae6650163c66a7eff1acd6eb8b0f752dcfa8eba5 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ae6650163c66a7eff1acd6eb8b0f752dcfa8eba5 | loop: fix concurrent lo_open/lo_release
范龙飞 reports that KASAN can report a use-after-free in __lock_acquire.
The reason is due to insufficient serialization in lo_release(), which
will continue to use the loop device even after it has decremented the
lo_refcnt to zero.
In the meantime, another process can come in, o... | 0 | static void lo_release(struct gendisk *disk, fmode_t mode)
static void __lo_release(struct loop_device *lo)
{
int err;
if (atomic_dec_return(&lo->lo_refcnt))
return;
mutex_lock(&lo->lo_ctl_mutex);
if (lo->lo_flags & LO_FLAGS_AUTOCLEAR) {
/*
* In autoclear mode, stop the loop thread
* and remove conf... | 282,721,688,139,326,470,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2018-5344 | In the Linux kernel through 4.14.13, drivers/block/loop.c mishandles lo_release serialization, which allows attackers to cause a denial of service (__lock_acquire use-after-free) or possibly have unspecified other impact. | https://nvd.nist.gov/vuln/detail/CVE-2018-5344 |
3,796 | linux | c1fa0768a8713b135848f78fd43ffc208d8ded70 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c1fa0768a8713b135848f78fd43ffc208d8ded70 | powerpc/tm: Flush TM only if CPU has TM feature
Commit cd63f3c ("powerpc/tm: Fix saving of TM SPRs in core dump")
added code to access TM SPRs in flush_tmregs_to_thread(). However
flush_tmregs_to_thread() does not check if TM feature is available on
CPU before trying to access TM SPRs in order to copy live state to
th... | 1 | static void flush_tmregs_to_thread(struct task_struct *tsk)
{
/*
* If task is not current, it will have been flushed already to
* it's thread_struct during __switch_to().
*
* A reclaim flushes ALL the state or if not in TM save TM SPRs
* in the appropriate thread structures from live.
*/
if (tsk != cu... | 117,879,822,457,848,680,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2018-1091 | In the flush_tmregs_to_thread function in arch/powerpc/kernel/ptrace.c in the Linux kernel before 4.13.5, a guest kernel crash can be triggered from unprivileged userspace during a core dump on a POWER host due to a missing processor feature check and an erroneous use of transactional memory (TM) instructions in the co... | https://nvd.nist.gov/vuln/detail/CVE-2018-1091 |
161,053 | linux | c1fa0768a8713b135848f78fd43ffc208d8ded70 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c1fa0768a8713b135848f78fd43ffc208d8ded70 | powerpc/tm: Flush TM only if CPU has TM feature
Commit cd63f3c ("powerpc/tm: Fix saving of TM SPRs in core dump")
added code to access TM SPRs in flush_tmregs_to_thread(). However
flush_tmregs_to_thread() does not check if TM feature is available on
CPU before trying to access TM SPRs in order to copy live state to
th... | 0 | static void flush_tmregs_to_thread(struct task_struct *tsk)
{
/*
* If task is not current, it will have been flushed already to
* it's thread_struct during __switch_to().
*
* A reclaim flushes ALL the state or if not in TM save TM SPRs
* in the appropriate thread structures from live.
*/
if ((!cpu_has... | 93,527,856,526,487,000,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2018-1091 | In the flush_tmregs_to_thread function in arch/powerpc/kernel/ptrace.c in the Linux kernel before 4.13.5, a guest kernel crash can be triggered from unprivileged userspace during a core dump on a POWER host due to a missing processor feature check and an erroneous use of transactional memory (TM) instructions in the co... | https://nvd.nist.gov/vuln/detail/CVE-2018-1091 |
3,802 | linux | 57ebd808a97d7c5b1e1afb937c2db22beba3c1f8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57ebd808a97d7c5b1e1afb937c2db22beba3c1f8 | netfilter: add back stackpointer size checks
The rationale for removing the check is only correct for rulesets
generated by ip(6)tables.
In iptables, a jump can only occur to a user-defined chain, i.e.
because we size the stack based on number of user-defined chains we
cannot exceed stack size.
However, the underlyi... | 1 | ipt_do_table(struct sk_buff *skb,
const struct nf_hook_state *state,
struct xt_table *table)
{
unsigned int hook = state->hook;
static const char nulldevname[IFNAMSIZ] __attribute__((aligned(sizeof(long))));
const struct iphdr *ip;
/* Initializing verdict to NF_DROP keeps gcc happy. */
unsigned int ver... | 317,586,211,130,688,100,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2018-1065 | The netfilter subsystem in the Linux kernel through 4.15.7 mishandles the case of a rule blob that contains a jump but lacks a user-defined chain, which allows local users to cause a denial of service (NULL pointer dereference) by leveraging the CAP_NET_RAW or CAP_NET_ADMIN capability, related to arpt_do_table in net/i... | https://nvd.nist.gov/vuln/detail/CVE-2018-1065 |
161,059 | linux | 57ebd808a97d7c5b1e1afb937c2db22beba3c1f8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57ebd808a97d7c5b1e1afb937c2db22beba3c1f8 | netfilter: add back stackpointer size checks
The rationale for removing the check is only correct for rulesets
generated by ip(6)tables.
In iptables, a jump can only occur to a user-defined chain, i.e.
because we size the stack based on number of user-defined chains we
cannot exceed stack size.
However, the underlyi... | 0 | ipt_do_table(struct sk_buff *skb,
const struct nf_hook_state *state,
struct xt_table *table)
{
unsigned int hook = state->hook;
static const char nulldevname[IFNAMSIZ] __attribute__((aligned(sizeof(long))));
const struct iphdr *ip;
/* Initializing verdict to NF_DROP keeps gcc happy. */
unsigned int ver... | 67,780,899,779,179,170,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2018-1065 | The netfilter subsystem in the Linux kernel through 4.15.7 mishandles the case of a rule blob that contains a jump but lacks a user-defined chain, which allows local users to cause a denial of service (NULL pointer dereference) by leveraging the CAP_NET_RAW or CAP_NET_ADMIN capability, related to arpt_do_table in net/i... | https://nvd.nist.gov/vuln/detail/CVE-2018-1065 |
9,585 | linux | 57ebd808a97d7c5b1e1afb937c2db22beba3c1f8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57ebd808a97d7c5b1e1afb937c2db22beba3c1f8 | netfilter: add back stackpointer size checks
The rationale for removing the check is only correct for rulesets
generated by ip(6)tables.
In iptables, a jump can only occur to a user-defined chain, i.e.
because we size the stack based on number of user-defined chains we
cannot exceed stack size.
However, the underlyi... | 1 | unsigned int arpt_do_table(struct sk_buff *skb,
const struct nf_hook_state *state,
struct xt_table *table)
{
unsigned int hook = state->hook;
static const char nulldevname[IFNAMSIZ] __attribute__((aligned(sizeof(long))));
unsigned int verdict = NF_DROP;
const struct arphdr *arp;
struct arpt_entry *e, *... | 28,617,907,846,005,074,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2018-1065 | The netfilter subsystem in the Linux kernel through 4.15.7 mishandles the case of a rule blob that contains a jump but lacks a user-defined chain, which allows local users to cause a denial of service (NULL pointer dereference) by leveraging the CAP_NET_RAW or CAP_NET_ADMIN capability, related to arpt_do_table in net/i... | https://nvd.nist.gov/vuln/detail/CVE-2018-1065 |
184,658 | linux | 57ebd808a97d7c5b1e1afb937c2db22beba3c1f8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57ebd808a97d7c5b1e1afb937c2db22beba3c1f8 | netfilter: add back stackpointer size checks
The rationale for removing the check is only correct for rulesets
generated by ip(6)tables.
In iptables, a jump can only occur to a user-defined chain, i.e.
because we size the stack based on number of user-defined chains we
cannot exceed stack size.
However, the underlyi... | 0 | unsigned int arpt_do_table(struct sk_buff *skb,
const struct nf_hook_state *state,
struct xt_table *table)
{
unsigned int hook = state->hook;
static const char nulldevname[IFNAMSIZ] __attribute__((aligned(sizeof(long))));
unsigned int verdict = NF_DROP;
const struct arphdr *arp;
struct arpt_entry *e, *... | 164,540,819,830,131,100,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2018-1065 | The netfilter subsystem in the Linux kernel through 4.15.7 mishandles the case of a rule blob that contains a jump but lacks a user-defined chain, which allows local users to cause a denial of service (NULL pointer dereference) by leveraging the CAP_NET_RAW or CAP_NET_ADMIN capability, related to arpt_do_table in net/i... | https://nvd.nist.gov/vuln/detail/CVE-2018-1065 |
9,586 | linux | 57ebd808a97d7c5b1e1afb937c2db22beba3c1f8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57ebd808a97d7c5b1e1afb937c2db22beba3c1f8 | netfilter: add back stackpointer size checks
The rationale for removing the check is only correct for rulesets
generated by ip(6)tables.
In iptables, a jump can only occur to a user-defined chain, i.e.
because we size the stack based on number of user-defined chains we
cannot exceed stack size.
However, the underlyi... | 1 | ip6t_do_table(struct sk_buff *skb,
const struct nf_hook_state *state,
struct xt_table *table)
{
unsigned int hook = state->hook;
static const char nulldevname[IFNAMSIZ] __attribute__((aligned(sizeof(long))));
/* Initializing verdict to NF_DROP keeps gcc happy. */
unsigned int verdict = NF_DROP;
const... | 143,731,313,107,222,320,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2018-1065 | The netfilter subsystem in the Linux kernel through 4.15.7 mishandles the case of a rule blob that contains a jump but lacks a user-defined chain, which allows local users to cause a denial of service (NULL pointer dereference) by leveraging the CAP_NET_RAW or CAP_NET_ADMIN capability, related to arpt_do_table in net/i... | https://nvd.nist.gov/vuln/detail/CVE-2018-1065 |
184,659 | linux | 57ebd808a97d7c5b1e1afb937c2db22beba3c1f8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57ebd808a97d7c5b1e1afb937c2db22beba3c1f8 | netfilter: add back stackpointer size checks
The rationale for removing the check is only correct for rulesets
generated by ip(6)tables.
In iptables, a jump can only occur to a user-defined chain, i.e.
because we size the stack based on number of user-defined chains we
cannot exceed stack size.
However, the underlyi... | 0 | ip6t_do_table(struct sk_buff *skb,
const struct nf_hook_state *state,
struct xt_table *table)
{
unsigned int hook = state->hook;
static const char nulldevname[IFNAMSIZ] __attribute__((aligned(sizeof(long))));
/* Initializing verdict to NF_DROP keeps gcc happy. */
unsigned int verdict = NF_DROP;
const... | 63,388,556,442,717,060,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2018-1065 | The netfilter subsystem in the Linux kernel through 4.15.7 mishandles the case of a rule blob that contains a jump but lacks a user-defined chain, which allows local users to cause a denial of service (NULL pointer dereference) by leveraging the CAP_NET_RAW or CAP_NET_ADMIN capability, related to arpt_do_table in net/i... | https://nvd.nist.gov/vuln/detail/CVE-2018-1065 |
3,803 | curl | ba1dbd78e5f1ed67c1b8d37ac89d90e5e330b628 | https://github.com/curl/curl | https://github.com/curl/curl/commit/ba1dbd78e5f1ed67c1b8d37ac89d90e5e330b628 | smtp: use the upload buffer size for scratch buffer malloc
... not the read buffer size, as that can be set smaller and thus cause
a buffer overflow! CVE-2018-0500
Reported-by: Peter Wu
Bug: https://curl.haxx.se/docs/adv_2018-70a2.html | 1 | CURLcode Curl_smtp_escape_eob(struct connectdata *conn, const ssize_t nread)
{
/* When sending a SMTP payload we must detect CRLF. sequences making sure
they are sent as CRLF.. instead, as a . on the beginning of a line will
be deleted by the server when not part of an EOB terminator and a
genuine CRLF... | 170,694,906,334,543,880,000,000,000,000,000,000,000 | smtp.c | 285,403,495,559,952,680,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2018-0500 | Curl_smtp_escape_eob in lib/smtp.c in curl 7.54.1 to and including curl 7.60.0 has a heap-based buffer overflow that might be exploitable by an attacker who can control the data that curl transmits over SMTP with certain settings (i.e., use of a nonstandard --limit-rate argument or CURLOPT_BUFFERSIZE value). | https://nvd.nist.gov/vuln/detail/CVE-2018-0500 |
161,060 | curl | ba1dbd78e5f1ed67c1b8d37ac89d90e5e330b628 | https://github.com/curl/curl | https://github.com/curl/curl/commit/ba1dbd78e5f1ed67c1b8d37ac89d90e5e330b628 | smtp: use the upload buffer size for scratch buffer malloc
... not the read buffer size, as that can be set smaller and thus cause
a buffer overflow! CVE-2018-0500
Reported-by: Peter Wu
Bug: https://curl.haxx.se/docs/adv_2018-70a2.html | 0 | CURLcode Curl_smtp_escape_eob(struct connectdata *conn, const ssize_t nread)
{
/* When sending a SMTP payload we must detect CRLF. sequences making sure
they are sent as CRLF.. instead, as a . on the beginning of a line will
be deleted by the server when not part of an EOB terminator and a
genuine CRLF... | 36,162,887,606,169,493,000,000,000,000,000,000,000 | smtp.c | 273,591,916,854,707,000,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2018-0500 | Curl_smtp_escape_eob in lib/smtp.c in curl 7.54.1 to and including curl 7.60.0 has a heap-based buffer overflow that might be exploitable by an attacker who can control the data that curl transmits over SMTP with certain settings (i.e., use of a nonstandard --limit-rate argument or CURLOPT_BUFFERSIZE value). | https://nvd.nist.gov/vuln/detail/CVE-2018-0500 |
3,805 | miniupnp | 7aeb624b44f86d335841242ff427433190e7168a | https://github.com/miniupnp/miniupnp | https://github.com/miniupnp/miniupnp/commit/7aeb624b44f86d335841242ff427433190e7168a | properly initialize data structure for SOAP parsing in ParseNameValue()
topelt field was not properly initialized.
should fix #268 | 1 | ParseNameValue(const char * buffer, int bufsize,
struct NameValueParserData * data)
{
struct xmlparser parser;
data->l_head = NULL;
data->portListing = NULL;
data->portListingLength = 0;
/* init xmlparser object */
parser.xmlstart = buffer;
parser.xmlsize = bufsize;
parser.data = data;
par... | 18,049,727,750,159,877,000,000,000,000,000,000,000 | upnpreplyparse.c | 41,172,885,683,690,726,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-1000494 | Uninitialized stack variable vulnerability in NameValueParserEndElt (upnpreplyparse.c) in miniupnpd < 2.0 allows an attacker to cause Denial of Service (Segmentation fault and Memory Corruption) or possibly have unspecified other impact | https://nvd.nist.gov/vuln/detail/CVE-2017-1000494 |
161,062 | miniupnp | 7aeb624b44f86d335841242ff427433190e7168a | https://github.com/miniupnp/miniupnp | https://github.com/miniupnp/miniupnp/commit/7aeb624b44f86d335841242ff427433190e7168a | properly initialize data structure for SOAP parsing in ParseNameValue()
topelt field was not properly initialized.
should fix #268 | 0 | ParseNameValue(const char * buffer, int bufsize,
struct NameValueParserData * data)
{
struct xmlparser parser;
memset(data, 0, sizeof(struct NameValueParserData));
/* init xmlparser object */
parser.xmlstart = buffer;
parser.xmlsize = bufsize;
parser.data = data;
parser.starteltfunc = NameVa... | 134,272,332,068,689,500,000,000,000,000,000,000,000 | upnpreplyparse.c | 17,618,813,680,030,090,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-1000494 | Uninitialized stack variable vulnerability in NameValueParserEndElt (upnpreplyparse.c) in miniupnpd < 2.0 allows an attacker to cause Denial of Service (Segmentation fault and Memory Corruption) or possibly have unspecified other impact | https://nvd.nist.gov/vuln/detail/CVE-2017-1000494 |
3,806 | wildmidi | 814f31d8eceda8401eb812fc2e94ed143fdad0ab | https://github.com/Mindwerks/wildmidi | https://github.com/Mindwerks/wildmidi/commit/814f31d8eceda8401eb812fc2e94ed143fdad0ab | wildmidi_lib.c (WildMidi_Open, WildMidi_OpenBuffer): refuse to proceed if less then 18 bytes of input
Fixes bug #178. | 1 | WM_SYMBOL midi *WildMidi_Open(const char *midifile) {
uint8_t *mididata = NULL;
uint32_t midisize = 0;
uint8_t mus_hdr[] = { 'M', 'U', 'S', 0x1A };
uint8_t xmi_hdr[] = { 'F', 'O', 'R', 'M' };
midi * ret = NULL;
if (!WM_Initialized) {
_WM_GLOBAL_ERROR(__FUNCTION__, __LINE__, WM_ERR_NOT_I... | 49,238,147,717,637,630,000,000,000,000,000,000,000 | wildmidi_lib.c | 287,548,982,026,805,930,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-1000418 | The WildMidi_Open function in WildMIDI since commit d8a466829c67cacbb1700beded25c448d99514e5 allows remote attackers to cause a denial of service (heap-based buffer overflow and application crash) or possibly have unspecified other impact via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2017-1000418 |
161,063 | wildmidi | 814f31d8eceda8401eb812fc2e94ed143fdad0ab | https://github.com/Mindwerks/wildmidi | https://github.com/Mindwerks/wildmidi/commit/814f31d8eceda8401eb812fc2e94ed143fdad0ab | wildmidi_lib.c (WildMidi_Open, WildMidi_OpenBuffer): refuse to proceed if less then 18 bytes of input
Fixes bug #178. | 0 | WM_SYMBOL midi *WildMidi_Open(const char *midifile) {
uint8_t *mididata = NULL;
uint32_t midisize = 0;
uint8_t mus_hdr[] = { 'M', 'U', 'S', 0x1A };
uint8_t xmi_hdr[] = { 'F', 'O', 'R', 'M' };
midi * ret = NULL;
if (!WM_Initialized) {
_WM_GLOBAL_ERROR(__FUNCTION__, __LINE__, WM_ERR_NOT_I... | 157,587,241,671,448,090,000,000,000,000,000,000,000 | wildmidi_lib.c | 3,831,009,829,527,502,300,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-1000418 | The WildMidi_Open function in WildMIDI since commit d8a466829c67cacbb1700beded25c448d99514e5 allows remote attackers to cause a denial of service (heap-based buffer overflow and application crash) or possibly have unspecified other impact via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2017-1000418 |
3,814 | linux | b86e33075ed1909d8002745b56ecf73b833db143 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b86e33075ed1909d8002745b56ecf73b833db143 | f2fs: fix a dead loop in f2fs_fiemap()
A dead loop can be triggered in f2fs_fiemap() using the test case
as below:
...
fd = open();
fallocate(fd, 0, 0, 4294967296);
ioctl(fd, FS_IOC_FIEMAP, fiemap_buf);
...
It's caused by an overflow in __get_data_block():
...
bh->b_size = map.m_len << inode->i_blkbits;
...
... | 1 | static int __get_data_block(struct inode *inode, sector_t iblock,
struct buffer_head *bh, int create, int flag,
pgoff_t *next_pgofs)
{
struct f2fs_map_blocks map;
int err;
map.m_lblk = iblock;
map.m_len = bh->b_size >> inode->i_blkbits;
map.m_next_pgofs = next_pgofs;
err = f2fs_map_blocks(inode, &map, cre... | 36,840,277,564,373,170,000,000,000,000,000,000,000 | data.c | 145,455,815,818,505,820,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2017-18257 | The __get_data_block function in fs/f2fs/data.c in the Linux kernel before 4.11 allows local users to cause a denial of service (integer overflow and loop) via crafted use of the open and fallocate system calls with an FS_IOC_FIEMAP ioctl. | https://nvd.nist.gov/vuln/detail/CVE-2017-18257 |
161,066 | linux | b86e33075ed1909d8002745b56ecf73b833db143 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b86e33075ed1909d8002745b56ecf73b833db143 | f2fs: fix a dead loop in f2fs_fiemap()
A dead loop can be triggered in f2fs_fiemap() using the test case
as below:
...
fd = open();
fallocate(fd, 0, 0, 4294967296);
ioctl(fd, FS_IOC_FIEMAP, fiemap_buf);
...
It's caused by an overflow in __get_data_block():
...
bh->b_size = map.m_len << inode->i_blkbits;
...
... | 0 | static int __get_data_block(struct inode *inode, sector_t iblock,
struct buffer_head *bh, int create, int flag,
pgoff_t *next_pgofs)
{
struct f2fs_map_blocks map;
int err;
map.m_lblk = iblock;
map.m_len = bh->b_size >> inode->i_blkbits;
map.m_next_pgofs = next_pgofs;
err = f2fs_map_blocks(inode, &map, cre... | 114,871,232,152,569,200,000,000,000,000,000,000,000 | data.c | 6,535,832,732,518,038,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2017-18257 | The __get_data_block function in fs/f2fs/data.c in the Linux kernel before 4.11 allows local users to cause a denial of service (integer overflow and loop) via crafted use of the open and fallocate system calls with an FS_IOC_FIEMAP ioctl. | https://nvd.nist.gov/vuln/detail/CVE-2017-18257 |
3,815 | linux | 1572e45a924f254d9570093abde46430c3172e3d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1572e45a924f254d9570093abde46430c3172e3d | perf/core: Fix the perf_cpu_time_max_percent check
Use "proc_dointvec_minmax" instead of "proc_dointvec" to check the input
value from user-space.
If not, we can set a big value and some vars will overflow like
"sysctl_perf_event_sample_rate" which will cause a lot of unexpected
problems.
Signed-off-by: Tan Xiaojun ... | 1 | int perf_cpu_time_max_percent_handler(struct ctl_table *table, int write,
void __user *buffer, size_t *lenp,
loff_t *ppos)
{
int ret = proc_dointvec(table, write, buffer, lenp, ppos);
if (ret || !write)
return ret;
if (sysctl_perf_cpu_time_max_percent == 100 ||
sysctl_perf_cpu_time_max_percent... | 108,483,018,357,036,800,000,000,000,000,000,000,000 | core.c | 304,500,610,601,399,240,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2017-18255 | The perf_cpu_time_max_percent_handler function in kernel/events/core.c in the Linux kernel before 4.11 allows local users to cause a denial of service (integer overflow) or possibly have unspecified other impact via a large value, as demonstrated by an incorrect sample-rate calculation. | https://nvd.nist.gov/vuln/detail/CVE-2017-18255 |
161,067 | linux | 1572e45a924f254d9570093abde46430c3172e3d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1572e45a924f254d9570093abde46430c3172e3d | perf/core: Fix the perf_cpu_time_max_percent check
Use "proc_dointvec_minmax" instead of "proc_dointvec" to check the input
value from user-space.
If not, we can set a big value and some vars will overflow like
"sysctl_perf_event_sample_rate" which will cause a lot of unexpected
problems.
Signed-off-by: Tan Xiaojun ... | 0 | int perf_cpu_time_max_percent_handler(struct ctl_table *table, int write,
void __user *buffer, size_t *lenp,
loff_t *ppos)
{
int ret = proc_dointvec_minmax(table, write, buffer, lenp, ppos);
if (ret || !write)
return ret;
if (sysctl_perf_cpu_time_max_percent == 100 ||
sysctl_perf_cpu_time_max_... | 175,092,103,451,078,970,000,000,000,000,000,000,000 | core.c | 58,482,490,314,812,680,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2017-18255 | The perf_cpu_time_max_percent_handler function in kernel/events/core.c in the Linux kernel before 4.11 allows local users to cause a denial of service (integer overflow) or possibly have unspecified other impact via a large value, as demonstrated by an incorrect sample-rate calculation. | https://nvd.nist.gov/vuln/detail/CVE-2017-18255 |
3,816 | linux | 30a61ddf8117c26ac5b295e1233eaa9629a94ca3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/30a61ddf8117c26ac5b295e1233eaa9629a94ca3 | f2fs: fix race condition in between free nid allocator/initializer
In below concurrent case, allocated nid can be loaded into free nid cache
and be allocated again.
Thread A Thread B
- f2fs_create
- f2fs_new_inode
- alloc_nid
- __insert_nid_to_list(ALLOC_NID_LIST)
- f2fs_balance_fs_bg
- build_free... | 1 | static bool add_free_nid(struct f2fs_sb_info *sbi, nid_t nid, bool build)
{
struct f2fs_nm_info *nm_i = NM_I(sbi);
struct free_nid *i;
struct nat_entry *ne;
int err;
/* 0 nid should not be used */
if (unlikely(nid == 0))
return false;
if (build) {
/* do not add allocated nids */
ne = __lookup_na... | 84,542,765,132,488,550,000,000,000,000,000,000,000 | node.c | 42,220,681,768,883,035,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2017-18249 | The add_free_nid function in fs/f2fs/node.c in the Linux kernel before 4.12 does not properly track an allocated nid, which allows local users to cause a denial of service (race condition) or possibly have unspecified other impact via concurrent threads. | https://nvd.nist.gov/vuln/detail/CVE-2017-18249 |
161,068 | linux | 30a61ddf8117c26ac5b295e1233eaa9629a94ca3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/30a61ddf8117c26ac5b295e1233eaa9629a94ca3 | f2fs: fix race condition in between free nid allocator/initializer
In below concurrent case, allocated nid can be loaded into free nid cache
and be allocated again.
Thread A Thread B
- f2fs_create
- f2fs_new_inode
- alloc_nid
- __insert_nid_to_list(ALLOC_NID_LIST)
- f2fs_balance_fs_bg
- build_free... | 0 | static bool add_free_nid(struct f2fs_sb_info *sbi, nid_t nid, bool build)
{
struct f2fs_nm_info *nm_i = NM_I(sbi);
struct free_nid *i, *e;
struct nat_entry *ne;
int err = -EINVAL;
bool ret = false;
/* 0 nid should not be used */
if (unlikely(nid == 0))
return false;
i = f2fs_kmem_cache_alloc(free_... | 143,852,670,703,339,160,000,000,000,000,000,000,000 | node.c | 297,282,821,800,725,050,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2017-18249 | The add_free_nid function in fs/f2fs/node.c in the Linux kernel before 4.12 does not properly track an allocated nid, which allows local users to cause a denial of service (race condition) or possibly have unspecified other impact via concurrent threads. | https://nvd.nist.gov/vuln/detail/CVE-2017-18249 |
3,817 | cups | 49fa4983f25b64ec29d548ffa3b9782426007df3 | https://github.com/apple/cups | https://github.com/apple/cups/commit/49fa4983f25b64ec29d548ffa3b9782426007df3 | DBUS notifications could crash the scheduler (Issue #5143)
- scheduler/ipp.c: Make sure requesting-user-name string is valid UTF-8. | 1 | add_job(cupsd_client_t *con, /* I - Client connection */
cupsd_printer_t *printer, /* I - Destination printer */
mime_type_t *filetype) /* I - First print file type, if any */
{
http_status_t status; /* Policy status */
ipp_attribute_t *attr, /* Current attribute */
*auth_info; /* auth-info attribute ... | 143,641,121,189,248,620,000,000,000,000,000,000,000 | ipp.c | 103,444,657,439,025,130,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2017-18248 | The add_job function in scheduler/ipp.c in CUPS before 2.2.6, when D-Bus support is enabled, can be crashed by remote attackers by sending print jobs with an invalid username, related to a D-Bus notification. | https://nvd.nist.gov/vuln/detail/CVE-2017-18248 |
161,069 | cups | 49fa4983f25b64ec29d548ffa3b9782426007df3 | https://github.com/apple/cups | https://github.com/apple/cups/commit/49fa4983f25b64ec29d548ffa3b9782426007df3 | DBUS notifications could crash the scheduler (Issue #5143)
- scheduler/ipp.c: Make sure requesting-user-name string is valid UTF-8. | 0 | add_job(cupsd_client_t *con, /* I - Client connection */
cupsd_printer_t *printer, /* I - Destination printer */
mime_type_t *filetype) /* I - First print file type, if any */
{
http_status_t status; /* Policy status */
ipp_attribute_t *attr, /* Current attribute */
*auth_info; /* auth-info attribute ... | 36,981,301,760,995,975,000,000,000,000,000,000,000 | ipp.c | 336,753,608,928,609,100,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2017-18248 | The add_job function in scheduler/ipp.c in CUPS before 2.2.6, when D-Bus support is enabled, can be crashed by remote attackers by sending print jobs with an invalid username, related to a D-Bus notification. | https://nvd.nist.gov/vuln/detail/CVE-2017-18248 |
3,837 | linux | 70feee0e1ef331b22cc51f383d532a0d043fbdcc | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/70feee0e1ef331b22cc51f383d532a0d043fbdcc | mlock: fix mlock count can not decrease in race condition
Kefeng reported that when running the follow test, the mlock count in
meminfo will increase permanently:
[1] testcase
linux:~ # cat test_mlockal
grep Mlocked /proc/meminfo
for j in `seq 0 10`
do
for i in `seq 4 15`
do
./p_mlockall >> log &
done... | 1 | static void __munlock_pagevec(struct pagevec *pvec, struct zone *zone)
{
int i;
int nr = pagevec_count(pvec);
int delta_munlocked;
struct pagevec pvec_putback;
int pgrescued = 0;
pagevec_init(&pvec_putback, 0);
/* Phase 1: page isolation */
spin_lock_irq(zone_lru_lock(zone));
for (i = 0; i < nr; i++) {... | 115,707,399,857,902,040,000,000,000,000,000,000,000 | mlock.c | 124,452,116,569,757,200,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2017-18221 | The __munlock_pagevec function in mm/mlock.c in the Linux kernel before 4.11.4 allows local users to cause a denial of service (NR_MLOCK accounting corruption) via crafted use of mlockall and munlockall system calls. | https://nvd.nist.gov/vuln/detail/CVE-2017-18221 |
161,087 | linux | 70feee0e1ef331b22cc51f383d532a0d043fbdcc | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/70feee0e1ef331b22cc51f383d532a0d043fbdcc | mlock: fix mlock count can not decrease in race condition
Kefeng reported that when running the follow test, the mlock count in
meminfo will increase permanently:
[1] testcase
linux:~ # cat test_mlockal
grep Mlocked /proc/meminfo
for j in `seq 0 10`
do
for i in `seq 4 15`
do
./p_mlockall >> log &
done... | 0 | static void __munlock_pagevec(struct pagevec *pvec, struct zone *zone)
{
int i;
int nr = pagevec_count(pvec);
int delta_munlocked = -nr;
struct pagevec pvec_putback;
int pgrescued = 0;
pagevec_init(&pvec_putback, 0);
/* Phase 1: page isolation */
spin_lock_irq(zone_lru_lock(zone));
for (i = 0; i < nr; ... | 230,159,455,498,024,730,000,000,000,000,000,000,000 | mlock.c | 296,885,345,766,349,730,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2017-18221 | The __munlock_pagevec function in mm/mlock.c in the Linux kernel before 4.11.4 allows local users to cause a denial of service (NR_MLOCK accounting corruption) via crafted use of mlockall and munlockall system calls. | https://nvd.nist.gov/vuln/detail/CVE-2017-18221 |
3,838 | linux | 27463ad99f738ed93c7c8b3e2e5bc8c4853a2ff2 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/27463ad99f738ed93c7c8b3e2e5bc8c4853a2ff2 | net: hns: Fix a skb used after free bug
skb maybe freed in hns_nic_net_xmit_hw() and return NETDEV_TX_OK,
which cause hns_nic_net_xmit to use a freed skb.
BUG: KASAN: use-after-free in hns_nic_net_xmit_hw+0x62c/0x940...
[17659.112635] alloc_debug_processing+0x18c/0x1a0
[17659.117208] __slab_alloc+0x52c/0x... | 1 | static netdev_tx_t hns_nic_net_xmit(struct sk_buff *skb,
struct net_device *ndev)
{
struct hns_nic_priv *priv = netdev_priv(ndev);
int ret;
assert(skb->queue_mapping < ndev->ae_handle->q_num);
ret = hns_nic_net_xmit_hw(ndev, skb,
&tx_ring_data(priv, skb->queue_mapping));
if (ret == NETDEV_TX_OK... | 286,205,539,332,141,500,000,000,000,000,000,000,000 | hns_enet.c | 118,232,006,227,961,090,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2017-18218 | In drivers/net/ethernet/hisilicon/hns/hns_enet.c in the Linux kernel before 4.13, local users can cause a denial of service (use-after-free and BUG) or possibly have unspecified other impact by leveraging differences in skb handling between hns_nic_net_xmit_hw and hns_nic_net_xmit. | https://nvd.nist.gov/vuln/detail/CVE-2017-18218 |
161,088 | linux | 27463ad99f738ed93c7c8b3e2e5bc8c4853a2ff2 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/27463ad99f738ed93c7c8b3e2e5bc8c4853a2ff2 | net: hns: Fix a skb used after free bug
skb maybe freed in hns_nic_net_xmit_hw() and return NETDEV_TX_OK,
which cause hns_nic_net_xmit to use a freed skb.
BUG: KASAN: use-after-free in hns_nic_net_xmit_hw+0x62c/0x940...
[17659.112635] alloc_debug_processing+0x18c/0x1a0
[17659.117208] __slab_alloc+0x52c/0x... | 0 | static netdev_tx_t hns_nic_net_xmit(struct sk_buff *skb,
struct net_device *ndev)
{
struct hns_nic_priv *priv = netdev_priv(ndev);
assert(skb->queue_mapping < ndev->ae_handle->q_num);
return hns_nic_net_xmit_hw(ndev, skb,
&tx_ring_data(priv, skb->queue_mapping));
}
| 276,942,828,215,711,460,000,000,000,000,000,000,000 | hns_enet.c | 78,177,005,362,597,400,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2017-18218 | In drivers/net/ethernet/hisilicon/hns/hns_enet.c in the Linux kernel before 4.13, local users can cause a denial of service (use-after-free and BUG) or possibly have unspecified other impact by leveraging differences in skb handling between hns_nic_net_xmit_hw and hns_nic_net_xmit. | https://nvd.nist.gov/vuln/detail/CVE-2017-18218 |
3,839 | linux | 27463ad99f738ed93c7c8b3e2e5bc8c4853a2ff2 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/27463ad99f738ed93c7c8b3e2e5bc8c4853a2ff2 | net: hns: Fix a skb used after free bug
skb maybe freed in hns_nic_net_xmit_hw() and return NETDEV_TX_OK,
which cause hns_nic_net_xmit to use a freed skb.
BUG: KASAN: use-after-free in hns_nic_net_xmit_hw+0x62c/0x940...
[17659.112635] alloc_debug_processing+0x18c/0x1a0
[17659.117208] __slab_alloc+0x52c/0x... | 1 | int hns_nic_net_xmit_hw(struct net_device *ndev,
struct sk_buff *skb,
struct hns_nic_ring_data *ring_data)
{
struct hns_nic_priv *priv = netdev_priv(ndev);
struct hnae_ring *ring = ring_data->ring;
struct device *dev = ring_to_dev(ring);
struct netdev_queue *dev_queue;
struct skb_frag_struct *frag;
int b... | 111,953,708,316,717,710,000,000,000,000,000,000,000 | hns_enet.c | 118,232,006,227,961,090,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2017-18218 | In drivers/net/ethernet/hisilicon/hns/hns_enet.c in the Linux kernel before 4.13, local users can cause a denial of service (use-after-free and BUG) or possibly have unspecified other impact by leveraging differences in skb handling between hns_nic_net_xmit_hw and hns_nic_net_xmit. | https://nvd.nist.gov/vuln/detail/CVE-2017-18218 |
161,089 | linux | 27463ad99f738ed93c7c8b3e2e5bc8c4853a2ff2 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/27463ad99f738ed93c7c8b3e2e5bc8c4853a2ff2 | net: hns: Fix a skb used after free bug
skb maybe freed in hns_nic_net_xmit_hw() and return NETDEV_TX_OK,
which cause hns_nic_net_xmit to use a freed skb.
BUG: KASAN: use-after-free in hns_nic_net_xmit_hw+0x62c/0x940...
[17659.112635] alloc_debug_processing+0x18c/0x1a0
[17659.117208] __slab_alloc+0x52c/0x... | 0 | int hns_nic_net_xmit_hw(struct net_device *ndev,
netdev_tx_t hns_nic_net_xmit_hw(struct net_device *ndev,
struct sk_buff *skb,
struct hns_nic_ring_data *ring_data)
{
struct hns_nic_priv *priv = netdev_priv(ndev);
struct hnae_ring *ring = ring_data->ring;
struct device *dev = ring_to_dev(ring);
struct net... | 24,547,272,934,065,800,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2017-18218 | In drivers/net/ethernet/hisilicon/hns/hns_enet.c in the Linux kernel before 4.13, local users can cause a denial of service (use-after-free and BUG) or possibly have unspecified other impact by leveraging differences in skb handling between hns_nic_net_xmit_hw and hns_nic_net_xmit. | https://nvd.nist.gov/vuln/detail/CVE-2017-18218 |
3,843 | linux | 6ea8d958a2c95a1d514015d4e29ba21a8c0a1a91 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6ea8d958a2c95a1d514015d4e29ba21a8c0a1a91 | mm/madvise.c: fix madvise() infinite loop under special circumstances
MADVISE_WILLNEED has always been a noop for DAX (formerly XIP) mappings.
Unfortunately madvise_willneed() doesn't communicate this information
properly to the generic madvise syscall implementation. The calling
convention is quite subtle there. ma... | 1 | static long madvise_willneed(struct vm_area_struct *vma,
struct vm_area_struct **prev,
unsigned long start, unsigned long end)
{
struct file *file = vma->vm_file;
#ifdef CONFIG_SWAP
if (!file) {
*prev = vma;
force_swapin_readahead(vma, start, end);
return 0;
}
if (shmem_mapping(fil... | 171,648,586,462,786,750,000,000,000,000,000,000,000 | madvise.c | 200,513,704,618,787,880,000,000,000,000,000,000,000 | [
"CWE-835"
] | CVE-2017-18208 | The madvise_willneed function in mm/madvise.c in the Linux kernel before 4.14.4 allows local users to cause a denial of service (infinite loop) by triggering use of MADVISE_WILLNEED for a DAX mapping. | https://nvd.nist.gov/vuln/detail/CVE-2017-18208 |
161,093 | linux | 6ea8d958a2c95a1d514015d4e29ba21a8c0a1a91 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6ea8d958a2c95a1d514015d4e29ba21a8c0a1a91 | mm/madvise.c: fix madvise() infinite loop under special circumstances
MADVISE_WILLNEED has always been a noop for DAX (formerly XIP) mappings.
Unfortunately madvise_willneed() doesn't communicate this information
properly to the generic madvise syscall implementation. The calling
convention is quite subtle there. ma... | 0 | static long madvise_willneed(struct vm_area_struct *vma,
struct vm_area_struct **prev,
unsigned long start, unsigned long end)
{
struct file *file = vma->vm_file;
*prev = vma;
#ifdef CONFIG_SWAP
if (!file) {
force_swapin_readahead(vma, start, end);
return 0;
}
if (shmem_mapping(file... | 136,863,598,882,178,340,000,000,000,000,000,000,000 | madvise.c | 315,371,466,740,442,060,000,000,000,000,000,000,000 | [
"CWE-835"
] | CVE-2017-18208 | The madvise_willneed function in mm/madvise.c in the Linux kernel before 4.14.4 allows local users to cause a denial of service (infinite loop) by triggering use of MADVISE_WILLNEED for a DAX mapping. | https://nvd.nist.gov/vuln/detail/CVE-2017-18208 |
3,844 | linux | 28f5a8a7c033cbf3e32277f4cc9c6afd74f05300 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/28f5a8a7c033cbf3e32277f4cc9c6afd74f05300 | ocfs2: should wait dio before inode lock in ocfs2_setattr()
we should wait dio requests to finish before inode lock in
ocfs2_setattr(), otherwise the following deadlock will happen:
process 1 process 2 process 3
truncate file 'A' end_io of writing file 'A' receiving the ... | 1 | int ocfs2_setattr(struct dentry *dentry, struct iattr *attr)
{
int status = 0, size_change;
int inode_locked = 0;
struct inode *inode = d_inode(dentry);
struct super_block *sb = inode->i_sb;
struct ocfs2_super *osb = OCFS2_SB(sb);
struct buffer_head *bh = NULL;
handle_t *handle = NULL;
struct dquot *transfer_to... | 12,293,169,081,478,398,000,000,000,000,000,000,000 | None | null | [
"CWE-401"
] | CVE-2017-18204 | The ocfs2_setattr function in fs/ocfs2/file.c in the Linux kernel before 4.14.2 allows local users to cause a denial of service (deadlock) via DIO requests. | https://nvd.nist.gov/vuln/detail/CVE-2017-18204 |
161,094 | linux | 28f5a8a7c033cbf3e32277f4cc9c6afd74f05300 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/28f5a8a7c033cbf3e32277f4cc9c6afd74f05300 | ocfs2: should wait dio before inode lock in ocfs2_setattr()
we should wait dio requests to finish before inode lock in
ocfs2_setattr(), otherwise the following deadlock will happen:
process 1 process 2 process 3
truncate file 'A' end_io of writing file 'A' receiving the ... | 0 | int ocfs2_setattr(struct dentry *dentry, struct iattr *attr)
{
int status = 0, size_change;
int inode_locked = 0;
struct inode *inode = d_inode(dentry);
struct super_block *sb = inode->i_sb;
struct ocfs2_super *osb = OCFS2_SB(sb);
struct buffer_head *bh = NULL;
handle_t *handle = NULL;
struct dquot *transfer_to... | 303,343,984,416,342,600,000,000,000,000,000,000,000 | None | null | [
"CWE-401"
] | CVE-2017-18204 | The ocfs2_setattr function in fs/ocfs2/file.c in the Linux kernel before 4.14.2 allows local users to cause a denial of service (deadlock) via DIO requests. | https://nvd.nist.gov/vuln/detail/CVE-2017-18204 |
3,845 | linux | b9a41d21dceadf8104812626ef85dc56ee8a60ed | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b9a41d21dceadf8104812626ef85dc56ee8a60ed | dm: fix race between dm_get_from_kobject() and __dm_destroy()
The following BUG_ON was hit when testing repeat creation and removal of
DM devices:
kernel BUG at drivers/md/dm.c:2919!
CPU: 7 PID: 750 Comm: systemd-udevd Not tainted 4.1.44
Call Trace:
[<ffffffff81649e8b>] dm_get_from_kobject+0x34/0x3a
... | 1 | struct mapped_device *dm_get_from_kobject(struct kobject *kobj)
{
struct mapped_device *md;
md = container_of(kobj, struct mapped_device, kobj_holder.kobj);
if (test_bit(DMF_FREEING, &md->flags) ||
dm_deleting_md(md))
return NULL;
dm_get(md);
return md;
}
| 232,285,841,910,144,100,000,000,000,000,000,000,000 | dm.c | 56,799,825,473,684,530,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2017-18203 | The dm_get_from_kobject function in drivers/md/dm.c in the Linux kernel before 4.14.3 allow local users to cause a denial of service (BUG) by leveraging a race condition with __dm_destroy during creation and removal of DM devices. | https://nvd.nist.gov/vuln/detail/CVE-2017-18203 |
161,095 | linux | b9a41d21dceadf8104812626ef85dc56ee8a60ed | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b9a41d21dceadf8104812626ef85dc56ee8a60ed | dm: fix race between dm_get_from_kobject() and __dm_destroy()
The following BUG_ON was hit when testing repeat creation and removal of
DM devices:
kernel BUG at drivers/md/dm.c:2919!
CPU: 7 PID: 750 Comm: systemd-udevd Not tainted 4.1.44
Call Trace:
[<ffffffff81649e8b>] dm_get_from_kobject+0x34/0x3a
... | 0 | struct mapped_device *dm_get_from_kobject(struct kobject *kobj)
{
struct mapped_device *md;
md = container_of(kobj, struct mapped_device, kobj_holder.kobj);
spin_lock(&_minor_lock);
if (test_bit(DMF_FREEING, &md->flags) || dm_deleting_md(md)) {
md = NULL;
goto out;
}
dm_get(md);
out:
spin_unlock(&_mino... | 205,060,632,129,092,020,000,000,000,000,000,000,000 | dm.c | 285,194,235,611,758,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2017-18203 | The dm_get_from_kobject function in drivers/md/dm.c in the Linux kernel before 4.14.3 allow local users to cause a denial of service (BUG) by leveraging a race condition with __dm_destroy during creation and removal of DM devices. | https://nvd.nist.gov/vuln/detail/CVE-2017-18203 |
3,847 | linux | 638164a2718f337ea224b747cf5977ef143166a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/638164a2718f337ea224b747cf5977ef143166a4 | f2fs: fix potential panic during fstrim
As Ju Hyung Park reported:
"When 'fstrim' is called for manual trim, a BUG() can be triggered
randomly with this patch.
I'm seeing this issue on both x86 Desktop and arm64 Android phone.
On x86 Desktop, this was caused during Ubuntu boot-up. I have a
cronjob installed which c... | 1 | void f2fs_wait_discard_bios(struct f2fs_sb_info *sbi)
{
__issue_discard_cmd(sbi, false);
__drop_discard_cmd(sbi);
__wait_discard_cmd(sbi, false);
}
| 66,587,864,384,024,680,000,000,000,000,000,000,000 | segment.c | 277,647,022,130,075,500,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2017-18200 | The f2fs implementation in the Linux kernel before 4.14 mishandles reference counts associated with f2fs_wait_discard_bios calls, which allows local users to cause a denial of service (BUG), as demonstrated by fstrim. | https://nvd.nist.gov/vuln/detail/CVE-2017-18200 |
161,097 | linux | 638164a2718f337ea224b747cf5977ef143166a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/638164a2718f337ea224b747cf5977ef143166a4 | f2fs: fix potential panic during fstrim
As Ju Hyung Park reported:
"When 'fstrim' is called for manual trim, a BUG() can be triggered
randomly with this patch.
I'm seeing this issue on both x86 Desktop and arm64 Android phone.
On x86 Desktop, this was caused during Ubuntu boot-up. I have a
cronjob installed which c... | 0 | void f2fs_wait_discard_bios(struct f2fs_sb_info *sbi)
void f2fs_wait_discard_bios(struct f2fs_sb_info *sbi, bool umount)
{
__issue_discard_cmd(sbi, false);
__drop_discard_cmd(sbi);
__wait_discard_cmd(sbi, !umount);
}
| 223,328,090,790,695,620,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2017-18200 | The f2fs implementation in the Linux kernel before 4.14 mishandles reference counts associated with f2fs_wait_discard_bios calls, which allows local users to cause a denial of service (BUG), as demonstrated by fstrim. | https://nvd.nist.gov/vuln/detail/CVE-2017-18200 |
3,849 | linux | dad48e73127ba10279ea33e6dbc8d3905c4d31c0 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/dad48e73127ba10279ea33e6dbc8d3905c4d31c0 | f2fs: fix a bug caused by NULL extent tree
Thread A: Thread B:
-f2fs_remount
-sbi->mount_opt.opt = 0;
<--- -f2fs_iget
-do_read_inode
-f2fs_init_extent_tree
-F2FS_I(inode)->extent_tree is NULL
-default_options && parse_options
-remount return
... | 1 | bool f2fs_init_extent_tree(struct inode *inode, struct f2fs_extent *i_ext)
{
struct f2fs_sb_info *sbi = F2FS_I_SB(inode);
struct extent_tree *et;
struct extent_node *en;
struct extent_info ei;
if (!f2fs_may_extent_tree(inode)) {
/* drop largest extent */
if (i_ext && i_ext->len) {
i_ext->len = 0;
ret... | 144,565,331,810,619,090,000,000,000,000,000,000,000 | extent_cache.c | 121,324,559,268,227,700,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-18193 | fs/f2fs/extent_cache.c in the Linux kernel before 4.13 mishandles extent trees, which allows local users to cause a denial of service (BUG) via an application with multiple threads. | https://nvd.nist.gov/vuln/detail/CVE-2017-18193 |
161,099 | linux | dad48e73127ba10279ea33e6dbc8d3905c4d31c0 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/dad48e73127ba10279ea33e6dbc8d3905c4d31c0 | f2fs: fix a bug caused by NULL extent tree
Thread A: Thread B:
-f2fs_remount
-sbi->mount_opt.opt = 0;
<--- -f2fs_iget
-do_read_inode
-f2fs_init_extent_tree
-F2FS_I(inode)->extent_tree is NULL
-default_options && parse_options
-remount return
... | 0 | bool f2fs_init_extent_tree(struct inode *inode, struct f2fs_extent *i_ext)
static bool __f2fs_init_extent_tree(struct inode *inode, struct f2fs_extent *i_ext)
{
struct f2fs_sb_info *sbi = F2FS_I_SB(inode);
struct extent_tree *et;
struct extent_node *en;
struct extent_info ei;
if (!f2fs_may_extent_tree(inode)) ... | 242,004,554,196,614,770,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2017-18193 | fs/f2fs/extent_cache.c in the Linux kernel before 4.13 mishandles extent trees, which allows local users to cause a denial of service (BUG) via an application with multiple threads. | https://nvd.nist.gov/vuln/detail/CVE-2017-18193 |
3,850 | cups | afa80cb2b457bf8d64f775bed307588610476c41 | https://github.com/apple/cups | https://github.com/apple/cups/commit/afa80cb2b457bf8d64f775bed307588610476c41 | Don't treat "localhost.localdomain" as an allowed replacement for localhost, since it isn't. | 1 | valid_host(cupsd_client_t *con) /* I - Client connection */
{
cupsd_alias_t *a; /* Current alias */
cupsd_netif_t *netif; /* Current network interface */
const char *end; /* End character */
char *ptr; /* Pointer into host value */
/*
* Copy the Host: header for later use...
*/
strlcpy(con->... | 159,854,871,526,072,820,000,000,000,000,000,000,000 | client.c | 181,717,129,039,375,560,000,000,000,000,000,000,000 | [
"CWE-290"
] | CVE-2017-18190 | A localhost.localdomain whitelist entry in valid_host() in scheduler/client.c in CUPS before 2.2.2 allows remote attackers to execute arbitrary IPP commands by sending POST requests to the CUPS daemon in conjunction with DNS rebinding. The localhost.localdomain name is often resolved via a DNS server (neither the OS no... | https://nvd.nist.gov/vuln/detail/CVE-2017-18190 |
161,100 | cups | afa80cb2b457bf8d64f775bed307588610476c41 | https://github.com/apple/cups | https://github.com/apple/cups/commit/afa80cb2b457bf8d64f775bed307588610476c41 | Don't treat "localhost.localdomain" as an allowed replacement for localhost, since it isn't. | 0 | valid_host(cupsd_client_t *con) /* I - Client connection */
{
cupsd_alias_t *a; /* Current alias */
cupsd_netif_t *netif; /* Current network interface */
const char *end; /* End character */
char *ptr; /* Pointer into host value */
/*
* Copy the Host: header for later use...
*/
strlcpy(con->... | 234,780,014,241,071,320,000,000,000,000,000,000,000 | client.c | 103,799,922,917,723,230,000,000,000,000,000,000,000 | [
"CWE-290"
] | CVE-2017-18190 | A localhost.localdomain whitelist entry in valid_host() in scheduler/client.c in CUPS before 2.2.2 allows remote attackers to execute arbitrary IPP commands by sending POST requests to the CUPS daemon in conjunction with DNS rebinding. The localhost.localdomain name is often resolved via a DNS server (neither the OS no... | https://nvd.nist.gov/vuln/detail/CVE-2017-18190 |
3,851 | mbedtls | 83c9f495ffe70c7dd280b41fdfd4881485a3bc28 | https://github.com/ARMmbed/mbedtls | https://github.com/ARMmbed/mbedtls/commit/83c9f495ffe70c7dd280b41fdfd4881485a3bc28 | Prevent bounds check bypass through overflow in PSK identity parsing
The check `if( *p + n > end )` in `ssl_parse_client_psk_identity` is
unsafe because `*p + n` might overflow, thus bypassing the check. As
`n` is a user-specified value up to 65K, this is relevant if the
library happens to be located in the last 65K o... | 1 | static int ssl_parse_client_psk_identity( mbedtls_ssl_context *ssl, unsigned char **p,
const unsigned char *end )
{
int ret = 0;
size_t n;
if( ssl->conf->f_psk == NULL &&
( ssl->conf->psk == NULL || ssl->conf->psk_identity == NULL ||
ssl->conf->ps... | 246,504,953,524,229,660,000,000,000,000,000,000,000 | ssl_srv.c | 242,941,228,807,408,900,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2017-18187 | In ARM mbed TLS before 2.7.0, there is a bounds-check bypass through an integer overflow in PSK identity parsing in the ssl_parse_client_psk_identity() function in library/ssl_srv.c. | https://nvd.nist.gov/vuln/detail/CVE-2017-18187 |
161,101 | mbedtls | 83c9f495ffe70c7dd280b41fdfd4881485a3bc28 | https://github.com/ARMmbed/mbedtls | https://github.com/ARMmbed/mbedtls/commit/83c9f495ffe70c7dd280b41fdfd4881485a3bc28 | Prevent bounds check bypass through overflow in PSK identity parsing
The check `if( *p + n > end )` in `ssl_parse_client_psk_identity` is
unsafe because `*p + n` might overflow, thus bypassing the check. As
`n` is a user-specified value up to 65K, this is relevant if the
library happens to be located in the last 65K o... | 0 | static int ssl_parse_client_psk_identity( mbedtls_ssl_context *ssl, unsigned char **p,
const unsigned char *end )
{
int ret = 0;
size_t n;
if( ssl->conf->f_psk == NULL &&
( ssl->conf->psk == NULL || ssl->conf->psk_identity == NULL ||
ssl->conf->ps... | 26,183,726,826,899,012,000,000,000,000,000,000,000 | ssl_srv.c | 60,632,523,941,907,960,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2017-18187 | In ARM mbed TLS before 2.7.0, there is a bounds-check bypass through an integer overflow in PSK identity parsing in the ssl_parse_client_psk_identity() function in library/ssl_srv.c. | https://nvd.nist.gov/vuln/detail/CVE-2017-18187 |
3,852 | linux | 8dca4a41f1ad65043a78c2338d9725f859c8d2c3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8dca4a41f1ad65043a78c2338d9725f859c8d2c3 | pinctrl/amd: Drop pinctrl_unregister for devm_ registered device
It's not necessary to unregister pin controller device registered
with devm_pinctrl_register() and using pinctrl_unregister() leads
to a double free.
Fixes: 3bfd44306c65 ("pinctrl: amd: Add support for additional GPIO")
Signed-off-by: Wei Yongjun <weiyo... | 1 | static int amd_gpio_remove(struct platform_device *pdev)
{
struct amd_gpio *gpio_dev;
gpio_dev = platform_get_drvdata(pdev);
gpiochip_remove(&gpio_dev->gc);
pinctrl_unregister(gpio_dev->pctrl);
return 0;
}
| 100,344,955,333,259,860,000,000,000,000,000,000,000 | pinctrl-amd.c | 137,063,333,804,755,300,000,000,000,000,000,000,000 | [
"CWE-415"
] | CVE-2017-18174 | In the Linux kernel before 4.7, the amd_gpio_remove function in drivers/pinctrl/pinctrl-amd.c calls the pinctrl_unregister function, leading to a double free. | https://nvd.nist.gov/vuln/detail/CVE-2017-18174 |
161,102 | linux | 8dca4a41f1ad65043a78c2338d9725f859c8d2c3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8dca4a41f1ad65043a78c2338d9725f859c8d2c3 | pinctrl/amd: Drop pinctrl_unregister for devm_ registered device
It's not necessary to unregister pin controller device registered
with devm_pinctrl_register() and using pinctrl_unregister() leads
to a double free.
Fixes: 3bfd44306c65 ("pinctrl: amd: Add support for additional GPIO")
Signed-off-by: Wei Yongjun <weiyo... | 0 | static int amd_gpio_remove(struct platform_device *pdev)
{
struct amd_gpio *gpio_dev;
gpio_dev = platform_get_drvdata(pdev);
gpiochip_remove(&gpio_dev->gc);
return 0;
}
| 16,907,051,573,240,250,000,000,000,000,000,000,000 | pinctrl-amd.c | 118,956,490,816,980,920,000,000,000,000,000,000,000 | [
"CWE-415"
] | CVE-2017-18174 | In the Linux kernel before 4.7, the amd_gpio_remove function in drivers/pinctrl/pinctrl-amd.c calls the pinctrl_unregister function, leading to a double free. | https://nvd.nist.gov/vuln/detail/CVE-2017-18174 |
3,858 | linux | 2638fd0f92d4397884fd991d8f4925cb3f081901 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2638fd0f92d4397884fd991d8f4925cb3f081901 | netfilter: xt_TCPMSS: add more sanity tests on tcph->doff
Denys provided an awesome KASAN report pointing to an use
after free in xt_TCPMSS
I have provided three patches to fix this issue, either in xt_TCPMSS or
in xt_tcpudp.c. It seems xt_TCPMSS patch has the smallest possible
impact.
Signed-off-by: Eric Dumazet <e... | 1 | tcpmss_mangle_packet(struct sk_buff *skb,
const struct xt_action_param *par,
unsigned int family,
unsigned int tcphoff,
unsigned int minlen)
{
const struct xt_tcpmss_info *info = par->targinfo;
struct tcphdr *tcph;
int len, tcp_hdrlen;
unsigned int i;
__be16 oldval;
u16 newmss;
u8 *op... | 250,029,302,786,329,280,000,000,000,000,000,000,000 | xt_TCPMSS.c | 261,370,175,787,540,400,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2017-18017 | The tcpmss_mangle_packet function in net/netfilter/xt_TCPMSS.c in the Linux kernel before 4.11, and 4.9.x before 4.9.36, allows remote attackers to cause a denial of service (use-after-free and memory corruption) or possibly have unspecified other impact by leveraging the presence of xt_TCPMSS in an iptables action. | https://nvd.nist.gov/vuln/detail/CVE-2017-18017 |
161,108 | linux | 2638fd0f92d4397884fd991d8f4925cb3f081901 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2638fd0f92d4397884fd991d8f4925cb3f081901 | netfilter: xt_TCPMSS: add more sanity tests on tcph->doff
Denys provided an awesome KASAN report pointing to an use
after free in xt_TCPMSS
I have provided three patches to fix this issue, either in xt_TCPMSS or
in xt_tcpudp.c. It seems xt_TCPMSS patch has the smallest possible
impact.
Signed-off-by: Eric Dumazet <e... | 0 | tcpmss_mangle_packet(struct sk_buff *skb,
const struct xt_action_param *par,
unsigned int family,
unsigned int tcphoff,
unsigned int minlen)
{
const struct xt_tcpmss_info *info = par->targinfo;
struct tcphdr *tcph;
int len, tcp_hdrlen;
unsigned int i;
__be16 oldval;
u16 newmss;
u8 *op... | 240,589,034,835,230,740,000,000,000,000,000,000,000 | xt_TCPMSS.c | 126,674,226,486,833,980,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2017-18017 | The tcpmss_mangle_packet function in net/netfilter/xt_TCPMSS.c in the Linux kernel before 4.11, and 4.9.x before 4.9.36, allows remote attackers to cause a denial of service (use-after-free and memory corruption) or possibly have unspecified other impact by leveraging the presence of xt_TCPMSS in an iptables action. | https://nvd.nist.gov/vuln/detail/CVE-2017-18017 |
3,859 | linux | 21b5944350052d2583e82dd59b19a9ba94a007f0 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/21b5944350052d2583e82dd59b19a9ba94a007f0 | net: Fix double free and memory corruption in get_net_ns_by_id()
(I can trivially verify that that idr_remove in cleanup_net happens
after the network namespace count has dropped to zero --EWB)
Function get_net_ns_by_id() does not check for net::count
after it has found a peer in netns_ids idr.
It may dereference a... | 1 | struct net *get_net_ns_by_id(struct net *net, int id)
{
struct net *peer;
if (id < 0)
return NULL;
rcu_read_lock();
spin_lock_bh(&net->nsid_lock);
peer = idr_find(&net->netns_ids, id);
if (peer)
get_net(peer);
spin_unlock_bh(&net->nsid_lock);
rcu_read_unlock();
return peer;
}
| 126,228,411,105,494,450,000,000,000,000,000,000,000 | net_namespace.c | 229,167,366,123,156,130,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2017-15129 | A use-after-free vulnerability was found in network namespaces code affecting the Linux kernel before 4.14.11. The function get_net_ns_by_id() in net/core/net_namespace.c does not check for the net::count value after it has found a peer network in netns_ids idr, which could lead to double free and memory corruption. Th... | https://nvd.nist.gov/vuln/detail/CVE-2017-15129 |
161,109 | linux | 21b5944350052d2583e82dd59b19a9ba94a007f0 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/21b5944350052d2583e82dd59b19a9ba94a007f0 | net: Fix double free and memory corruption in get_net_ns_by_id()
(I can trivially verify that that idr_remove in cleanup_net happens
after the network namespace count has dropped to zero --EWB)
Function get_net_ns_by_id() does not check for net::count
after it has found a peer in netns_ids idr.
It may dereference a... | 0 | struct net *get_net_ns_by_id(struct net *net, int id)
{
struct net *peer;
if (id < 0)
return NULL;
rcu_read_lock();
spin_lock_bh(&net->nsid_lock);
peer = idr_find(&net->netns_ids, id);
if (peer)
peer = maybe_get_net(peer);
spin_unlock_bh(&net->nsid_lock);
rcu_read_unlock();
return peer;
}
| 199,598,220,940,675,900,000,000,000,000,000,000,000 | net_namespace.c | 89,942,350,547,691,740,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2017-15129 | A use-after-free vulnerability was found in network namespaces code affecting the Linux kernel before 4.14.11. The function get_net_ns_by_id() in net/core/net_namespace.c does not check for the net::count value after it has found a peer network in netns_ids idr, which could lead to double free and memory corruption. Th... | https://nvd.nist.gov/vuln/detail/CVE-2017-15129 |
3,860 | linux | 1e3921471354244f70fe268586ff94a97a6dd4df | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1e3921471354244f70fe268586ff94a97a6dd4df | userfaultfd: hugetlbfs: prevent UFFDIO_COPY to fill beyond the end of i_size
This oops:
kernel BUG at fs/hugetlbfs/inode.c:484!
RIP: remove_inode_hugepages+0x3d0/0x410
Call Trace:
hugetlbfs_setattr+0xd9/0x130
notify_change+0x292/0x410
do_truncate+0x65/0xa0
do_sys_ftruncate.constprop.3+0x11a/0x18... | 1 | int hugetlb_mcopy_atomic_pte(struct mm_struct *dst_mm,
pte_t *dst_pte,
struct vm_area_struct *dst_vma,
unsigned long dst_addr,
unsigned long src_addr,
struct page **pagep)
{
int vm_shared = dst_vma->vm_flags & VM_SHARED;
struct hstate *h = hstate_vma(dst_vma);
pte_t _dst_pte;... | 285,571,524,825,774,600,000,000,000,000,000,000,000 | hugetlb.c | 273,321,831,039,362,950,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-15128 | A flaw was found in the hugetlb_mcopy_atomic_pte function in mm/hugetlb.c in the Linux kernel before 4.13.12. A lack of size check could cause a denial of service (BUG). | https://nvd.nist.gov/vuln/detail/CVE-2017-15128 |
161,110 | linux | 1e3921471354244f70fe268586ff94a97a6dd4df | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1e3921471354244f70fe268586ff94a97a6dd4df | userfaultfd: hugetlbfs: prevent UFFDIO_COPY to fill beyond the end of i_size
This oops:
kernel BUG at fs/hugetlbfs/inode.c:484!
RIP: remove_inode_hugepages+0x3d0/0x410
Call Trace:
hugetlbfs_setattr+0xd9/0x130
notify_change+0x292/0x410
do_truncate+0x65/0xa0
do_sys_ftruncate.constprop.3+0x11a/0x18... | 0 | int hugetlb_mcopy_atomic_pte(struct mm_struct *dst_mm,
pte_t *dst_pte,
struct vm_area_struct *dst_vma,
unsigned long dst_addr,
unsigned long src_addr,
struct page **pagep)
{
struct address_space *mapping;
pgoff_t idx;
unsigned long size;
int vm_shared = dst_vma->vm_flags & VM_... | 202,391,246,281,638,860,000,000,000,000,000,000,000 | hugetlb.c | 140,652,589,322,022,340,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-15128 | A flaw was found in the hugetlb_mcopy_atomic_pte function in mm/hugetlb.c in the Linux kernel before 4.13.12. A lack of size check could cause a denial of service (BUG). | https://nvd.nist.gov/vuln/detail/CVE-2017-15128 |
3,865 | knc | f237f3e09ecbaf59c897f5046538a7b1a3fa40c1 | https://github.com/elric1/knc | https://github.com/elric1/knc/commit/f237f3e09ecbaf59c897f5046538a7b1a3fa40c1 | knc: fix a couple of memory leaks.
One of these can be remotely triggered during the authentication
phase which leads to a remote DoS possibility.
Pointed out by: Imre Rad <radimre83@gmail.com> | 1 | read_packet(int fd, gss_buffer_t buf, int timeout, int first)
{
int ret;
static uint32_t len = 0;
static char len_buf[4];
static int len_buf_pos = 0;
static char * tmpbuf = 0;
static int tmpbuf_pos = 0;
if (first) {
len_buf_pos = 0;
return -2;
}
if (len_buf_pos < 4) {
ret = timed_read(fd, &len_... | 224,824,590,746,883,080,000,000,000,000,000,000,000 | gssstdio.c | 8,886,790,502,415,457,000,000,000,000,000,000,000 | [
"CWE-400"
] | CVE-2017-9732 | The read_packet function in knc (Kerberised NetCat) before 1.11-1 is vulnerable to denial of service (memory exhaustion) that can be exploited remotely without authentication, possibly affecting another services running on the targeted host. | https://nvd.nist.gov/vuln/detail/CVE-2017-9732 |
161,114 | knc | f237f3e09ecbaf59c897f5046538a7b1a3fa40c1 | https://github.com/elric1/knc | https://github.com/elric1/knc/commit/f237f3e09ecbaf59c897f5046538a7b1a3fa40c1 | knc: fix a couple of memory leaks.
One of these can be remotely triggered during the authentication
phase which leads to a remote DoS possibility.
Pointed out by: Imre Rad <radimre83@gmail.com> | 0 | read_packet(int fd, gss_buffer_t buf, int timeout, int first)
{
int ret;
static uint32_t len = 0;
static char len_buf[4];
static int len_buf_pos = 0;
static char * tmpbuf = 0;
static int tmpbuf_pos = 0;
if (first) {
len_buf_pos = 0;
return -2;
}
if (len_buf_pos < 4) {
ret = timed_read(fd, &len_... | 146,476,194,780,541,850,000,000,000,000,000,000,000 | gssstdio.c | 236,094,621,676,270,260,000,000,000,000,000,000,000 | [
"CWE-400"
] | CVE-2017-9732 | The read_packet function in knc (Kerberised NetCat) before 1.11-1 is vulnerable to denial of service (memory exhaustion) that can be exploited remotely without authentication, possibly affecting another services running on the targeted host. | https://nvd.nist.gov/vuln/detail/CVE-2017-9732 |
3,866 | util-linux | dffab154d29a288aa171ff50263ecc8f2e14a891 | https://github.com/karelzak/util-linux | https://github.com/karelzak/util-linux/commit/dffab154d29a288aa171ff50263ecc8f2e14a891 | su: properly clear child PID
Reported-by: Tobias Stöckmann <tobias@stoeckmann.org>
Signed-off-by: Karel Zak <kzak@redhat.com> | 1 | create_watching_parent (void)
{
pid_t child;
sigset_t ourset;
struct sigaction oldact[3];
int status = 0;
int retval;
retval = pam_open_session (pamh, 0);
if (is_pam_failure(retval))
{
cleanup_pam (retval);
errx (EXIT_FAILURE, _("cannot open session: %s"),
pam_strerror (pamh, retval... | 132,373,565,874,554,270,000,000,000,000,000,000,000 | su-common.c | 260,033,572,435,501,420,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2017-2616 | A race condition was found in util-linux before 2.32.1 in the way su handled the management of child processes. A local authenticated attacker could use this flaw to kill other processes with root privileges under specific conditions. | https://nvd.nist.gov/vuln/detail/CVE-2017-2616 |
161,115 | util-linux | dffab154d29a288aa171ff50263ecc8f2e14a891 | https://github.com/karelzak/util-linux | https://github.com/karelzak/util-linux/commit/dffab154d29a288aa171ff50263ecc8f2e14a891 | su: properly clear child PID
Reported-by: Tobias Stöckmann <tobias@stoeckmann.org>
Signed-off-by: Karel Zak <kzak@redhat.com> | 0 | create_watching_parent (void)
{
pid_t child;
sigset_t ourset;
struct sigaction oldact[3];
int status = 0;
int retval;
retval = pam_open_session (pamh, 0);
if (is_pam_failure(retval))
{
cleanup_pam (retval);
errx (EXIT_FAILURE, _("cannot open session: %s"),
pam_strerror (pamh, retval... | 242,326,247,116,681,320,000,000,000,000,000,000,000 | su-common.c | 129,079,729,540,465,230,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2017-2616 | A race condition was found in util-linux before 2.32.1 in the way su handled the management of child processes. A local authenticated attacker could use this flaw to kill other processes with root privileges under specific conditions. | https://nvd.nist.gov/vuln/detail/CVE-2017-2616 |
3,877 | pacemaker | 5d71e65049 | https://github.com/ClusterLabs/pacemaker | https://github.com/ClusterLabs/pacemaker/commit/5d71e65049 | High: libcrmcommon: fix CVE-2016-7035 (improper IPC guarding)
It was discovered that at some not so uncommon circumstances, some
pacemaker daemons could be talked to, via libqb-facilitated IPC, by
unprivileged clients due to flawed authorization decision. Depending
on the capabilities of affected daemons, this might ... | 1 | crm_client_new(qb_ipcs_connection_t * c, uid_t uid_client, gid_t gid_client)
{
static uid_t uid_server = 0;
static gid_t gid_cluster = 0;
crm_client_t *client = NULL;
CRM_LOG_ASSERT(c);
if (c == NULL) {
return NULL;
}
if (gid_cluster == 0) {
uid_server = getuid();
... | 332,194,409,869,094,700,000,000,000,000,000,000,000 | ipc.c | 236,018,087,578,267,460,000,000,000,000,000,000,000 | [
"CWE-285"
] | CVE-2016-7035 | An authorization flaw was found in Pacemaker before 1.1.16, where it did not properly guard its IPC interface. An attacker with an unprivileged account on a Pacemaker node could use this flaw to, for example, force the Local Resource Manager daemon to execute a script as root and thereby gain root access on the machine... | https://nvd.nist.gov/vuln/detail/CVE-2016-7035 |
161,124 | pacemaker | 5d71e65049 | https://github.com/ClusterLabs/pacemaker | https://github.com/ClusterLabs/pacemaker/commit/5d71e65049 | High: libcrmcommon: fix CVE-2016-7035 (improper IPC guarding)
It was discovered that at some not so uncommon circumstances, some
pacemaker daemons could be talked to, via libqb-facilitated IPC, by
unprivileged clients due to flawed authorization decision. Depending
on the capabilities of affected daemons, this might ... | 0 | crm_client_new(qb_ipcs_connection_t * c, uid_t uid_client, gid_t gid_client)
{
static gid_t gid_cluster = 0;
crm_client_t *client = NULL;
CRM_LOG_ASSERT(c);
if (c == NULL) {
return NULL;
}
if (gid_cluster == 0) {
if(crm_user_lookup(CRM_DAEMON_USER, NULL, &gid_cluster)... | 71,785,123,703,182,670,000,000,000,000,000,000,000 | ipc.c | 188,157,731,451,493,530,000,000,000,000,000,000,000 | [
"CWE-285"
] | CVE-2016-7035 | An authorization flaw was found in Pacemaker before 1.1.16, where it did not properly guard its IPC interface. An attacker with an unprivileged account on a Pacemaker node could use this flaw to, for example, force the Local Resource Manager daemon to execute a script as root and thereby gain root access on the machine... | https://nvd.nist.gov/vuln/detail/CVE-2016-7035 |
3,878 | libtiff | 391e77fcd217e78b2c51342ac3ddb7100ecacdd2 | https://github.com/vadz/libtiff | https://github.com/vadz/libtiff/commit/391e77fcd217e78b2c51342ac3ddb7100ecacdd2 | * libtiff/tif_pixarlog.c: fix potential buffer write overrun in
PixarLogDecode() on corrupted/unexpected images (reported by Mathias Svensson) | 1 | PixarLogDecode(TIFF* tif, uint8* op, tmsize_t occ, uint16 s)
{
static const char module[] = "PixarLogDecode";
TIFFDirectory *td = &tif->tif_dir;
PixarLogState* sp = DecoderState(tif);
tmsize_t i;
tmsize_t nsamples;
int llen;
uint16 *up;
switch (sp->user_datafmt) {
case PIXARLOGDATAFMT_FLOAT:
nsamples = occ ... | 310,103,018,809,032,760,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2016-5314 | Buffer overflow in the PixarLogDecode function in tif_pixarlog.c in LibTIFF 4.0.6 and earlier allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a crafted TIFF image, as demonstrated by overwriting the vgetparent function pointer with rgb2ycbcr. | https://nvd.nist.gov/vuln/detail/CVE-2016-5314 |
161,125 | libtiff | 391e77fcd217e78b2c51342ac3ddb7100ecacdd2 | https://github.com/vadz/libtiff | https://github.com/vadz/libtiff/commit/391e77fcd217e78b2c51342ac3ddb7100ecacdd2 | * libtiff/tif_pixarlog.c: fix potential buffer write overrun in
PixarLogDecode() on corrupted/unexpected images (reported by Mathias Svensson) | 0 | PixarLogDecode(TIFF* tif, uint8* op, tmsize_t occ, uint16 s)
{
static const char module[] = "PixarLogDecode";
TIFFDirectory *td = &tif->tif_dir;
PixarLogState* sp = DecoderState(tif);
tmsize_t i;
tmsize_t nsamples;
int llen;
uint16 *up;
switch (sp->user_datafmt) {
case PIXARLOGDATAFMT_FLOAT:
nsamples = occ ... | 63,994,839,641,883,780,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2016-5314 | Buffer overflow in the PixarLogDecode function in tif_pixarlog.c in LibTIFF 4.0.6 and earlier allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a crafted TIFF image, as demonstrated by overwriting the vgetparent function pointer with rgb2ycbcr. | https://nvd.nist.gov/vuln/detail/CVE-2016-5314 |
3,887 | libtiff | 3c5eb8b1be544e41d2c336191bc4936300ad7543 | https://github.com/vadz/libtiff | https://github.com/vadz/libtiff/commit/3c5eb8b1be544e41d2c336191bc4936300ad7543 | * libtiff/tif_{unix,vms,win32}.c (_TIFFmalloc): ANSI C does not
require malloc() to return NULL pointer if requested allocation
size is zero. Assure that _TIFFmalloc does. | 1 | _TIFFmalloc(tmsize_t s)
{
return (malloc((size_t) s));
}
| 51,150,050,486,560,425,000,000,000,000,000,000,000 | None | null | [
"CWE-369"
] | CVE-2014-8130 | The _TIFFmalloc function in tif_unix.c in LibTIFF 4.0.3 does not reject a zero size, which allows remote attackers to cause a denial of service (divide-by-zero error and application crash) via a crafted TIFF image that is mishandled by the TIFFWriteScanline function in tif_write.c, as demonstrated by tiffdither. | https://nvd.nist.gov/vuln/detail/CVE-2014-8130 |
79,346 | libtiff | 3c5eb8b1be544e41d2c336191bc4936300ad7543 | https://github.com/vadz/libtiff | https://github.com/vadz/libtiff/commit/3c5eb8b1be544e41d2c336191bc4936300ad7543 | * libtiff/tif_{unix,vms,win32}.c (_TIFFmalloc): ANSI C does not
require malloc() to return NULL pointer if requested allocation
size is zero. Assure that _TIFFmalloc does. | 0 | _TIFFrealloc(void* p, tmsize_t s)
{
return (realloc(p, (size_t) s));
}
| 205,137,396,355,273,140,000,000,000,000,000,000,000 | None | null | [
"CWE-369"
] | CVE-2014-8130 | The _TIFFmalloc function in tif_unix.c in LibTIFF 4.0.3 does not reject a zero size, which allows remote attackers to cause a denial of service (divide-by-zero error and application crash) via a crafted TIFF image that is mishandled by the TIFFWriteScanline function in tif_write.c, as demonstrated by tiffdither. | https://nvd.nist.gov/vuln/detail/CVE-2014-8130 |
3,888 | libtiff | 3c5eb8b1be544e41d2c336191bc4936300ad7543 | https://github.com/vadz/libtiff | https://github.com/vadz/libtiff/commit/3c5eb8b1be544e41d2c336191bc4936300ad7543 | * libtiff/tif_{unix,vms,win32}.c (_TIFFmalloc): ANSI C does not
require malloc() to return NULL pointer if requested allocation
size is zero. Assure that _TIFFmalloc does. | 1 | _TIFFmalloc(tsize_t s)
{
return (malloc((size_t) s));
}
| 163,740,521,083,677,580,000,000,000,000,000,000,000 | None | null | [
"CWE-369"
] | CVE-2014-8130 | The _TIFFmalloc function in tif_unix.c in LibTIFF 4.0.3 does not reject a zero size, which allows remote attackers to cause a denial of service (divide-by-zero error and application crash) via a crafted TIFF image that is mishandled by the TIFFWriteScanline function in tif_write.c, as demonstrated by tiffdither. | https://nvd.nist.gov/vuln/detail/CVE-2014-8130 |
79,346 | libtiff | 3c5eb8b1be544e41d2c336191bc4936300ad7543 | https://github.com/vadz/libtiff | https://github.com/vadz/libtiff/commit/3c5eb8b1be544e41d2c336191bc4936300ad7543 | * libtiff/tif_{unix,vms,win32}.c (_TIFFmalloc): ANSI C does not
require malloc() to return NULL pointer if requested allocation
size is zero. Assure that _TIFFmalloc does. | 0 | _TIFFrealloc(void* p, tmsize_t s)
{
return (realloc(p, (size_t) s));
}
| 205,137,396,355,273,140,000,000,000,000,000,000,000 | None | null | [
"CWE-369"
] | CVE-2014-8130 | The _TIFFmalloc function in tif_unix.c in LibTIFF 4.0.3 does not reject a zero size, which allows remote attackers to cause a denial of service (divide-by-zero error and application crash) via a crafted TIFF image that is mishandled by the TIFFWriteScanline function in tif_write.c, as demonstrated by tiffdither. | https://nvd.nist.gov/vuln/detail/CVE-2014-8130 |
3,889 | libmspack | 2f084136cfe0d05e5bf5703f3e83c6d955234b4d | https://github.com/kyz/libmspack | https://github.com/kyz/libmspack/commit/2f084136cfe0d05e5bf5703f3e83c6d955234b4d | length checks when looking for control files | 1 | static int chmd_read_headers(struct mspack_system *sys, struct mspack_file *fh,
struct mschmd_header *chm, int entire)
{
unsigned int section, name_len, x, errors, num_chunks;
unsigned char buf[0x54], *chunk = NULL, *name, *p, *end;
struct mschmd_file *fi, *link = NULL;
off_t offset... | 20,608,871,291,788,966,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2019-1010305 | libmspack 0.9.1alpha is affected by: Buffer Overflow. The impact is: Information Disclosure. The component is: function chmd_read_headers() in libmspack(file libmspack/mspack/chmd.c). The attack vector is: the victim must open a specially crafted chm file. The fixed version is: after commit 2f084136cfe0d05e5bf5703f3e83... | https://nvd.nist.gov/vuln/detail/CVE-2019-1010305 |
161,137 | libmspack | 2f084136cfe0d05e5bf5703f3e83c6d955234b4d | https://github.com/kyz/libmspack | https://github.com/kyz/libmspack/commit/2f084136cfe0d05e5bf5703f3e83c6d955234b4d | length checks when looking for control files | 0 | static int chmd_read_headers(struct mspack_system *sys, struct mspack_file *fh,
struct mschmd_header *chm, int entire)
{
unsigned int section, name_len, x, errors, num_chunks;
unsigned char buf[0x54], *chunk = NULL, *name, *p, *end;
struct mschmd_file *fi, *link = NULL;
off_t offset... | 211,777,395,711,187,100,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2019-1010305 | libmspack 0.9.1alpha is affected by: Buffer Overflow. The impact is: Information Disclosure. The component is: function chmd_read_headers() in libmspack(file libmspack/mspack/chmd.c). The attack vector is: the victim must open a specially crafted chm file. The fixed version is: after commit 2f084136cfe0d05e5bf5703f3e83... | https://nvd.nist.gov/vuln/detail/CVE-2019-1010305 |
3,890 | cJSON | be749d7efa7c9021da746e685bd6dec79f9dd99b | https://github.com/DaveGamble/cJSON | https://github.com/DaveGamble/cJSON/commit/be749d7efa7c9021da746e685bd6dec79f9dd99b | Fix crash of cJSON_GetObjectItemCaseSensitive when calling it on arrays | 1 | static cJSON *get_object_item(const cJSON * const object, const char * const name, const cJSON_bool case_sensitive)
{
cJSON *current_element = NULL;
if ((object == NULL) || (name == NULL))
{
return NULL;
}
current_element = object->child;
if (case_sensitive)
{
while ((cu... | 140,993,672,709,749,150,000,000,000,000,000,000,000 | None | null | [
"CWE-754"
] | CVE-2019-1010239 | DaveGamble/cJSON cJSON 1.7.8 is affected by: Improper Check for Unusual or Exceptional Conditions. The impact is: Null dereference, so attack can cause denial of service. The component is: cJSON_GetObjectItemCaseSensitive() function. The attack vector is: crafted json file. The fixed version is: 1.7.9 and later. | https://nvd.nist.gov/vuln/detail/CVE-2019-1010239 |
161,142 | cJSON | be749d7efa7c9021da746e685bd6dec79f9dd99b | https://github.com/DaveGamble/cJSON | https://github.com/DaveGamble/cJSON/commit/be749d7efa7c9021da746e685bd6dec79f9dd99b | Fix crash of cJSON_GetObjectItemCaseSensitive when calling it on arrays | 0 | static cJSON *get_object_item(const cJSON * const object, const char * const name, const cJSON_bool case_sensitive)
{
cJSON *current_element = NULL;
if ((object == NULL) || (name == NULL))
{
return NULL;
}
current_element = object->child;
if (case_sensitive)
{
while ((cu... | 183,426,283,531,350,660,000,000,000,000,000,000,000 | None | null | [
"CWE-754"
] | CVE-2019-1010239 | DaveGamble/cJSON cJSON 1.7.8 is affected by: Improper Check for Unusual or Exceptional Conditions. The impact is: Null dereference, so attack can cause denial of service. The component is: cJSON_GetObjectItemCaseSensitive() function. The attack vector is: crafted json file. The fixed version is: 1.7.9 and later. | https://nvd.nist.gov/vuln/detail/CVE-2019-1010239 |
3,891 | VeraCrypt | f30f9339c9a0b9bbcc6f5ad38804af39db1f479e | https://github.com/veracrypt/VeraCrypt | https://github.com/veracrypt/VeraCrypt/commit/f30f9339c9a0b9bbcc6f5ad38804af39db1f479e | Windows: fix low severity vulnerability in driver that allowed reading 3 bytes of kernel stack memory (with a rare possibility of 25 additional bytes). Reported by Tim Harrison. | 1 | NTSTATUS ProcessMainDeviceControlIrp (PDEVICE_OBJECT DeviceObject, PEXTENSION Extension, PIRP Irp)
{
PIO_STACK_LOCATION irpSp = IoGetCurrentIrpStackLocation (Irp);
NTSTATUS ntStatus;
switch (irpSp->Parameters.DeviceIoControl.IoControlCode)
{
case TC_IOCTL_GET_DRIVER_VERSION:
case TC_IOCTL_LEGACY_GET_DRIVER_VERSI... | 102,220,743,591,744,230,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2019-1010208 | IDRIX, Truecrypt Veracrypt, Truecrypt Prior to 1.23-Hotfix-1 (Veracrypt), all versions (Truecrypt) is affected by: Buffer Overflow. The impact is: Minor information disclosure of kernel stack. The component is: Veracrypt NT Driver (veracrypt.sys). The attack vector is: Locally executed code, IOCTL request to driver. Th... | https://nvd.nist.gov/vuln/detail/CVE-2019-1010208 |
161,143 | VeraCrypt | f30f9339c9a0b9bbcc6f5ad38804af39db1f479e | https://github.com/veracrypt/VeraCrypt | https://github.com/veracrypt/VeraCrypt/commit/f30f9339c9a0b9bbcc6f5ad38804af39db1f479e | Windows: fix low severity vulnerability in driver that allowed reading 3 bytes of kernel stack memory (with a rare possibility of 25 additional bytes). Reported by Tim Harrison. | 0 | NTSTATUS ProcessMainDeviceControlIrp (PDEVICE_OBJECT DeviceObject, PEXTENSION Extension, PIRP Irp)
{
PIO_STACK_LOCATION irpSp = IoGetCurrentIrpStackLocation (Irp);
NTSTATUS ntStatus;
switch (irpSp->Parameters.DeviceIoControl.IoControlCode)
{
case TC_IOCTL_GET_DRIVER_VERSION:
case TC_IOCTL_LEGACY_GET_DRIVER_VERSI... | 133,924,060,655,620,960,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2019-1010208 | IDRIX, Truecrypt Veracrypt, Truecrypt Prior to 1.23-Hotfix-1 (Veracrypt), all versions (Truecrypt) is affected by: Buffer Overflow. The impact is: Minor information disclosure of kernel stack. The component is: Veracrypt NT Driver (veracrypt.sys). The attack vector is: Locally executed code, IOCTL request to driver. Th... | https://nvd.nist.gov/vuln/detail/CVE-2019-1010208 |
3,892 | libarchive | 8312eaa576014cd9b965012af51bc1f967b12423 | https://github.com/libarchive/libarchive | https://github.com/libarchive/libarchive/commit/8312eaa576014cd9b965012af51bc1f967b12423 | iso9660: Fail when expected Rockridge extensions is missing
A corrupted or malicious ISO9660 image can cause read_CE() to loop
forever.
read_CE() calls parse_rockridge(), expecting a Rockridge extension
to be read. However, parse_rockridge() is structured as a while
loop starting with a sanity check, and if the sanit... | 1 | parse_rockridge(struct archive_read *a, struct file_info *file,
const unsigned char *p, const unsigned char *end)
{
struct iso9660 *iso9660;
iso9660 = (struct iso9660 *)(a->format->data);
while (p + 4 <= end /* Enough space for another entry. */
&& p[0] >= 'A' && p[0] <= 'Z' /* Sanity-check 1st cha... | 54,247,877,453,009,570,000,000,000,000,000,000,000 | archive_read_support_format_iso9660.c | 163,147,012,537,271,200,000,000,000,000,000,000,000 | [
"CWE-400"
] | CVE-2019-1000020 | libarchive version commit 5a98dcf8a86364b3c2c469c85b93647dfb139961 onwards (version v2.8.0 onwards) contains a CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability in ISO9660 parser, archive_read_support_format_iso9660.c, read_CE()/parse_rockridge() that can result in DoS by infinite loop. This... | https://nvd.nist.gov/vuln/detail/CVE-2019-1000020 |
161,144 | libarchive | 8312eaa576014cd9b965012af51bc1f967b12423 | https://github.com/libarchive/libarchive | https://github.com/libarchive/libarchive/commit/8312eaa576014cd9b965012af51bc1f967b12423 | iso9660: Fail when expected Rockridge extensions is missing
A corrupted or malicious ISO9660 image can cause read_CE() to loop
forever.
read_CE() calls parse_rockridge(), expecting a Rockridge extension
to be read. However, parse_rockridge() is structured as a while
loop starting with a sanity check, and if the sanit... | 0 | parse_rockridge(struct archive_read *a, struct file_info *file,
const unsigned char *p, const unsigned char *end)
{
struct iso9660 *iso9660;
int entry_seen = 0;
iso9660 = (struct iso9660 *)(a->format->data);
while (p + 4 <= end /* Enough space for another entry. */
&& p[0] >= 'A' && p[0] <= 'Z' /*... | 188,676,922,302,035,600,000,000,000,000,000,000,000 | archive_read_support_format_iso9660.c | 216,213,086,100,530,100,000,000,000,000,000,000,000 | [
"CWE-400"
] | CVE-2019-1000020 | libarchive version commit 5a98dcf8a86364b3c2c469c85b93647dfb139961 onwards (version v2.8.0 onwards) contains a CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability in ISO9660 parser, archive_read_support_format_iso9660.c, read_CE()/parse_rockridge() that can result in DoS by infinite loop. This... | https://nvd.nist.gov/vuln/detail/CVE-2019-1000020 |
3,893 | libarchive | 65a23f5dbee4497064e9bb467f81138a62b0dae1 | https://github.com/libarchive/libarchive | https://github.com/libarchive/libarchive/commit/65a23f5dbee4497064e9bb467f81138a62b0dae1 | 7zip: fix crash when parsing certain archives
Fuzzing with CRCs disabled revealed that a call to get_uncompressed_data()
would sometimes fail to return at least 'minimum' bytes. This can cause
the crc32() invocation in header_bytes to read off into invalid memory.
A specially crafted archive can use this to cause a c... | 1 | get_uncompressed_data(struct archive_read *a, const void **buff, size_t size,
size_t minimum)
{
struct _7zip *zip = (struct _7zip *)a->format->data;
ssize_t bytes_avail;
if (zip->codec == _7Z_COPY && zip->codec2 == (unsigned long)-1) {
/* Copy mode. */
/*
* Note: '1' here is a performance optimizatio... | 172,034,182,329,715,270,000,000,000,000,000,000,000 | archive_read_support_format_7zip.c | 100,268,367,669,914,640,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2019-1000019 | libarchive version commit bf9aec176c6748f0ee7a678c5f9f9555b9a757c1 onwards (release v3.0.2 onwards) contains a CWE-125: Out-of-bounds Read vulnerability in 7zip decompression, archive_read_support_format_7zip.c, header_bytes() that can result in a crash (denial of service). This attack appears to be exploitable via the... | https://nvd.nist.gov/vuln/detail/CVE-2019-1000019 |
161,145 | libarchive | 65a23f5dbee4497064e9bb467f81138a62b0dae1 | https://github.com/libarchive/libarchive | https://github.com/libarchive/libarchive/commit/65a23f5dbee4497064e9bb467f81138a62b0dae1 | 7zip: fix crash when parsing certain archives
Fuzzing with CRCs disabled revealed that a call to get_uncompressed_data()
would sometimes fail to return at least 'minimum' bytes. This can cause
the crc32() invocation in header_bytes to read off into invalid memory.
A specially crafted archive can use this to cause a c... | 0 | get_uncompressed_data(struct archive_read *a, const void **buff, size_t size,
size_t minimum)
{
struct _7zip *zip = (struct _7zip *)a->format->data;
ssize_t bytes_avail;
if (zip->codec == _7Z_COPY && zip->codec2 == (unsigned long)-1) {
/* Copy mode. */
*buff = __archive_read_ahead(a, minimum, &bytes_ava... | 160,627,871,233,903,730,000,000,000,000,000,000,000 | archive_read_support_format_7zip.c | 151,252,267,452,448,840,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2019-1000019 | libarchive version commit bf9aec176c6748f0ee7a678c5f9f9555b9a757c1 onwards (release v3.0.2 onwards) contains a CWE-125: Out-of-bounds Read vulnerability in 7zip decompression, archive_read_support_format_7zip.c, header_bytes() that can result in a crash (denial of service). This attack appears to be exploitable via the... | https://nvd.nist.gov/vuln/detail/CVE-2019-1000019 |
3,894 | ImageMagick | ecf7c6b288e11e7e7f75387c5e9e93e423b98397 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/ecf7c6b288e11e7e7f75387c5e9e93e423b98397 | ... | 1 | static MagickBooleanType TraceBezier(MVGInfo *mvg_info,
const size_t number_coordinates)
{
double
alpha,
*coefficients,
weight;
PointInfo
end,
point,
*points;
PrimitiveInfo
*primitive_info;
register PrimitiveInfo
*p;
register ssize_t
i,
j;
size_t
control_po... | 121,438,564,734,510,890,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2019-17547 | In ImageMagick before 7.0.8-62, TraceBezier in MagickCore/draw.c has a use-after-free. | https://nvd.nist.gov/vuln/detail/CVE-2019-17547 |
161,146 | ImageMagick | ecf7c6b288e11e7e7f75387c5e9e93e423b98397 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/ecf7c6b288e11e7e7f75387c5e9e93e423b98397 | ... | 0 | static MagickBooleanType TraceBezier(MVGInfo *mvg_info,
const size_t number_coordinates)
{
double
alpha,
*coefficients,
weight;
PointInfo
end,
point,
*points;
PrimitiveInfo
*primitive_info;
register PrimitiveInfo
*p;
register ssize_t
i,
j;
size_t
control_po... | 53,838,315,941,647,200,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2019-17547 | In ImageMagick before 7.0.8-62, TraceBezier in MagickCore/draw.c has a use-after-free. | https://nvd.nist.gov/vuln/detail/CVE-2019-17547 |
3,895 | FFmpeg | 02f909dc24b1f05cfbba75077c7707b905e63cd2 | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/02f909dc24b1f05cfbba75077c7707b905e63cd2 | avcodec/vqavideo: Set video size
Fixes: out of array access
Fixes: 15919/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_VQA_fuzzer-5657368257363968
Found-by: continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> | 1 | static av_cold int vqa_decode_init(AVCodecContext *avctx)
{
VqaContext *s = avctx->priv_data;
int i, j, codebook_index, ret;
s->avctx = avctx;
avctx->pix_fmt = AV_PIX_FMT_PAL8;
/* make sure the extradata made it */
if (s->avctx->extradata_size != VQA_HEADER_SIZE) {
av_log(s->avctx, AV_... | 316,842,430,652,442,060,000,000,000,000,000,000,000 | vqavideo.c | 113,080,214,120,645,070,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2019-17542 | FFmpeg before 4.2 has a heap-based buffer overflow in vqa_decode_chunk because of an out-of-array access in vqa_decode_init in libavcodec/vqavideo.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-17542 |
161,147 | FFmpeg | 02f909dc24b1f05cfbba75077c7707b905e63cd2 | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/02f909dc24b1f05cfbba75077c7707b905e63cd2 | avcodec/vqavideo: Set video size
Fixes: out of array access
Fixes: 15919/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_VQA_fuzzer-5657368257363968
Found-by: continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> | 0 | static av_cold int vqa_decode_init(AVCodecContext *avctx)
{
VqaContext *s = avctx->priv_data;
int i, j, codebook_index, ret;
s->avctx = avctx;
avctx->pix_fmt = AV_PIX_FMT_PAL8;
/* make sure the extradata made it */
if (s->avctx->extradata_size != VQA_HEADER_SIZE) {
av_log(s->avctx, AV_... | 143,994,595,100,513,200,000,000,000,000,000,000,000 | vqavideo.c | 175,073,293,057,007,080,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2019-17542 | FFmpeg before 4.2 has a heap-based buffer overflow in vqa_decode_chunk because of an out-of-array access in vqa_decode_init in libavcodec/vqavideo.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-17542 |
3,904 | linux | 6caabe7f197d3466d238f70915d65301f1716626 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6caabe7f197d3466d238f70915d65301f1716626 | net: hsr: fix memory leak in hsr_dev_finalize()
If hsr_add_port(hsr, hsr_dev, HSR_PT_MASTER) failed to
add port, it directly returns res and forgets to free the node
that allocated in hsr_create_self_node(), and forgets to delete
the node->mac_list linked in hsr->self_node_db.
BUG: memory leak
unreferenced object 0xf... | 1 | int hsr_dev_finalize(struct net_device *hsr_dev, struct net_device *slave[2],
unsigned char multicast_spec, u8 protocol_version)
{
struct hsr_priv *hsr;
struct hsr_port *port;
int res;
hsr = netdev_priv(hsr_dev);
INIT_LIST_HEAD(&hsr->ports);
INIT_LIST_HEAD(&hsr->node_db);
INIT_LIST_HEAD(&hsr->self_node_d... | 119,005,556,713,086,030,000,000,000,000,000,000,000 | hsr_device.c | 256,445,192,119,124,600,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2019-16995 | In the Linux kernel before 5.0.3, a memory leak exits in hsr_dev_finalize() in net/hsr/hsr_device.c if hsr_add_port fails to add a port, which may cause denial of service, aka CID-6caabe7f197d. | https://nvd.nist.gov/vuln/detail/CVE-2019-16995 |
161,156 | linux | 6caabe7f197d3466d238f70915d65301f1716626 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6caabe7f197d3466d238f70915d65301f1716626 | net: hsr: fix memory leak in hsr_dev_finalize()
If hsr_add_port(hsr, hsr_dev, HSR_PT_MASTER) failed to
add port, it directly returns res and forgets to free the node
that allocated in hsr_create_self_node(), and forgets to delete
the node->mac_list linked in hsr->self_node_db.
BUG: memory leak
unreferenced object 0xf... | 0 | int hsr_dev_finalize(struct net_device *hsr_dev, struct net_device *slave[2],
unsigned char multicast_spec, u8 protocol_version)
{
struct hsr_priv *hsr;
struct hsr_port *port;
int res;
hsr = netdev_priv(hsr_dev);
INIT_LIST_HEAD(&hsr->ports);
INIT_LIST_HEAD(&hsr->node_db);
INIT_LIST_HEAD(&hsr->self_node_d... | 161,566,885,197,368,530,000,000,000,000,000,000,000 | hsr_device.c | 7,271,764,243,903,613,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2019-16995 | In the Linux kernel before 5.0.3, a memory leak exits in hsr_dev_finalize() in net/hsr/hsr_device.c if hsr_add_port fails to add a port, which may cause denial of service, aka CID-6caabe7f197d. | https://nvd.nist.gov/vuln/detail/CVE-2019-16995 |
3,905 | linux | 07f12b26e21ab359261bf75cfcb424fdc7daeb6d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/07f12b26e21ab359261bf75cfcb424fdc7daeb6d | net: sit: fix memory leak in sit_init_net()
If register_netdev() is failed to register sitn->fb_tunnel_dev,
it will go to err_reg_dev and forget to free netdev(sitn->fb_tunnel_dev).
BUG: memory leak
unreferenced object 0xffff888378daad00 (size 512):
comm "syz-executor.1", pid 4006, jiffies 4295121142 (age 16.115s)
... | 1 | static int __net_init sit_init_net(struct net *net)
{
struct sit_net *sitn = net_generic(net, sit_net_id);
struct ip_tunnel *t;
int err;
sitn->tunnels[0] = sitn->tunnels_wc;
sitn->tunnels[1] = sitn->tunnels_l;
sitn->tunnels[2] = sitn->tunnels_r;
sitn->tunnels[3] = sitn->tunnels_r_l;
if (!net_has_fallback_tunn... | 172,436,102,843,847,500,000,000,000,000,000,000,000 | sit.c | 116,232,482,481,814,840,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2019-16994 | In the Linux kernel before 5.0, a memory leak exists in sit_init_net() in net/ipv6/sit.c when register_netdev() fails to register sitn->fb_tunnel_dev, which may cause denial of service, aka CID-07f12b26e21a. | https://nvd.nist.gov/vuln/detail/CVE-2019-16994 |
161,157 | linux | 07f12b26e21ab359261bf75cfcb424fdc7daeb6d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/07f12b26e21ab359261bf75cfcb424fdc7daeb6d | net: sit: fix memory leak in sit_init_net()
If register_netdev() is failed to register sitn->fb_tunnel_dev,
it will go to err_reg_dev and forget to free netdev(sitn->fb_tunnel_dev).
BUG: memory leak
unreferenced object 0xffff888378daad00 (size 512):
comm "syz-executor.1", pid 4006, jiffies 4295121142 (age 16.115s)
... | 0 | static int __net_init sit_init_net(struct net *net)
{
struct sit_net *sitn = net_generic(net, sit_net_id);
struct ip_tunnel *t;
int err;
sitn->tunnels[0] = sitn->tunnels_wc;
sitn->tunnels[1] = sitn->tunnels_l;
sitn->tunnels[2] = sitn->tunnels_r;
sitn->tunnels[3] = sitn->tunnels_r_l;
if (!net_has_fallback_tunn... | 102,464,713,481,150,640,000,000,000,000,000,000,000 | sit.c | 171,654,959,636,271,480,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2019-16994 | In the Linux kernel before 5.0, a memory leak exists in sit_init_net() in net/ipv6/sit.c when register_netdev() fails to register sitn->fb_tunnel_dev, which may cause denial of service, aka CID-07f12b26e21a. | https://nvd.nist.gov/vuln/detail/CVE-2019-16994 |
3,912 | linux | 7d0a06586b2686ba80c4a2da5f91cb10ffbea736 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7d0a06586b2686ba80c4a2da5f91cb10ffbea736 | net/rds: Fix info leak in rds6_inc_info_copy()
The rds6_inc_info_copy() function has a couple struct members which
are leaking stack information. The ->tos field should hold actual
information and the ->flags field needs to be zeroed out.
Fixes: 3eb450367d08 ("rds: add type of service(tos) infrastructure")
Fixes: b7... | 1 | void rds6_inc_info_copy(struct rds_incoming *inc,
struct rds_info_iterator *iter,
struct in6_addr *saddr, struct in6_addr *daddr,
int flip)
{
struct rds6_info_message minfo6;
minfo6.seq = be64_to_cpu(inc->i_hdr.h_sequence);
minfo6.len = be32_to_cpu(inc->i_hdr.h_len);
if (flip) {
minfo6.laddr = *d... | 4,978,163,243,173,314,000,000,000,000,000,000,000 | recv.c | 312,731,406,193,587,000,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2019-16714 | In the Linux kernel before 5.2.14, rds6_inc_info_copy in net/rds/recv.c allows attackers to obtain sensitive information from kernel stack memory because tos and flags fields are not initialized. | https://nvd.nist.gov/vuln/detail/CVE-2019-16714 |
161,164 | linux | 7d0a06586b2686ba80c4a2da5f91cb10ffbea736 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7d0a06586b2686ba80c4a2da5f91cb10ffbea736 | net/rds: Fix info leak in rds6_inc_info_copy()
The rds6_inc_info_copy() function has a couple struct members which
are leaking stack information. The ->tos field should hold actual
information and the ->flags field needs to be zeroed out.
Fixes: 3eb450367d08 ("rds: add type of service(tos) infrastructure")
Fixes: b7... | 0 | void rds6_inc_info_copy(struct rds_incoming *inc,
struct rds_info_iterator *iter,
struct in6_addr *saddr, struct in6_addr *daddr,
int flip)
{
struct rds6_info_message minfo6;
minfo6.seq = be64_to_cpu(inc->i_hdr.h_sequence);
minfo6.len = be32_to_cpu(inc->i_hdr.h_len);
minfo6.tos = inc->i_conn->c_tos;
... | 152,443,194,092,886,500,000,000,000,000,000,000,000 | recv.c | 219,022,359,119,506,270,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2019-16714 | In the Linux kernel before 5.2.14, rds6_inc_info_copy in net/rds/recv.c allows attackers to obtain sensitive information from kernel stack memory because tos and flags fields are not initialized. | https://nvd.nist.gov/vuln/detail/CVE-2019-16714 |
3,913 | ngiflib | 37d939a6f511d16d4c95678025c235fe62e6417a | https://github.com/miniupnp/ngiflib | https://github.com/miniupnp/ngiflib/commit/37d939a6f511d16d4c95678025c235fe62e6417a | fix deinterlacing for small pictures
fixes #12 | 1 | static void WritePixel(struct ngiflib_img * i, struct ngiflib_decode_context * context, u8 v) {
struct ngiflib_gif * p = i->parent;
if(v!=i->gce.transparent_color || !i->gce.transparent_flag) {
#ifndef NGIFLIB_INDEXED_ONLY
if(p->mode & NGIFLIB_MODE_INDEXED) {
#endif /* NGIFLIB_INDEXED_ONLY */
*context->frbuff_p... | 48,375,775,932,930,180,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2019-16347 | ngiflib 0.4 has a heap-based buffer overflow in WritePixels() in ngiflib.c when called from DecodeGifImg, because deinterlacing for small pictures is mishandled. | https://nvd.nist.gov/vuln/detail/CVE-2019-16347 |
161,165 | ngiflib | 37d939a6f511d16d4c95678025c235fe62e6417a | https://github.com/miniupnp/ngiflib | https://github.com/miniupnp/ngiflib/commit/37d939a6f511d16d4c95678025c235fe62e6417a | fix deinterlacing for small pictures
fixes #12 | 0 | static void WritePixel(struct ngiflib_img * i, struct ngiflib_decode_context * context, u8 v) {
struct ngiflib_gif * p = i->parent;
if(v!=i->gce.transparent_color || !i->gce.transparent_flag) {
#ifndef NGIFLIB_INDEXED_ONLY
if(p->mode & NGIFLIB_MODE_INDEXED) {
#endif /* NGIFLIB_INDEXED_ONLY */
*context->frbuff_p... | 330,795,260,211,732,530,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2019-16347 | ngiflib 0.4 has a heap-based buffer overflow in WritePixels() in ngiflib.c when called from DecodeGifImg, because deinterlacing for small pictures is mishandled. | https://nvd.nist.gov/vuln/detail/CVE-2019-16347 |
3,914 | ngiflib | 37d939a6f511d16d4c95678025c235fe62e6417a | https://github.com/miniupnp/ngiflib | https://github.com/miniupnp/ngiflib/commit/37d939a6f511d16d4c95678025c235fe62e6417a | fix deinterlacing for small pictures
fixes #12 | 1 | static void WritePixels(struct ngiflib_img * i, struct ngiflib_decode_context * context, const u8 * pixels, u16 n) {
u16 tocopy;
struct ngiflib_gif * p = i->parent;
while(n > 0) {
tocopy = (context->Xtogo < n) ? context->Xtogo : n;
if(!i->gce.transparent_flag) {
#ifndef NGIFLIB_INDEXED_ONLY
if(p->mode & NGI... | 121,149,780,617,115,000,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2019-16347 | ngiflib 0.4 has a heap-based buffer overflow in WritePixels() in ngiflib.c when called from DecodeGifImg, because deinterlacing for small pictures is mishandled. | https://nvd.nist.gov/vuln/detail/CVE-2019-16347 |
161,166 | ngiflib | 37d939a6f511d16d4c95678025c235fe62e6417a | https://github.com/miniupnp/ngiflib | https://github.com/miniupnp/ngiflib/commit/37d939a6f511d16d4c95678025c235fe62e6417a | fix deinterlacing for small pictures
fixes #12 | 0 | static void WritePixels(struct ngiflib_img * i, struct ngiflib_decode_context * context, const u8 * pixels, u16 n) {
u16 tocopy;
struct ngiflib_gif * p = i->parent;
while(n > 0) {
tocopy = (context->Xtogo < n) ? context->Xtogo : n;
if(!i->gce.transparent_flag) {
#ifndef NGIFLIB_INDEXED_ONLY
if(p->mode & NGI... | 253,087,558,076,132,280,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2019-16347 | ngiflib 0.4 has a heap-based buffer overflow in WritePixels() in ngiflib.c when called from DecodeGifImg, because deinterlacing for small pictures is mishandled. | https://nvd.nist.gov/vuln/detail/CVE-2019-16347 |
3,915 | pam_p11 | d150b60e1e14c261b113f55681419ad1dfa8a76c | https://github.com/OpenSC/pam_p11 | https://github.com/OpenSC/pam_p11/commit/d150b60e1e14c261b113f55681419ad1dfa8a76c | Use EVP_PKEY_size() to allocate correct size of signature buffer. (#18)
Do not use fixed buffer size for signature, EVP_SignFinal() requires
buffer for signature at least EVP_PKEY_size(pkey) bytes in size.
Fixes crash when using 4K RSA signatures (https://github.com/OpenSC/pam_p11/issues/16, https://github.com/OpenS... | 1 | static int key_verify(pam_handle_t *pamh, int flags, PKCS11_KEY *authkey)
{
int ok = 0;
unsigned char challenge[30];
unsigned char signature[256];
unsigned int siglen = sizeof signature;
const EVP_MD *md = EVP_sha1();
EVP_MD_CTX *md_ctx = EVP_MD_CTX_new();
EVP_PKEY *privkey = PKCS11_get_private_key(authkey... | 188,572,096,424,461,200,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2019-16058 | An issue was discovered in the pam_p11 component 0.2.0 and 0.3.0 for OpenSC. If a smart card creates a signature with a length longer than 256 bytes, this triggers a buffer overflow. This may be the case for RSA keys with 4096 bits depending on the signature scheme. | https://nvd.nist.gov/vuln/detail/CVE-2019-16058 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.