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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
160,803 | linux | d2f007dbe7e4c9583eea6eb04d60001e85c6f1bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d2f007dbe7e4c9583eea6eb04d60001e85c6f1bd | userns: also map extents in the reverse map to kernel IDs
The current logic first clones the extent array and sorts both copies, then
maps the lower IDs of the forward mapping into the lower namespace, but
doesn't map the lower IDs of the reverse mapping.
This means that code in a nested user namespace with >5 extent... | 0 | static ssize_t map_write(struct file *file, const char __user *buf,
size_t count, loff_t *ppos,
int cap_setid,
struct uid_gid_map *map,
struct uid_gid_map *parent_map)
{
struct seq_file *seq = file->private_data;
struct user_namespace *ns = seq->private;
struct uid_gid_map new_map;
unsigned idx;
st... | 226,881,423,832,249,180,000,000,000,000,000,000,000 | user_namespace.c | 310,601,865,174,752,000,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2018-18955 | In the Linux kernel 4.15.x through 4.19.x before 4.19.2, map_write() in kernel/user_namespace.c allows privilege escalation because it mishandles nested user namespaces with more than 5 UID or GID ranges. A user who has CAP_SYS_ADMIN in an affected user namespace can bypass access controls on resources outside the name... | https://nvd.nist.gov/vuln/detail/CVE-2018-18955 |
3,519 | linux | e4f3aa2e1e67bb48dfbaaf1cad59013d5a5bc276 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e4f3aa2e1e67bb48dfbaaf1cad59013d5a5bc276 | cdrom: fix improper type cast, which can leat to information leak.
There is another cast from unsigned long to int which causes
a bounds check to fail with specially crafted input. The value is
then used as an index in the slot array in cdrom_slot_status().
This issue is similar to CVE-2018-16658 and CVE-2018-10940.
... | 1 | static int cdrom_ioctl_select_disc(struct cdrom_device_info *cdi,
unsigned long arg)
{
cd_dbg(CD_DO_IOCTL, "entering CDROM_SELECT_DISC\n");
if (!CDROM_CAN(CDC_SELECT_DISC))
return -ENOSYS;
if (arg != CDSL_CURRENT && arg != CDSL_NONE) {
if ((int)arg >= cdi->capacity)
return -EINVAL;
}
/*
* ->sel... | 224,235,905,693,533,500,000,000,000,000,000,000,000 | cdrom.c | 303,156,356,238,150,500,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2018-18710 | An issue was discovered in the Linux kernel through 4.19. An information leak in cdrom_ioctl_select_disc in drivers/cdrom/cdrom.c could be used by local attackers to read kernel memory because a cast from unsigned long to int interferes with bounds checking. This is similar to CVE-2018-10940 and CVE-2018-16658. | https://nvd.nist.gov/vuln/detail/CVE-2018-18710 |
160,804 | linux | e4f3aa2e1e67bb48dfbaaf1cad59013d5a5bc276 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e4f3aa2e1e67bb48dfbaaf1cad59013d5a5bc276 | cdrom: fix improper type cast, which can leat to information leak.
There is another cast from unsigned long to int which causes
a bounds check to fail with specially crafted input. The value is
then used as an index in the slot array in cdrom_slot_status().
This issue is similar to CVE-2018-16658 and CVE-2018-10940.
... | 0 | static int cdrom_ioctl_select_disc(struct cdrom_device_info *cdi,
unsigned long arg)
{
cd_dbg(CD_DO_IOCTL, "entering CDROM_SELECT_DISC\n");
if (!CDROM_CAN(CDC_SELECT_DISC))
return -ENOSYS;
if (arg != CDSL_CURRENT && arg != CDSL_NONE) {
if (arg >= cdi->capacity)
return -EINVAL;
}
/*
* ->select_d... | 283,348,960,063,412,630,000,000,000,000,000,000,000 | cdrom.c | 287,339,906,156,499,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2018-18710 | An issue was discovered in the Linux kernel through 4.19. An information leak in cdrom_ioctl_select_disc in drivers/cdrom/cdrom.c could be used by local attackers to read kernel memory because a cast from unsigned long to int interferes with bounds checking. This is similar to CVE-2018-10940 and CVE-2018-16658. | https://nvd.nist.gov/vuln/detail/CVE-2018-18710 |
3,520 | linux | 7b38460dc8e4eafba06c78f8e37099d3b34d473c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7b38460dc8e4eafba06c78f8e37099d3b34d473c | xfs: don't fail when converting shortform attr to long form during ATTR_REPLACE
Kanda Motohiro reported that expanding a tiny xattr into a large xattr
fails on XFS because we remove the tiny xattr from a shortform fork and
then try to re-add it after converting the fork to extents format having
not removed the ATTR_RE... | 1 | xfs_attr_shortform_addname(xfs_da_args_t *args)
{
int newsize, forkoff, retval;
trace_xfs_attr_sf_addname(args);
retval = xfs_attr_shortform_lookup(args);
if ((args->flags & ATTR_REPLACE) && (retval == -ENOATTR)) {
return retval;
} else if (retval == -EEXIST) {
if (args->flags & ATTR_CREATE)
return retv... | 35,925,866,201,613,620,000,000,000,000,000,000,000 | xfs_attr.c | 51,495,444,875,997,870,000,000,000,000,000,000,000 | [
"CWE-754"
] | CVE-2018-18690 | In the Linux kernel before 4.17, a local attacker able to set attributes on an xfs filesystem could make this filesystem non-operational until the next mount by triggering an unchecked error condition during an xfs attribute change, because xfs_attr_shortform_addname in fs/xfs/libxfs/xfs_attr.c mishandles ATTR_REPLACE ... | https://nvd.nist.gov/vuln/detail/CVE-2018-18690 |
160,805 | linux | 7b38460dc8e4eafba06c78f8e37099d3b34d473c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7b38460dc8e4eafba06c78f8e37099d3b34d473c | xfs: don't fail when converting shortform attr to long form during ATTR_REPLACE
Kanda Motohiro reported that expanding a tiny xattr into a large xattr
fails on XFS because we remove the tiny xattr from a shortform fork and
then try to re-add it after converting the fork to extents format having
not removed the ATTR_RE... | 0 | xfs_attr_shortform_addname(xfs_da_args_t *args)
{
int newsize, forkoff, retval;
trace_xfs_attr_sf_addname(args);
retval = xfs_attr_shortform_lookup(args);
if ((args->flags & ATTR_REPLACE) && (retval == -ENOATTR)) {
return retval;
} else if (retval == -EEXIST) {
if (args->flags & ATTR_CREATE)
return retv... | 105,830,264,928,146,840,000,000,000,000,000,000,000 | xfs_attr.c | 22,841,724,263,228,720,000,000,000,000,000,000,000 | [
"CWE-754"
] | CVE-2018-18690 | In the Linux kernel before 4.17, a local attacker able to set attributes on an xfs filesystem could make this filesystem non-operational until the next mount by triggering an unchecked error condition during an xfs attribute change, because xfs_attr_shortform_addname in fs/xfs/libxfs/xfs_attr.c mishandles ATTR_REPLACE ... | https://nvd.nist.gov/vuln/detail/CVE-2018-18690 |
3,523 | libmspack | 8759da8db6ec9e866cb8eb143313f397f925bb4f | https://github.com/kyz/libmspack | https://github.com/kyz/libmspack/commit/8759da8db6ec9e866cb8eb143313f397f925bb4f | Avoid returning CHM file entries that are "blank" because they have embedded null bytes | 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, length;
int num_e... | 286,877,828,864,113,330,000,000,000,000,000,000,000 | chmd.c | 86,023,333,538,823,280,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2018-18585 | chmd_read_headers in mspack/chmd.c in libmspack before 0.8alpha accepts a filename that has '\0' as its first or second character (such as the "/\0" name). | https://nvd.nist.gov/vuln/detail/CVE-2018-18585 |
160,808 | libmspack | 8759da8db6ec9e866cb8eb143313f397f925bb4f | https://github.com/kyz/libmspack | https://github.com/kyz/libmspack/commit/8759da8db6ec9e866cb8eb143313f397f925bb4f | Avoid returning CHM file entries that are "blank" because they have embedded null bytes | 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, length;
int num_e... | 112,914,575,198,027,150,000,000,000,000,000,000,000 | chmd.c | 147,705,968,754,428,370,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2018-18585 | chmd_read_headers in mspack/chmd.c in libmspack before 0.8alpha accepts a filename that has '\0' as its first or second character (such as the "/\0" name). | https://nvd.nist.gov/vuln/detail/CVE-2018-18585 |
3,532 | gnulib | 278b4175c9d7dd47c1a3071554aac02add3b3c35 | https://github.com/coreutils/gnulib | https://github.com/coreutils/gnulib/commit/278b4175c9d7dd47c1a3071554aac02add3b3c35 | vasnprintf: Fix heap memory overrun bug.
Reported by Ben Pfaff <blp@cs.stanford.edu> in
<https://lists.gnu.org/archive/html/bug-gnulib/2018-09/msg00107.html>.
* lib/vasnprintf.c (convert_to_decimal): Allocate one more byte of
memory.
* tests/test-vasnprintf.c (test_function): Add another test. | 1 | convert_to_decimal (mpn_t a, size_t extra_zeroes)
{
mp_limb_t *a_ptr = a.limbs;
size_t a_len = a.nlimbs;
/* 0.03345 is slightly larger than log(2)/(9*log(10)). */
size_t c_len = 9 * ((size_t)(a_len * (GMP_LIMB_BITS * 0.03345f)) + 1);
char *c_ptr = (char *) malloc (xsum (c_len, extra_zeroes));
if (c_ptr... | 267,101,733,010,542,500,000,000,000,000,000,000,000 | vasnprintf.c | 310,190,725,670,108,440,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2018-17942 | The convert_to_decimal function in vasnprintf.c in Gnulib before 2018-09-23 has a heap-based buffer overflow because memory is not allocated for a trailing '\0' character during %f processing. | https://nvd.nist.gov/vuln/detail/CVE-2018-17942 |
160,815 | gnulib | 278b4175c9d7dd47c1a3071554aac02add3b3c35 | https://github.com/coreutils/gnulib | https://github.com/coreutils/gnulib/commit/278b4175c9d7dd47c1a3071554aac02add3b3c35 | vasnprintf: Fix heap memory overrun bug.
Reported by Ben Pfaff <blp@cs.stanford.edu> in
<https://lists.gnu.org/archive/html/bug-gnulib/2018-09/msg00107.html>.
* lib/vasnprintf.c (convert_to_decimal): Allocate one more byte of
memory.
* tests/test-vasnprintf.c (test_function): Add another test. | 0 | convert_to_decimal (mpn_t a, size_t extra_zeroes)
{
mp_limb_t *a_ptr = a.limbs;
size_t a_len = a.nlimbs;
/* 0.03345 is slightly larger than log(2)/(9*log(10)). */
size_t c_len = 9 * ((size_t)(a_len * (GMP_LIMB_BITS * 0.03345f)) + 1);
/* We need extra_zeroes bytes for zeroes, followed by c_len bytes for th... | 29,296,428,698,027,960,000,000,000,000,000,000,000 | vasnprintf.c | 144,629,186,487,586,950,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2018-17942 | The convert_to_decimal function in vasnprintf.c in Gnulib before 2018-09-23 has a heap-based buffer overflow because memory is not allocated for a trailing '\0' character during %f processing. | https://nvd.nist.gov/vuln/detail/CVE-2018-17942 |
3,537 | texlive-source | 6ed0077520e2b0da1fd060c7f88db7b2e6068e4c | https://github.com/TeX-Live/texlive-source | https://github.com/TeX-Live/texlive-source/commit/6ed0077520e2b0da1fd060c7f88db7b2e6068e4c | writet1 protection against buffer overflow
git-svn-id: svn://tug.org/texlive/trunk/Build/source@48697 c570f23f-e606-0410-a88d-b1316a301751 | 1 | static void t1_check_unusual_charstring(void)
{
char *p = strstr(t1_line_array, charstringname) + strlen(charstringname);
int i;
/* if no number follows "/CharStrings", let's read the next line */
if (sscanf(p, "%i", &i) != 1) {
/* pdftex_warn("no number found after `%s', I assume it's on the ne... | 111,289,472,377,531,110,000,000,000,000,000,000,000 | writet1.c | 296,322,236,862,841,300,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2018-17407 | An issue was discovered in t1_check_unusual_charstring functions in writet1.c files in TeX Live before 2018-09-21. A buffer overflow in the handling of Type 1 fonts allows arbitrary code execution when a malicious font is loaded by one of the vulnerable tools: pdflatex, pdftex, dvips, or luatex. | https://nvd.nist.gov/vuln/detail/CVE-2018-17407 |
160,819 | texlive-source | 6ed0077520e2b0da1fd060c7f88db7b2e6068e4c | https://github.com/TeX-Live/texlive-source | https://github.com/TeX-Live/texlive-source/commit/6ed0077520e2b0da1fd060c7f88db7b2e6068e4c | writet1 protection against buffer overflow
git-svn-id: svn://tug.org/texlive/trunk/Build/source@48697 c570f23f-e606-0410-a88d-b1316a301751 | 0 | static void t1_check_unusual_charstring(void)
{
char *p = strstr(t1_line_array, charstringname) + strlen(charstringname);
int i;
/* if no number follows "/CharStrings", let's read the next line */
if (sscanf(p, "%i", &i) != 1) {
/* pdftex_warn("no number found after `%s', I assume it's on the ne... | 28,914,771,234,379,316,000,000,000,000,000,000,000 | writet1.c | 207,961,708,727,176,200,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2018-17407 | An issue was discovered in t1_check_unusual_charstring functions in writet1.c files in TeX Live before 2018-09-21. A buffer overflow in the handling of Type 1 fonts allows arbitrary code execution when a malicious font is loaded by one of the vulnerable tools: pdflatex, pdftex, dvips, or luatex. | https://nvd.nist.gov/vuln/detail/CVE-2018-17407 |
3,538 | texlive-source | 6ed0077520e2b0da1fd060c7f88db7b2e6068e4c | https://github.com/TeX-Live/texlive-source | https://github.com/TeX-Live/texlive-source/commit/6ed0077520e2b0da1fd060c7f88db7b2e6068e4c | writet1 protection against buffer overflow
git-svn-id: svn://tug.org/texlive/trunk/Build/source@48697 c570f23f-e606-0410-a88d-b1316a301751 | 1 | static void t1_check_unusual_charstring(void)
{
char *p = strstr(t1_line_array, charstringname) + strlen(charstringname);
int i;
/*tex If no number follows |/CharStrings|, let's read the next line. */
if (sscanf(p, "%i", &i) != 1) {
strcpy(t1_buf_array, t1_line_array);
t1_getline();
... | 186,302,796,745,694,270,000,000,000,000,000,000,000 | writet1.c | 34,977,694,572,360,150,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2018-17407 | An issue was discovered in t1_check_unusual_charstring functions in writet1.c files in TeX Live before 2018-09-21. A buffer overflow in the handling of Type 1 fonts allows arbitrary code execution when a malicious font is loaded by one of the vulnerable tools: pdflatex, pdftex, dvips, or luatex. | https://nvd.nist.gov/vuln/detail/CVE-2018-17407 |
160,820 | texlive-source | 6ed0077520e2b0da1fd060c7f88db7b2e6068e4c | https://github.com/TeX-Live/texlive-source | https://github.com/TeX-Live/texlive-source/commit/6ed0077520e2b0da1fd060c7f88db7b2e6068e4c | writet1 protection against buffer overflow
git-svn-id: svn://tug.org/texlive/trunk/Build/source@48697 c570f23f-e606-0410-a88d-b1316a301751 | 0 | static void t1_check_unusual_charstring(void)
{
char *p = strstr(t1_line_array, charstringname) + strlen(charstringname);
int i;
/*tex If no number follows |/CharStrings|, let's read the next line. */
if (sscanf(p, "%i", &i) != 1) {
strcpy(t1_buf_array, t1_line_array);
t1_getline();
... | 70,685,846,074,402,140,000,000,000,000,000,000,000 | writet1.c | 176,966,978,252,540,900,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2018-17407 | An issue was discovered in t1_check_unusual_charstring functions in writet1.c files in TeX Live before 2018-09-21. A buffer overflow in the handling of Type 1 fonts allows arbitrary code execution when a malicious font is loaded by one of the vulnerable tools: pdflatex, pdftex, dvips, or luatex. | https://nvd.nist.gov/vuln/detail/CVE-2018-17407 |
3,539 | ovs | 9237a63c47bd314b807cda0bd2216264e82edbe8 | https://github.com/openvswitch/ovs | https://github.com/openvswitch/ovs/commit/9237a63c47bd314b807cda0bd2216264e82edbe8 | ofp-actions: Avoid buffer overread in BUNDLE action decoding.
Reported-at: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=9052
Signed-off-by: Ben Pfaff <blp@ovn.org>
Acked-by: Justin Pettit <jpettit@ovn.org> | 1 | decode_bundle(bool load, const struct nx_action_bundle *nab,
const struct vl_mff_map *vl_mff_map, uint64_t *tlv_bitmap,
struct ofpbuf *ofpacts)
{
static struct vlog_rate_limit rl = VLOG_RATE_LIMIT_INIT(1, 5);
struct ofpact_bundle *bundle;
uint32_t slave_type;
size_t slaves_si... | 246,918,809,104,071,950,000,000,000,000,000,000,000 | ofp-actions.c | 262,989,974,079,934,800,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2018-17206 | An issue was discovered in Open vSwitch (OvS) 2.7.x through 2.7.6. The decode_bundle function inside lib/ofp-actions.c is affected by a buffer over-read issue during BUNDLE action decoding. | https://nvd.nist.gov/vuln/detail/CVE-2018-17206 |
160,821 | ovs | 9237a63c47bd314b807cda0bd2216264e82edbe8 | https://github.com/openvswitch/ovs | https://github.com/openvswitch/ovs/commit/9237a63c47bd314b807cda0bd2216264e82edbe8 | ofp-actions: Avoid buffer overread in BUNDLE action decoding.
Reported-at: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=9052
Signed-off-by: Ben Pfaff <blp@ovn.org>
Acked-by: Justin Pettit <jpettit@ovn.org> | 0 | decode_bundle(bool load, const struct nx_action_bundle *nab,
const struct vl_mff_map *vl_mff_map, uint64_t *tlv_bitmap,
struct ofpbuf *ofpacts)
{
static struct vlog_rate_limit rl = VLOG_RATE_LIMIT_INIT(1, 5);
struct ofpact_bundle *bundle;
uint32_t slave_type;
size_t slaves_si... | 195,807,527,044,650,800,000,000,000,000,000,000,000 | ofp-actions.c | 152,341,426,811,875,400,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2018-17206 | An issue was discovered in Open vSwitch (OvS) 2.7.x through 2.7.6. The decode_bundle function inside lib/ofp-actions.c is affected by a buffer over-read issue during BUNDLE action decoding. | https://nvd.nist.gov/vuln/detail/CVE-2018-17206 |
3,540 | ovs | 0befd1f3745055c32940f5faf9559be6a14395e6 | https://github.com/openvswitch/ovs | https://github.com/openvswitch/ovs/commit/0befd1f3745055c32940f5faf9559be6a14395e6 | ofproto: Fix OVS crash when reverting old flows in bundle commit
During bundle commit flows which are added in bundle are applied
to ofproto in-order. In case if a flow cannot be added (e.g. flow
action is go-to group id which does not exist), OVS tries to
revert back all previous flows which were successfully applied... | 1 | OVS_REQUIRES(ofproto_mutex)
{
const struct rule_actions *actions = rule_get_actions(rule);
/* A rule may not be reinserted. */
ovs_assert(rule->state == RULE_INITIALIZED);
if (rule->hard_timeout || rule->idle_timeout) {
ovs_list_insert(&ofproto->expirable, &rule->expirable);
}
... | 230,678,121,195,317,530,000,000,000,000,000,000,000 | ofproto.c | 288,950,316,551,410,930,000,000,000,000,000,000,000 | [
"CWE-617"
] | CVE-2018-17205 | An issue was discovered in Open vSwitch (OvS) 2.7.x through 2.7.6, affecting ofproto_rule_insert__ in ofproto/ofproto.c. During bundle commit, flows that are added in a bundle are applied to ofproto in order. If a flow cannot be added (e.g., the flow action is a go-to for a group id that does not exist), OvS tries to r... | https://nvd.nist.gov/vuln/detail/CVE-2018-17205 |
160,822 | ovs | 0befd1f3745055c32940f5faf9559be6a14395e6 | https://github.com/openvswitch/ovs | https://github.com/openvswitch/ovs/commit/0befd1f3745055c32940f5faf9559be6a14395e6 | ofproto: Fix OVS crash when reverting old flows in bundle commit
During bundle commit flows which are added in bundle are applied
to ofproto in-order. In case if a flow cannot be added (e.g. flow
action is go-to group id which does not exist), OVS tries to
revert back all previous flows which were successfully applied... | 0 | OVS_REQUIRES(ofproto_mutex)
{
const struct rule_actions *actions = rule_get_actions(rule);
/* A rule may not be reinserted. */
ovs_assert(rule->state != RULE_INSERTED);
if (rule->hard_timeout || rule->idle_timeout) {
ovs_list_insert(&ofproto->expirable, &rule->expirable);
}
c... | 184,955,909,361,138,470,000,000,000,000,000,000,000 | ofproto.c | 237,752,752,948,949,440,000,000,000,000,000,000,000 | [
"CWE-617"
] | CVE-2018-17205 | An issue was discovered in Open vSwitch (OvS) 2.7.x through 2.7.6, affecting ofproto_rule_insert__ in ofproto/ofproto.c. During bundle commit, flows that are added in a bundle are applied to ofproto in order. If a flow cannot be added (e.g., the flow action is a go-to for a group id that does not exist), OvS tries to r... | https://nvd.nist.gov/vuln/detail/CVE-2018-17205 |
3,541 | ovs | 4af6da3b275b764b1afe194df6499b33d2bf4cde | https://github.com/openvswitch/ovs | https://github.com/openvswitch/ovs/commit/4af6da3b275b764b1afe194df6499b33d2bf4cde | ofp-group: Don't assert-fail decoding bad OF1.5 group mod type or command.
When decoding a group mod, the current code validates the group type and
command after the whole group mod has been decoded. The OF1.5 decoder,
however, tries to use the type and command earlier, when it might still be
invalid. This caused an... | 1 | parse_group_prop_ntr_selection_method(struct ofpbuf *payload,
enum ofp11_group_type group_type,
enum ofp15_group_mod_command group_cmd,
struct ofputil_group_props *gp)
{
struct ntr_group_prop_selection_... | 160,132,015,962,314,390,000,000,000,000,000,000,000 | ofp-util.c | 208,088,101,152,268,600,000,000,000,000,000,000,000 | [
"CWE-617"
] | CVE-2018-17204 | An issue was discovered in Open vSwitch (OvS) 2.7.x through 2.7.6, affecting parse_group_prop_ntr_selection_method in lib/ofp-util.c. When decoding a group mod, it validates the group type and command after the whole group mod has been decoded. The OF1.5 decoder, however, tries to use the type and command earlier, when... | https://nvd.nist.gov/vuln/detail/CVE-2018-17204 |
160,823 | ovs | 4af6da3b275b764b1afe194df6499b33d2bf4cde | https://github.com/openvswitch/ovs | https://github.com/openvswitch/ovs/commit/4af6da3b275b764b1afe194df6499b33d2bf4cde | ofp-group: Don't assert-fail decoding bad OF1.5 group mod type or command.
When decoding a group mod, the current code validates the group type and
command after the whole group mod has been decoded. The OF1.5 decoder,
however, tries to use the type and command earlier, when it might still be
invalid. This caused an... | 0 | parse_group_prop_ntr_selection_method(struct ofpbuf *payload,
enum ofp11_group_type group_type,
enum ofp15_group_mod_command group_cmd,
struct ofputil_group_props *gp)
{
struct ntr_group_prop_selection_... | 182,836,166,393,477,830,000,000,000,000,000,000,000 | ofp-util.c | 315,162,344,303,096,600,000,000,000,000,000,000,000 | [
"CWE-617"
] | CVE-2018-17204 | An issue was discovered in Open vSwitch (OvS) 2.7.x through 2.7.6, affecting parse_group_prop_ntr_selection_method in lib/ofp-util.c. When decoding a group mod, it validates the group type and command after the whole group mod has been decoded. The OF1.5 decoder, however, tries to use the type and command earlier, when... | https://nvd.nist.gov/vuln/detail/CVE-2018-17204 |
3,544 | php-src | 23b057742e3cf199612fa8050ae86cae675e214e | https://github.com/php/php-src | https://github.com/php/php-src/commit/23b057742e3cf199612fa8050ae86cae675e214e | Fix for bug #76582
The brigade seems to end up in a messed up state if something fails
in shutdown, so we clean it up. | 1 | static int php_handler(request_rec *r)
{
php_struct * volatile ctx;
void *conf;
apr_bucket_brigade * volatile brigade;
apr_bucket *bucket;
apr_status_t rv;
request_rec * volatile parent_req = NULL;
TSRMLS_FETCH();
#define PHPAP_INI_OFF php_apache_ini_dtor(r, parent_req TSRMLS_CC);
conf = ap_get_module_config(... | 182,394,297,957,195,980,000,000,000,000,000,000,000 | sapi_apache2.c | 187,699,522,903,415,300,000,000,000,000,000,000,000 | [
"CWE-79"
] | CVE-2018-17082 | The Apache2 component in PHP before 5.6.38, 7.0.x before 7.0.32, 7.1.x before 7.1.22, and 7.2.x before 7.2.10 allows XSS via the body of a "Transfer-Encoding: chunked" request, because the bucket brigade is mishandled in the php_handler function in sapi/apache2handler/sapi_apache2.c. | https://nvd.nist.gov/vuln/detail/CVE-2018-17082 |
160,826 | php-src | 23b057742e3cf199612fa8050ae86cae675e214e | https://github.com/php/php-src | https://github.com/php/php-src/commit/23b057742e3cf199612fa8050ae86cae675e214e | Fix for bug #76582
The brigade seems to end up in a messed up state if something fails
in shutdown, so we clean it up. | 0 | static int php_handler(request_rec *r)
{
php_struct * volatile ctx;
void *conf;
apr_bucket_brigade * volatile brigade;
apr_bucket *bucket;
apr_status_t rv;
request_rec * volatile parent_req = NULL;
TSRMLS_FETCH();
#define PHPAP_INI_OFF php_apache_ini_dtor(r, parent_req TSRMLS_CC);
conf = ap_get_module_config(... | 286,403,665,457,396,430,000,000,000,000,000,000,000 | None | null | [
"CWE-79"
] | CVE-2018-17082 | The Apache2 component in PHP before 5.6.38, 7.0.x before 7.0.32, 7.1.x before 7.1.22, and 7.2.x before 7.2.10 allows XSS via the body of a "Transfer-Encoding: chunked" request, because the bucket brigade is mishandled in the php_handler function in sapi/apache2handler/sapi_apache2.c. | https://nvd.nist.gov/vuln/detail/CVE-2018-17082 |
3,545 | curl | d530e92f59ae9bb2d47066c3c460b25d2ffeb211 | https://github.com/curl/curl | https://github.com/curl/curl/commit/d530e92f59ae9bb2d47066c3c460b25d2ffeb211 | voutf: fix bad arethmetic when outputting warnings to stderr
CVE-2018-16842
Reported-by: Brian Carpenter
Bug: https://curl.haxx.se/docs/CVE-2018-16842.html | 1 | static void voutf(struct GlobalConfig *config,
const char *prefix,
const char *fmt,
va_list ap)
{
size_t width = (79 - strlen(prefix));
if(!config->mute) {
size_t len;
char *ptr;
char *print_buffer;
print_buffer = curlx_mvaprintf(fmt, ap);
i... | 243,200,030,011,946,100,000,000,000,000,000,000,000 | tool_msgs.c | 68,505,042,536,067,880,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2018-16842 | Curl versions 7.14.1 through 7.61.1 are vulnerable to a heap-based buffer over-read in the tool_msgs.c:voutf() function that may result in information exposure and denial of service. | https://nvd.nist.gov/vuln/detail/CVE-2018-16842 |
160,827 | curl | d530e92f59ae9bb2d47066c3c460b25d2ffeb211 | https://github.com/curl/curl | https://github.com/curl/curl/commit/d530e92f59ae9bb2d47066c3c460b25d2ffeb211 | voutf: fix bad arethmetic when outputting warnings to stderr
CVE-2018-16842
Reported-by: Brian Carpenter
Bug: https://curl.haxx.se/docs/CVE-2018-16842.html | 0 | static void voutf(struct GlobalConfig *config,
const char *prefix,
const char *fmt,
va_list ap)
{
size_t width = (79 - strlen(prefix));
if(!config->mute) {
size_t len;
char *ptr;
char *print_buffer;
print_buffer = curlx_mvaprintf(fmt, ap);
i... | 208,474,190,621,146,730,000,000,000,000,000,000,000 | tool_msgs.c | 152,586,217,686,603,770,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2018-16842 | Curl versions 7.14.1 through 7.61.1 are vulnerable to a heap-based buffer over-read in the tool_msgs.c:voutf() function that may result in information exposure and denial of service. | https://nvd.nist.gov/vuln/detail/CVE-2018-16842 |
3,546 | curl | 81d135d67155c5295b1033679c606165d4e28f3f | https://github.com/curl/curl | https://github.com/curl/curl/commit/81d135d67155c5295b1033679c606165d4e28f3f | Curl_close: clear data->multi_easy on free to avoid use-after-free
Regression from b46cfbc068 (7.59.0)
CVE-2018-16840
Reported-by: Brian Carpenter (Geeknik Labs)
Bug: https://curl.haxx.se/docs/CVE-2018-16840.html | 1 | CURLcode Curl_close(struct Curl_easy *data)
{
struct Curl_multi *m;
if(!data)
return CURLE_OK;
Curl_expire_clear(data); /* shut off timers */
m = data->multi;
if(m)
/* This handle is still part of a multi handle, take care of this first
and detach this handle from there. */
curl_multi_... | 146,738,609,343,169,300,000,000,000,000,000,000,000 | url.c | 21,183,698,655,484,456,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2018-16840 | A heap use-after-free flaw was found in curl versions from 7.59.0 through 7.61.1 in the code related to closing an easy handle. When closing and cleaning up an 'easy' handle in the `Curl_close()` function, the library code first frees a struct (without nulling the pointer) and might then subsequently erroneously write ... | https://nvd.nist.gov/vuln/detail/CVE-2018-16840 |
160,828 | curl | 81d135d67155c5295b1033679c606165d4e28f3f | https://github.com/curl/curl | https://github.com/curl/curl/commit/81d135d67155c5295b1033679c606165d4e28f3f | Curl_close: clear data->multi_easy on free to avoid use-after-free
Regression from b46cfbc068 (7.59.0)
CVE-2018-16840
Reported-by: Brian Carpenter (Geeknik Labs)
Bug: https://curl.haxx.se/docs/CVE-2018-16840.html | 0 | CURLcode Curl_close(struct Curl_easy *data)
{
struct Curl_multi *m;
if(!data)
return CURLE_OK;
Curl_expire_clear(data); /* shut off timers */
m = data->multi;
if(m)
/* This handle is still part of a multi handle, take care of this first
and detach this handle from there. */
curl_multi_... | 172,911,595,972,806,660,000,000,000,000,000,000,000 | url.c | 247,136,759,109,366,500,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2018-16840 | A heap use-after-free flaw was found in curl versions from 7.59.0 through 7.61.1 in the code related to closing an easy handle. When closing and cleaning up an 'easy' handle in the `Curl_close()` function, the library code first frees a struct (without nulling the pointer) and might then subsequently erroneously write ... | https://nvd.nist.gov/vuln/detail/CVE-2018-16840 |
3,547 | curl | f3a24d7916b9173c69a3e0ee790102993833d6c5 | https://github.com/curl/curl | https://github.com/curl/curl/commit/f3a24d7916b9173c69a3e0ee790102993833d6c5 | Curl_auth_create_plain_message: fix too-large-input-check
CVE-2018-16839
Reported-by: Harry Sintonen
Bug: https://curl.haxx.se/docs/CVE-2018-16839.html | 1 | CURLcode Curl_auth_create_plain_message(struct Curl_easy *data,
const char *userp,
const char *passwdp,
char **outptr, size_t *outlen)
{
CURLcode result;
char *plainauth;
size_t ulen;
size_t p... | 151,646,974,909,090,780,000,000,000,000,000,000,000 | cleartext.c | 284,710,761,622,311,070,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2018-16839 | Curl versions 7.33.0 through 7.61.1 are vulnerable to a buffer overrun in the SASL authentication code that may lead to denial of service. | https://nvd.nist.gov/vuln/detail/CVE-2018-16839 |
160,829 | curl | f3a24d7916b9173c69a3e0ee790102993833d6c5 | https://github.com/curl/curl | https://github.com/curl/curl/commit/f3a24d7916b9173c69a3e0ee790102993833d6c5 | Curl_auth_create_plain_message: fix too-large-input-check
CVE-2018-16839
Reported-by: Harry Sintonen
Bug: https://curl.haxx.se/docs/CVE-2018-16839.html | 0 | CURLcode Curl_auth_create_plain_message(struct Curl_easy *data,
const char *userp,
const char *passwdp,
char **outptr, size_t *outlen)
{
CURLcode result;
char *plainauth;
size_t ulen;
size_t p... | 4,353,853,054,091,528,400,000,000,000,000,000,000 | cleartext.c | 82,198,062,066,106,020,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2018-16839 | Curl versions 7.33.0 through 7.61.1 are vulnerable to a buffer overrun in the SASL authentication code that may lead to denial of service. | https://nvd.nist.gov/vuln/detail/CVE-2018-16839 |
3,548 | mongo-c-driver | 0d9a4d98bfdf4acd2c0138d4aaeb4e2e0934bd84 | https://github.com/mongodb/mongo-c-driver | https://github.com/mongodb/mongo-c-driver/commit/0d9a4d98bfdf4acd2c0138d4aaeb4e2e0934bd84 | Fix for CVE-2018-16790 -- Verify bounds before binary length read.
As reported here: https://jira.mongodb.org/browse/CDRIVER-2819,
a heap overread occurs due a failure to correctly verify data
bounds.
In the original check, len - o returns the data left including the
sizeof(l) we just read. Instead, the comparison sh... | 1 | _bson_iter_next_internal (bson_iter_t *iter, /* INOUT */
uint32_t next_keylen, /* IN */
const char **key, /* OUT */
uint32_t *bson_type, /* OUT */
bool *unsupported) /* OUT */
{
const uint8_t *data;
... | 247,944,174,862,272,700,000,000,000,000,000,000,000 | bson-iter.c | 140,668,676,497,403,740,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2018-16790 | _bson_iter_next_internal in bson-iter.c in libbson 1.12.0, as used in MongoDB mongo-c-driver and other products, has a heap-based buffer over-read via a crafted bson buffer. | https://nvd.nist.gov/vuln/detail/CVE-2018-16790 |
160,830 | mongo-c-driver | 0d9a4d98bfdf4acd2c0138d4aaeb4e2e0934bd84 | https://github.com/mongodb/mongo-c-driver | https://github.com/mongodb/mongo-c-driver/commit/0d9a4d98bfdf4acd2c0138d4aaeb4e2e0934bd84 | Fix for CVE-2018-16790 -- Verify bounds before binary length read.
As reported here: https://jira.mongodb.org/browse/CDRIVER-2819,
a heap overread occurs due a failure to correctly verify data
bounds.
In the original check, len - o returns the data left including the
sizeof(l) we just read. Instead, the comparison sh... | 0 | _bson_iter_next_internal (bson_iter_t *iter, /* INOUT */
uint32_t next_keylen, /* IN */
const char **key, /* OUT */
uint32_t *bson_type, /* OUT */
bool *unsupported) /* OUT */
{
const uint8_t *data;
... | 167,535,859,404,624,770,000,000,000,000,000,000,000 | bson-iter.c | 108,063,000,104,905,270,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2018-16790 | _bson_iter_next_internal in bson-iter.c in libbson 1.12.0, as used in MongoDB mongo-c-driver and other products, has a heap-based buffer over-read via a crafted bson buffer. | https://nvd.nist.gov/vuln/detail/CVE-2018-16790 |
3,550 | ImageMagick6 | 1007b98f8795ad4bea6bc5f68a32d83e982fdae4 | https://github.com/ImageMagick/ImageMagick6 | https://github.com/ImageMagick/ImageMagick6/commit/1007b98f8795ad4bea6bc5f68a32d83e982fdae4 | https://github.com/ImageMagick/ImageMagick/issues/1119 | 1 | static Image *ReadOneJNGImage(MngInfo *mng_info,
const ImageInfo *image_info, ExceptionInfo *exception)
{
Image
*alpha_image,
*color_image,
*image,
*jng_image;
ImageInfo
*alpha_image_info,
*color_image_info;
MagickBooleanType
logging;
int
unique_filenames;
ssize_t
y... | 54,473,371,976,532,860,000,000,000,000,000,000,000 | png.c | 229,500,338,170,202,940,000,000,000,000,000,000,000 | [
"CWE-617"
] | CVE-2018-16749 | In ImageMagick 7.0.7-29 and earlier, a missing NULL check in ReadOneJNGImage in coders/png.c allows an attacker to cause a denial of service (WriteBlob assertion failure and application exit) via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2018-16749 |
160,832 | ImageMagick6 | 1007b98f8795ad4bea6bc5f68a32d83e982fdae4 | https://github.com/ImageMagick/ImageMagick6 | https://github.com/ImageMagick/ImageMagick6/commit/1007b98f8795ad4bea6bc5f68a32d83e982fdae4 | https://github.com/ImageMagick/ImageMagick/issues/1119 | 0 | static Image *ReadOneJNGImage(MngInfo *mng_info,
const ImageInfo *image_info, ExceptionInfo *exception)
{
Image
*alpha_image,
*color_image,
*image,
*jng_image;
ImageInfo
*alpha_image_info,
*color_image_info;
MagickBooleanType
logging;
int
unique_filenames;
ssize_t
y... | 272,132,981,447,451,400,000,000,000,000,000,000,000 | png.c | 284,866,657,602,277,840,000,000,000,000,000,000,000 | [
"CWE-617"
] | CVE-2018-16749 | In ImageMagick 7.0.7-29 and earlier, a missing NULL check in ReadOneJNGImage in coders/png.c allows an attacker to cause a denial of service (WriteBlob assertion failure and application exit) via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2018-16749 |
3,552 | ImageMagick | ecb31dbad39ccdc65868d5d2a37f0f0521250832 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/ecb31dbad39ccdc65868d5d2a37f0f0521250832 | https://github.com/ImageMagick/ImageMagick/issues/1268 | 1 | static Image *ReadBMPImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
BMPInfo
bmp_info;
Image
*image;
MagickBooleanType
status;
MagickOffsetType
offset,
start_position;
MemoryInfo
*pixel_info;
Quantum
index;
register Quantum
*q;
register ssize_t
i,... | 231,882,249,216,637,050,000,000,000,000,000,000,000 | bmp.c | 74,586,236,604,626,345,000,000,000,000,000,000,000 | [
"CWE-770"
] | CVE-2018-16645 | There is an excessive memory allocation issue in the functions ReadBMPImage of coders/bmp.c and ReadDIBImage of coders/dib.c in ImageMagick 7.0.8-11, which allows remote attackers to cause a denial of service via a crafted image file. | https://nvd.nist.gov/vuln/detail/CVE-2018-16645 |
160,833 | ImageMagick | ecb31dbad39ccdc65868d5d2a37f0f0521250832 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/ecb31dbad39ccdc65868d5d2a37f0f0521250832 | https://github.com/ImageMagick/ImageMagick/issues/1268 | 0 | static Image *ReadBMPImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
BMPInfo
bmp_info;
Image
*image;
MagickBooleanType
status;
MagickOffsetType
offset,
start_position;
MemoryInfo
*pixel_info;
Quantum
index;
register Quantum
*q;
register ssize_t
i,... | 70,073,407,539,865,480,000,000,000,000,000,000,000 | bmp.c | 303,093,137,720,368,650,000,000,000,000,000,000,000 | [
"CWE-770"
] | CVE-2018-16645 | There is an excessive memory allocation issue in the functions ReadBMPImage of coders/bmp.c and ReadDIBImage of coders/dib.c in ImageMagick 7.0.8-11, which allows remote attackers to cause a denial of service via a crafted image file. | https://nvd.nist.gov/vuln/detail/CVE-2018-16645 |
3,553 | ImageMagick | afa878a689870c28b6994ecf3bb8dbfb2b76d135 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/afa878a689870c28b6994ecf3bb8dbfb2b76d135 | https://github.com/ImageMagick/ImageMagick/issues/1269 | 1 | static Image *ReadPICTImage(const ImageInfo *image_info,
ExceptionInfo *exception)
{
#define ThrowPICTException(exception,message) \
{ \
if (tile_image != (Image *) NULL) \
tile_image=DestroyImage(tile_image); \
if (read_info != (ImageInfo *) NULL) \
read_info=DestroyImageInfo(read_info); \
ThrowReaderE... | 268,226,971,198,431,460,000,000,000,000,000,000,000 | pict.c | 85,654,100,738,905,160,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2018-16644 | There is a missing check for length in the functions ReadDCMImage of coders/dcm.c and ReadPICTImage of coders/pict.c in ImageMagick 7.0.8-11, which allows remote attackers to cause a denial of service via a crafted image. | https://nvd.nist.gov/vuln/detail/CVE-2018-16644 |
160,834 | ImageMagick | afa878a689870c28b6994ecf3bb8dbfb2b76d135 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/afa878a689870c28b6994ecf3bb8dbfb2b76d135 | https://github.com/ImageMagick/ImageMagick/issues/1269 | 0 | static Image *ReadPICTImage(const ImageInfo *image_info,
ExceptionInfo *exception)
{
#define ThrowPICTException(exception,message) \
{ \
if (tile_image != (Image *) NULL) \
tile_image=DestroyImage(tile_image); \
if (read_info != (ImageInfo *) NULL) \
read_info=DestroyImageInfo(read_info); \
ThrowReaderE... | 78,336,055,644,383,780,000,000,000,000,000,000,000 | pict.c | 121,947,124,142,744,590,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2018-16644 | There is a missing check for length in the functions ReadDCMImage of coders/dcm.c and ReadPICTImage of coders/pict.c in ImageMagick 7.0.8-11, which allows remote attackers to cause a denial of service via a crafted image. | https://nvd.nist.gov/vuln/detail/CVE-2018-16644 |
3,554 | ImageMagick | 6b6bff054d569a77973f2140c0e86366e6168a6c | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/6b6bff054d569a77973f2140c0e86366e6168a6c | https://github.com/ImageMagick/ImageMagick/issues/1199 | 1 | static Image *ReadCALSImage(const ImageInfo *image_info,
ExceptionInfo *exception)
{
char
filename[MagickPathExtent],
header[MagickPathExtent],
message[MagickPathExtent];
FILE
*file;
Image
*image;
ImageInfo
*read_info;
int
c,
unique_file;
MagickBooleanType
status;
... | 230,963,622,459,541,900,000,000,000,000,000,000,000 | cals.c | 249,874,488,600,858,530,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2018-16643 | The functions ReadDCMImage in coders/dcm.c, ReadPWPImage in coders/pwp.c, ReadCALSImage in coders/cals.c, and ReadPICTImage in coders/pict.c in ImageMagick 7.0.8-4 do not check the return value of the fputc function, which allows remote attackers to cause a denial of service via a crafted image file. | https://nvd.nist.gov/vuln/detail/CVE-2018-16643 |
160,835 | ImageMagick | 6b6bff054d569a77973f2140c0e86366e6168a6c | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/6b6bff054d569a77973f2140c0e86366e6168a6c | https://github.com/ImageMagick/ImageMagick/issues/1199 | 0 | static Image *ReadCALSImage(const ImageInfo *image_info,
ExceptionInfo *exception)
{
char
filename[MagickPathExtent],
header[MagickPathExtent],
message[MagickPathExtent];
FILE
*file;
Image
*image;
ImageInfo
*read_info;
int
c,
unique_file;
MagickBooleanType
status;
... | 231,866,792,832,064,480,000,000,000,000,000,000,000 | cals.c | 101,335,737,070,926,740,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2018-16643 | The functions ReadDCMImage in coders/dcm.c, ReadPWPImage in coders/pwp.c, ReadCALSImage in coders/cals.c, and ReadPICTImage in coders/pict.c in ImageMagick 7.0.8-4 do not check the return value of the fputc function, which allows remote attackers to cause a denial of service via a crafted image file. | https://nvd.nist.gov/vuln/detail/CVE-2018-16643 |
3,555 | ImageMagick | 6b6bff054d569a77973f2140c0e86366e6168a6c | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/6b6bff054d569a77973f2140c0e86366e6168a6c | https://github.com/ImageMagick/ImageMagick/issues/1199 | 1 | static Image *ReadDCMImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
#define ThrowDCMException(exception,message) \
{ \
if (info.scale != (Quantum *) NULL) \
info.scale=(Quantum *) RelinquishMagickMemory(info.scale); \
if (data != (unsigned char *) NULL) \
data=(unsigned char *) RelinquishMagi... | 32,603,143,152,590,400,000,000,000,000,000,000,000 | dcm.c | 23,780,388,635,429,870,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2018-16643 | The functions ReadDCMImage in coders/dcm.c, ReadPWPImage in coders/pwp.c, ReadCALSImage in coders/cals.c, and ReadPICTImage in coders/pict.c in ImageMagick 7.0.8-4 do not check the return value of the fputc function, which allows remote attackers to cause a denial of service via a crafted image file. | https://nvd.nist.gov/vuln/detail/CVE-2018-16643 |
160,836 | ImageMagick | 6b6bff054d569a77973f2140c0e86366e6168a6c | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/6b6bff054d569a77973f2140c0e86366e6168a6c | https://github.com/ImageMagick/ImageMagick/issues/1199 | 0 | static Image *ReadDCMImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
#define ThrowDCMException(exception,message) \
{ \
if (info.scale != (Quantum *) NULL) \
info.scale=(Quantum *) RelinquishMagickMemory(info.scale); \
if (data != (unsigned char *) NULL) \
data=(unsigned char *) RelinquishMagi... | 91,367,814,297,112,820,000,000,000,000,000,000,000 | dcm.c | 328,072,244,229,553,650,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2018-16643 | The functions ReadDCMImage in coders/dcm.c, ReadPWPImage in coders/pwp.c, ReadCALSImage in coders/cals.c, and ReadPICTImage in coders/pict.c in ImageMagick 7.0.8-4 do not check the return value of the fputc function, which allows remote attackers to cause a denial of service via a crafted image file. | https://nvd.nist.gov/vuln/detail/CVE-2018-16643 |
3,557 | ImageMagick | 6b6bff054d569a77973f2140c0e86366e6168a6c | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/6b6bff054d569a77973f2140c0e86366e6168a6c | https://github.com/ImageMagick/ImageMagick/issues/1199 | 1 | static Image *ReadPWPImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
char
filename[MagickPathExtent];
FILE
*file;
Image
*image,
*next_image,
*pwp_image;
ImageInfo
*read_info;
int
c,
unique_file;
MagickBooleanType
status;
register Image
*p;
reg... | 327,038,602,402,263,440,000,000,000,000,000,000,000 | pwp.c | 138,360,736,349,985,270,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2018-16643 | The functions ReadDCMImage in coders/dcm.c, ReadPWPImage in coders/pwp.c, ReadCALSImage in coders/cals.c, and ReadPICTImage in coders/pict.c in ImageMagick 7.0.8-4 do not check the return value of the fputc function, which allows remote attackers to cause a denial of service via a crafted image file. | https://nvd.nist.gov/vuln/detail/CVE-2018-16643 |
160,837 | ImageMagick | 6b6bff054d569a77973f2140c0e86366e6168a6c | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/6b6bff054d569a77973f2140c0e86366e6168a6c | https://github.com/ImageMagick/ImageMagick/issues/1199 | 0 | static Image *ReadPWPImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
char
filename[MagickPathExtent];
FILE
*file;
Image
*image,
*next_image,
*pwp_image;
ImageInfo
*read_info;
int
c,
unique_file;
MagickBooleanType
status;
register Image
*p;
reg... | 104,712,069,338,175,260,000,000,000,000,000,000,000 | pwp.c | 169,197,474,977,632,440,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2018-16643 | The functions ReadDCMImage in coders/dcm.c, ReadPWPImage in coders/pwp.c, ReadCALSImage in coders/cals.c, and ReadPICTImage in coders/pict.c in ImageMagick 7.0.8-4 do not check the return value of the fputc function, which allows remote attackers to cause a denial of service via a crafted image file. | https://nvd.nist.gov/vuln/detail/CVE-2018-16643 |
3,558 | ImageMagick | cc4ac341f29fa368da6ef01c207deaf8c61f6a2e | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/cc4ac341f29fa368da6ef01c207deaf8c61f6a2e | https://github.com/ImageMagick/ImageMagick/issues/1162 | 1 | static void InsertRow(Image *image,ssize_t depth,unsigned char *p,ssize_t y,
ExceptionInfo *exception)
{
size_t bit; ssize_t x;
register Quantum *q;
Quantum index;
index=0;
switch (depth)
{
case 1: /* Convert bitmap scanline. */
{
q=QueueAuthenticPixels(image,0,y,image->columns,1,e... | 248,821,212,902,523,860,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2018-16642 | The function InsertRow in coders/cut.c in ImageMagick 7.0.7-37 allows remote attackers to cause a denial of service via a crafted image file due to an out-of-bounds write. | https://nvd.nist.gov/vuln/detail/CVE-2018-16642 |
160,838 | ImageMagick | cc4ac341f29fa368da6ef01c207deaf8c61f6a2e | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/cc4ac341f29fa368da6ef01c207deaf8c61f6a2e | https://github.com/ImageMagick/ImageMagick/issues/1162 | 0 | static void InsertRow(Image *image,ssize_t depth,unsigned char *p,ssize_t y,
static MagickBooleanType InsertRow(Image *image,ssize_t bpp,unsigned char *p,
ssize_t y,ExceptionInfo *exception)
{
int
bit;
Quantum
index;
register Quantum
*q;
ssize_t
x;
q=QueueAuthenticPixels(image,0,y,imag... | 69,438,133,789,081,240,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2018-16642 | The function InsertRow in coders/cut.c in ImageMagick 7.0.7-37 allows remote attackers to cause a denial of service via a crafted image file due to an out-of-bounds write. | https://nvd.nist.gov/vuln/detail/CVE-2018-16642 |
3,560 | Little-CMS | 768f70ca405cd3159d990e962d54456773bb8cf8 | https://github.com/mm2/Little-CMS | https://github.com/mm2/Little-CMS/commit/768f70ca405cd3159d990e962d54456773bb8cf8 | Upgrade Visual studio 2017 15.8
- Upgrade to 15.8
- Add check on CGATS memory allocation (thanks to Quang Nguyen for
pointing out this) | 1 | void AllocateDataSet(cmsIT8* it8)
{
TABLE* t = GetTable(it8);
if (t -> Data) return; // Already allocated
t-> nSamples = atoi(cmsIT8GetProperty(it8, "NUMBER_OF_FIELDS"));
t-> nPatches = atoi(cmsIT8GetProperty(it8, "NUMBER_OF_SETS"));
t-> Data = (char**)AllocChunk (it8, ((cmsUInt32Number... | 130,867,891,295,494,080,000,000,000,000,000,000,000 | cmscgats.c | 158,410,423,807,065,500,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2018-16435 | Little CMS (aka Little Color Management System) 2.9 has an integer overflow in the AllocateDataSet function in cmscgats.c, leading to a heap-based buffer overflow in the SetData function via a crafted file in the second argument to cmsIT8LoadFromFile. | https://nvd.nist.gov/vuln/detail/CVE-2018-16435 |
160,839 | Little-CMS | 768f70ca405cd3159d990e962d54456773bb8cf8 | https://github.com/mm2/Little-CMS | https://github.com/mm2/Little-CMS/commit/768f70ca405cd3159d990e962d54456773bb8cf8 | Upgrade Visual studio 2017 15.8
- Upgrade to 15.8
- Add check on CGATS memory allocation (thanks to Quang Nguyen for
pointing out this) | 0 | void AllocateDataSet(cmsIT8* it8)
{
TABLE* t = GetTable(it8);
if (t -> Data) return; // Already allocated
t-> nSamples = atoi(cmsIT8GetProperty(it8, "NUMBER_OF_FIELDS"));
t-> nPatches = atoi(cmsIT8GetProperty(it8, "NUMBER_OF_SETS"));
if (t -> nSamples < 0 || t->nSamples > 0x7ffe || t->n... | 59,248,935,362,505,855,000,000,000,000,000,000,000 | cmscgats.c | 148,931,863,871,035,900,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2018-16435 | Little CMS (aka Little Color Management System) 2.9 has an integer overflow in the AllocateDataSet function in cmscgats.c, leading to a heap-based buffer overflow in the SetData function via a crafted file in the second argument to cmsIT8LoadFromFile. | https://nvd.nist.gov/vuln/detail/CVE-2018-16435 |
3,594 | linux | f1e255d60ae66a9f672ff9a207ee6cd8e33d2679 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f1e255d60ae66a9f672ff9a207ee6cd8e33d2679 | USB: yurex: fix out-of-bounds uaccess in read handler
In general, accessing userspace memory beyond the length of the supplied
buffer in VFS read/write handlers can lead to both kernel memory corruption
(via kernel_read()/kernel_write(), which can e.g. be triggered via
sys_splice()) and privilege escalation inside use... | 1 | static ssize_t yurex_read(struct file *file, char __user *buffer, size_t count,
loff_t *ppos)
{
struct usb_yurex *dev;
int retval = 0;
int bytes_read = 0;
char in_buffer[20];
unsigned long flags;
dev = file->private_data;
mutex_lock(&dev->io_mutex);
if (!dev->interface) { /* already disconnect... | 31,187,263,457,320,156,000,000,000,000,000,000,000 | yurex.c | 153,797,157,770,324,700,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2018-16276 | An issue was discovered in yurex_read in drivers/usb/misc/yurex.c in the Linux kernel before 4.17.7. Local attackers could use user access read/writes with incorrect bounds checking in the yurex USB driver to crash the kernel or potentially escalate privileges. | https://nvd.nist.gov/vuln/detail/CVE-2018-16276 |
160,869 | linux | f1e255d60ae66a9f672ff9a207ee6cd8e33d2679 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f1e255d60ae66a9f672ff9a207ee6cd8e33d2679 | USB: yurex: fix out-of-bounds uaccess in read handler
In general, accessing userspace memory beyond the length of the supplied
buffer in VFS read/write handlers can lead to both kernel memory corruption
(via kernel_read()/kernel_write(), which can e.g. be triggered via
sys_splice()) and privilege escalation inside use... | 0 | static ssize_t yurex_read(struct file *file, char __user *buffer, size_t count,
loff_t *ppos)
{
struct usb_yurex *dev;
int len = 0;
char in_buffer[20];
unsigned long flags;
dev = file->private_data;
mutex_lock(&dev->io_mutex);
if (!dev->interface) { /* already disconnected */
mutex_unlock(&de... | 305,428,393,974,800,400,000,000,000,000,000,000,000 | yurex.c | 9,926,892,678,482,792,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2018-16276 | An issue was discovered in yurex_read in drivers/usb/misc/yurex.c in the Linux kernel before 4.17.7. Local attackers could use user access read/writes with incorrect bounds checking in the yurex USB driver to crash the kernel or potentially escalate privileges. | https://nvd.nist.gov/vuln/detail/CVE-2018-16276 |
3,595 | axtls-8266 | 5efe2947ab45e81d84b5f707c51d1c64be52f36c | https://github.com/igrr/axtls-8266 | https://github.com/igrr/axtls-8266/commit/5efe2947ab45e81d84b5f707c51d1c64be52f36c | Apply CVE fixes for X509 parsing
Apply patches developed by Sze Yiu which correct a vulnerability in
X509 parsing. See CVE-2018-16150 and CVE-2018-16149 for more info. | 1 | static bigint *sig_verify(BI_CTX *ctx, const uint8_t *sig, int sig_len,
bigint *modulus, bigint *pub_exp)
{
int i, size;
bigint *decrypted_bi, *dat_bi;
bigint *bir = NULL;
uint8_t *block = (uint8_t *)malloc(sig_len);
/* decrypt */
dat_bi = bi_import(ctx, sig, sig_len);
ctx-... | 270,479,850,159,638,380,000,000,000,000,000,000,000 | x509.c | 310,893,347,411,045,500,000,000,000,000,000,000,000 | [
"CWE-347"
] | CVE-2018-16253 | In sig_verify() in x509.c in axTLS version 2.1.3 and before, the PKCS#1 v1.5 signature verification does not properly verify the ASN.1 metadata. Consequently, a remote attacker can forge signatures when small public exponents are being used, which could lead to impersonation through fake X.509 certificates. This is an ... | https://nvd.nist.gov/vuln/detail/CVE-2018-16253 |
160,870 | axtls-8266 | 5efe2947ab45e81d84b5f707c51d1c64be52f36c | https://github.com/igrr/axtls-8266 | https://github.com/igrr/axtls-8266/commit/5efe2947ab45e81d84b5f707c51d1c64be52f36c | Apply CVE fixes for X509 parsing
Apply patches developed by Sze Yiu which correct a vulnerability in
X509 parsing. See CVE-2018-16150 and CVE-2018-16149 for more info. | 0 | static bigint *sig_verify(BI_CTX *ctx, const uint8_t *sig, int sig_len,
static bigint *sig_verify(BI_CTX *ctx, const uint8_t *sig, int sig_len, uint8_t sig_type,
bigint *modulus, bigint *pub_exp)
{
int i;
bigint *decrypted_bi, *dat_bi;
bigint *bir = NULL;
uint8_t *block = (uint8_t *)malloc(... | 89,095,336,772,554,800,000,000,000,000,000,000,000 | None | null | [
"CWE-347"
] | CVE-2018-16253 | In sig_verify() in x509.c in axTLS version 2.1.3 and before, the PKCS#1 v1.5 signature verification does not properly verify the ASN.1 metadata. Consequently, a remote attacker can forge signatures when small public exponents are being used, which could lead to impersonation through fake X.509 certificates. This is an ... | https://nvd.nist.gov/vuln/detail/CVE-2018-16253 |
3,597 | libxkbcommon | 96df3106d49438e442510c59acad306e94f3db4d | https://github.com/xkbcommon/libxkbcommon | https://github.com/xkbcommon/libxkbcommon/commit/96df3106d49438e442510c59acad306e94f3db4d | xkbcomp: Don't crash on no-op modmask expressions
If we have an expression of the form 'l1' in an interp section, we
unconditionally try to dereference its args, even if it has none.
Signed-off-by: Daniel Stone <daniels@collabora.com> | 1 | ResolveStateAndPredicate(ExprDef *expr, enum xkb_match_operation *pred_rtrn,
xkb_mod_mask_t *mods_rtrn, CompatInfo *info)
{
if (expr == NULL) {
*pred_rtrn = MATCH_ANY_OR_NONE;
*mods_rtrn = MOD_REAL_MASK_ALL;
return true;
}
*pred_rtrn = MATCH_EXACTLY;
i... | 322,677,027,855,373,450,000,000,000,000,000,000,000 | compat.c | 62,511,665,433,778,810,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2018-15863 | Unchecked NULL pointer usage in ResolveStateAndPredicate in xkbcomp/compat.c in xkbcommon before 0.8.2 could be used by local attackers to crash (NULL pointer dereference) the xkbcommon parser by supplying a crafted keymap file with a no-op modmask expression. | https://nvd.nist.gov/vuln/detail/CVE-2018-15863 |
160,872 | libxkbcommon | 96df3106d49438e442510c59acad306e94f3db4d | https://github.com/xkbcommon/libxkbcommon | https://github.com/xkbcommon/libxkbcommon/commit/96df3106d49438e442510c59acad306e94f3db4d | xkbcomp: Don't crash on no-op modmask expressions
If we have an expression of the form 'l1' in an interp section, we
unconditionally try to dereference its args, even if it has none.
Signed-off-by: Daniel Stone <daniels@collabora.com> | 0 | ResolveStateAndPredicate(ExprDef *expr, enum xkb_match_operation *pred_rtrn,
xkb_mod_mask_t *mods_rtrn, CompatInfo *info)
{
if (expr == NULL) {
*pred_rtrn = MATCH_ANY_OR_NONE;
*mods_rtrn = MOD_REAL_MASK_ALL;
return true;
}
*pred_rtrn = MATCH_EXACTLY;
i... | 72,505,359,917,534,650,000,000,000,000,000,000,000 | compat.c | 283,034,088,681,410,400,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2018-15863 | Unchecked NULL pointer usage in ResolveStateAndPredicate in xkbcomp/compat.c in xkbcommon before 0.8.2 could be used by local attackers to crash (NULL pointer dereference) the xkbcommon parser by supplying a crafted keymap file with a no-op modmask expression. | https://nvd.nist.gov/vuln/detail/CVE-2018-15863 |
3,598 | libxkbcommon | bb4909d2d8fa6b08155e449986a478101e2b2634 | https://github.com/xkbcommon/libxkbcommon | https://github.com/xkbcommon/libxkbcommon/commit/bb4909d2d8fa6b08155e449986a478101e2b2634 | Fail expression lookup on invalid atoms
If we fail atom lookup, then we should not claim that we successfully
looked up the expression.
Signed-off-by: Daniel Stone <daniels@collabora.com> | 1 | ExprResolveLhs(struct xkb_context *ctx, const ExprDef *expr,
const char **elem_rtrn, const char **field_rtrn,
ExprDef **index_rtrn)
{
switch (expr->expr.op) {
case EXPR_IDENT:
*elem_rtrn = NULL;
*field_rtrn = xkb_atom_text(ctx, expr->ident.ident);
*index_rtr... | 31,784,033,323,607,916,000,000,000,000,000,000,000 | expr.c | 36,624,667,439,648,246,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2018-15859 | Unchecked NULL pointer usage when parsing invalid atoms in ExprResolveLhs in xkbcomp/expr.c in xkbcommon before 0.8.2 could be used by local attackers to crash (NULL pointer dereference) the xkbcommon parser by supplying a crafted keymap file, because lookup failures are mishandled. | https://nvd.nist.gov/vuln/detail/CVE-2018-15859 |
160,873 | libxkbcommon | bb4909d2d8fa6b08155e449986a478101e2b2634 | https://github.com/xkbcommon/libxkbcommon | https://github.com/xkbcommon/libxkbcommon/commit/bb4909d2d8fa6b08155e449986a478101e2b2634 | Fail expression lookup on invalid atoms
If we fail atom lookup, then we should not claim that we successfully
looked up the expression.
Signed-off-by: Daniel Stone <daniels@collabora.com> | 0 | ExprResolveLhs(struct xkb_context *ctx, const ExprDef *expr,
const char **elem_rtrn, const char **field_rtrn,
ExprDef **index_rtrn)
{
switch (expr->expr.op) {
case EXPR_IDENT:
*elem_rtrn = NULL;
*field_rtrn = xkb_atom_text(ctx, expr->ident.ident);
*index_rtr... | 77,460,604,937,986,880,000,000,000,000,000,000,000 | expr.c | 155,589,504,409,794,330,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2018-15859 | Unchecked NULL pointer usage when parsing invalid atoms in ExprResolveLhs in xkbcomp/expr.c in xkbcommon before 0.8.2 could be used by local attackers to crash (NULL pointer dereference) the xkbcommon parser by supplying a crafted keymap file, because lookup failures are mishandled. | https://nvd.nist.gov/vuln/detail/CVE-2018-15859 |
3,599 | libxkbcommon | badb428e63387140720f22486b3acbd3d738859f | https://github.com/xkbcommon/libxkbcommon | https://github.com/xkbcommon/libxkbcommon/commit/badb428e63387140720f22486b3acbd3d738859f | keycodes: don't try to copy zero key aliases
Move the aliases copy to within the (num_key_aliases > 0) block.
Passing info->aliases into this fuction with invalid aliases will
cause log messages but num_key_aliases stays on 0. The key_aliases array
is never allocated and remains NULL. We then loop through the aliases... | 1 | CopyKeyAliasesToKeymap(struct xkb_keymap *keymap, KeyNamesInfo *info)
{
AliasInfo *alias;
unsigned i, num_key_aliases;
struct xkb_key_alias *key_aliases;
/*
* Do some sanity checking on the aliases. We can't do it before
* because keys and their aliases may be added out-of-order.
*/
... | 36,688,546,490,544,030,000,000,000,000,000,000,000 | keycodes.c | 170,792,000,299,261,260,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2018-15858 | Unchecked NULL pointer usage when handling invalid aliases in CopyKeyAliasesToKeymap in xkbcomp/keycodes.c in xkbcommon before 0.8.1 could be used by local attackers to crash (NULL pointer dereference) the xkbcommon parser by supplying a crafted keymap file. | https://nvd.nist.gov/vuln/detail/CVE-2018-15858 |
160,874 | libxkbcommon | badb428e63387140720f22486b3acbd3d738859f | https://github.com/xkbcommon/libxkbcommon | https://github.com/xkbcommon/libxkbcommon/commit/badb428e63387140720f22486b3acbd3d738859f | keycodes: don't try to copy zero key aliases
Move the aliases copy to within the (num_key_aliases > 0) block.
Passing info->aliases into this fuction with invalid aliases will
cause log messages but num_key_aliases stays on 0. The key_aliases array
is never allocated and remains NULL. We then loop through the aliases... | 0 | CopyKeyAliasesToKeymap(struct xkb_keymap *keymap, KeyNamesInfo *info)
{
AliasInfo *alias;
unsigned i, num_key_aliases;
struct xkb_key_alias *key_aliases;
/*
* Do some sanity checking on the aliases. We can't do it before
* because keys and their aliases may be added out-of-order.
*/
... | 222,688,645,802,915,670,000,000,000,000,000,000,000 | keycodes.c | 4,630,575,712,486,583,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2018-15858 | Unchecked NULL pointer usage when handling invalid aliases in CopyKeyAliasesToKeymap in xkbcomp/keycodes.c in xkbcommon before 0.8.1 could be used by local attackers to crash (NULL pointer dereference) the xkbcommon parser by supplying a crafted keymap file. | https://nvd.nist.gov/vuln/detail/CVE-2018-15858 |
3,600 | libxkbcommon | c1e5ac16e77a21f87bdf3bc4dea61b037a17dddb | https://github.com/xkbcommon/libxkbcommon | https://github.com/xkbcommon/libxkbcommon/commit/c1e5ac16e77a21f87bdf3bc4dea61b037a17dddb | xkbcomp: fix pointer value for FreeStmt
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> | 1 | ExprAppendMultiKeysymList(ExprDef *expr, ExprDef *append)
{
unsigned nSyms = darray_size(expr->keysym_list.syms);
unsigned numEntries = darray_size(append->keysym_list.syms);
darray_append(expr->keysym_list.symsMapIndex, nSyms);
darray_append(expr->keysym_list.symsNumEntries, numEntries);
darray_... | 50,655,231,442,243,785,000,000,000,000,000,000,000 | ast-build.c | 176,330,050,765,854,960,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2018-15857 | An invalid free in ExprAppendMultiKeysymList in xkbcomp/ast-build.c in xkbcommon before 0.8.1 could be used by local attackers to crash xkbcommon keymap parsers or possibly have unspecified other impact by supplying a crafted keymap file. | https://nvd.nist.gov/vuln/detail/CVE-2018-15857 |
160,875 | libxkbcommon | c1e5ac16e77a21f87bdf3bc4dea61b037a17dddb | https://github.com/xkbcommon/libxkbcommon | https://github.com/xkbcommon/libxkbcommon/commit/c1e5ac16e77a21f87bdf3bc4dea61b037a17dddb | xkbcomp: fix pointer value for FreeStmt
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> | 0 | ExprAppendMultiKeysymList(ExprDef *expr, ExprDef *append)
{
unsigned nSyms = darray_size(expr->keysym_list.syms);
unsigned numEntries = darray_size(append->keysym_list.syms);
darray_append(expr->keysym_list.symsMapIndex, nSyms);
darray_append(expr->keysym_list.symsNumEntries, numEntries);
darray_... | 47,338,399,590,845,790,000,000,000,000,000,000,000 | ast-build.c | 131,620,493,378,436,240,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2018-15857 | An invalid free in ExprAppendMultiKeysymList in xkbcomp/ast-build.c in xkbcommon before 0.8.1 could be used by local attackers to crash xkbcommon keymap parsers or possibly have unspecified other impact by supplying a crafted keymap file. | https://nvd.nist.gov/vuln/detail/CVE-2018-15857 |
3,601 | libxkbcommon | 842e4351c2c97de6051cab6ce36b4a81e709a0e1 | https://github.com/xkbcommon/libxkbcommon | https://github.com/xkbcommon/libxkbcommon/commit/842e4351c2c97de6051cab6ce36b4a81e709a0e1 | compose: fix infinite loop in parser on some inputs
The parser would enter an infinite loop if an unterminated keysym
literal occurs at EOF.
Found with the afl fuzzer.
Signed-off-by: Ran Benita <ran234@gmail.com> | 1 | lex(struct scanner *s, union lvalue *val)
{
skip_more_whitespace_and_comments:
/* Skip spaces. */
while (is_space(peek(s)))
if (next(s) == '\n')
return TOK_END_OF_LINE;
/* Skip comments. */
if (chr(s, '#')) {
skip_to_eol(s);
goto skip_more_whitespace_and_comments;
... | 100,560,431,963,326,220,000,000,000,000,000,000,000 | parser.c | 167,577,738,802,424,040,000,000,000,000,000,000,000 | [
"CWE-835"
] | CVE-2018-15856 | An infinite loop when reaching EOL unexpectedly in compose/parser.c (aka the keymap parser) in xkbcommon before 0.8.1 could be used by local attackers to cause a denial of service during parsing of crafted keymap files. | https://nvd.nist.gov/vuln/detail/CVE-2018-15856 |
160,876 | libxkbcommon | 842e4351c2c97de6051cab6ce36b4a81e709a0e1 | https://github.com/xkbcommon/libxkbcommon | https://github.com/xkbcommon/libxkbcommon/commit/842e4351c2c97de6051cab6ce36b4a81e709a0e1 | compose: fix infinite loop in parser on some inputs
The parser would enter an infinite loop if an unterminated keysym
literal occurs at EOF.
Found with the afl fuzzer.
Signed-off-by: Ran Benita <ran234@gmail.com> | 0 | lex(struct scanner *s, union lvalue *val)
{
skip_more_whitespace_and_comments:
/* Skip spaces. */
while (is_space(peek(s)))
if (next(s) == '\n')
return TOK_END_OF_LINE;
/* Skip comments. */
if (chr(s, '#')) {
skip_to_eol(s);
goto skip_more_whitespace_and_comments;
... | 326,549,141,061,115,580,000,000,000,000,000,000,000 | parser.c | 54,335,916,326,469,340,000,000,000,000,000,000,000 | [
"CWE-835"
] | CVE-2018-15856 | An infinite loop when reaching EOL unexpectedly in compose/parser.c (aka the keymap parser) in xkbcommon before 0.8.1 could be used by local attackers to cause a denial of service during parsing of crafted keymap files. | https://nvd.nist.gov/vuln/detail/CVE-2018-15856 |
3,602 | libxkbcommon | 917636b1d0d70205a13f89062b95e3a0fc31d4ff | https://github.com/xkbcommon/libxkbcommon | https://github.com/xkbcommon/libxkbcommon/commit/917636b1d0d70205a13f89062b95e3a0fc31d4ff | xkbcomp: fix crash when parsing an xkb_geometry section
xkb_geometry sections are ignored; previously the had done so by
returning NULL for the section's XkbFile, however some sections of the
code do not expect this. Instead, create an XkbFile for it, it will
never be processes and discarded later.
Caught with the af... | 1 | CompileKeymap(XkbFile *file, struct xkb_keymap *keymap, enum merge_mode merge)
{
bool ok;
XkbFile *files[LAST_KEYMAP_FILE_TYPE + 1] = { NULL };
enum xkb_file_type type;
struct xkb_context *ctx = keymap->ctx;
/* Collect section files and check for duplicates. */
for (file = (XkbFile *) file->def... | 188,930,561,233,461,670,000,000,000,000,000,000,000 | keymap.c | 77,713,275,270,082,730,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2018-15855 | Unchecked NULL pointer usage in xkbcommon before 0.8.1 could be used by local attackers to crash (NULL pointer dereference) the xkbcommon parser by supplying a crafted keymap file, because the XkbFile for an xkb_geometry section was mishandled. | https://nvd.nist.gov/vuln/detail/CVE-2018-15855 |
160,877 | libxkbcommon | 917636b1d0d70205a13f89062b95e3a0fc31d4ff | https://github.com/xkbcommon/libxkbcommon | https://github.com/xkbcommon/libxkbcommon/commit/917636b1d0d70205a13f89062b95e3a0fc31d4ff | xkbcomp: fix crash when parsing an xkb_geometry section
xkb_geometry sections are ignored; previously the had done so by
returning NULL for the section's XkbFile, however some sections of the
code do not expect this. Instead, create an XkbFile for it, it will
never be processes and discarded later.
Caught with the af... | 0 | CompileKeymap(XkbFile *file, struct xkb_keymap *keymap, enum merge_mode merge)
{
bool ok;
XkbFile *files[LAST_KEYMAP_FILE_TYPE + 1] = { NULL };
enum xkb_file_type type;
struct xkb_context *ctx = keymap->ctx;
/* Collect section files and check for duplicates. */
for (file = (XkbFile *) file->def... | 162,450,249,631,361,230,000,000,000,000,000,000,000 | keymap.c | 16,064,074,085,906,369,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2018-15855 | Unchecked NULL pointer usage in xkbcommon before 0.8.1 could be used by local attackers to crash (NULL pointer dereference) the xkbcommon parser by supplying a crafted keymap file, because the XkbFile for an xkb_geometry section was mishandled. | https://nvd.nist.gov/vuln/detail/CVE-2018-15855 |
3,604 | Openswan | 9eaa6c2a823c1d2b58913506a15f9474bf857a3d | https://github.com/xelerance/Openswan | https://github.com/xelerance/Openswan/commit/9eaa6c2a823c1d2b58913506a15f9474bf857a3d | wo#7449 . verify padding contents for IKEv2 RSA sig check
Special thanks to Sze Yiu Chau of Purdue University (schau@purdue.edu)
who reported the issue. | 1 | err_t verify_signed_hash(const struct RSA_public_key *k
, u_char *s, unsigned int s_max_octets
, u_char **psig
, size_t hash_len
, const u_char *sig_val, size_t sig_len)
{
unsigned int padlen;
/* actual exponent... | 27,311,431,029,886,654,000,000,000,000,000,000,000 | signatures.c | 134,374,594,679,708,330,000,000,000,000,000,000,000 | [
"CWE-347"
] | CVE-2018-15836 | In verify_signed_hash() in lib/liboswkeys/signatures.c in Openswan before 2.6.50.1, the RSA implementation does not verify the value of padding string during PKCS#1 v1.5 signature verification. Consequently, a remote attacker can forge signatures when small public exponents are being used. IKEv2 signature verification ... | https://nvd.nist.gov/vuln/detail/CVE-2018-15836 |
160,878 | Openswan | 9eaa6c2a823c1d2b58913506a15f9474bf857a3d | https://github.com/xelerance/Openswan | https://github.com/xelerance/Openswan/commit/9eaa6c2a823c1d2b58913506a15f9474bf857a3d | wo#7449 . verify padding contents for IKEv2 RSA sig check
Special thanks to Sze Yiu Chau of Purdue University (schau@purdue.edu)
who reported the issue. | 0 | err_t verify_signed_hash(const struct RSA_public_key *k
, u_char *s, unsigned int s_max_octets
, u_char **psig
, size_t hash_len
, const u_char *sig_val, size_t sig_len)
{
unsigned int padlen;
/* actual exponent... | 230,170,942,939,828,600,000,000,000,000,000,000,000 | signatures.c | 13,568,690,642,104,144,000,000,000,000,000,000,000 | [
"CWE-347"
] | CVE-2018-15836 | In verify_signed_hash() in lib/liboswkeys/signatures.c in Openswan before 2.6.50.1, the RSA implementation does not verify the value of padding string during PKCS#1 v1.5 signature verification. Consequently, a remote attacker can forge signatures when small public exponents are being used. IKEv2 signature verification ... | https://nvd.nist.gov/vuln/detail/CVE-2018-15836 |
3,607 | linux | fdf82a7856b32d905c39afc85e34364491e46346 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fdf82a7856b32d905c39afc85e34364491e46346 | x86/speculation: Protect against userspace-userspace spectreRSB
The article "Spectre Returns! Speculation Attacks using the Return Stack
Buffer" [1] describes two new (sub-)variants of spectrev2-like attacks,
making use solely of the RSB contents even on CPUs that don't fallback to
BTB on RSB underflow (Skylake+).
... | 1 | static void __init spectre_v2_select_mitigation(void)
{
enum spectre_v2_mitigation_cmd cmd = spectre_v2_parse_cmdline();
enum spectre_v2_mitigation mode = SPECTRE_V2_NONE;
/*
* If the CPU is not affected and the command line mode is NONE or AUTO
* then nothing to do.
*/
if (!boot_cpu_has_bug(X86_BUG_SPECT... | 315,846,410,972,680,360,000,000,000,000,000,000,000 | bugs.c | 84,576,212,440,621,210,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2018-15572 | The spectre_v2_select_mitigation function in arch/x86/kernel/cpu/bugs.c in the Linux kernel before 4.18.1 does not always fill RSB upon a context switch, which makes it easier for attackers to conduct userspace-userspace spectreRSB attacks. | https://nvd.nist.gov/vuln/detail/CVE-2018-15572 |
160,882 | linux | fdf82a7856b32d905c39afc85e34364491e46346 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fdf82a7856b32d905c39afc85e34364491e46346 | x86/speculation: Protect against userspace-userspace spectreRSB
The article "Spectre Returns! Speculation Attacks using the Return Stack
Buffer" [1] describes two new (sub-)variants of spectrev2-like attacks,
making use solely of the RSB contents even on CPUs that don't fallback to
BTB on RSB underflow (Skylake+).
... | 0 | static void __init spectre_v2_select_mitigation(void)
{
enum spectre_v2_mitigation_cmd cmd = spectre_v2_parse_cmdline();
enum spectre_v2_mitigation mode = SPECTRE_V2_NONE;
/*
* If the CPU is not affected and the command line mode is NONE or AUTO
* then nothing to do.
*/
if (!boot_cpu_has_bug(X86_BUG_SPECT... | 25,624,612,780,284,354,000,000,000,000,000,000,000 | bugs.c | 250,829,947,716,343,630,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2018-15572 | The spectre_v2_select_mitigation function in arch/x86/kernel/cpu/bugs.c in the Linux kernel before 4.18.1 does not always fill RSB upon a context switch, which makes it easier for attackers to conduct userspace-userspace spectreRSB attacks. | https://nvd.nist.gov/vuln/detail/CVE-2018-15572 |
3,608 | libgit2 | 1f9a8510e1d2f20ed7334eeeddb92c4dd8e7c649 | https://github.com/libgit2/libgit2 | https://github.com/libgit2/libgit2/commit/1f9a8510e1d2f20ed7334eeeddb92c4dd8e7c649 | smart_pkt: fix potential OOB-read when processing ng packet
OSS-fuzz has reported a potential out-of-bounds read when processing a
"ng" smart packet:
==1==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x6310000249c0 at pc 0x000000493a92 bp 0x7ffddc882cd0 sp 0x7ffddc882480
READ of size 65529 at 0x631000024... | 1 | static int ng_pkt(git_pkt **out, const char *line, size_t len)
{
git_pkt_ng *pkt;
const char *ptr;
size_t alloclen;
pkt = git__malloc(sizeof(*pkt));
GITERR_CHECK_ALLOC(pkt);
pkt->ref = NULL;
pkt->type = GIT_PKT_NG;
line += 3; /* skip "ng " */
if (!(ptr = strchr(line, ' ')))
goto out_err;
len = ptr ... | 104,719,273,059,594,510,000,000,000,000,000,000,000 | smart_pkt.c | 110,262,442,168,514,210,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2018-15501 | In ng_pkt in transports/smart_pkt.c in libgit2 before 0.26.6 and 0.27.x before 0.27.4, a remote attacker can send a crafted smart-protocol "ng" packet that lacks a '\0' byte to trigger an out-of-bounds read that leads to DoS. | https://nvd.nist.gov/vuln/detail/CVE-2018-15501 |
160,883 | libgit2 | 1f9a8510e1d2f20ed7334eeeddb92c4dd8e7c649 | https://github.com/libgit2/libgit2 | https://github.com/libgit2/libgit2/commit/1f9a8510e1d2f20ed7334eeeddb92c4dd8e7c649 | smart_pkt: fix potential OOB-read when processing ng packet
OSS-fuzz has reported a potential out-of-bounds read when processing a
"ng" smart packet:
==1==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x6310000249c0 at pc 0x000000493a92 bp 0x7ffddc882cd0 sp 0x7ffddc882480
READ of size 65529 at 0x631000024... | 0 | static int ng_pkt(git_pkt **out, const char *line, size_t len)
{
git_pkt_ng *pkt;
const char *ptr;
size_t alloclen;
pkt = git__malloc(sizeof(*pkt));
GITERR_CHECK_ALLOC(pkt);
pkt->ref = NULL;
pkt->type = GIT_PKT_NG;
if (len < 3)
goto out_err;
line += 3; /* skip "ng " */
len -= 3;
if (!(ptr = memchr(l... | 19,224,577,093,974,947,000,000,000,000,000,000,000 | smart_pkt.c | 264,506,239,085,388,540,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2018-15501 | In ng_pkt in transports/smart_pkt.c in libgit2 before 0.26.6 and 0.27.x before 0.27.4, a remote attacker can send a crafted smart-protocol "ng" packet that lacks a '\0' byte to trigger an out-of-bounds read that leads to DoS. | https://nvd.nist.gov/vuln/detail/CVE-2018-15501 |
3,609 | src | 779974d35b4859c07bc3cb8a12c74b43b0a7d1e0 | https://github.com/openbsd/src | https://github.com/openbsd/src/commit/779974d35b4859c07bc3cb8a12c74b43b0a7d1e0 | delay bailout for invalid authenticating user until after the packet
containing the request has been fully parsed. Reported by Dariusz Tytko
and Michał Sajdak; ok deraadt | 1 | userauth_hostbased(struct ssh *ssh)
{
Authctxt *authctxt = ssh->authctxt;
struct sshbuf *b;
struct sshkey *key = NULL;
char *pkalg, *cuser, *chost;
u_char *pkblob, *sig;
size_t alen, blen, slen;
int r, pktype, authenticated = 0;
if (!authctxt->valid) {
debug2("%s: disabled because of invalid user", __func... | 163,718,903,000,687,200,000,000,000,000,000,000,000 | auth2-hostbased.c | 94,121,909,882,891,920,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2018-15473 | OpenSSH through 7.7 is prone to a user enumeration vulnerability due to not delaying bailout for an invalid authenticating user until after the packet containing the request has been fully parsed, related to auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c. | https://nvd.nist.gov/vuln/detail/CVE-2018-15473 |
160,884 | src | 779974d35b4859c07bc3cb8a12c74b43b0a7d1e0 | https://github.com/openbsd/src | https://github.com/openbsd/src/commit/779974d35b4859c07bc3cb8a12c74b43b0a7d1e0 | delay bailout for invalid authenticating user until after the packet
containing the request has been fully parsed. Reported by Dariusz Tytko
and Michał Sajdak; ok deraadt | 0 | userauth_hostbased(struct ssh *ssh)
{
Authctxt *authctxt = ssh->authctxt;
struct sshbuf *b;
struct sshkey *key = NULL;
char *pkalg, *cuser, *chost;
u_char *pkblob, *sig;
size_t alen, blen, slen;
int r, pktype, authenticated = 0;
/* XXX use sshkey_froms() */
if ((r = sshpkt_get_cstring(ssh, &pkalg, &alen)... | 210,449,543,875,787,900,000,000,000,000,000,000,000 | auth2-hostbased.c | 263,842,082,217,637,360,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2018-15473 | OpenSSH through 7.7 is prone to a user enumeration vulnerability due to not delaying bailout for an invalid authenticating user until after the packet containing the request has been fully parsed, related to auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c. | https://nvd.nist.gov/vuln/detail/CVE-2018-15473 |
3,610 | src | 779974d35b4859c07bc3cb8a12c74b43b0a7d1e0 | https://github.com/openbsd/src | https://github.com/openbsd/src/commit/779974d35b4859c07bc3cb8a12c74b43b0a7d1e0 | delay bailout for invalid authenticating user until after the packet
containing the request has been fully parsed. Reported by Dariusz Tytko
and Michał Sajdak; ok deraadt | 1 | userauth_pubkey(struct ssh *ssh)
{
Authctxt *authctxt = ssh->authctxt;
struct passwd *pw = authctxt->pw;
struct sshbuf *b;
struct sshkey *key = NULL;
char *pkalg, *userstyle = NULL, *key_s = NULL, *ca_s = NULL;
u_char *pkblob, *sig, have_sig;
size_t blen, slen;
int r, pktype;
int authenticated = 0;
st... | 267,521,840,593,734,700,000,000,000,000,000,000,000 | auth2-pubkey.c | 260,497,764,924,877,280,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2018-15473 | OpenSSH through 7.7 is prone to a user enumeration vulnerability due to not delaying bailout for an invalid authenticating user until after the packet containing the request has been fully parsed, related to auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c. | https://nvd.nist.gov/vuln/detail/CVE-2018-15473 |
160,885 | src | 779974d35b4859c07bc3cb8a12c74b43b0a7d1e0 | https://github.com/openbsd/src | https://github.com/openbsd/src/commit/779974d35b4859c07bc3cb8a12c74b43b0a7d1e0 | delay bailout for invalid authenticating user until after the packet
containing the request has been fully parsed. Reported by Dariusz Tytko
and Michał Sajdak; ok deraadt | 0 | userauth_pubkey(struct ssh *ssh)
{
Authctxt *authctxt = ssh->authctxt;
struct passwd *pw = authctxt->pw;
struct sshbuf *b = NULL;
struct sshkey *key = NULL;
char *pkalg = NULL, *userstyle = NULL, *key_s = NULL, *ca_s = NULL;
u_char *pkblob = NULL, *sig = NULL, have_sig;
size_t blen, slen;
int r, pktype;
... | 142,634,408,544,224,380,000,000,000,000,000,000,000 | auth2-pubkey.c | 48,557,532,259,418,060,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2018-15473 | OpenSSH through 7.7 is prone to a user enumeration vulnerability due to not delaying bailout for an invalid authenticating user until after the packet containing the request has been fully parsed, related to auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c. | https://nvd.nist.gov/vuln/detail/CVE-2018-15473 |
9,563 | src | 779974d35b4859c07bc3cb8a12c74b43b0a7d1e0 | https://github.com/openbsd/src | https://github.com/openbsd/src/commit/779974d35b4859c07bc3cb8a12c74b43b0a7d1e0 | delay bailout for invalid authenticating user until after the packet
containing the request has been fully parsed. Reported by Dariusz Tytko
and Michał Sajdak; ok deraadt | 1 | userauth_gssapi(struct ssh *ssh)
{
Authctxt *authctxt = ssh->authctxt;
gss_OID_desc goid = {0, NULL};
Gssctxt *ctxt = NULL;
int r, present;
u_int mechs;
OM_uint32 ms;
size_t len;
u_char *doid = NULL;
if (!authctxt->valid || authctxt->user == NULL)
return (0);
if ((r = sshpkt_get_u32(ssh, &mechs)) != 0)... | 135,574,210,007,241,960,000,000,000,000,000,000,000 | auth2-gss.c | 162,181,254,281,413,600,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2018-15473 | OpenSSH through 7.7 is prone to a user enumeration vulnerability due to not delaying bailout for an invalid authenticating user until after the packet containing the request has been fully parsed, related to auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c. | https://nvd.nist.gov/vuln/detail/CVE-2018-15473 |
184,637 | src | 779974d35b4859c07bc3cb8a12c74b43b0a7d1e0 | https://github.com/openbsd/src | https://github.com/openbsd/src/commit/779974d35b4859c07bc3cb8a12c74b43b0a7d1e0 | delay bailout for invalid authenticating user until after the packet
containing the request has been fully parsed. Reported by Dariusz Tytko
and Michał Sajdak; ok deraadt | 0 | userauth_gssapi(struct ssh *ssh)
{
Authctxt *authctxt = ssh->authctxt;
gss_OID_desc goid = {0, NULL};
Gssctxt *ctxt = NULL;
int r, present;
u_int mechs;
OM_uint32 ms;
size_t len;
u_char *doid = NULL;
if ((r = sshpkt_get_u32(ssh, &mechs)) != 0)
fatal("%s: %s", __func__, ssh_err(r));
if (mechs == 0) {... | 310,289,999,956,773,660,000,000,000,000,000,000,000 | auth2-gss.c | 41,062,347,975,447,610,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2018-15473 | OpenSSH through 7.7 is prone to a user enumeration vulnerability due to not delaying bailout for an invalid authenticating user until after the packet containing the request has been fully parsed, related to auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c. | https://nvd.nist.gov/vuln/detail/CVE-2018-15473 |
3,611 | php-src | f151e048ed27f6f4eef729f3310d053ab5da71d4 | https://github.com/php/php-src | https://github.com/php/php-src/commit/f151e048ed27f6f4eef729f3310d053ab5da71d4 | Fixed bug #76459 windows linkinfo lacks openbasedir check | 1 | PHP_FUNCTION(linkinfo)
{
char *link;
size_t link_len;
zend_stat_t sb;
int ret;
if (zend_parse_parameters(ZEND_NUM_ARGS(), "p", &link, &link_len) == FAILURE) {
return;
}
ret = VCWD_STAT(link, &sb);
if (ret == -1) {
php_error_docref(NULL, E_WARNING, "%s", strerror(errno));
RETURN_LONG(Z_L(-1)... | 81,678,671,678,671,030,000,000,000,000,000,000,000 | link_win32.c | 7,661,815,426,260,158,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2018-15132 | An issue was discovered in ext/standard/link_win32.c in PHP before 5.6.37, 7.0.x before 7.0.31, 7.1.x before 7.1.20, and 7.2.x before 7.2.8. The linkinfo function on Windows doesn't implement the open_basedir check. This could be abused to find files on paths outside of the allowed directories. | https://nvd.nist.gov/vuln/detail/CVE-2018-15132 |
160,886 | php-src | f151e048ed27f6f4eef729f3310d053ab5da71d4 | https://github.com/php/php-src | https://github.com/php/php-src/commit/f151e048ed27f6f4eef729f3310d053ab5da71d4 | Fixed bug #76459 windows linkinfo lacks openbasedir check | 0 | PHP_FUNCTION(linkinfo)
{
char *link;
char *dirname;
size_t link_len;
zend_stat_t sb;
int ret;
if (zend_parse_parameters(ZEND_NUM_ARGS(), "p", &link, &link_len) == FAILURE) {
return;
}
dirname = estrndup(link, link_len);
php_dirname(dirname, link_len);
if (php_check_open_basedir(dirname)) {
efr... | 309,977,831,807,690,120,000,000,000,000,000,000,000 | link_win32.c | 269,970,007,046,084,050,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2018-15132 | An issue was discovered in ext/standard/link_win32.c in PHP before 5.6.37, 7.0.x before 7.0.31, 7.1.x before 7.1.20, and 7.2.x before 7.2.8. The linkinfo function on Windows doesn't implement the open_basedir check. This could be abused to find files on paths outside of the allowed directories. | https://nvd.nist.gov/vuln/detail/CVE-2018-15132 |
3,612 | pango | 71aaeaf020340412b8d012fe23a556c0420eda5f | http://github.com/bratsche/pango | https://github.com/GNOME/pango/commit/71aaeaf020340412b8d012fe23a556c0420eda5f | Prevent an assertion with invalid Unicode sequences
Invalid Unicode sequences, such as 0x2665 0xfe0e 0xfe0f,
can trick the Emoji iter code into returning an empty
segment, which then triggers an assertion in the itemizer.
Prevent this by ensuring that we make progress.
This issue was reported by Jeffrey M. | 1 | _pango_emoji_iter_next (PangoEmojiIter *iter)
{
PangoEmojiType current_emoji_type = PANGO_EMOJI_TYPE_INVALID;
if (iter->end == iter->text_end)
return FALSE;
iter->start = iter->end;
for (; iter->end < iter->text_end; iter->end = g_utf8_next_char (iter->end))
{
gunichar ch = g_utf8_get_char (ite... | 267,323,365,278,579,830,000,000,000,000,000,000,000 | pango-emoji.c | 204,716,741,270,840,960,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2018-15120 | libpango in Pango 1.40.8 through 1.42.3, as used in hexchat and other products, allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via crafted text with invalid Unicode sequences. | https://nvd.nist.gov/vuln/detail/CVE-2018-15120 |
160,887 | pango | 71aaeaf020340412b8d012fe23a556c0420eda5f | http://github.com/bratsche/pango | https://github.com/GNOME/pango/commit/71aaeaf020340412b8d012fe23a556c0420eda5f | Prevent an assertion with invalid Unicode sequences
Invalid Unicode sequences, such as 0x2665 0xfe0e 0xfe0f,
can trick the Emoji iter code into returning an empty
segment, which then triggers an assertion in the itemizer.
Prevent this by ensuring that we make progress.
This issue was reported by Jeffrey M. | 0 | _pango_emoji_iter_next (PangoEmojiIter *iter)
{
PangoEmojiType current_emoji_type = PANGO_EMOJI_TYPE_INVALID;
if (iter->end == iter->text_end)
return FALSE;
iter->start = iter->end;
for (; iter->end < iter->text_end; iter->end = g_utf8_next_char (iter->end))
{
gunichar ch = g_utf8_get_char (ite... | 290,041,755,194,649,100,000,000,000,000,000,000,000 | pango-emoji.c | 295,999,534,900,274,750,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2018-15120 | libpango in Pango 1.40.8 through 1.42.3, as used in hexchat and other products, allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via crafted text with invalid Unicode sequences. | https://nvd.nist.gov/vuln/detail/CVE-2018-15120 |
3,614 | libmspack | 0b0ef9344255ff5acfac6b7af09198ac9c9756c8 | https://github.com/kyz/libmspack | https://github.com/kyz/libmspack/commit/0b0ef9344255ff5acfac6b7af09198ac9c9756c8 | kwaj_read_headers(): fix handling of non-terminated strings | 1 | static int kwajd_read_headers(struct mspack_system *sys,
struct mspack_file *fh,
struct mskwajd_header *hdr)
{
unsigned char buf[16];
int i;
/* read in the header */
if (sys->read(fh, &buf[0], kwajh_SIZEOF) != kwajh_SIZEOF) {
return MSPACK_ERR_READ;
}
/* check for "KWAJ" sig... | 276,727,971,155,017,370,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2018-14681 | An issue was discovered in kwajd_read_headers in mspack/kwajd.c in libmspack before 0.7alpha. Bad KWAJ file header extensions could cause a one or two byte overwrite. | https://nvd.nist.gov/vuln/detail/CVE-2018-14681 |
160,889 | libmspack | 0b0ef9344255ff5acfac6b7af09198ac9c9756c8 | https://github.com/kyz/libmspack | https://github.com/kyz/libmspack/commit/0b0ef9344255ff5acfac6b7af09198ac9c9756c8 | kwaj_read_headers(): fix handling of non-terminated strings | 0 | static int kwajd_read_headers(struct mspack_system *sys,
struct mspack_file *fh,
struct mskwajd_header *hdr)
{
unsigned char buf[16];
int i;
/* read in the header */
if (sys->read(fh, &buf[0], kwajh_SIZEOF) != kwajh_SIZEOF) {
return MSPACK_ERR_READ;
}
/* check for "KWAJ" sig... | 206,755,372,745,728,700,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2018-14681 | An issue was discovered in kwajd_read_headers in mspack/kwajd.c in libmspack before 0.7alpha. Bad KWAJ file header extensions could cause a one or two byte overwrite. | https://nvd.nist.gov/vuln/detail/CVE-2018-14681 |
3,620 | FFmpeg | fa19fbcf712a6a6cc5a5cfdc3254a97b9bce6582 | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/fa19fbcf712a6a6cc5a5cfdc3254a97b9bce6582 | avformat/movenc: Write version 2 of audio atom if channels is not known
The version 1 needs the channel count and would divide by 0
Fixes: division by 0
Fixes: fpe_movenc.c_1108_1.ogg
Fixes: fpe_movenc.c_1108_2.ogg
Fixes: fpe_movenc.c_1108_3.wav
Found-by: #CHEN HONGXU# <HCHEN017@e.ntu.edu.sg>
Signed-off-by: Michael N... | 1 | static int mov_write_audio_tag(AVFormatContext *s, AVIOContext *pb, MOVMuxContext *mov, MOVTrack *track)
{
int64_t pos = avio_tell(pb);
int version = 0;
uint32_t tag = track->tag;
if (track->mode == MODE_MOV) {
if (track->timescale > UINT16_MAX) {
if (mov_get_lpcm_flags(track->p... | 170,281,166,197,927,180,000,000,000,000,000,000,000 | movenc.c | 225,582,288,725,160,770,000,000,000,000,000,000,000 | [
"CWE-369"
] | CVE-2018-14395 | libavformat/movenc.c in FFmpeg 3.2 and 4.0.2 allows attackers to cause a denial of service (application crash caused by a divide-by-zero error) with a user crafted audio file when converting to the MOV audio format. | https://nvd.nist.gov/vuln/detail/CVE-2018-14395 |
160,893 | FFmpeg | fa19fbcf712a6a6cc5a5cfdc3254a97b9bce6582 | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/fa19fbcf712a6a6cc5a5cfdc3254a97b9bce6582 | avformat/movenc: Write version 2 of audio atom if channels is not known
The version 1 needs the channel count and would divide by 0
Fixes: division by 0
Fixes: fpe_movenc.c_1108_1.ogg
Fixes: fpe_movenc.c_1108_2.ogg
Fixes: fpe_movenc.c_1108_3.wav
Found-by: #CHEN HONGXU# <HCHEN017@e.ntu.edu.sg>
Signed-off-by: Michael N... | 0 | static int mov_write_audio_tag(AVFormatContext *s, AVIOContext *pb, MOVMuxContext *mov, MOVTrack *track)
{
int64_t pos = avio_tell(pb);
int version = 0;
uint32_t tag = track->tag;
if (track->mode == MODE_MOV) {
if (track->timescale > UINT16_MAX || !track->par->channels) {
if (mo... | 178,081,446,296,866,100,000,000,000,000,000,000,000 | movenc.c | 14,702,391,465,652,286,000,000,000,000,000,000,000 | [
"CWE-369"
] | CVE-2018-14395 | libavformat/movenc.c in FFmpeg 3.2 and 4.0.2 allows attackers to cause a denial of service (application crash caused by a divide-by-zero error) with a user crafted audio file when converting to the MOV audio format. | https://nvd.nist.gov/vuln/detail/CVE-2018-14395 |
3,622 | neomutt | 9bfab35522301794483f8f9ed60820bdec9be59e | https://github.com/neomutt/neomutt | https://github.com/neomutt/neomutt/commit/9bfab35522301794483f8f9ed60820bdec9be59e | sanitise cache paths
Co-authored-by: JerikoOne <jeriko.one@gmx.us> | 1 | static int nntp_hcache_namer(const char *path, char *dest, size_t destlen)
{
return snprintf(dest, destlen, "%s.hcache", path);
}
| 226,490,900,771,100,700,000,000,000,000,000,000,000 | newsrc.c | 212,530,194,709,979,250,000,000,000,000,000,000,000 | [
"CWE-22"
] | CVE-2018-14363 | An issue was discovered in NeoMutt before 2018-07-16. newsrc.c does not properly restrict '/' characters that may have unsafe interaction with cache pathnames. | https://nvd.nist.gov/vuln/detail/CVE-2018-14363 |
173,656 | neomutt | 9bfab35522301794483f8f9ed60820bdec9be59e | https://github.com/neomutt/neomutt | https://github.com/neomutt/neomutt/commit/9bfab35522301794483f8f9ed60820bdec9be59e | sanitise cache paths
Co-authored-by: JerikoOne <jeriko.one@gmx.us> | 0 | static int pop_hcache_namer(const char *path, char *dest, size_t destlen)
{
return snprintf(dest, destlen, "%s." HC_FEXT, path);
}
| 43,441,825,516,546,360,000,000,000,000,000,000,000 | pop.c | 75,915,389,016,422,660,000,000,000,000,000,000,000 | [
"CWE-22"
] | CVE-2018-14363 | An issue was discovered in NeoMutt before 2018-07-16. newsrc.c does not properly restrict '/' characters that may have unsafe interaction with cache pathnames. | https://nvd.nist.gov/vuln/detail/CVE-2018-14363 |
3,633 | neomutt | 1b0f0d0988e6df4e32e9f4bf8780846ea95d4485 | https://github.com/neomutt/neomutt | https://github.com/neomutt/neomutt/commit/1b0f0d0988e6df4e32e9f4bf8780846ea95d4485 | Don't overflow stack buffer in msg_parse_fetch | 1 | static int msg_parse_fetch(struct ImapHeader *h, char *s)
{
char tmp[SHORT_STRING];
char *ptmp = NULL;
if (!s)
return -1;
while (*s)
{
SKIPWS(s);
if (mutt_str_strncasecmp("FLAGS", s, 5) == 0)
{
s = msg_parse_flags(h, s);
if (!s)
return -1;
}
else if (mutt_str_str... | 8,085,076,253,557,074,000,000,000,000,000,000,000 | message.c | 194,626,342,975,920,640,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2018-14350 | An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. imap/message.c has a stack-based buffer overflow for a FETCH response with a long INTERNALDATE field. | https://nvd.nist.gov/vuln/detail/CVE-2018-14350 |
160,901 | neomutt | 1b0f0d0988e6df4e32e9f4bf8780846ea95d4485 | https://github.com/neomutt/neomutt | https://github.com/neomutt/neomutt/commit/1b0f0d0988e6df4e32e9f4bf8780846ea95d4485 | Don't overflow stack buffer in msg_parse_fetch | 0 | static int msg_parse_fetch(struct ImapHeader *h, char *s)
{
char tmp[SHORT_STRING];
char *ptmp = NULL;
if (!s)
return -1;
while (*s)
{
SKIPWS(s);
if (mutt_str_strncasecmp("FLAGS", s, 5) == 0)
{
s = msg_parse_flags(h, s);
if (!s)
return -1;
}
else if (mutt_str_str... | 142,994,027,755,677,740,000,000,000,000,000,000,000 | message.c | 232,570,102,444,709,630,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2018-14350 | An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. imap/message.c has a stack-based buffer overflow for a FETCH response with a long INTERNALDATE field. | https://nvd.nist.gov/vuln/detail/CVE-2018-14350 |
3,637 | neomutt | 93b8ac558752d09e1c56d4f1bc82631316fa9c82 | https://github.com/neomutt/neomutt | https://github.com/neomutt/neomutt/commit/93b8ac558752d09e1c56d4f1bc82631316fa9c82 | Ensure UID in fetch_uidl | 1 | static int fetch_uidl(char *line, void *data)
{
int i, index;
struct Context *ctx = (struct Context *) data;
struct PopData *pop_data = (struct PopData *) ctx->data;
char *endp = NULL;
errno = 0;
index = strtol(line, &endp, 10);
if (errno)
return -1;
while (*endp == ' ')
endp++;
memmove(lin... | 91,378,846,021,011,030,000,000,000,000,000,000,000 | pop.c | 75,915,389,016,422,660,000,000,000,000,000,000,000 | [
"CWE-824"
] | CVE-2018-14356 | An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. pop.c mishandles a zero-length UID. | https://nvd.nist.gov/vuln/detail/CVE-2018-14356 |
160,904 | neomutt | 93b8ac558752d09e1c56d4f1bc82631316fa9c82 | https://github.com/neomutt/neomutt | https://github.com/neomutt/neomutt/commit/93b8ac558752d09e1c56d4f1bc82631316fa9c82 | Ensure UID in fetch_uidl | 0 | static int fetch_uidl(char *line, void *data)
{
int i, index;
struct Context *ctx = (struct Context *) data;
struct PopData *pop_data = (struct PopData *) ctx->data;
char *endp = NULL;
errno = 0;
index = strtol(line, &endp, 10);
if (errno)
return -1;
while (*endp == ' ')
endp++;
memmove(lin... | 185,584,679,931,062,030,000,000,000,000,000,000,000 | pop.c | 36,402,657,701,656,245,000,000,000,000,000,000,000 | [
"CWE-824"
] | CVE-2018-14356 | An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. pop.c mishandles a zero-length UID. | https://nvd.nist.gov/vuln/detail/CVE-2018-14356 |
3,638 | neomutt | 95e80bf9ff10f68cb6443f760b85df4117cb15eb | https://github.com/neomutt/neomutt | https://github.com/neomutt/neomutt/commit/95e80bf9ff10f68cb6443f760b85df4117cb15eb | Quote path in imap_subscribe | 1 | int imap_subscribe(char *path, bool subscribe)
{
struct ImapData *idata = NULL;
char buf[LONG_STRING];
char mbox[LONG_STRING];
char errstr[STRING];
struct Buffer err, token;
struct ImapMbox mx;
if (!mx_is_imap(path) || imap_parse_path(path, &mx) || !mx.mbox)
{
mutt_error(_("Bad mailbox name")... | 336,804,774,773,163,760,000,000,000,000,000,000,000 | imap.c | 118,871,774,482,714,800,000,000,000,000,000,000,000 | [
"CWE-77"
] | CVE-2018-14354 | An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. They allow remote IMAP servers to execute arbitrary commands via backquote characters, related to the mailboxes command associated with a manual subscription or unsubscription. | https://nvd.nist.gov/vuln/detail/CVE-2018-14354 |
160,905 | neomutt | 95e80bf9ff10f68cb6443f760b85df4117cb15eb | https://github.com/neomutt/neomutt | https://github.com/neomutt/neomutt/commit/95e80bf9ff10f68cb6443f760b85df4117cb15eb | Quote path in imap_subscribe | 0 | int imap_subscribe(char *path, bool subscribe)
{
struct ImapData *idata = NULL;
char buf[LONG_STRING];
char mbox[LONG_STRING];
char errstr[STRING];
struct Buffer err, token;
struct ImapMbox mx;
size_t len = 0;
if (!mx_is_imap(path) || imap_parse_path(path, &mx) || !mx.mbox)
{
mutt_error(_("... | 101,270,824,666,906,070,000,000,000,000,000,000,000 | imap.c | 54,818,956,878,466,930,000,000,000,000,000,000,000 | [
"CWE-77"
] | CVE-2018-14354 | An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. They allow remote IMAP servers to execute arbitrary commands via backquote characters, related to the mailboxes command associated with a manual subscription or unsubscription. | https://nvd.nist.gov/vuln/detail/CVE-2018-14354 |
3,639 | neomutt | 3c49c44be9b459d9c616bcaef6eb5d51298c1741 | https://github.com/neomutt/neomutt | https://github.com/neomutt/neomutt/commit/3c49c44be9b459d9c616bcaef6eb5d51298c1741 | Ensure litlen isn't larger than our mailbox | 1 | static void cmd_parse_status(struct ImapData *idata, char *s)
{
char *value = NULL;
struct Buffy *inc = NULL;
struct ImapMbox mx;
struct ImapStatus *status = NULL;
unsigned int olduv, oldun;
unsigned int litlen;
short new = 0;
short new_msg_count = 0;
char *mailbox = imap_next_word(s);
/* We need ... | 255,835,415,023,365,760,000,000,000,000,000,000,000 | command.c | 171,255,987,523,769,300,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2018-14351 | An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. imap/command.c mishandles a long IMAP status mailbox literal count size. | https://nvd.nist.gov/vuln/detail/CVE-2018-14351 |
160,906 | neomutt | 3c49c44be9b459d9c616bcaef6eb5d51298c1741 | https://github.com/neomutt/neomutt | https://github.com/neomutt/neomutt/commit/3c49c44be9b459d9c616bcaef6eb5d51298c1741 | Ensure litlen isn't larger than our mailbox | 0 | static void cmd_parse_status(struct ImapData *idata, char *s)
{
char *value = NULL;
struct Buffy *inc = NULL;
struct ImapMbox mx;
struct ImapStatus *status = NULL;
unsigned int olduv, oldun;
unsigned int litlen;
short new = 0;
short new_msg_count = 0;
char *mailbox = imap_next_word(s);
/* We need ... | 116,531,805,154,572,040,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2018-14351 | An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. imap/command.c mishandles a long IMAP status mailbox literal count size. | https://nvd.nist.gov/vuln/detail/CVE-2018-14351 |
3,651 | libpng | 8a05766cb74af05c04c53e6c9d60c13fc4d59bf2 | https://github.com/glennrp/libpng | https://github.com/glennrp/libpng/commit/8a05766cb74af05c04c53e6c9d60c13fc4d59bf2 | [libpng16] Fix the calculation of row_factor in png_check_chunk_length
(Bug report by Thuan Pham, SourceForge issue #278) | 1 | png_check_chunk_length(png_const_structrp png_ptr, const png_uint_32 length)
{
png_alloc_size_t limit = PNG_UINT_31_MAX;
# ifdef PNG_SET_USER_LIMITS_SUPPORTED
if (png_ptr->user_chunk_malloc_max > 0 &&
png_ptr->user_chunk_malloc_max < limit)
limit = png_ptr->user_chunk_malloc_max;
# elif PNG_USER_CHU... | 110,259,438,980,219,460,000,000,000,000,000,000,000 | pngrutil.c | 326,867,964,072,458,030,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2018-13785 | In libpng 1.6.34, a wrong calculation of row_factor in the png_check_chunk_length function (pngrutil.c) may trigger an integer overflow and resultant divide-by-zero while processing a crafted PNG file, leading to a denial of service. | https://nvd.nist.gov/vuln/detail/CVE-2018-13785 |
160,910 | libpng | 8a05766cb74af05c04c53e6c9d60c13fc4d59bf2 | https://github.com/glennrp/libpng | https://github.com/glennrp/libpng/commit/8a05766cb74af05c04c53e6c9d60c13fc4d59bf2 | [libpng16] Fix the calculation of row_factor in png_check_chunk_length
(Bug report by Thuan Pham, SourceForge issue #278) | 0 | png_check_chunk_length(png_const_structrp png_ptr, const png_uint_32 length)
{
png_alloc_size_t limit = PNG_UINT_31_MAX;
# ifdef PNG_SET_USER_LIMITS_SUPPORTED
if (png_ptr->user_chunk_malloc_max > 0 &&
png_ptr->user_chunk_malloc_max < limit)
limit = png_ptr->user_chunk_malloc_max;
# elif PNG_USER_CHU... | 99,686,576,898,257,730,000,000,000,000,000,000,000 | pngrutil.c | 143,097,416,311,373,610,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2018-13785 | In libpng 1.6.34, a wrong calculation of row_factor in the png_check_chunk_length function (pngrutil.c) may trigger an integer overflow and resultant divide-by-zero while processing a crafted PNG file, leading to a denial of service. | https://nvd.nist.gov/vuln/detail/CVE-2018-13785 |
3,652 | linux | 9f645bcc566a1e9f921bdae7528a01ced5bc3713 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9f645bcc566a1e9f921bdae7528a01ced5bc3713 | video: uvesafb: Fix integer overflow in allocation
cmap->len can get close to INT_MAX/2, allowing for an integer overflow in
allocation. This uses kmalloc_array() instead to catch the condition.
Reported-by: Dr Silvio Cesare of InfoSect <silvio.cesare@gmail.com>
Fixes: 8bdb3a2d7df48 ("uvesafb: the driver core")
Cc: s... | 1 | static int uvesafb_setcmap(struct fb_cmap *cmap, struct fb_info *info)
{
struct uvesafb_pal_entry *entries;
int shift = 16 - dac_width;
int i, err = 0;
if (info->var.bits_per_pixel == 8) {
if (cmap->start + cmap->len > info->cmap.start +
info->cmap.len || cmap->start < info->cmap.start)
return -EINVAL... | 129,461,505,887,171,650,000,000,000,000,000,000,000 | uvesafb.c | 8,702,348,276,085,379,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2018-13406 | An integer overflow in the uvesafb_setcmap function in drivers/video/fbdev/uvesafb.c in the Linux kernel before 4.17.4 could result in local attackers being able to crash the kernel or potentially elevate privileges because kmalloc_array is not used. | https://nvd.nist.gov/vuln/detail/CVE-2018-13406 |
160,911 | linux | 9f645bcc566a1e9f921bdae7528a01ced5bc3713 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9f645bcc566a1e9f921bdae7528a01ced5bc3713 | video: uvesafb: Fix integer overflow in allocation
cmap->len can get close to INT_MAX/2, allowing for an integer overflow in
allocation. This uses kmalloc_array() instead to catch the condition.
Reported-by: Dr Silvio Cesare of InfoSect <silvio.cesare@gmail.com>
Fixes: 8bdb3a2d7df48 ("uvesafb: the driver core")
Cc: s... | 0 | static int uvesafb_setcmap(struct fb_cmap *cmap, struct fb_info *info)
{
struct uvesafb_pal_entry *entries;
int shift = 16 - dac_width;
int i, err = 0;
if (info->var.bits_per_pixel == 8) {
if (cmap->start + cmap->len > info->cmap.start +
info->cmap.len || cmap->start < info->cmap.start)
return -EINVAL... | 147,952,423,274,284,670,000,000,000,000,000,000,000 | uvesafb.c | 169,039,628,371,384,440,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2018-13406 | An integer overflow in the uvesafb_setcmap function in drivers/video/fbdev/uvesafb.c in the Linux kernel before 4.17.4 could result in local attackers being able to crash the kernel or potentially elevate privileges because kmalloc_array is not used. | https://nvd.nist.gov/vuln/detail/CVE-2018-13406 |
3,653 | linux | 0fa3ecd87848c9c93c2c828ef4c3a8ca36ce46c7 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0fa3ecd87848c9c93c2c828ef4c3a8ca36ce46c7 | Fix up non-directory creation in SGID directories
sgid directories have special semantics, making newly created files in
the directory belong to the group of the directory, and newly created
subdirectories will also become sgid. This is historically used for
group-shared directories.
But group directories writable b... | 1 | void inode_init_owner(struct inode *inode, const struct inode *dir,
umode_t mode)
{
inode->i_uid = current_fsuid();
if (dir && dir->i_mode & S_ISGID) {
inode->i_gid = dir->i_gid;
if (S_ISDIR(mode))
mode |= S_ISGID;
} else
inode->i_gid = current_fsgid();
inode->i_mode = mode;
}
| 215,180,090,082,961,630,000,000,000,000,000,000,000 | inode.c | 212,299,787,291,086,200,000,000,000,000,000,000,000 | [
"CWE-269"
] | CVE-2018-13405 | The inode_init_owner function in fs/inode.c in the Linux kernel through 3.16 allows local users to create files with an unintended group ownership, in a scenario where a directory is SGID to a certain group and is writable by a user who is not a member of that group. Here, the non-member can trigger creation of a plain... | https://nvd.nist.gov/vuln/detail/CVE-2018-13405 |
160,912 | linux | 0fa3ecd87848c9c93c2c828ef4c3a8ca36ce46c7 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0fa3ecd87848c9c93c2c828ef4c3a8ca36ce46c7 | Fix up non-directory creation in SGID directories
sgid directories have special semantics, making newly created files in
the directory belong to the group of the directory, and newly created
subdirectories will also become sgid. This is historically used for
group-shared directories.
But group directories writable b... | 0 | void inode_init_owner(struct inode *inode, const struct inode *dir,
umode_t mode)
{
inode->i_uid = current_fsuid();
if (dir && dir->i_mode & S_ISGID) {
inode->i_gid = dir->i_gid;
/* Directories are special, and always inherit S_ISGID */
if (S_ISDIR(mode))
mode |= S_ISGID;
else if ((mode & (S_ISGID... | 217,090,363,072,080,700,000,000,000,000,000,000,000 | inode.c | 83,084,926,837,076,020,000,000,000,000,000,000,000 | [
"CWE-269"
] | CVE-2018-13405 | The inode_init_owner function in fs/inode.c in the Linux kernel through 3.16 allows local users to create files with an unintended group ownership, in a scenario where a directory is SGID to a certain group and is writable by a user who is not a member of that group. Here, the non-member can trigger creation of a plain... | https://nvd.nist.gov/vuln/detail/CVE-2018-13405 |
3,654 | FFmpeg | 00e8181bd97c834fe60751b0c511d4bb97875f78 | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/00e8181bd97c834fe60751b0c511d4bb97875f78 | avcodec/ac3_parser: Check init_get_bits8() for failure
Fixes: null pointer dereference
Fixes: ffmpeg_crash_6.avi
Found-by: Thuan Pham, Marcel Böhme, Andrew Santosa and Alexandru Razvan Caciulescu with AFLSmart
Reviewed-by: Paul B Mahol <onemda@gmail.com>
Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> | 1 | int avpriv_ac3_parse_header(AC3HeaderInfo **phdr, const uint8_t *buf,
size_t size)
{
GetBitContext gb;
AC3HeaderInfo *hdr;
int err;
if (!*phdr)
*phdr = av_mallocz(sizeof(AC3HeaderInfo));
if (!*phdr)
return AVERROR(ENOMEM);
hdr = *phdr;
init_ge... | 236,477,656,578,978,820,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2018-13303 | In FFmpeg 4.0.1, a missing check for failure of a call to init_get_bits8() in the avpriv_ac3_parse_header function in libavcodec/ac3_parser.c may trigger a NULL pointer dereference while converting a crafted AVI file to MPEG4, leading to a denial of service. | https://nvd.nist.gov/vuln/detail/CVE-2018-13303 |
160,915 | FFmpeg | 00e8181bd97c834fe60751b0c511d4bb97875f78 | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/00e8181bd97c834fe60751b0c511d4bb97875f78 | avcodec/ac3_parser: Check init_get_bits8() for failure
Fixes: null pointer dereference
Fixes: ffmpeg_crash_6.avi
Found-by: Thuan Pham, Marcel Böhme, Andrew Santosa and Alexandru Razvan Caciulescu with AFLSmart
Reviewed-by: Paul B Mahol <onemda@gmail.com>
Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> | 0 | int avpriv_ac3_parse_header(AC3HeaderInfo **phdr, const uint8_t *buf,
size_t size)
{
GetBitContext gb;
AC3HeaderInfo *hdr;
int err;
if (!*phdr)
*phdr = av_mallocz(sizeof(AC3HeaderInfo));
if (!*phdr)
return AVERROR(ENOMEM);
hdr = *phdr;
err = i... | 69,022,085,928,273,560,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2018-13303 | In FFmpeg 4.0.1, a missing check for failure of a call to init_get_bits8() in the avpriv_ac3_parse_header function in libavcodec/ac3_parser.c may trigger a NULL pointer dereference while converting a crafted AVI file to MPEG4, leading to a denial of service. | https://nvd.nist.gov/vuln/detail/CVE-2018-13303 |
3,655 | FFmpeg | 2aa9047486dbff12d9e040f917e5f799ed2fd78b | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/2aa9047486dbff12d9e040f917e5f799ed2fd78b | avcodec/mpeg4videodec: Check read profile before setting it
Fixes: null pointer dereference
Fixes: ffmpeg_crash_7.avi
Found-by: Thuan Pham, Marcel Böhme, Andrew Santosa and Alexandru Razvan Caciulescu with AFLSmart
Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> | 1 | int ff_mpeg4_decode_picture_header(Mpeg4DecContext *ctx, GetBitContext *gb)
{
MpegEncContext *s = &ctx->m;
unsigned startcode, v;
int ret;
int vol = 0;
/* search next start code */
align_get_bits(gb);
if (!s->studio_profile && s->avctx->bits_per_raw_sample != 8)
s->avctx->bits_per_... | 328,896,097,922,084,930,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2018-13301 | In FFmpeg 4.0.1, due to a missing check of a profile value before setting it, the ff_mpeg4_decode_picture_header function in libavcodec/mpeg4videodec.c may trigger a NULL pointer dereference while converting a crafted AVI file to MPEG4, leading to a denial of service. | https://nvd.nist.gov/vuln/detail/CVE-2018-13301 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.