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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
2,802 | linux | c70422f760c120480fee4de6c38804c72aa26bc1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c70422f760c120480fee4de6c38804c72aa26bc1 | Merge tag 'nfsd-4.12' of git://linux-nfs.org/~bfields/linux
Pull nfsd updates from Bruce Fields:
"Another RDMA update from Chuck Lever, and a bunch of miscellaneous
bugfixes"
* tag 'nfsd-4.12' of git://linux-nfs.org/~bfields/linux: (26 commits)
nfsd: Fix up the "supattr_exclcreat" attributes
nfsd: encoders mus... | 1 | nfsd4_layout_verify(struct svc_export *exp, unsigned int layout_type)
{
if (!exp->ex_layout_types) {
dprintk("%s: export does not support pNFS\n", __func__);
return NULL;
}
if (!(exp->ex_layout_types & (1 << layout_type))) {
dprintk("%s: layout type %d not supported\n",
__func__, layout_type);
retu... | 218,091,687,735,945,600,000,000,000,000,000,000,000 | nfs4proc.c | 255,541,904,113,810,930,000,000,000,000,000,000,000 | [
"CWE-404"
] | CVE-2017-9059 | The NFSv4 implementation in the Linux kernel through 4.11.1 allows local users to cause a denial of service (resource consumption) by leveraging improper channel callback shutdown when unmounting an NFSv4 filesystem, aka a "module reference and kernel daemon" leak. | https://nvd.nist.gov/vuln/detail/CVE-2017-9059 |
2,840 | libav | fe6eea99efac66839052af547426518efd970b24 | https://github.com/libav/libav | https://github.com/libav/libav/commit/fe6eea99efac66839052af547426518efd970b24 | nsvdec: don't ignore the return value of av_get_packet()
Fixes invalid reads with corrupted files.
CC: libav-stable@libav.org
Bug-Id: 1039 | 1 | static int nsv_read_chunk(AVFormatContext *s, int fill_header)
{
NSVContext *nsv = s->priv_data;
AVIOContext *pb = s->pb;
AVStream *st[2] = {NULL, NULL};
NSVStream *nst;
AVPacket *pkt;
int i, err = 0;
uint8_t auxcount; /* number of aux metadata, also 4 bits of vsize */
uint32_t vsize;
... | 329,107,632,410,302,050,000,000,000,000,000,000,000 | nsvdec.c | 312,307,119,600,340,800,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-9051 | libav before 12.1 is vulnerable to an invalid read of size 1 due to NULL pointer dereferencing in the nsv_read_chunk function in libavformat/nsvdec.c. | https://nvd.nist.gov/vuln/detail/CVE-2017-9051 |
2,843 | linux | 30572418b445d85fcfe6c8fe84c947d2606767d8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/30572418b445d85fcfe6c8fe84c947d2606767d8 | USB: serial: omninet: fix reference leaks at open
This driver needlessly took another reference to the tty on open, a
reference which was then never released on close. This lead to not just
a leak of the tty, but also a driver reference leak that prevented the
driver from being unloaded after a port had once been open... | 1 | static int omninet_open(struct tty_struct *tty, struct usb_serial_port *port)
{
struct usb_serial *serial = port->serial;
struct usb_serial_port *wport;
wport = serial->port[1];
tty_port_tty_set(&wport->port, tty);
return usb_serial_generic_open(tty, port);
}
| 228,248,121,981,779,100,000,000,000,000,000,000,000 | omninet.c | 237,005,556,314,206,100,000,000,000,000,000,000,000 | [
"CWE-404"
] | CVE-2017-8925 | The omninet_open function in drivers/usb/serial/omninet.c in the Linux kernel before 4.10.4 allows local users to cause a denial of service (tty exhaustion) by leveraging reference count mishandling. | https://nvd.nist.gov/vuln/detail/CVE-2017-8925 |
2,844 | linux | 654b404f2a222f918af9b0cd18ad469d0c941a8e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/654b404f2a222f918af9b0cd18ad469d0c941a8e | USB: serial: io_ti: fix information leak in completion handler
Add missing sanity check to the bulk-in completion handler to avoid an
integer underflow that can be triggered by a malicious device.
This avoids leaking 128 kB of memory content from after the URB transfer
buffer to user space.
Fixes: 8c209e6782ca ("USB... | 1 | static void edge_bulk_in_callback(struct urb *urb)
{
struct edgeport_port *edge_port = urb->context;
struct device *dev = &edge_port->port->dev;
unsigned char *data = urb->transfer_buffer;
int retval = 0;
int port_number;
int status = urb->status;
switch (status) {
case 0:
/* success */
break;
case -ECONN... | 237,137,810,113,617,050,000,000,000,000,000,000,000 | io_ti.c | 270,680,887,866,764,350,000,000,000,000,000,000,000 | [
"CWE-191"
] | CVE-2017-8924 | The edge_bulk_in_callback function in drivers/usb/serial/io_ti.c in the Linux kernel before 4.10.4 allows local users to obtain sensitive information (in the dmesg ringbuffer and syslog) from uninitialized kernel memory by using a crafted USB device (posing as an io_ti USB serial device) to trigger an integer underflow... | https://nvd.nist.gov/vuln/detail/CVE-2017-8924 |
2,845 | linux | 657831ffc38e30092a2d5f03d385d710eb88b09a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/657831ffc38e30092a2d5f03d385d710eb88b09a | dccp/tcp: do not inherit mc_list from parent
syzkaller found a way to trigger double frees from ip_mc_drop_socket()
It turns out that leave a copy of parent mc_list at accept() time,
which is very bad.
Very similar to commit 8b485ce69876 ("tcp: do not inherit
fastopen_req from parent")
Initial report from Pray3r, c... | 1 | struct sock *inet_csk_clone_lock(const struct sock *sk,
const struct request_sock *req,
const gfp_t priority)
{
struct sock *newsk = sk_clone_lock(sk, priority);
if (newsk) {
struct inet_connection_sock *newicsk = inet_csk(newsk);
newsk->sk_state = TCP_SYN_RECV;
newicsk->icsk_bind_hash = NULL;
in... | 228,213,845,731,710,600,000,000,000,000,000,000,000 | inet_connection_sock.c | 173,250,766,656,989,700,000,000,000,000,000,000,000 | [
"CWE-415"
] | CVE-2017-8890 | The inet_csk_clone_lock function in net/ipv4/inet_connection_sock.c in the Linux kernel through 4.10.15 allows attackers to cause a denial of service (double free) or possibly have unspecified other impact by leveraging use of the accept system call. | https://nvd.nist.gov/vuln/detail/CVE-2017-8890 |
2,846 | media-tree | 354dd3924a2e43806774953de536257548b5002c | https://github.com/stoth68000/media-tree | https://github.com/stoth68000/media-tree/commit/354dd3924a2e43806774953de536257548b5002c | [PATCH] saa7164: Bug - Double fetch PCIe access condition
Avoid a double fetch by reusing the values from the prior transfer.
Originally reported via https://bugzilla.kernel.org/show_bug.cgi?id=195559
Thanks to Pengfei Wang <wpengfeinudt@gmail.com> for reporting.
Signed-off-by: Steven Toth <stoth@kernellabs.com> | 1 | int saa7164_bus_get(struct saa7164_dev *dev, struct tmComResInfo* msg,
void *buf, int peekonly)
{
struct tmComResBusInfo *bus = &dev->bus;
u32 bytes_to_read, write_distance, curr_grp, curr_gwp,
new_grp, buf_size, space_rem;
struct tmComResInfo msg_tmp;
int ret = SAA_ERR_BAD_PARAMETER;
saa7164_bus_verify(dev);
... | 117,942,364,588,084,660,000,000,000,000,000,000,000 | saa7164-bus.c | 229,727,223,372,613,800,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-8831 | The saa7164_bus_get function in drivers/media/pci/saa7164/saa7164-bus.c in the Linux kernel through 4.11.5 allows local users to cause a denial of service (out-of-bounds array access) or possibly have unspecified other impact by changing a certain sequence-number value, aka a "double fetch" vulnerability. | https://nvd.nist.gov/vuln/detail/CVE-2017-8831 |
2,847 | libetpan | 1fe8fbc032ccda1db9af66d93016b49c16c1f22d | https://github.com/dinhviethoa/libetpan | https://github.com/dinhviethoa/libetpan/commit/1fe8fbc032ccda1db9af66d93016b49c16c1f22d | Fixed crash #274 | 1 | static int mailimf_group_parse(const char * message, size_t length,
size_t * indx,
struct mailimf_group ** result)
{
size_t cur_token;
char * display_name;
struct mailimf_mailbox_list * mailbox_list;
struct mailimf_group * group;
int r;
int res;
cur_token = * indx;
mailbox_li... | 201,558,413,158,031,750,000,000,000,000,000,000,000 | mailimf.c | 184,503,527,321,366,240,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-8825 | A null dereference vulnerability has been found in the MIME handling component of LibEtPan before 1.8, as used in MailCore and MailCore 2. A crash can occur in low-level/imf/mailimf.c during a failed parse of a Cc header containing multiple e-mail addresses. | https://nvd.nist.gov/vuln/detail/CVE-2017-8825 |
2,855 | yara | 83d799804648c2a0895d40a19835d9b757c6fa4e | https://github.com/VirusTotal/yara | https://github.com/VirusTotal/yara/commit/83d799804648c2a0895d40a19835d9b757c6fa4e | Fix issue #646 (#648)
* Fix issue #646 and some edge cases with wide regexps using \b and \B
* Rename function IS_WORD_CHAR to _yr_re_is_word_char | 1 | int yr_re_exec(
uint8_t* re_code,
uint8_t* input_data,
size_t input_size,
int flags,
RE_MATCH_CALLBACK_FUNC callback,
void* callback_args)
{
uint8_t* ip;
uint8_t* input;
uint8_t mask;
uint8_t value;
RE_FIBER_LIST fibers;
RE_THREAD_STORAGE* storage;
RE_FIBER* fiber;
RE_FIBE... | 71,603,843,470,270,060,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2017-8294 | libyara/re.c in the regex component in YARA 3.5.0 allows remote attackers to cause a denial of service (out-of-bounds read and application crash) via a crafted rule that is mishandled in the yr_re_exec function. | https://nvd.nist.gov/vuln/detail/CVE-2017-8294 |
2,858 | weechat | 2fb346f25f79e412cf0ed314fdf791763c19b70b | https://github.com/weechat/weechat | https://github.com/weechat/weechat/commit/2fb346f25f79e412cf0ed314fdf791763c19b70b | irc: fix parsing of DCC filename | 1 | irc_ctcp_dcc_filename_without_quotes (const char *filename)
{
int length;
length = strlen (filename);
if (length > 0)
{
if ((filename[0] == '\"') && (filename[length - 1] == '\"'))
return weechat_strndup (filename + 1, length - 2);
}
return strdup (filename);
}
| 205,848,505,954,917,040,000,000,000,000,000,000,000 | irc-ctcp.c | 222,746,897,467,776,350,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-8073 | WeeChat before 1.7.1 allows a remote crash by sending a filename via DCC to the IRC plugin. This occurs in the irc_ctcp_dcc_filename_without_quotes function during quote removal, with a buffer overflow. | https://nvd.nist.gov/vuln/detail/CVE-2017-8073 |
2,859 | linux | 8e9faa15469ed7c7467423db4c62aeed3ff4cae3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8e9faa15469ed7c7467423db4c62aeed3ff4cae3 | HID: cp2112: fix gpio-callback error handling
In case of a zero-length report, the gpio direction_input callback would
currently return success instead of an errno.
Fixes: 1ffb3c40ffb5 ("HID: cp2112: make transfer buffers DMA capable")
Cc: stable <stable@vger.kernel.org> # 4.9
Signed-off-by: Johan Hovold <johan@k... | 1 | static int cp2112_gpio_direction_input(struct gpio_chip *chip, unsigned offset)
{
struct cp2112_device *dev = gpiochip_get_data(chip);
struct hid_device *hdev = dev->hdev;
u8 *buf = dev->in_out_buffer;
int ret;
mutex_lock(&dev->lock);
ret = hid_hw_raw_request(hdev, CP2112_GPIO_CONFIG, buf,
CP2112_GPIO_CONF... | 160,178,556,256,165,060,000,000,000,000,000,000,000 | hid-cp2112.c | 316,560,877,108,462,260,000,000,000,000,000,000,000 | [
"CWE-388"
] | CVE-2017-8072 | The cp2112_gpio_direction_input function in drivers/hid/hid-cp2112.c in the Linux kernel 4.9.x before 4.9.9 does not have the expected EIO error status for a zero-length report, which allows local users to have an unspecified impact via unknown vectors. | https://nvd.nist.gov/vuln/detail/CVE-2017-8072 |
2,864 | linux | 2d6a0e9de03ee658a9adc3bfb2f0ca55dff1e478 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2d6a0e9de03ee658a9adc3bfb2f0ca55dff1e478 | catc: Use heap buffer for memory size test
Allocating USB buffers on the stack is not portable, and no longer
works on x86_64 (with VMAP_STACK enabled as per default).
Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Signed-off-by: David S. Miller <davem@davemloft.net> | 1 | static int catc_probe(struct usb_interface *intf, const struct usb_device_id *id)
{
struct device *dev = &intf->dev;
struct usb_device *usbdev = interface_to_usbdev(intf);
struct net_device *netdev;
struct catc *catc;
u8 broadcast[ETH_ALEN];
int i, pktsz, ret;
if (usb_set_interface(usbdev,
intf->altset... | 172,337,252,027,272,000,000,000,000,000,000,000,000 | catc.c | 102,177,431,267,909,100,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-8070 | drivers/net/usb/catc.c in the Linux kernel 4.9.x before 4.9.11 interacts incorrectly with the CONFIG_VMAP_STACK option, which allows local users to cause a denial of service (system crash or memory corruption) or possibly have unspecified other impact by leveraging use of more than one virtual page for a DMA scatterlis... | https://nvd.nist.gov/vuln/detail/CVE-2017-8070 |
2,869 | linux | c919a3069c775c1c876bec55e00b2305d5125caa | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c919a3069c775c1c876bec55e00b2305d5125caa | can: gs_usb: Don't use stack memory for USB transfers
Fixes: 05ca5270005c can: gs_usb: add ethtool set_phys_id callback to locate physical device
The gs_usb driver is performing USB transfers using buffers allocated on
the stack. This causes the driver to not function with vmapped stacks.
Instead, allocate memory for... | 1 | static int gs_usb_probe(struct usb_interface *intf,
const struct usb_device_id *id)
{
struct gs_usb *dev;
int rc = -ENOMEM;
unsigned int icount, i;
struct gs_host_config hconf = {
.byte_order = 0x0000beef,
};
struct gs_device_config dconf;
/* send host config */
rc = usb_control_msg(interface_to_usb... | 35,449,025,086,418,550,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2017-8066 | drivers/net/can/usb/gs_usb.c in the Linux kernel 4.9.x and 4.10.x before 4.10.2 interacts incorrectly with the CONFIG_VMAP_STACK option, which allows local users to cause a denial of service (system crash or memory corruption) or possibly have unspecified other impact by leveraging use of more than one virtual page for... | https://nvd.nist.gov/vuln/detail/CVE-2017-8066 |
2,870 | linux | 3b30460c5b0ed762be75a004e924ec3f8711e032 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/3b30460c5b0ed762be75a004e924ec3f8711e032 | crypto: ccm - move cbcmac input off the stack
Commit f15f05b0a5de ("crypto: ccm - switch to separate cbcmac driver")
refactored the CCM driver to allow separate implementations of the
underlying MAC to be provided by a platform. However, in doing so, it
moved some data from the linear region to the stack, which violat... | 1 | static int crypto_ccm_auth(struct aead_request *req, struct scatterlist *plain,
unsigned int cryptlen)
{
struct crypto_ccm_req_priv_ctx *pctx = crypto_ccm_reqctx(req);
struct crypto_aead *aead = crypto_aead_reqtfm(req);
struct crypto_ccm_ctx *ctx = crypto_aead_ctx(aead);
AHASH_REQUEST_ON_STACK(ahreq, ctx->ma... | 161,394,947,663,770,550,000,000,000,000,000,000,000 | ccm.c | 52,708,401,148,709,490,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-8065 | crypto/ccm.c in the Linux kernel 4.9.x and 4.10.x through 4.10.12 interacts incorrectly with the CONFIG_VMAP_STACK option, which allows local users to cause a denial of service (system crash or memory corruption) or possibly have unspecified other impact by leveraging use of more than one virtual page for a DMA scatter... | https://nvd.nist.gov/vuln/detail/CVE-2017-8065 |
2,871 | linux | 005145378c9ad7575a01b6ce1ba118fb427f583a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/005145378c9ad7575a01b6ce1ba118fb427f583a | [media] dvb-usb-v2: avoid use-after-free
I ran into a stack frame size warning because of the on-stack copy of
the USB device structure:
drivers/media/usb/dvb-usb-v2/dvb_usb_core.c: In function 'dvb_usbv2_disconnect':
drivers/media/usb/dvb-usb-v2/dvb_usb_core.c:1029:1: error: the frame size of 1104 bytes is larger th... | 1 | void dvb_usbv2_disconnect(struct usb_interface *intf)
{
struct dvb_usb_device *d = usb_get_intfdata(intf);
const char *name = d->name;
struct device dev = d->udev->dev;
dev_dbg(&d->udev->dev, "%s: bInterfaceNumber=%d\n", __func__,
intf->cur_altsetting->desc.bInterfaceNumber);
if (d->props->exit)
d->pr... | 148,512,682,073,296,000,000,000,000,000,000,000,000 | dvb_usb_core.c | 230,411,649,417,370,660,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-8064 | drivers/media/usb/dvb-usb-v2/dvb_usb_core.c in the Linux kernel 4.9.x and 4.10.x before 4.10.12 interacts incorrectly with the CONFIG_VMAP_STACK option, which allows local users to cause a denial of service (system crash or memory corruption) or possibly have unspecified other impact by leveraging use of more than one ... | https://nvd.nist.gov/vuln/detail/CVE-2017-8064 |
2,872 | linux | 3f190e3aec212fc8c61e202c51400afa7384d4bc | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/3f190e3aec212fc8c61e202c51400afa7384d4bc | [media] cxusb: Use a dma capable buffer also for reading
Commit 17ce039b4e54 ("[media] cxusb: don't do DMA on stack")
added a kmalloc'ed bounce buffer for writes, but missed to do the same
for reads. As the read only happens after the write is finished, we can
reuse the same buffer.
As dvb_usb_generic_rw handles a re... | 1 | static int cxusb_ctrl_msg(struct dvb_usb_device *d,
u8 cmd, u8 *wbuf, int wlen, u8 *rbuf, int rlen)
{
struct cxusb_state *st = d->priv;
int ret, wo;
if (1 + wlen > MAX_XFER_SIZE) {
warn("i2c wr: len=%d is too big!\n", wlen);
return -EOPNOTSUPP;
}
wo = (rbuf == NULL || rlen == 0); /* write-only ... | 94,634,085,436,169,420,000,000,000,000,000,000,000 | cxusb.c | 106,348,669,266,247,720,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-8063 | drivers/media/usb/dvb-usb/cxusb.c in the Linux kernel 4.9.x and 4.10.x before 4.10.12 interacts incorrectly with the CONFIG_VMAP_STACK option, which allows local users to cause a denial of service (system crash) or possibly have unspecified other impact by leveraging use of more than one virtual page for a DMA scatterl... | https://nvd.nist.gov/vuln/detail/CVE-2017-8063 |
2,878 | linux | 67b0503db9c29b04eadfeede6bebbfe5ddad94ef | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/67b0503db9c29b04eadfeede6bebbfe5ddad94ef | [media] dvb-usb-firmware: don't do DMA on stack
The buffer allocation for the firmware data was changed in
commit 43fab9793c1f ("[media] dvb-usb: don't use stack for firmware load")
but the same applies for the reset value.
Fixes: 43fab9793c1f ("[media] dvb-usb: don't use stack for firmware load")
Cc: stable@vger.ker... | 1 | int usb_cypress_load_firmware(struct usb_device *udev, const struct firmware *fw, int type)
{
struct hexline *hx;
u8 reset;
int ret,pos=0;
hx = kmalloc(sizeof(*hx), GFP_KERNEL);
if (!hx)
return -ENOMEM;
/* stop the CPU */
reset = 1;
if ((ret = usb_cypress_writemem(udev,cypress[type].cpu_cs_register,&... | 176,821,963,037,391,380,000,000,000,000,000,000,000 | dvb-usb-firmware.c | 64,285,303,903,213,470,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-8061 | drivers/media/usb/dvb-usb/dvb-usb-firmware.c in the Linux kernel 4.9.x and 4.10.x before 4.10.7 interacts incorrectly with the CONFIG_VMAP_STACK option, which allows local users to cause a denial of service (system crash or memory corruption) or possibly have unspecified other impact by leveraging use of more than one ... | https://nvd.nist.gov/vuln/detail/CVE-2017-8061 |
2,879 | imageworsener | ca3356eb49fee03e2eaf6b6aff826988c1122d93 | https://github.com/jsummers/imageworsener | https://github.com/jsummers/imageworsener/commit/ca3356eb49fee03e2eaf6b6aff826988c1122d93 | Fixed a GIF decoding bug (divide by zero)
Fixes issue #15 | 1 | static int iwgif_read_image(struct iwgifrcontext *rctx)
{
int retval=0;
struct lzwdeccontext d;
size_t subblocksize;
int has_local_ct;
int local_ct_size;
unsigned int root_codesize;
if(!iwgif_read(rctx,rctx->rbuf,9)) goto done;
rctx->image_left = (int)iw_get_ui16le(&rctx->rbuf[0]);
rctx->image_top = (int)iw... | 221,178,602,343,877,060,000,000,000,000,000,000,000 | None | null | [
"CWE-369"
] | CVE-2017-7962 | The iwgif_read_image function in imagew-gif.c in libimageworsener.a in ImageWorsener 1.3.0 allows remote attackers to cause a denial of service (divide-by-zero error and application crash) via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2017-7962 |
2,886 | linux | 13bf9fbff0e5e099e2b6f003a0ab8ae145436309 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/13bf9fbff0e5e099e2b6f003a0ab8ae145436309 | nfsd: stricter decoding of write-like NFSv2/v3 ops
The NFSv2/v3 code does not systematically check whether we decode past
the end of the buffer. This generally appears to be harmless, but there
are a few places where we do arithmetic on the pointers involved and
don't account for the possibility that a length could b... | 1 | nfssvc_decode_writeargs(struct svc_rqst *rqstp, __be32 *p,
struct nfsd_writeargs *args)
{
unsigned int len, hdr, dlen;
struct kvec *head = rqstp->rq_arg.head;
int v;
p = decode_fh(p, &args->fh);
if (!p)
return 0;
p++; /* beginoffset */
args->offset = ntohl(*p++); /* offset */
p++; /* totalcount *... | 130,270,113,193,931,700,000,000,000,000,000,000,000 | nfsxdr.c | 273,111,468,959,666,900,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-7895 | The NFSv2 and NFSv3 server implementations in the Linux kernel through 4.10.13 lack certain checks for the end of a buffer, which allows remote attackers to trigger pointer-arithmetic errors or possibly have unspecified other impact via crafted requests, related to fs/nfsd/nfs3xdr.c and fs/nfsd/nfsxdr.c. | https://nvd.nist.gov/vuln/detail/CVE-2017-7895 |
2,887 | linux | a4866aa812518ed1a37d8ea0c881dc946409de94 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a4866aa812518ed1a37d8ea0c881dc946409de94 | mm: Tighten x86 /dev/mem with zeroing reads
Under CONFIG_STRICT_DEVMEM, reading System RAM through /dev/mem is
disallowed. However, on x86, the first 1MB was always allowed for BIOS
and similar things, regardless of it actually being System RAM. It was
possible for heap to end up getting allocated in low 1MB RAM, and ... | 1 | int devmem_is_allowed(unsigned long pagenr)
{
if (pagenr < 256)
return 1;
if (iomem_is_exclusive(pagenr << PAGE_SHIFT))
return 0;
if (!page_is_ram(pagenr))
return 1;
return 0;
}
| 205,621,365,268,399,100,000,000,000,000,000,000,000 | init.c | 183,327,595,980,331,130,000,000,000,000,000,000,000 | [
"CWE-732"
] | CVE-2017-7889 | The mm subsystem in the Linux kernel through 3.2 does not properly enforce the CONFIG_STRICT_DEVMEM protection mechanism, which allows local users to read or write to kernel memory locations in the first megabyte (and bypass slab-allocation access restrictions) via an application that opens the /dev/mem file, related t... | https://nvd.nist.gov/vuln/detail/CVE-2017-7889 |
2,890 | feh | f7a547b7ef8fc8ebdeaa4c28515c9d72e592fb6d | https://github.com/derf/feh | https://github.com/derf/feh/commit/f7a547b7ef8fc8ebdeaa4c28515c9d72e592fb6d | Fix double-free/OOB-write while receiving IPC data
If a malicious client pretends to be the E17 window manager, it is
possible to trigger an out of boundary heap write while receiving an
IPC message.
The length of the already received message is stored in an unsigned
short, which overflows after receiving 64 KB of da... | 1 | char *enl_ipc_get(const char *msg_data)
{
static char *message = NULL;
static unsigned short len = 0;
char buff[13], *ret_msg = NULL;
register unsigned char i;
unsigned char blen;
if (msg_data == IPC_TIMEOUT) {
return(IPC_TIMEOUT);
}
for (i = 0; i < 12; i++) {
buff[i] = msg_data[i];
}
buff[12] = 0... | 60,648,109,727,763,895,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2017-7875 | In wallpaper.c in feh before v2.18.3, if a malicious client pretends to be the E17 window manager, it is possible to trigger an out-of-boundary heap write while receiving an IPC message. An integer overflow leads to a buffer overflow and/or a double free. | https://nvd.nist.gov/vuln/detail/CVE-2017-7875 |
2,891 | FFmpeg | e371f031b942d73e02c090170975561fabd5c264 | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/e371f031b942d73e02c090170975561fabd5c264 | avcodec/pngdec: Fix off by 1 size in decode_zbuf()
Fixes out of array access
Fixes: 444/fuzz-2-ffmpeg_VIDEO_AV_CODEC_ID_PNG_fuzzer
Found-by: continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/targets/ffmpeg
Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> | 1 | static int decode_zbuf(AVBPrint *bp, const uint8_t *data,
const uint8_t *data_end)
{
z_stream zstream;
unsigned char *buf;
unsigned buf_size;
int ret;
zstream.zalloc = ff_png_zalloc;
zstream.zfree = ff_png_zfree;
zstream.opaque = NULL;
if (inflateInit(&zstream) !... | 228,936,594,929,323,730,000,000,000,000,000,000,000 | pngdec.c | 41,085,005,464,758,127,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2017-7866 | FFmpeg before 2017-01-23 has an out-of-bounds write caused by a stack-based buffer overflow related to the decode_zbuf function in libavcodec/pngdec.c. | https://nvd.nist.gov/vuln/detail/CVE-2017-7866 |
2,892 | FFmpeg | e477f09d0b3619f3d29173b2cd593e17e2d1978e | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/e477f09d0b3619f3d29173b2cd593e17e2d1978e | avcodec/pngdec: Check trns more completely
Fixes out of array access
Fixes: 546/clusterfuzz-testcase-4809433909559296
Found-by: continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/targets/ffmpeg
Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> | 1 | static int decode_frame_common(AVCodecContext *avctx, PNGDecContext *s,
AVFrame *p, AVPacket *avpkt)
{
AVDictionary *metadata = NULL;
uint32_t tag, length;
int decode_next_dat = 0;
int ret;
for (;;) {
length = bytestream2_get_bytes_left(&s->gb);
if (l... | 274,328,107,409,287,370,000,000,000,000,000,000,000 | pngdec.c | 106,174,170,009,033,120,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2017-7863 | FFmpeg before 2017-02-04 has an out-of-bounds write caused by a heap-based buffer overflow related to the decode_frame_common function in libavcodec/pngdec.c. | https://nvd.nist.gov/vuln/detail/CVE-2017-7863 |
2,894 | radare2 | d2632f6483a3ceb5d8e0a5fb11142c51c43978b4 | https://github.com/radare/radare2 | https://github.com/radare/radare2/commit/d2632f6483a3ceb5d8e0a5fb11142c51c43978b4 | Fix crash in fuzzed wasm r2_hoobr_consume_init_expr | 1 | static size_t consume_init_expr (ut8 *buf, ut8 *max, ut8 eoc, void *out, ut32 *offset) {
ut32 i = 0;
while (buf + i < max && buf[i] != eoc) {
i += 1;
}
if (buf[i] != eoc) {
return 0;
}
if (offset) {
*offset += i + 1;
}
return i + 1;
}
| 84,335,932,977,894,030,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2017-7854 | The consume_init_expr function in wasm.c in radare2 1.3.0 allows remote attackers to cause a denial of service (heap-based buffer over-read and application crash) via a crafted Web Assembly file. | https://nvd.nist.gov/vuln/detail/CVE-2017-7854 |
2,897 | libsndfile | 60b234301adf258786d8b90be5c1d437fc8799e0 | https://github.com/erikd/libsndfile | https://github.com/erikd/libsndfile/commit/60b234301adf258786d8b90be5c1d437fc8799e0 | src/flac.c: Improve error handling
Especially when dealing with corrupt or malicious files. | 1 | flac_buffer_copy (SF_PRIVATE *psf)
{ FLAC_PRIVATE* pflac = (FLAC_PRIVATE*) psf->codec_data ;
const FLAC__Frame *frame = pflac->frame ;
const int32_t* const *buffer = pflac->wbuffer ;
unsigned i = 0, j, offset, channels, len ;
/*
** frame->header.blocksize is variable and we're using a constant blocksize
** of FL... | 89,983,668,964,280,690,000,000,000,000,000,000,000 | flac.c | 74,586,289,804,404,630,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-7585 | In libsndfile before 1.0.28, an error in the "flac_buffer_copy()" function (flac.c) can be exploited to cause a stack-based buffer overflow via a specially crafted FLAC file. | https://nvd.nist.gov/vuln/detail/CVE-2017-7585 |
2,899 | linux | e6838a29ecb484c97e4efef9429643b9851fba6e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e6838a29ecb484c97e4efef9429643b9851fba6e | nfsd: check for oversized NFSv2/v3 arguments
A client can append random data to the end of an NFSv2 or NFSv3 RPC call
without our complaining; we'll just stop parsing at the end of the
expected data and ignore the rest.
Encoded arguments and replies are stored together in an array of pages,
and if a call is too large... | 1 | nfsd_dispatch(struct svc_rqst *rqstp, __be32 *statp)
{
struct svc_procedure *proc;
kxdrproc_t xdr;
__be32 nfserr;
__be32 *nfserrp;
dprintk("nfsd_dispatch: vers %d proc %d\n",
rqstp->rq_vers, rqstp->rq_proc);
proc = rqstp->rq_procinfo;
/*
* Give the xdr decoder a chance to change this if it wa... | 205,869,635,902,889,700,000,000,000,000,000,000,000 | nfssvc.c | 20,448,023,932,971,708,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2017-7645 | The NFSv2/NFSv3 server in the nfsd subsystem in the Linux kernel through 4.10.11 allows remote attackers to cause a denial of service (system crash) via a long RPC reply, related to net/sunrpc/svc.c, fs/nfsd/nfs3xdr.c, and fs/nfsd/nfsxdr.c. | https://nvd.nist.gov/vuln/detail/CVE-2017-7645 |
2,902 | libsndfile | f457b7b5ecfe91697ed01cfc825772c4d8de1236 | https://github.com/erikd/libsndfile | https://github.com/erikd/libsndfile/commit/f457b7b5ecfe91697ed01cfc825772c4d8de1236 | src/id3.c : Improve error handling | 1 | id3_skip (SF_PRIVATE * psf)
{ unsigned char buf [10] ;
memset (buf, 0, sizeof (buf)) ;
psf_binheader_readf (psf, "pb", 0, buf, 10) ;
if (buf [0] == 'I' && buf [1] == 'D' && buf [2] == '3')
{ int offset = buf [6] & 0x7f ;
offset = (offset << 7) | (buf [7] & 0x7f) ;
offset = (offset << 7) | (buf [8] & 0x7f) ;
... | 72,220,393,470,780,400,000,000,000,000,000,000,000 | id3.c | 5,429,618,960,530,921,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-7586 | In libsndfile before 1.0.28, an error in the "header_read()" function (common.c) when handling ID3 tags can be exploited to cause a stack-based buffer overflow via a specially crafted FLAC file. | https://nvd.nist.gov/vuln/detail/CVE-2017-7586 |
2,903 | linux | 6399f1fae4ec29fab5ec76070435555e256ca3a6 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6399f1fae4ec29fab5ec76070435555e256ca3a6 | ipv6: avoid overflow of offset in ip6_find_1stfragopt
In some cases, offset can overflow and can cause an infinite loop in
ip6_find_1stfragopt(). Make it unsigned int to prevent the overflow, and
cap it at IPV6_MAXPLEN, since packets larger than that should be invalid.
This problem has been here since before the begi... | 1 | int ip6_find_1stfragopt(struct sk_buff *skb, u8 **nexthdr)
{
u16 offset = sizeof(struct ipv6hdr);
unsigned int packet_len = skb_tail_pointer(skb) -
skb_network_header(skb);
int found_rhdr = 0;
*nexthdr = &ipv6_hdr(skb)->nexthdr;
while (offset <= packet_len) {
struct ipv6_opt_hdr *exthdr;
switch ... | 326,175,448,375,358,240,000,000,000,000,000,000,000 | output_core.c | 30,941,489,126,421,635,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2017-7542 | The ip6_find_1stfragopt function in net/ipv6/output_core.c in the Linux kernel through 4.12.3 allows local users to cause a denial of service (integer overflow and infinite loop) by leveraging the ability to open a raw socket. | https://nvd.nist.gov/vuln/detail/CVE-2017-7542 |
2,904 | linux | 8f44c9a41386729fea410e688959ddaa9d51be7c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8f44c9a41386729fea410e688959ddaa9d51be7c | brcmfmac: fix possible buffer overflow in brcmf_cfg80211_mgmt_tx()
The lower level nl80211 code in cfg80211 ensures that "len" is between
25 and NL80211_ATTR_FRAME (2304). We subtract DOT11_MGMT_HDR_LEN (24) from
"len" so thats's max of 2280. However, the action_frame->data[] buffer is
only BRCMF_FIL_ACTION_FRAME_SI... | 1 | brcmf_cfg80211_mgmt_tx(struct wiphy *wiphy, struct wireless_dev *wdev,
struct cfg80211_mgmt_tx_params *params, u64 *cookie)
{
struct brcmf_cfg80211_info *cfg = wiphy_to_cfg(wiphy);
struct ieee80211_channel *chan = params->chan;
const u8 *buf = params->buf;
size_t len = params->len;
const struct ieee80211_... | 43,745,744,403,145,920,000,000,000,000,000,000,000 | cfg80211.c | 271,021,627,446,521,250,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-7541 | The brcmf_cfg80211_mgmt_tx function in drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c in the Linux kernel before 4.12.3 allows local users to cause a denial of service (buffer overflow and system crash) or possibly gain privileges via a crafted NL80211_CMD_FRAME Netlink packet. | https://nvd.nist.gov/vuln/detail/CVE-2017-7541 |
2,906 | linux | 49d31c2f389acfe83417083e1208422b4091cd9e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/49d31c2f389acfe83417083e1208422b4091cd9e | dentry name snapshots
take_dentry_name_snapshot() takes a safe snapshot of dentry name;
if the name is a short one, it gets copied into caller-supplied
structure, otherwise an extra reference to external name is grabbed
(those are never modified). In either case the pointer to stable
string is stored into the same st... | 1 | int vfs_rename(struct inode *old_dir, struct dentry *old_dentry,
struct inode *new_dir, struct dentry *new_dentry,
struct inode **delegated_inode, unsigned int flags)
{
int error;
bool is_dir = d_is_dir(old_dentry);
const unsigned char *old_name;
struct inode *source = old_dentry->d_inode;
str... | 3,742,682,420,476,444,700,000,000,000,000,000,000 | namei.c | 197,616,719,765,189,360,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2017-7533 | Race condition in the fsnotify implementation in the Linux kernel through 4.12.4 allows local users to gain privileges or cause a denial of service (memory corruption) via a crafted application that leverages simultaneous execution of the inotify_handle_event and vfs_rename functions. | https://nvd.nist.gov/vuln/detail/CVE-2017-7533 |
2,911 | linux | ee0d8d8482345ff97a75a7d747efc309f13b0d80 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ee0d8d8482345ff97a75a7d747efc309f13b0d80 | ipx: call ipxitf_put() in ioctl error path
We should call ipxitf_put() if the copy_to_user() fails.
Reported-by: 李强 <liqiang6-s@360.cn>
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: David S. Miller <davem@davemloft.net> | 1 | static int ipxitf_ioctl(unsigned int cmd, void __user *arg)
{
int rc = -EINVAL;
struct ifreq ifr;
int val;
switch (cmd) {
case SIOCSIFADDR: {
struct sockaddr_ipx *sipx;
struct ipx_interface_definition f;
rc = -EFAULT;
if (copy_from_user(&ifr, arg, sizeof(ifr)))
break;
sipx = (struct sockaddr_ipx *)&... | 171,185,150,646,835,850,000,000,000,000,000,000,000 | af_ipx.c | 45,846,410,308,896,070,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2017-7487 | The ipxitf_ioctl function in net/ipx/af_ipx.c in the Linux kernel through 4.11.1 mishandles reference counts, which allows local users to cause a denial of service (use-after-free) or possibly have unspecified other impact via a failed SIOCGIFADDR ioctl call for an IPX interface. | https://nvd.nist.gov/vuln/detail/CVE-2017-7487 |
2,912 | linux | c9f838d104fed6f2f61d68164712e3204bf5271b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c9f838d104fed6f2f61d68164712e3204bf5271b | KEYS: fix keyctl_set_reqkey_keyring() to not leak thread keyrings
This fixes CVE-2017-7472.
Running the following program as an unprivileged user exhausts kernel
memory by leaking thread keyrings:
#include <keyutils.h>
int main()
{
for (;;)
keyctl_set_reqkey_keyring(KEY_REQKEY_DEFL_THREAD_KEYRING);
}
Fix ... | 1 | long keyctl_set_reqkey_keyring(int reqkey_defl)
{
struct cred *new;
int ret, old_setting;
old_setting = current_cred_xxx(jit_keyring);
if (reqkey_defl == KEY_REQKEY_DEFL_NO_CHANGE)
return old_setting;
new = prepare_creds();
if (!new)
return -ENOMEM;
switch (reqkey_defl) {
case KEY_REQKEY_DEFL_THREAD_K... | 284,639,174,361,900,800,000,000,000,000,000,000,000 | keyctl.c | 278,644,936,964,768,320,000,000,000,000,000,000,000 | [
"CWE-404"
] | CVE-2017-7472 | The KEYS subsystem in the Linux kernel before 4.10.13 allows local users to cause a denial of service (memory consumption) via a series of KEY_REQKEY_DEFL_THREAD_KEYRING keyctl_set_reqkey_keyring calls. | https://nvd.nist.gov/vuln/detail/CVE-2017-7472 |
2,916 | proftpd | 349addc3be4fcdad9bd4ec01ad1ccd916c898ed8 | https://github.com/proftpd/proftpd | https://github.com/proftpd/proftpd/commit/349addc3be4fcdad9bd4ec01ad1ccd916c898ed8 | Walk the entire DefaultRoot path, checking for symlinks of any component,
when AllowChrootSymlinks is disabled. | 1 | static int get_default_root(pool *p, int allow_symlinks, const char **root) {
config_rec *c = NULL;
const char *dir = NULL;
int res;
c = find_config(main_server->conf, CONF_PARAM, "DefaultRoot", FALSE);
while (c != NULL) {
pr_signals_handle();
/* Check the groups acl */
if (c->argc < 2) {
... | 329,129,884,821,134,700,000,000,000,000,000,000,000 | mod_auth.c | 155,904,831,524,822,930,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2017-7418 | ProFTPD before 1.3.5e and 1.3.6 before 1.3.6rc5 controls whether the home directory of a user could contain a symbolic link through the AllowChrootSymlinks configuration option, but checks only the last path component when enforcing AllowChrootSymlinks. Attackers with local access could bypass the AllowChrootSymlinks c... | https://nvd.nist.gov/vuln/detail/CVE-2017-7418 |
2,923 | radare2 | 7ab66cca5bbdf6cb2d69339ef4f513d95e532dbf | https://github.com/radare/radare2 | https://github.com/radare/radare2/commit/7ab66cca5bbdf6cb2d69339ef4f513d95e532dbf | Fix #7152 - Null deref in cms | 1 | RCMS *r_pkcs7_parse_cms (const ut8 *buffer, ut32 length) {
RASN1Object *object;
RCMS *container;
if (!buffer || !length) {
return NULL;
}
container = R_NEW0 (RCMS);
if (!container) {
return NULL;
}
object = r_asn1_create_object (buffer, length);
if (!object || object->list.length != 2 || !object->list.o... | 137,332,301,054,576,720,000,000,000,000,000,000,000 | r_pkcs7.c | 308,198,352,120,592,400,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-7274 | The r_pkcs7_parse_cms function in libr/util/r_pkcs7.c in radare2 1.3.0 allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted PE file. | https://nvd.nist.gov/vuln/detail/CVE-2017-7274 |
2,924 | linux | 1ebb71143758f45dc0fa76e2f48429e13b16d110 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1ebb71143758f45dc0fa76e2f48429e13b16d110 | HID: hid-cypress: validate length of report
Make sure we have enough of a report structure to validate before
looking at it.
Reported-by: Benoit Camredon <benoit.camredon@airbus.com>
Tested-by: Benoit Camredon <benoit.camredon@airbus.com>
Cc: stable <stable@vger.kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@l... | 1 | static __u8 *cp_report_fixup(struct hid_device *hdev, __u8 *rdesc,
unsigned int *rsize)
{
unsigned long quirks = (unsigned long)hid_get_drvdata(hdev);
unsigned int i;
if (!(quirks & CP_RDESC_SWAPPED_MIN_MAX))
return rdesc;
for (i = 0; i < *rsize - 4; i++)
if (rdesc[i] == 0x29 && rdesc[i + 2] == 0x19) {... | 312,370,685,237,397,730,000,000,000,000,000,000,000 | hid-cypress.c | 110,245,277,823,408,490,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2017-7273 | The cp_report_fixup function in drivers/hid/hid-cypress.c in the Linux kernel 3.2 and 4.x before 4.9.4 allows physically proximate attackers to cause a denial of service (integer underflow) or possibly have unspecified other impact via a crafted HID report. | https://nvd.nist.gov/vuln/detail/CVE-2017-7273 |
2,925 | linux | f843ee6dd019bcece3e74e76ad9df0155655d0df | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f843ee6dd019bcece3e74e76ad9df0155655d0df | xfrm_user: validate XFRM_MSG_NEWAE incoming ESN size harder
Kees Cook has pointed out that xfrm_replay_state_esn_len() is subject to
wrapping issues. To ensure we are correctly ensuring that the two ESN
structures are the same size compare both the overall size as reported
by xfrm_replay_state_esn_len() and the inter... | 1 | static inline int xfrm_replay_verify_len(struct xfrm_replay_state_esn *replay_esn,
struct nlattr *rp)
{
struct xfrm_replay_state_esn *up;
int ulen;
if (!replay_esn || !rp)
return 0;
up = nla_data(rp);
ulen = xfrm_replay_state_esn_len(up);
if (nla_len(rp) < ulen || xfrm_replay_state_esn_len(replay_es... | 134,565,758,832,959,560,000,000,000,000,000,000,000 | xfrm_user.c | 126,956,852,781,034,030,000,000,000,000,000,000,000 | [
"CWE-284"
] | CVE-2017-7184 | The xfrm_replay_verify_len function in net/xfrm/xfrm_user.c in the Linux kernel through 4.10.6 does not validate certain size data after an XFRM_MSG_NEWAE update, which allows local users to obtain root privileges or cause a denial of service (heap-based out-of-bounds access) by leveraging the CAP_NET_ADMIN capability,... | https://nvd.nist.gov/vuln/detail/CVE-2017-7184 |
2,941 | LibRaw-demosaic-pack-GPL2 | 194f592e205990ea8fce72b6c571c14350aca716 | https://github.com/LibRaw/LibRaw-demosaic-pack-GPL2 | https://github.com/LibRaw/LibRaw-demosaic-pack-GPL2/commit/194f592e205990ea8fce72b6c571c14350aca716 | Fixed possible foveon buffer overrun (Secunia SA750000) | 1 | void CLASS foveon_load_camf()
{
unsigned type, wide, high, i, j, row, col, diff;
ushort huff[258], vpred[2][2] = {{512,512},{512,512}}, hpred[2];
fseek (ifp, meta_offset, SEEK_SET);
type = get4(); get4(); get4();
wide = get4();
high = get4();
if (type == 2) {
fread (meta_data, 1, meta_len... | 256,409,674,907,308,300,000,000,000,000,000,000,000 | dcraw_foveon.c | 125,246,949,532,026,940,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-6890 | A boundary error within the "foveon_load_camf()" function (dcraw_foveon.c) when initializing a huffman table in LibRaw-demosaic-pack-GPL2 before 0.18.2 can be exploited to cause a stack-based buffer overflow. | https://nvd.nist.gov/vuln/detail/CVE-2017-6890 |
2,942 | linux | 040757f738e13caaa9c5078bca79aa97e11dde88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/040757f738e13caaa9c5078bca79aa97e11dde88 | ucount: Remove the atomicity from ucount->count
Always increment/decrement ucount->count under the ucounts_lock. The
increments are there already and moving the decrements there means the
locking logic of the code is simpler. This simplification in the
locking logic fixes a race between put_ucounts and get_ucounts t... | 1 | static struct ucounts *get_ucounts(struct user_namespace *ns, kuid_t uid)
{
struct hlist_head *hashent = ucounts_hashentry(ns, uid);
struct ucounts *ucounts, *new;
spin_lock_irq(&ucounts_lock);
ucounts = find_ucounts(ns, uid, hashent);
if (!ucounts) {
spin_unlock_irq(&ucounts_lock);
new = kzalloc(sizeof(*new... | 171,561,312,948,769,470,000,000,000,000,000,000,000 | ucount.c | 48,367,944,907,307,025,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2017-6874 | Race condition in kernel/ucount.c in the Linux kernel through 4.10.2 allows local users to cause a denial of service (use-after-free and system crash) or possibly have unspecified other impact via crafted system calls that leverage certain decrement behavior that causes incorrect interaction between put_ucounts and get... | https://nvd.nist.gov/vuln/detail/CVE-2017-6874 |
2,943 | linux | 040757f738e13caaa9c5078bca79aa97e11dde88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/040757f738e13caaa9c5078bca79aa97e11dde88 | ucount: Remove the atomicity from ucount->count
Always increment/decrement ucount->count under the ucounts_lock. The
increments are there already and moving the decrements there means the
locking logic of the code is simpler. This simplification in the
locking logic fixes a race between put_ucounts and get_ucounts t... | 1 | static void put_ucounts(struct ucounts *ucounts)
{
unsigned long flags;
if (atomic_dec_and_test(&ucounts->count)) {
spin_lock_irqsave(&ucounts_lock, flags);
hlist_del_init(&ucounts->node);
spin_unlock_irqrestore(&ucounts_lock, flags);
kfree(ucounts);
}
}
| 275,296,759,605,816,550,000,000,000,000,000,000,000 | ucount.c | 48,367,944,907,307,025,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2017-6874 | Race condition in kernel/ucount.c in the Linux kernel through 4.10.2 allows local users to cause a denial of service (use-after-free and system crash) or possibly have unspecified other impact via crafted system calls that leverage certain decrement behavior that causes incorrect interaction between put_ucounts and get... | https://nvd.nist.gov/vuln/detail/CVE-2017-6874 |
2,955 | ImageMagick | 126c7c98ea788241922c30df4a5633ea692cf8df | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/126c7c98ea788241922c30df4a5633ea692cf8df | None | 1 | static Image *ReadWEBPImage(const ImageInfo *image_info,
ExceptionInfo *exception)
{
Image
*image;
int
webp_status;
MagickBooleanType
status;
register unsigned char
*p;
size_t
length;
ssize_t
count,
y;
unsigned char
header[12],
*stream;
WebPDecoderConfig
... | 300,565,529,183,679,020,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2017-6502 | An issue was discovered in ImageMagick 6.9.7. A specially crafted webp file could lead to a file-descriptor leak in libmagickcore (thus, a DoS). | https://nvd.nist.gov/vuln/detail/CVE-2017-6502 |
2,956 | ImageMagick | d31fec57e9dfb0516deead2053a856e3c71e9751 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/d31fec57e9dfb0516deead2053a856e3c71e9751 | None | 1 | static Image *ReadXCFImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
char
magick[14];
Image
*image;
int
foundPropEnd = 0;
MagickBooleanType
status;
MagickOffsetType
offset;
register ssize_t
i;
size_t
image_type,
length;
ssize_t
count;
XCFDocInf... | 121,445,273,043,908,960,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2017-6501 | An issue was discovered in ImageMagick 6.9.7. A specially crafted xcf file could lead to a NULL pointer dereference. | https://nvd.nist.gov/vuln/detail/CVE-2017-6501 |
2,957 | ImageMagick | 3007531bfd326c5c1e29cd41d2cd80c166de8528 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/3007531bfd326c5c1e29cd41d2cd80c166de8528 | None | 1 | static Image *ReadSUNImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
#define RMT_EQUAL_RGB 1
#define RMT_NONE 0
#define RMT_RAW 2
#define RT_STANDARD 1
#define RT_ENCODED 2
#define RT_FORMAT_RGB 3
typedef struct _SUNInfo
{
unsigned int
magic,
width,
height,
depth,
... | 70,149,318,854,072,030,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2017-6500 | An issue was discovered in ImageMagick 6.9.7. A specially crafted sun file triggers a heap-based buffer over-read. | https://nvd.nist.gov/vuln/detail/CVE-2017-6500 |
2,958 | ImageMagick | 7f2dc7a1afc067d0c89f12c82bcdec0445fb1b94 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/7f2dc7a1afc067d0c89f12c82bcdec0445fb1b94 | None | 1 | static MagickBooleanType ReadPSDChannel(Image *image,
const ImageInfo *image_info,const PSDInfo *psd_info,LayerInfo* layer_info,
const size_t channel,const PSDCompressionType compression,
ExceptionInfo *exception)
{
Image
*channel_image,
*mask;
MagickOffsetType
offset;
MagickBooleanType
st... | 117,570,474,827,984,470,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2017-6497 | An issue was discovered in ImageMagick 6.9.7. A specially crafted psd file could lead to a NULL pointer dereference (thus, a DoS). | https://nvd.nist.gov/vuln/detail/CVE-2017-6497 |
2,959 | libplist | 32ee5213fe64f1e10ec76c1ee861ee6f233120dd | https://github.com/libimobiledevice/libplist | https://github.com/libimobiledevice/libplist/commit/32ee5213fe64f1e10ec76c1ee861ee6f233120dd | bplist: Fix data range check for string/data/dict/array nodes
Passing a size of 0xFFFFFFFFFFFFFFFF to parse_string_node() might result
in a memcpy with a size of -1, leading to undefined behavior.
This commit makes sure that the actual node data (which depends on the size)
is in the range start_of_object..start_of_obj... | 1 | static plist_t parse_bin_node(struct bplist_data *bplist, const char** object)
{
uint16_t type = 0;
uint64_t size = 0;
if (!object)
return NULL;
type = (**object) & BPLIST_MASK;
size = (**object) & BPLIST_FILL;
(*object)++;
if (size == BPLIST_FILL) {
switch (type) {
... | 107,766,688,895,305,960,000,000,000,000,000,000,000 | bplist.c | 174,307,687,247,168,460,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2017-6436 | The parse_string_node function in bplist.c in libimobiledevice libplist 1.12 allows local users to cause a denial of service (memory allocation error) via a crafted plist file. | https://nvd.nist.gov/vuln/detail/CVE-2017-6436 |
2,960 | libplist | fbd8494d5e4e46bf2e90cb6116903e404374fb56 | https://github.com/libimobiledevice/libplist | https://github.com/libimobiledevice/libplist/commit/fbd8494d5e4e46bf2e90cb6116903e404374fb56 | bplist: Make sure to bail out if malloc() fails in parse_string_node()
Credit to Wang Junjie <zhunkibatu@gmail.com> (#93) | 1 | static plist_t parse_string_node(const char **bnode, uint64_t size)
{
plist_data_t data = plist_new_plist_data();
data->type = PLIST_STRING;
data->strval = (char *) malloc(sizeof(char) * (size + 1));
memcpy(data->strval, *bnode, size);
data->strval[size] = '\0';
data->length = strlen(data... | 231,582,573,904,587,900,000,000,000,000,000,000,000 | bplist.c | 177,494,911,893,507,770,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-6435 | The parse_string_node function in bplist.c in libimobiledevice libplist 1.12 allows local users to cause a denial of service (memory corruption) via a crafted plist file. | https://nvd.nist.gov/vuln/detail/CVE-2017-6435 |
2,961 | ettercap | 626dc56686f15f2dda13c48f78c2a666cb6d8506 | https://github.com/Ettercap/ettercap | https://github.com/LocutusOfBorg/ettercap/commit/626dc56686f15f2dda13c48f78c2a666cb6d8506 | Exit gracefully in case of corrupted filters (Closes issue #782) | 1 | size_t compile_tree(struct filter_op **fop)
{
int i = 1;
struct filter_op *array = NULL;
struct unfold_elm *ue;
BUG_IF(tree_root == NULL);
fprintf(stdout, " Unfolding the meta-tree ");
fflush(stdout);
/* start the recursion on the tree */
unfold_blk(&tree_root);
fprintf(stdou... | 311,024,811,689,886,400,000,000,000,000,000,000,000 | ef_compiler.c | 188,094,826,871,701,180,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-6430 | The compile_tree function in ef_compiler.c in the Etterfilter utility in Ettercap 0.8.2 and earlier allows remote attackers to cause a denial of service (out-of-bounds read) via a crafted filter. | https://nvd.nist.gov/vuln/detail/CVE-2017-6430 |
2,963 | tcpreplay | d689d14dbcd768c028eab2fb378d849e543dcfe9 | https://github.com/appneta/tcpreplay | https://github.com/appneta/tcpreplay/commit/d689d14dbcd768c028eab2fb378d849e543dcfe9 | #278 fail if capture has a packet that is too large (#286)
* #278 fail if capture has a packet that is too large
* Update CHANGELOG | 1 | main(int argc, char *argv[])
{
int i, fd, swapped, pkthdrlen, ret, optct, backwards, caplentoobig;
struct pcap_file_header pcap_fh;
struct pcap_pkthdr pcap_ph;
struct pcap_sf_patched_pkthdr pcap_patched_ph; /* Kuznetzov */
char buf[10000];
struct stat statinfo;
uint64_t pktcnt;
uint32_t ... | 38,007,024,114,931,970,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2017-6429 | Buffer overflow in the tcpcapinfo utility in Tcpreplay before 4.2.0 Beta 1 allows remote attackers to have unspecified impact via a pcap file with an over-size packet. | https://nvd.nist.gov/vuln/detail/CVE-2017-6429 |
2,966 | linux | 4c03b862b12f980456f9de92db6d508a4999b788 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4c03b862b12f980456f9de92db6d508a4999b788 | irda: Fix lockdep annotations in hashbin_delete().
A nested lock depth was added to the hasbin_delete() code but it
doesn't actually work some well and results in tons of lockdep splats.
Fix the code instead to properly drop the lock around the operation
and just keep peeking the head of the hashbin queue.
Reported-... | 1 | int hashbin_delete( hashbin_t* hashbin, FREE_FUNC free_func)
{
irda_queue_t* queue;
unsigned long flags = 0;
int i;
IRDA_ASSERT(hashbin != NULL, return -1;);
IRDA_ASSERT(hashbin->magic == HB_MAGIC, return -1;);
/* Synchronize */
if ( hashbin->hb_type & HB_LOCK ) {
spin_lock_irqsave_nested(&hashbin->hb_... | 206,634,777,008,621,900,000,000,000,000,000,000,000 | irqueue.c | 180,656,762,559,532,160,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2017-6348 | The hashbin_delete function in net/irda/irqueue.c in the Linux kernel before 4.9.13 improperly manages lock dropping, which allows local users to cause a denial of service (deadlock) via crafted operations on IrDA devices. | https://nvd.nist.gov/vuln/detail/CVE-2017-6348 |
2,967 | linux | ca4ef4574f1ee5252e2cd365f8f5d5bafd048f32 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ca4ef4574f1ee5252e2cd365f8f5d5bafd048f32 | ip: fix IP_CHECKSUM handling
The skbs processed by ip_cmsg_recv() are not guaranteed to
be linear e.g. when sending UDP packets over loopback with
MSGMORE.
Using csum_partial() on [potentially] the whole skb len
is dangerous; instead be on the safe side and use skb_checksum().
Thanks to syzkaller team to detect the i... | 1 | static void ip_cmsg_recv_checksum(struct msghdr *msg, struct sk_buff *skb,
int tlen, int offset)
{
__wsum csum = skb->csum;
if (skb->ip_summed != CHECKSUM_COMPLETE)
return;
if (offset != 0)
csum = csum_sub(csum,
csum_partial(skb_transport_header(skb) + tlen,
offset, 0));
put_cmsg(msg... | 2,758,578,986,743,986,000,000,000,000,000,000,000 | ip_sockglue.c | 129,711,950,433,725,550,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-6347 | The ip_cmsg_recv_checksum function in net/ipv4/ip_sockglue.c in the Linux kernel before 4.10.1 has incorrect expectations about skb data layout, which allows local users to cause a denial of service (buffer over-read) or possibly have unspecified other impact via crafted system calls, as demonstrated by use of the MSG_... | https://nvd.nist.gov/vuln/detail/CVE-2017-6347 |
2,971 | tnef | 8dccf79857ceeb7a6d3e42c1e762e7b865d5344d | https://github.com/verdammelt/tnef | https://github.com/verdammelt/tnef/commit/8dccf79857ceeb7a6d3e42c1e762e7b865d5344d | Check types to avoid invalid reads/writes. | 1 | file_add_mapi_attrs (File* file, MAPI_Attr** attrs)
{
int i;
for (i = 0; attrs[i]; i++)
{
MAPI_Attr* a = attrs[i];
if (a->num_values)
{
switch (a->name)
{
case MAPI_ATTACH_LONG_FILENAME:
if (file->name) XFREE(file->name);
file->name = strdup( (char*)a->values[0].data.buf );
b... | 96,018,736,304,519,730,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2017-6309 | An issue was discovered in tnef before 1.4.13. Two type confusions have been identified in the parse_file() function. These might lead to invalid read and write operations, controlled by an attacker. | https://nvd.nist.gov/vuln/detail/CVE-2017-6309 |
2,973 | tnef | 8dccf79857ceeb7a6d3e42c1e762e7b865d5344d | https://github.com/verdammelt/tnef | https://github.com/verdammelt/tnef/commit/8dccf79857ceeb7a6d3e42c1e762e7b865d5344d | Check types to avoid invalid reads/writes. | 1 | parse_file (FILE* input_file, char* directory,
char *body_filename, char *body_pref,
int flags)
{
uint32 d;
uint16 key;
Attr *attr = NULL;
File *file = NULL;
int rtf_size = 0, html_size = 0;
MessageBody body;
memset (&body, '\0', sizeof (MessageBody));
/* store the program op... | 18,306,511,750,823,043,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2017-6309 | An issue was discovered in tnef before 1.4.13. Two type confusions have been identified in the parse_file() function. These might lead to invalid read and write operations, controlled by an attacker. | https://nvd.nist.gov/vuln/detail/CVE-2017-6309 |
2,980 | linux | ccf7abb93af09ad0868ae9033d1ca8108bdaec82 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ccf7abb93af09ad0868ae9033d1ca8108bdaec82 | tcp: avoid infinite loop in tcp_splice_read()
Splicing from TCP socket is vulnerable when a packet with URG flag is
received and stored into receive queue.
__tcp_splice_read() returns 0, and sk_wait_data() immediately
returns since there is the problematic skb in queue.
This is a nice way to burn cpu (aka infinite l... | 1 | ssize_t tcp_splice_read(struct socket *sock, loff_t *ppos,
struct pipe_inode_info *pipe, size_t len,
unsigned int flags)
{
struct sock *sk = sock->sk;
struct tcp_splice_state tss = {
.pipe = pipe,
.len = len,
.flags = flags,
};
long timeo;
ssize_t spliced;
int ret;
sock_rps_record_flow(sk);
/*
* ... | 191,298,991,681,737,000,000,000,000,000,000,000,000 | tcp.c | 168,008,675,481,430,550,000,000,000,000,000,000,000 | [
"CWE-835"
] | CVE-2017-6214 | The tcp_splice_read function in net/ipv4/tcp.c in the Linux kernel before 4.9.11 allows remote attackers to cause a denial of service (infinite loop and soft lockup) via vectors involving a TCP packet with the URG flag. | https://nvd.nist.gov/vuln/detail/CVE-2017-6214 |
2,982 | radare2 | 72794dc3523bbd5bb370de3c5857cb736c387e18 | https://github.com/radare/radare2 | https://github.com/radare/radare2/commit/72794dc3523bbd5bb370de3c5857cb736c387e18 | Fix #6829 oob write because of using wrong struct | 1 | static RList *relocs(RBinFile *arch) {
struct r_bin_bflt_obj *obj = (struct r_bin_bflt_obj*)arch->o->bin_obj;
RList *list = r_list_newf ((RListFree)free);
int i, len, n_got, amount;
if (!list || !obj) {
r_list_free (list);
return NULL;
}
if (obj->hdr->flags & FLAT_FLAG_GOTPIC) {
n_got = get_ngot_entries (ob... | 160,655,422,748,405,760,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2017-6194 | The relocs function in libr/bin/p/bin_bflt.c in radare2 1.2.1 allows remote attackers to cause a denial of service (heap-based buffer overflow and application crash) or possibly have unspecified other impact via a crafted binary file. | https://nvd.nist.gov/vuln/detail/CVE-2017-6194 |
2,984 | linux | 5edabca9d4cff7f1f2b68f0bac55ef99d9798ba4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/5edabca9d4cff7f1f2b68f0bac55ef99d9798ba4 | dccp: fix freeing skb too early for IPV6_RECVPKTINFO
In the current DCCP implementation an skb for a DCCP_PKT_REQUEST packet
is forcibly freed via __kfree_skb in dccp_rcv_state_process if
dccp_v6_conn_request successfully returns.
However, if IPV6_RECVPKTINFO is set on a socket, the address of the skb
is saved to ire... | 1 | int dccp_rcv_state_process(struct sock *sk, struct sk_buff *skb,
struct dccp_hdr *dh, unsigned int len)
{
struct dccp_sock *dp = dccp_sk(sk);
struct dccp_skb_cb *dcb = DCCP_SKB_CB(skb);
const int old_state = sk->sk_state;
int queued = 0;
/*
* Step 3: Process LISTEN state
*
* If S.state == LISTEN,... | 27,879,741,734,073,553,000,000,000,000,000,000,000 | input.c | 209,999,782,273,914,530,000,000,000,000,000,000,000 | [
"CWE-415"
] | CVE-2017-6074 | The dccp_rcv_state_process function in net/dccp/input.c in the Linux kernel through 4.9.11 mishandles DCCP_PKT_REQUEST packet data structures in the LISTEN state, which allows local users to obtain root privileges or cause a denial of service (double free) via an application that makes an IPV6_RECVPKTINFO setsockopt sy... | https://nvd.nist.gov/vuln/detail/CVE-2017-6074 |
2,985 | linux | 321027c1fe77f892f4ea07846aeae08cefbbb290 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/321027c1fe77f892f4ea07846aeae08cefbbb290 | perf/core: Fix concurrent sys_perf_event_open() vs. 'move_group' race
Di Shen reported a race between two concurrent sys_perf_event_open()
calls where both try and move the same pre-existing software group
into a hardware context.
The problem is exactly that described in commit:
f63a8daa5812 ("perf: Fix event->ctx... | 1 | SYSCALL_DEFINE5(perf_event_open,
struct perf_event_attr __user *, attr_uptr,
pid_t, pid, int, cpu, int, group_fd, unsigned long, flags)
{
struct perf_event *group_leader = NULL, *output_event = NULL;
struct perf_event *event, *sibling;
struct perf_event_attr attr;
struct perf_event_context *ctx, *uninitialized_... | 208,685,279,778,457,650,000,000,000,000,000,000,000 | core.c | 94,529,149,543,289,880,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2017-6001 | Race condition in kernel/events/core.c in the Linux kernel before 4.9.7 allows local users to gain privileges via a crafted application that makes concurrent perf_event_open system calls for moving a software group into a hardware context. NOTE: this vulnerability exists because of an incomplete fix for CVE-2016-6786. | https://nvd.nist.gov/vuln/detail/CVE-2017-6001 |
2,986 | lxc | 16af238036a5464ae8f2420ed3af214f0de875f9 | https://github.com/lxc/lxc | https://github.com/lxc/lxc/commit/16af238036a5464ae8f2420ed3af214f0de875f9 | CVE-2017-5985: Ensure target netns is caller-owned
Before this commit, lxc-user-nic could potentially have been tricked into
operating on a network namespace over which the caller did not hold privilege.
This commit ensures that the caller is privileged over the network namespace by
temporarily dropping privilege.
L... | 1 | static int rename_in_ns(int pid, char *oldname, char **newnamep)
{
int fd = -1, ofd = -1, ret, ifindex = -1;
bool grab_newname = false;
ofd = lxc_preserve_ns(getpid(), "net");
if (ofd < 0) {
fprintf(stderr, "Failed opening network namespace path for '%d'.", getpid());
return -1;
}
fd = lxc_preserve... | 146,498,421,034,155,620,000,000,000,000,000,000,000 | lxc_user_nic.c | 304,260,501,931,038,600,000,000,000,000,000,000,000 | [
"CWE-862"
] | CVE-2017-5985 | lxc-user-nic in Linux Containers (LXC) allows local users with a lxc-usernet allocation to create network interfaces on the host and choose the name of those interfaces by leveraging lack of netns ownership check. | https://nvd.nist.gov/vuln/detail/CVE-2017-5985 |
2,987 | linux | 34b2cef20f19c87999fff3da4071e66937db9644 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/34b2cef20f19c87999fff3da4071e66937db9644 | ipv4: keep skb->dst around in presence of IP options
Andrey Konovalov got crashes in __ip_options_echo() when a NULL skb->dst
is accessed.
ipv4_pktinfo_prepare() should not drop the dst if (evil) IP options
are present.
We could refine the test to the presence of ts_needtime or srr,
but IP options are not often used... | 1 | void ipv4_pktinfo_prepare(const struct sock *sk, struct sk_buff *skb)
{
struct in_pktinfo *pktinfo = PKTINFO_SKB_CB(skb);
bool prepare = (inet_sk(sk)->cmsg_flags & IP_CMSG_PKTINFO) ||
ipv6_sk_rxinfo(sk);
if (prepare && skb_rtable(skb)) {
/* skb->cb is overloaded: prior to this point it is IP{6}CB
* wh... | 35,518,848,998,638,900,000,000,000,000,000,000,000 | ip_sockglue.c | 174,240,548,531,368,950,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-5970 | The ipv4_pktinfo_prepare function in net/ipv4/ip_sockglue.c in the Linux kernel through 4.9.9 allows attackers to cause a denial of service (system crash) via (1) an application that makes crafted system calls or possibly (2) IPv4 traffic with invalid IP options. | https://nvd.nist.gov/vuln/detail/CVE-2017-5970 |
2,993 | gst-plugins-ugly | d21017b52a585f145e8d62781bcc1c5fefc7ee37 | https://github.com/GStreamer/gst-plugins-ugly | https://github.com/GStreamer/gst-plugins-ugly/commit/d21017b52a585f145e8d62781bcc1c5fefc7ee37 | asfdemux: Check that we have enough data available before parsing bool/uint extended content descriptors
https://bugzilla.gnome.org/show_bug.cgi?id=777955 | 1 | gst_asf_demux_process_ext_content_desc (GstASFDemux * demux, guint8 * data,
guint64 size)
{
/* Other known (and unused) 'text/unicode' metadata available :
*
* WM/Lyrics =
* WM/MediaPrimaryClassID = {D1607DBC-E323-4BE2-86A1-48A42A28441E}
* WMFSDKVersion = 9.00.00.2980
* WMFSDKNeeded = 0.0.0... | 306,631,311,044,549,150,000,000,000,000,000,000,000 | gstasfdemux.c | 57,664,672,486,925,360,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-5847 | The gst_asf_demux_process_ext_content_desc function in gst/asfdemux/gstasfdemux.c in gst-plugins-ugly in GStreamer allows remote attackers to cause a denial of service (out-of-bounds heap read) via vectors involving extended content descriptors. | https://nvd.nist.gov/vuln/detail/CVE-2017-5847 |
2,994 | linux | e1d35d4dc7f089e6c9c080d556feedf9c706f0c7 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e1d35d4dc7f089e6c9c080d556feedf9c706f0c7 | None | 1 | long do_shmat(int shmid, char __user *shmaddr, int shmflg, ulong *raddr,
unsigned long shmlba)
{
struct shmid_kernel *shp;
unsigned long addr;
unsigned long size;
struct file *file;
int err;
unsigned long flags;
unsigned long prot;
int acc_mode;
struct ipc_namespace *ns;
struct shm_file_data *sfd... | 97,526,004,713,347,220,000,000,000,000,000,000,000 | shm.c | 88,612,487,660,318,380,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2017-5669 | The do_shmat function in ipc/shm.c in the Linux kernel through 4.9.12 does not restrict the address calculated by a certain rounding operation, which allows local users to map page zero, and consequently bypass a protection mechanism that exists for the mmap system call, by making crafted shmget and shmat system calls ... | https://nvd.nist.gov/vuln/detail/CVE-2017-5669 |
2,995 | bitlbee | 30d598ce7cd3f136ee9d7097f39fa9818a272441 | https://github.com/bitlbee/bitlbee | https://github.com/bitlbee/bitlbee/commit/30d598ce7cd3f136ee9d7097f39fa9818a272441 | purple: Fix crash on ft requests from unknown contacts
Followup to 701ab81 (included in 3.5) which was a partial fix which only
improved things for non-libpurple file transfers (that is, just jabber) | 1 | static gboolean prplcb_xfer_new_send_cb(gpointer data, gint fd, b_input_condition cond)
{
PurpleXfer *xfer = data;
struct im_connection *ic = purple_ic_by_pa(xfer->account);
struct prpl_xfer_data *px = xfer->ui_data;
PurpleBuddy *buddy;
const char *who;
buddy = purple_find_buddy(xfer->account, xfer->who);
who =... | 227,444,511,891,830,250,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2017-5668 | bitlbee-libpurple before 3.5.1 allows remote attackers to cause a denial of service (NULL pointer dereference and crash) and possibly execute arbitrary code via a file transfer request for a contact that is not in the contact list. NOTE: this vulnerability exists because of an incomplete fix for CVE-2016-10189. | https://nvd.nist.gov/vuln/detail/CVE-2017-5668 |
2,996 | linux | 0f2ff82e11c86c05d051cae32b58226392d33bbf | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0f2ff82e11c86c05d051cae32b58226392d33bbf | drm/vc4: Fix an integer overflow in temporary allocation layout.
We copy the unvalidated ioctl arguments from the user into kernel
temporary memory to run the validation from, to avoid a race where the
user updates the unvalidate contents in between validating them and
copying them into the validated BO.
However, in ... | 1 | vc4_get_bcl(struct drm_device *dev, struct vc4_exec_info *exec)
{
struct drm_vc4_submit_cl *args = exec->args;
void *temp = NULL;
void *bin;
int ret = 0;
uint32_t bin_offset = 0;
uint32_t shader_rec_offset = roundup(bin_offset + args->bin_cl_size,
16);
uint32_t uniforms_offset = shader_rec_offset + arg... | 13,890,884,168,389,853,000,000,000,000,000,000,000 | vc4_gem.c | 226,657,629,471,123,600,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2017-5576 | Integer overflow in the vc4_get_bcl function in drivers/gpu/drm/vc4/vc4_gem.c in the VideoCore DRM driver in the Linux kernel before 4.9.7 allows local users to cause a denial of service or possibly have unspecified other impact via a crafted size value in a VC4_SUBMIT_CL ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2017-5576 |
2,997 | linux | 497de07d89c1410d76a15bec2bb41f24a2a89f31 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/497de07d89c1410d76a15bec2bb41f24a2a89f31 | tmpfs: clear S_ISGID when setting posix ACLs
This change was missed the tmpfs modification in In CVE-2016-7097
commit 073931017b49 ("posix_acl: Clear SGID bit when setting
file permissions")
It can test by xfstest generic/375, which failed to clear
setgid bit in the following test case on tmpfs:
touch $testfile
c... | 1 | int simple_set_acl(struct inode *inode, struct posix_acl *acl, int type)
{
int error;
if (type == ACL_TYPE_ACCESS) {
error = posix_acl_equiv_mode(acl, &inode->i_mode);
if (error < 0)
return 0;
if (error == 0)
acl = NULL;
}
inode->i_ctime = current_time(inode);
set_cached_acl(inode, type, acl);
... | 159,742,884,414,303,530,000,000,000,000,000,000,000 | posix_acl.c | 113,644,699,034,789,880,000,000,000,000,000,000,000 | [
"CWE-284"
] | CVE-2017-5551 | The simple_set_acl function in fs/posix_acl.c in the Linux kernel before 4.9.6 preserves the setgid bit during a setxattr call involving a tmpfs filesystem, which allows local users to gain group privileges by leveraging the existence of a setgid program with restrictions on execute permissions. NOTE: this vulnerabili... | https://nvd.nist.gov/vuln/detail/CVE-2017-5551 |
2,999 | linux | b9dc6f65bc5e232d1c05fe34b5daadc7e8bbf1fb | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b9dc6f65bc5e232d1c05fe34b5daadc7e8bbf1fb | fix a fencepost error in pipe_advance()
The logics in pipe_advance() used to release all buffers past the new
position failed in cases when the number of buffers to release was equal
to pipe->buffers. If that happened, none of them had been released,
leaving pipe full. Worse, it was trivial to trigger and we end up ... | 1 | static void pipe_advance(struct iov_iter *i, size_t size)
{
struct pipe_inode_info *pipe = i->pipe;
struct pipe_buffer *buf;
int idx = i->idx;
size_t off = i->iov_offset, orig_sz;
if (unlikely(i->count < size))
size = i->count;
orig_sz = size;
if (size) {
if (off) /* make it relative to the beginning ... | 251,446,843,832,026,800,000,000,000,000,000,000,000 | iov_iter.c | 310,542,128,948,734,980,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2017-5550 | Off-by-one error in the pipe_advance function in lib/iov_iter.c in the Linux kernel before 4.9.5 allows local users to obtain sensitive information from uninitialized heap-memory locations in opportunistic circumstances by reading from a pipe after an incorrect buffer-release decision. | https://nvd.nist.gov/vuln/detail/CVE-2017-5550 |
3,000 | linux | 146cc8a17a3b4996f6805ee5c080e7101277c410 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/146cc8a17a3b4996f6805ee5c080e7101277c410 | USB: serial: kl5kusb105: fix line-state error handling
The current implementation failed to detect short transfers when
attempting to read the line state, and also, to make things worse,
logged the content of the uninitialised heap transfer buffer.
Fixes: abf492e7b3ae ("USB: kl5kusb105: fix DMA buffers on stack")
Fix... | 1 | static int klsi_105_get_line_state(struct usb_serial_port *port,
unsigned long *line_state_p)
{
int rc;
u8 *status_buf;
__u16 status;
dev_info(&port->serial->dev->dev, "sending SIO Poll request\n");
status_buf = kmalloc(KLSI_STATUSBUF_LEN, GFP_KERNEL);
if (!status_buf)
return -ENOMEM;
status_buf[0] =... | 205,807,121,916,400,540,000,000,000,000,000,000,000 | kl5kusb105.c | 15,662,809,498,104,633,000,000,000,000,000,000,000 | [
"CWE-532"
] | CVE-2017-5549 | The klsi_105_get_line_state function in drivers/usb/serial/kl5kusb105.c in the Linux kernel before 4.9.5 places uninitialized heap-memory contents into a log entry upon a failure to read the line status, which allows local users to obtain sensitive information by reading the log. | https://nvd.nist.gov/vuln/detail/CVE-2017-5549 |
3,011 | ImageMagick | c8c6a0f123d5e35c173125365c97e2c0fc7eca42 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/c8c6a0f123d5e35c173125365c97e2c0fc7eca42 | Fix improper cast that could cause an overflow as demonstrated in #347. | 1 | ModuleExport MagickBooleanType ReadPSDLayers(Image *image,
const ImageInfo *image_info,const PSDInfo *psd_info,
const MagickBooleanType skip_layers,ExceptionInfo *exception)
{
char
type[4];
LayerInfo
*layer_info;
MagickSizeType
size;
MagickBooleanType
status;
register ssize_t
i;
... | 146,718,332,998,913,800,000,000,000,000,000,000,000 | psd.c | 212,652,989,353,549,180,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-5511 | coders/psd.c in ImageMagick allows remote attackers to have unspecified impact by leveraging an improper cast, which triggers a heap-based buffer overflow. | https://nvd.nist.gov/vuln/detail/CVE-2017-5511 |
3,015 | ImageMagick | d4ec73f866a7c42a2e7f301fcd696e5cb7a7d3ab | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/d4ec73f866a7c42a2e7f301fcd696e5cb7a7d3ab | https://github.com/ImageMagick/ImageMagick/issues/350 | 1 | static size_t WritePSDChannels(const PSDInfo *psd_info,
const ImageInfo *image_info,Image *image,Image *next_image,
MagickOffsetType size_offset,const MagickBooleanType separate,
ExceptionInfo *exception)
{
Image
*mask;
MagickOffsetType
rows_offset;
size_t
channels,
count,
length,
... | 239,807,711,795,078,700,000,000,000,000,000,000,000 | psd.c | 140,063,542,016,156,050,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2017-5509 | coders/psd.c in ImageMagick allows remote attackers to have unspecified impact via a crafted PSD file, which triggers an out-of-bounds write. | https://nvd.nist.gov/vuln/detail/CVE-2017-5509 |
3,016 | ImageMagick | c073a7712d82476b5fbee74856c46b88af9c3175 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/c073a7712d82476b5fbee74856c46b88af9c3175 | None | 1 | static Image *ReadTIFFImage(const ImageInfo *image_info,
ExceptionInfo *exception)
{
const char
*option;
float
*chromaticity,
x_position,
y_position,
x_resolution,
y_resolution;
Image
*image;
int
tiff_status;
MagickBooleanType
status;
MagickSizeType
number_pixe... | 127,924,341,757,895,050,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2017-5508 | Heap-based buffer overflow in the PushQuantumPixel function in ImageMagick before 6.9.7-3 and 7.x before 7.0.4-3 allows remote attackers to cause a denial of service (application crash) via a crafted TIFF file. | https://nvd.nist.gov/vuln/detail/CVE-2017-5508 |
3,017 | ImageMagick | 4493d9ca1124564da17f9b628ef9d0f1a6be9738 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/4493d9ca1124564da17f9b628ef9d0f1a6be9738 | None | 1 | static Image *ReadMPCImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
char
cache_filename[MaxTextExtent],
id[MaxTextExtent],
keyword[MaxTextExtent],
*options;
const unsigned char
*p;
GeometryInfo
geometry_info;
Image
*image;
int
c;
LinkedListInfo
*profil... | 148,492,496,864,491,130,000,000,000,000,000,000,000 | None | null | [
"CWE-772"
] | CVE-2017-5507 | Memory leak in coders/mpc.c in ImageMagick before 6.9.7-4 and 7.x before 7.0.4-4 allows remote attackers to cause a denial of service (memory consumption) via vectors involving a pixel cache. | https://nvd.nist.gov/vuln/detail/CVE-2017-5507 |
3,018 | ImageMagick | 6235f1f7a9f7b0f83b197f6cd0073dbb6602d0fb | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/6235f1f7a9f7b0f83b197f6cd0073dbb6602d0fb | None | 1 | static MagickBooleanType SyncExifProfile(Image *image, StringInfo *profile)
{
#define MaxDirectoryStack 16
#define EXIF_DELIMITER "\n"
#define EXIF_NUM_FORMATS 12
#define TAG_EXIF_OFFSET 0x8769
#define TAG_INTEROP_OFFSET 0xa005
typedef struct _DirectoryInfo
{
unsigned char
*directory;
size_t
... | 226,372,278,084,965,700,000,000,000,000,000,000,000 | None | null | [
"CWE-415"
] | CVE-2017-5506 | Double free vulnerability in magick/profile.c in ImageMagick allows remote attackers to have unspecified impact via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2017-5506 |
3,019 | php-src | 4cc0286f2f3780abc6084bcdae5dce595daa3c12 | https://github.com/php/php-src | https://github.com/php/php-src/commit/4cc0286f2f3780abc6084bcdae5dce595daa3c12 | Fix #73832 - leave the table in a safe state if the size is too big. | 1 | ZEND_API void ZEND_FASTCALL _zend_hash_init(HashTable *ht, uint32_t nSize, dtor_func_t pDestructor, zend_bool persistent ZEND_FILE_LINE_DC)
{
GC_REFCOUNT(ht) = 1;
GC_TYPE_INFO(ht) = IS_ARRAY;
ht->u.flags = (persistent ? HASH_FLAG_PERSISTENT : 0) | HASH_FLAG_APPLY_PROTECTION | HASH_FLAG_STATIC_KEYS;
ht->nTableSiz... | 325,470,889,852,098,170,000,000,000,000,000,000,000 | zend_hash.c | 7,152,610,647,614,559,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2017-5340 | Zend/zend_hash.c in PHP before 7.0.15 and 7.1.x before 7.1.1 mishandles certain cases that require large array allocations, which allows remote attackers to execute arbitrary code or cause a denial of service (integer overflow, uninitialized memory access, and use of arbitrary destructor function pointers) via crafted ... | https://nvd.nist.gov/vuln/detail/CVE-2017-5340 |
3,020 | bubblewrap | d7fc532c42f0e9bf427923bab85433282b3e5117 | https://github.com/containers/bubblewrap | https://github.com/projectatomic/bubblewrap/commit/d7fc532c42f0e9bf427923bab85433282b3e5117 | Call setsid() before executing sandboxed code (CVE-2017-5226)
This prevents the sandboxed code from getting a controlling tty,
which in turn prevents it from accessing the TIOCSTI ioctl and hence
faking terminal input.
Fixes: #142
Closes: #143
Approved by: cgwalters | 1 | main (int argc,
char **argv)
{
mode_t old_umask;
cleanup_free char *base_path = NULL;
int clone_flags;
char *old_cwd = NULL;
pid_t pid;
int event_fd = -1;
int child_wait_fd = -1;
const char *new_cwd;
uid_t ns_uid;
gid_t ns_gid;
struct stat sbuf;
uint64_t val;
int res UNUSED;
real_u... | 79,333,800,940,039,590,000,000,000,000,000,000,000 | bubblewrap.c | 240,192,248,288,204,800,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2017-5226 | When executing a program via the bubblewrap sandbox, the nonpriv session can escape to the parent session by using the TIOCSTI ioctl to push characters into the terminal's input buffer, allowing an attacker to escape the sandbox. | https://nvd.nist.gov/vuln/detail/CVE-2017-5226 |
3,023 | libtiff | 5c080298d59efa53264d7248bbe3a04660db6ef7 | https://github.com/vadz/libtiff | https://github.com/vadz/libtiff/commit/5c080298d59efa53264d7248bbe3a04660db6ef7 | * tools/tiffcp.c: error out cleanly in cpContig2SeparateByRow and
cpSeparate2ContigByRow if BitsPerSample != 8 to avoid heap based overflow.
Fixes http://bugzilla.maptools.org/show_bug.cgi?id=2656 and
http://bugzilla.maptools.org/show_bug.cgi?id=2657 | 1 | tiffcp(TIFF* in, TIFF* out)
{
uint16 bitspersample, samplesperpixel = 1;
uint16 input_compression, input_photometric = PHOTOMETRIC_MINISBLACK;
copyFunc cf;
uint32 width, length;
struct cpTag* p;
CopyField(TIFFTAG_IMAGEWIDTH, width);
CopyField(TIFFTAG_IMAGELENGTH, length);
CopyField(TIFFTAG_BITSPERSAMPLE, ... | 62,954,725,605,887,130,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2017-5225 | LibTIFF version 4.0.7 is vulnerable to a heap buffer overflow in the tools/tiffcp resulting in DoS or code execution via a crafted BitsPerSample value. | https://nvd.nist.gov/vuln/detail/CVE-2017-5225 |
3,024 | libplist | 3a55ddd3c4c11ce75a86afbefd085d8d397ff957 | https://github.com/libimobiledevice/libplist | https://github.com/libimobiledevice/libplist/commit/3a55ddd3c4c11ce75a86afbefd085d8d397ff957 | base64: Rework base64decode to handle split encoded data correctly | 1 | unsigned char *base64decode(const char *buf, size_t *size)
{
if (!buf || !size) return NULL;
size_t len = (*size > 0) ? *size : strlen(buf);
if (len <= 0) return NULL;
unsigned char *outbuf = (unsigned char*)malloc((len/4)*3+3);
const char *ptr = buf;
int p = 0;
size_t l = 0;
do {
ptr += strspn(ptr, ... | 127,181,077,677,972,860,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2017-5209 | The base64decode function in base64.c in libimobiledevice libplist through 1.12 allows attackers to obtain sensitive information from process memory or cause a denial of service (buffer over-read) via split encoded Apple Property List data. | https://nvd.nist.gov/vuln/detail/CVE-2017-5209 |
3,026 | firejail | 5d43fdcd215203868d440ffc42036f5f5ffc89fc | https://github.com/netblue30/firejail | https://github.com/netblue30/firejail/commit/5d43fdcd215203868d440ffc42036f5f5ffc89fc | security fix | 1 | void bandwidth_pid(pid_t pid, const char *command, const char *dev, int down, int up) {
EUID_ASSERT();
EUID_ROOT();
char *comm = pid_proc_comm(pid);
EUID_USER();
if (!comm) {
fprintf(stderr, "Error: cannot find sandbox\n");
exit(1);
}
if (strcmp(comm, "firejail") != 0) {
fprintf(stderr, "Error: cannot fin... | 13,630,448,442,118,780,000,000,000,000,000,000,000 | None | null | [
"CWE-269"
] | CVE-2017-5207 | Firejail before 0.9.44.4, when running a bandwidth command, allows local users to gain root privileges via the --shell argument. | https://nvd.nist.gov/vuln/detail/CVE-2017-5207 |
3,027 | firejail | 6b8dba29d73257311564ee7f27b9b14758cc693e | https://github.com/netblue30/firejail | https://github.com/netblue30/firejail/commit/6b8dba29d73257311564ee7f27b9b14758cc693e | security fix | 1 | static void detect_allow_debuggers(int argc, char **argv) {
int i;
for (i = 1; i < argc; i++) {
if (strcmp(argv[i], "--allow-debuggers") == 0) {
arg_allow_debuggers = 1;
break;
}
if (strcmp(argv[i], "--") == 0)
break;
if (strncmp(argv[i], "--", 2) != 0)
break;
}
}
| 181,511,617,357,868,100,000,000,000,000,000,000,000 | None | null | [
"CWE-703"
] | CVE-2017-5206 | Firejail before 0.9.44.4, when running on a Linux kernel before 4.8, allows context-dependent attackers to bypass a seccomp-based sandbox protection mechanism via the --allow-debuggers argument. | https://nvd.nist.gov/vuln/detail/CVE-2017-5206 |
3,044 | linux | c06cfb08b88dfbe13be44a69ae2fdc3a7c902d81 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c06cfb08b88dfbe13be44a69ae2fdc3a7c902d81 | KEYS: Remove key_type::match in favour of overriding default by match_preparse
A previous patch added a ->match_preparse() method to the key type. This is
allowed to override the function called by the iteration algorithm.
Therefore, we can just set a default that simply checks for an exact match of
the key descripti... | 1 | key_ref_t keyring_search(key_ref_t keyring,
struct key_type *type,
const char *description)
{
struct keyring_search_context ctx = {
.index_key.type = type,
.index_key.description = description,
.cred = current_cred(),
.match_data.cmp = type->match,
.match_data.raw_data = description,
.matc... | 145,414,750,816,567,050,000,000,000,000,000,000,000 | keyring.c | 232,402,781,306,047,000,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-2647 | The KEYS subsystem in the Linux kernel before 3.18 allows local users to gain privileges or cause a denial of service (NULL pointer dereference and system crash) via vectors involving a NULL value for a certain match field, related to the keyring_search_iterator function in keyring.c. | https://nvd.nist.gov/vuln/detail/CVE-2017-2647 |
3,051 | linux | 33ab91103b3415e12457e3104f0e4517ce12d0f3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/33ab91103b3415e12457e3104f0e4517ce12d0f3 | KVM: x86: fix emulation of "MOV SS, null selector"
This is CVE-2017-2583. On Intel this causes a failed vmentry because
SS's type is neither 3 nor 7 (even though the manual says this check is
only done for usable SS, and the dmesg splat says that SS is unusable!).
On AMD it's worse: svm.c is confused and sets CPL to ... | 1 | static int load_segment_descriptor(struct x86_emulate_ctxt *ctxt,
u16 selector, int seg)
{
u8 cpl = ctxt->ops->cpl(ctxt);
return __load_segment_descriptor(ctxt, selector, seg, cpl,
X86_TRANSFER_NONE, NULL);
}
| 161,015,162,063,737,200,000,000,000,000,000,000,000 | emulate.c | 56,368,919,375,607,000,000,000,000,000,000,000,000 | [
"CWE-284"
] | CVE-2017-2583 | The load_segment_descriptor implementation in arch/x86/kvm/emulate.c in the Linux kernel before 4.9.5 improperly emulates a "MOV SS, NULL selector" instruction, which allows guest OS users to cause a denial of service (guest OS crash) or gain guest OS privileges via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2017-2583 |
3,052 | tor | 09ea89764a4d3a907808ed7d4fe42abfe64bd486 | https://github.com/torproject/tor | https://github.com/torproject/tor/commit/09ea89764a4d3a907808ed7d4fe42abfe64bd486 | Fix log-uninitialized-stack bug in rend_service_intro_established.
Fixes bug 23490; bugfix on 0.2.7.2-alpha.
TROVE-2017-008
CVE-2017-0380 | 1 | rend_service_intro_established(origin_circuit_t *circuit,
const uint8_t *request,
size_t request_len)
{
rend_service_t *service;
rend_intro_point_t *intro;
char serviceid[REND_SERVICE_ID_LEN_BASE32+1];
(void) request;
(void) request_len;
tor_asse... | 331,095,980,763,480,200,000,000,000,000,000,000,000 | rendservice.c | 66,091,888,457,677,730,000,000,000,000,000,000,000 | [
"CWE-532"
] | CVE-2017-0380 | The rend_service_intro_established function in or/rendservice.c in Tor before 0.2.8.15, 0.2.9.x before 0.2.9.12, 0.3.0.x before 0.3.0.11, 0.3.1.x before 0.3.1.7, and 0.3.2.x before 0.3.2.1-alpha, when SafeLogging is disabled, allows attackers to obtain sensitive information by leveraging access to the log files of a hi... | https://nvd.nist.gov/vuln/detail/CVE-2017-0380 |
3,053 | tor | 665baf5ed5c6186d973c46cdea165c0548027350 | https://github.com/torproject/tor | https://github.com/torproject/tor/commit/665baf5ed5c6186d973c46cdea165c0548027350 | Consider the exit family when applying guard restrictions.
When the new path selection logic went into place, I accidentally
dropped the code that considered the _family_ of the exit node when
deciding if the guard was usable, and we didn't catch that during
code review.
This patch makes the guard_restriction_t code ... | 1 | entry_guard_obeys_restriction(const entry_guard_t *guard,
const entry_guard_restriction_t *rst)
{
tor_assert(guard);
if (! rst)
return 1; // No restriction? No problem.
return tor_memneq(guard->identity, rst->exclude_id, DIGEST_LEN);
}
| 1,599,956,303,315,477,000,000,000,000,000,000,000 | None | null | [
"CWE-200"
] | CVE-2017-0377 | Tor 0.3.x before 0.3.0.9 has a guard-selection algorithm that only considers the exit relay (not the exit relay's family), which might allow remote attackers to defeat intended anonymity properties by leveraging the existence of large families. | https://nvd.nist.gov/vuln/detail/CVE-2017-0377 |
3,054 | tor | 56a7c5bc15e0447203a491c1ee37de9939ad1dcd | https://github.com/torproject/tor | https://github.com/torproject/tor/commit/56a7c5bc15e0447203a491c1ee37de9939ad1dcd | TROVE-2017-005: Fix assertion failure in connection_edge_process_relay_cell
On an hidden service rendezvous circuit, a BEGIN_DIR could be sent
(maliciously) which would trigger a tor_assert() because
connection_edge_process_relay_cell() thought that the circuit is an
or_circuit_t but is an origin circuit in reality.
... | 1 | connection_edge_process_relay_cell(cell_t *cell, circuit_t *circ,
edge_connection_t *conn,
crypt_path_t *layer_hint)
{
static int num_seen=0;
relay_header_t rh;
unsigned domain = layer_hint?LD_APP:LD_EXIT;
int reason;
int optimistic_data = ... | 2,913,244,036,608,667,000,000,000,000,000,000,000 | None | null | [
"CWE-617"
] | CVE-2017-0375 | The hidden-service feature in Tor before 0.3.0.8 allows a denial of service (assertion failure and daemon exit) in the relay_send_end_cell_from_edge_ function via a malformed BEGIN cell. | https://nvd.nist.gov/vuln/detail/CVE-2017-0375 |
3,055 | tor | 79b59a2dfcb68897ee89d98587d09e55f07e68d7 | https://github.com/torproject/tor | https://github.com/torproject/tor/commit/79b59a2dfcb68897ee89d98587d09e55f07e68d7 | TROVE-2017-004: Fix assertion failure in relay_send_end_cell_from_edge_
This fixes an assertion failure in relay_send_end_cell_from_edge_() when an
origin circuit and a cpath_layer = NULL were passed.
A service rendezvous circuit could do such a thing when a malformed BEGIN cell
is received but shouldn't in the first... | 1 | connection_exit_begin_conn(cell_t *cell, circuit_t *circ)
{
edge_connection_t *n_stream;
relay_header_t rh;
char *address = NULL;
uint16_t port = 0;
or_circuit_t *or_circ = NULL;
const or_options_t *options = get_options();
begin_cell_t bcell;
int rv;
uint8_t end_reason=0;
assert_circuit_o... | 64,087,341,861,781,330,000,000,000,000,000,000,000 | connection_edge.c | 19,059,812,996,943,585,000,000,000,000,000,000,000 | [
"CWE-617"
] | CVE-2017-0375 | The hidden-service feature in Tor before 0.3.0.8 allows a denial of service (assertion failure and daemon exit) in the relay_send_end_cell_from_edge_ function via a malformed BEGIN cell. | https://nvd.nist.gov/vuln/detail/CVE-2017-0375 |
3,056 | openjpeg | da940424816e11d624362ce080bc026adffa26e8 | https://github.com/uclouvain/openjpeg | https://github.com/uclouvain/openjpeg/commit/da940424816e11d624362ce080bc026adffa26e8 | Merge pull request #834 from trylab/issue833
Fix issue 833. | 1 | opj_image_t* bmptoimage(const char *filename, opj_cparameters_t *parameters)
{
opj_image_cmptparm_t cmptparm[4]; /* maximum of 4 components */
OPJ_UINT8 lut_R[256], lut_G[256], lut_B[256];
OPJ_UINT8 const* pLUT[3];
opj_image_t * image = NULL;
FILE *IN;
OPJ_BITMAPFILEHEADER File_h;
OPJ_BITMAPINFOHEADER Info_h;
O... | 253,468,724,239,351,980,000,000,000,000,000,000,000 | None | null | [
"CWE-190"
] | CVE-2016-10507 | Integer overflow vulnerability in the bmp24toimage function in convertbmp.c in OpenJPEG before 2.2.0 allows remote attackers to cause a denial of service (heap-based buffer over-read and application crash) via a crafted bmp file. | https://nvd.nist.gov/vuln/detail/CVE-2016-10507 |
3,057 | openjpeg | d27ccf01c68a31ad62b33d2dc1ba2bb1eeaafe7b | https://github.com/uclouvain/openjpeg | https://github.com/uclouvain/openjpeg/commit/d27ccf01c68a31ad62b33d2dc1ba2bb1eeaafe7b | Avoid division by zero in opj_pi_next_rpcl, opj_pi_next_pcrl and opj_pi_next_cprl (#938)
Fixes issues with id:000026,sig:08,src:002419,op:int32,pos:60,val:+32 and
id:000019,sig:08,src:001098,op:flip1,pos:49 | 1 | static OPJ_BOOL opj_pi_next_pcrl(opj_pi_iterator_t * pi)
{
opj_pi_comp_t *comp = NULL;
opj_pi_resolution_t *res = NULL;
OPJ_UINT32 index = 0;
if (!pi->first) {
comp = &pi->comps[pi->compno];
goto LABEL_SKIP;
} else {
OPJ_UINT32 compno, resno;
pi->first = 0;
p... | 123,755,033,500,617,050,000,000,000,000,000,000,000 | pi.c | 270,132,454,060,460,450,000,000,000,000,000,000,000 | [
"CWE-369"
] | CVE-2016-10506 | Division-by-zero vulnerabilities in the functions opj_pi_next_cprl, opj_pi_next_pcrl, and opj_pi_next_rpcl in pi.c in OpenJPEG before 2.2.0 allow remote attackers to cause a denial of service (application crash) via crafted j2k files. | https://nvd.nist.gov/vuln/detail/CVE-2016-10506 |
3,058 | openjpeg | d27ccf01c68a31ad62b33d2dc1ba2bb1eeaafe7b | https://github.com/uclouvain/openjpeg | https://github.com/uclouvain/openjpeg/commit/d27ccf01c68a31ad62b33d2dc1ba2bb1eeaafe7b | Avoid division by zero in opj_pi_next_rpcl, opj_pi_next_pcrl and opj_pi_next_cprl (#938)
Fixes issues with id:000026,sig:08,src:002419,op:int32,pos:60,val:+32 and
id:000019,sig:08,src:001098,op:flip1,pos:49 | 1 | static OPJ_BOOL opj_pi_next_rpcl(opj_pi_iterator_t * pi)
{
opj_pi_comp_t *comp = NULL;
opj_pi_resolution_t *res = NULL;
OPJ_UINT32 index = 0;
if (!pi->first) {
goto LABEL_SKIP;
} else {
OPJ_UINT32 compno, resno;
pi->first = 0;
pi->dx = 0;
pi->dy = 0;
... | 335,653,816,269,023,140,000,000,000,000,000,000,000 | pi.c | 270,132,454,060,460,450,000,000,000,000,000,000,000 | [
"CWE-369"
] | CVE-2016-10506 | Division-by-zero vulnerabilities in the functions opj_pi_next_cprl, opj_pi_next_pcrl, and opj_pi_next_rpcl in pi.c in OpenJPEG before 2.2.0 allow remote attackers to cause a denial of service (application crash) via crafted j2k files. | https://nvd.nist.gov/vuln/detail/CVE-2016-10506 |
3,059 | openjpeg | 397f62c0a838e15d667ef50e27d5d011d2c79c04 | https://github.com/uclouvain/openjpeg | https://github.com/uclouvain/openjpeg/commit/397f62c0a838e15d667ef50e27d5d011d2c79c04 | Fix write heap buffer overflow in opj_mqc_byteout(). Discovered by Ke Liu of Tencent's Xuanwu LAB (#835) | 1 | static OPJ_BOOL opj_tcd_code_block_enc_allocate_data(opj_tcd_cblk_enc_t *
p_code_block)
{
OPJ_UINT32 l_data_size;
l_data_size = (OPJ_UINT32)((p_code_block->x1 - p_code_block->x0) *
(p_code_block->y1 - p_code_block->y0) * (OPJ_INT32)sizeof(OPJ_UINT32));
if (l_dat... | 337,954,804,662,270,270,000,000,000,000,000,000,000 | tcd.c | 328,280,904,317,908,030,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-10504 | Heap-based buffer overflow vulnerability in the opj_mqc_byteout function in mqc.c in OpenJPEG before 2.2.0 allows remote attackers to cause a denial of service (application crash) via a crafted bmp file. | https://nvd.nist.gov/vuln/detail/CVE-2016-10504 |
3,060 | yodl | fd85f8c94182558ff1480d06a236d6fb927979a3 | https://github.com/fbb-git/yodl | https://github.com/fbb-git/yodl/commit/fd85f8c94182558ff1480d06a236d6fb927979a3 | fixed invalid memory reads detected by the address sanitizer | 1 | void queue_push(register Queue *qp, size_t extra_length, char const *info)
{
register char *cp;
size_t memory_length;
size_t available_length;
size_t begin_length;
size_t n_begin;
size_t q_length;
if (!extra_length)
return;
memory_length = qp->d_memory_end - qp->d_memory;
... | 153,131,316,334,849,000,000,000,000,000,000,000,000 | queuepush.c | 235,046,411,350,534,700,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-10375 | Yodl before 3.07.01 has a Buffer Over-read in the queue_push function in queue/queuepush.c. | https://nvd.nist.gov/vuln/detail/CVE-2016-10375 |
3,061 | linux | 163ae1c6ad6299b19e22b4a35d5ab24a89791a98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/163ae1c6ad6299b19e22b4a35d5ab24a89791a98 | fscrypto: add authorization check for setting encryption policy
On an ext4 or f2fs filesystem with file encryption supported, a user
could set an encryption policy on any empty directory(*) to which they
had readonly access. This is obviously problematic, since such a
directory might be owned by another user and the ... | 1 | int fscrypt_process_policy(struct inode *inode,
const struct fscrypt_policy *policy)
{
if (policy->version != 0)
return -EINVAL;
if (!inode_has_encryption_context(inode)) {
if (!inode->i_sb->s_cop->empty_dir)
return -EOPNOTSUPP;
if (!inode->i_sb->s_cop->empty_dir(inode))
return -ENOTEMPTY;
re... | 6,328,866,400,043,231,000,000,000,000,000,000,000 | policy.c | 29,686,294,510,241,630,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2016-10318 | A missing authorization check in the fscrypt_process_policy function in fs/crypto/policy.c in the ext4 and f2fs filesystem encryption support in the Linux kernel before 4.7.4 allows a user to assign an encryption policy to a directory owned by a different user, potentially creating a denial of service. | https://nvd.nist.gov/vuln/detail/CVE-2016-10318 |
3,062 | libtiff | 9657bbe3cdce4aaa90e07d50c1c70ae52da0ba6a | https://github.com/vadz/libtiff | https://github.com/vadz/libtiff/commit/9657bbe3cdce4aaa90e07d50c1c70ae52da0ba6a | * tools/tiffcrop.c: fix readContigStripsIntoBuffer() in -i (ignore) mode so
that the output buffer is correctly incremented to avoid write outside bounds.
Reported by Agostino Sarubbo.
Fixes http://bugzilla.maptools.org/show_bug.cgi?id=2620 | 1 | static int readContigStripsIntoBuffer (TIFF* in, uint8* buf)
{
uint8* bufp = buf;
int32 bytes_read = 0;
uint32 strip, nstrips = TIFFNumberOfStrips(in);
uint32 stripsize = TIFFStripSize(in);
uint32 rows = 0;
uint32 rps = TIFFGetFieldDefaulted(in, TIFFTAG_ROWSPERSTRIP, &... | 157,081,213,207,287,040,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2016-10092 | Heap-based buffer overflow in the readContigStripsIntoBuffer function in tif_unix.c in LibTIFF 4.0.7, 3.9.3, 3.9.4, 3.9.5, 3.9.6, 3.9.7, 4.0.0alpha4, 4.0.0alpha5, 4.0.0alpha6, 4.0.0beta7, 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.4beta, 4.0.5 and 4.0.6 allows remote attackers to have unspecified impact via a crafted image... | https://nvd.nist.gov/vuln/detail/CVE-2016-10092 |
3,067 | libtiff | 5397a417e61258c69209904e652a1f409ec3b9df | https://github.com/vadz/libtiff | https://github.com/vadz/libtiff/commit/5397a417e61258c69209904e652a1f409ec3b9df | * tools/tiffcp.c: avoid uint32 underflow in cpDecodedStrips that
can cause various issues, such as buffer overflows in the library.
Reported by Agostino Sarubbo.
Fixes http://bugzilla.maptools.org/show_bug.cgi?id=2598 | 1 | DECLAREcpFunc(cpDecodedStrips)
{
tsize_t stripsize = TIFFStripSize(in);
tdata_t buf = _TIFFmalloc(stripsize);
(void) imagewidth; (void) spp;
if (buf) {
tstrip_t s, ns = TIFFNumberOfStrips(in);
uint32 row = 0;
_TIFFmemset(buf, 0, stripsize);
for (s = 0; s < ns; s++) {
tsize_t cc = (row + rowsperstri... | 178,116,550,796,212,240,000,000,000,000,000,000,000 | None | null | [
"CWE-191"
] | CVE-2016-10268 | tools/tiffcp.c in LibTIFF 4.0.7 allows remote attackers to cause a denial of service (integer underflow and heap-based buffer under-read) or possibly have unspecified other impact via a crafted TIFF image, related to "READ of size 78490" and libtiff/tif_unix.c:115:23. | https://nvd.nist.gov/vuln/detail/CVE-2016-10268 |
3,069 | libtiff | 438274f938e046d33cb0e1230b41da32ffe223e1 | https://github.com/vadz/libtiff | https://github.com/vadz/libtiff/commit/438274f938e046d33cb0e1230b41da32ffe223e1 | * libtiff/tif_read.c, libtiff/tiffiop.h: fix uint32 overflow in
TIFFReadEncodedStrip() that caused an integer division by zero.
Reported by Agostino Sarubbo.
Fixes http://bugzilla.maptools.org/show_bug.cgi?id=2596 | 1 | TIFFReadEncodedStrip(TIFF* tif, uint32 strip, void* buf, tmsize_t size)
{
static const char module[] = "TIFFReadEncodedStrip";
TIFFDirectory *td = &tif->tif_dir;
uint32 rowsperstrip;
uint32 stripsperplane;
uint32 stripinplane;
uint16 plane;
uint32 rows;
tmsize_t stripsize;
if (!TIFFCheckRead(tif,0))
return((... | 339,430,912,405,596,180,000,000,000,000,000,000,000 | None | null | [
"CWE-369"
] | CVE-2016-10266 | LibTIFF 4.0.7 allows remote attackers to cause a denial of service (divide-by-zero error and application crash) via a crafted TIFF image, related to libtiff/tif_read.c:351:22. | https://nvd.nist.gov/vuln/detail/CVE-2016-10266 |
3,070 | jasper | 1f0dfe5a42911b6880a1445f13f6d615ddb55387 | https://github.com/mdadams/jasper | https://github.com/mdadams/jasper/commit/1f0dfe5a42911b6880a1445f13f6d615ddb55387 | Fixed an integer overflow problem in the JPC codec that later resulted
in the use of uninitialized data. | 1 | static int jpc_pi_nextcprl(register jpc_pi_t *pi)
{
int rlvlno;
jpc_pirlvl_t *pirlvl;
jpc_pchg_t *pchg;
int prchind;
int prcvind;
int *prclyrno;
uint_fast32_t trx0;
uint_fast32_t try0;
uint_fast32_t r;
uint_fast32_t rpx;
uint_fast32_t rpy;
pchg = pi->pchg;
if (!pi->prgvolfirst) {
goto skip;
} else {
... | 27,132,933,908,144,510,000,000,000,000,000,000,000 | jpc_t2cod.c | 159,588,622,480,218,420,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2016-10251 | Integer overflow in the jpc_pi_nextcprl function in jpc_t2cod.c in JasPer before 1.900.20 allows remote attackers to have unspecified impact via a crafted file, which triggers use of an uninitialized value. | https://nvd.nist.gov/vuln/detail/CVE-2016-10251 |
3,072 | jasper | bdfe95a6e81ffb4b2fad31a76b57943695beed20 | https://github.com/mdadams/jasper | https://github.com/mdadams/jasper/commit/bdfe95a6e81ffb4b2fad31a76b57943695beed20 | Fixed another problem with incorrect cleanup of JP2 box data upon error. | 1 | jp2_box_t *jp2_box_get(jas_stream_t *in)
{
jp2_box_t *box;
jp2_boxinfo_t *boxinfo;
jas_stream_t *tmpstream;
uint_fast32_t len;
uint_fast64_t extlen;
bool dataflag;
box = 0;
tmpstream = 0;
if (!(box = jas_malloc(sizeof(jp2_box_t)))) {
goto error;
}
box->ops = &jp2_boxinfo_unk.ops;
if (jp2_getuint32(... | 326,030,235,497,033,800,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2016-10250 | The jp2_colr_destroy function in jp2_cod.c in JasPer before 1.900.13 allows remote attackers to cause a denial of service (NULL pointer dereference) by leveraging incorrect cleanup of JP2 box data on error. NOTE: this vulnerability exists because of an incomplete fix for CVE-2016-8887. | https://nvd.nist.gov/vuln/detail/CVE-2016-10250 |
3,076 | jasper | 2e82fa00466ae525339754bb3ab0a0474a31d4bd | https://github.com/mdadams/jasper | https://github.com/mdadams/jasper/commit/2e82fa00466ae525339754bb3ab0a0474a31d4bd | Fixed an integral type promotion problem by adding a JAS_CAST.
Modified the jpc_tsfb_synthesize function so that it will be a noop for
an empty sequence (in order to avoid dereferencing a null pointer). | 1 | int jpc_tsfb_synthesize(jpc_tsfb_t *tsfb, jas_seq2d_t *a)
{
return (tsfb->numlvls > 0) ? jpc_tsfb_synthesize2(tsfb,
jas_seq2d_getref(a, jas_seq2d_xstart(a), jas_seq2d_ystart(a)),
jas_seq2d_xstart(a), jas_seq2d_ystart(a), jas_seq2d_width(a),
jas_seq2d_height(a), jas_seq2d_rowstep(a), tsfb->numlvls - 1) : ... | 236,514,528,015,268,060,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2016-10248 | The jpc_tsfb_synthesize function in jpc_tsfb.c in JasPer before 1.900.9 allows remote attackers to cause a denial of service (NULL pointer dereference) via vectors involving an empty sequence. | https://nvd.nist.gov/vuln/detail/CVE-2016-10248 |
3,079 | yara | 890c3f850293176c0e996a602ffa88b315f4e98f | https://github.com/VirusTotal/yara | https://github.com/VirusTotal/yara/commit/890c3f850293176c0e996a602ffa88b315f4e98f | Fix issue #575 | 1 | yyparse (void *yyscanner, YR_COMPILER* compiler)
{
/* The lookahead symbol. */
int yychar;
/* The semantic value of the lookahead symbol. */
/* Default value used for initialization, for pacifying older GCCs
or non-GCC compilers. */
YY_INITIAL_VALUE (static YYSTYPE yyval_default;)
YYSTYPE yylval YY_INITIAL_VALU... | 295,340,460,274,806,520,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2017-8294 | libyara/re.c in the regex component in YARA 3.5.0 allows remote attackers to cause a denial of service (out-of-bounds read and application crash) via a crafted rule that is mishandled in the yr_re_exec function. | https://nvd.nist.gov/vuln/detail/CVE-2017-8294 |
3,084 | yara | 3119b232c9c453c98d8fa8b6ae4e37ba18117cd4 | https://github.com/VirusTotal/yara | https://github.com/VirusTotal/yara/commit/3119b232c9c453c98d8fa8b6ae4e37ba18117cd4 | re_lexer: Make reading escape sequences more robust (#586)
* Add test for issue #503
* re_lexer: Make reading escape sequences more robust
This commit fixes parsing incomplete escape sequences at the end of a
regular expression and parsing things like \xxy (invalid hex digits)
which before were silently turned into ... | 1 | int read_escaped_char(
yyscan_t yyscanner,
uint8_t* escaped_char)
{
char text[4] = {0, 0, 0, 0};
text[0] = '\\';
text[1] = RE_YY_INPUT(yyscanner);
if (text[1] == EOF)
return 0;
if (text[1] == 'x')
{
text[2] = RE_YY_INPUT(yyscanner);
if (text[2] == EOF)
return 0;
... | 136,843,762,981,117,980,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2017-8294 | libyara/re.c in the regex component in YARA 3.5.0 allows remote attackers to cause a denial of service (out-of-bounds read and application crash) via a crafted rule that is mishandled in the yr_re_exec function. | https://nvd.nist.gov/vuln/detail/CVE-2017-8294 |
3,086 | linux | 3a4b77cd47bb837b8557595ec7425f281f2ca1fe | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/3a4b77cd47bb837b8557595ec7425f281f2ca1fe | ext4: validate s_first_meta_bg at mount time
Ralf Spenneberg reported that he hit a kernel crash when mounting a
modified ext4 image. And it turns out that kernel crashed when
calculating fs overhead (ext4_calculate_overhead()), this is because
the image has very large s_first_meta_bg (debug code shows it's
842150400)... | 1 | static int ext4_fill_super(struct super_block *sb, void *data, int silent)
{
char *orig_data = kstrdup(data, GFP_KERNEL);
struct buffer_head *bh;
struct ext4_super_block *es = NULL;
struct ext4_sb_info *sbi = kzalloc(sizeof(*sbi), GFP_KERNEL);
ext4_fsblk_t block;
ext4_fsblk_t sb_block = get_sb_block(&data);
ext4... | 229,430,339,392,284,060,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2016-10208 | The ext4_fill_super function in fs/ext4/super.c in the Linux kernel through 4.9.8 does not properly validate meta block groups, which allows physically proximate attackers to cause a denial of service (out-of-bounds read and system crash) via a crafted ext4 image. | https://nvd.nist.gov/vuln/detail/CVE-2016-10208 |
3,087 | linux | 32c231164b762dddefa13af5a0101032c70b50ef | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/32c231164b762dddefa13af5a0101032c70b50ef | l2tp: fix racy SOCK_ZAPPED flag check in l2tp_ip{,6}_bind()
Lock socket before checking the SOCK_ZAPPED flag in l2tp_ip6_bind().
Without lock, a concurrent call could modify the socket flags between
the sock_flag(sk, SOCK_ZAPPED) test and the lock_sock() call. This way,
a socket could be inserted twice in l2tp_ip6_bin... | 1 | static int l2tp_ip_bind(struct sock *sk, struct sockaddr *uaddr, int addr_len)
{
struct inet_sock *inet = inet_sk(sk);
struct sockaddr_l2tpip *addr = (struct sockaddr_l2tpip *) uaddr;
struct net *net = sock_net(sk);
int ret;
int chk_addr_ret;
if (!sock_flag(sk, SOCK_ZAPPED))
return -EINVAL;
if (addr_len <... | 46,693,577,002,003,250,000,000,000,000,000,000,000 | l2tp_ip.c | 106,216,683,017,059,480,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2016-10200 | Race condition in the L2TPv3 IP Encapsulation feature in the Linux kernel before 4.8.14 allows local users to gain privileges or cause a denial of service (use-after-free) by making multiple bind system calls without properly ascertaining whether a socket has the SOCK_ZAPPED status, related to net/l2tp/l2tp_ip.c and ne... | https://nvd.nist.gov/vuln/detail/CVE-2016-10200 |
3,088 | linux | 32c231164b762dddefa13af5a0101032c70b50ef | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/32c231164b762dddefa13af5a0101032c70b50ef | l2tp: fix racy SOCK_ZAPPED flag check in l2tp_ip{,6}_bind()
Lock socket before checking the SOCK_ZAPPED flag in l2tp_ip6_bind().
Without lock, a concurrent call could modify the socket flags between
the sock_flag(sk, SOCK_ZAPPED) test and the lock_sock() call. This way,
a socket could be inserted twice in l2tp_ip6_bin... | 1 | static int l2tp_ip6_bind(struct sock *sk, struct sockaddr *uaddr, int addr_len)
{
struct inet_sock *inet = inet_sk(sk);
struct ipv6_pinfo *np = inet6_sk(sk);
struct sockaddr_l2tpip6 *addr = (struct sockaddr_l2tpip6 *) uaddr;
struct net *net = sock_net(sk);
__be32 v4addr = 0;
int addr_type;
int err;
if (!soc... | 130,756,436,615,173,770,000,000,000,000,000,000,000 | l2tp_ip6.c | 43,553,914,499,582,850,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2016-10200 | Race condition in the L2TPv3 IP Encapsulation feature in the Linux kernel before 4.8.14 allows local users to gain privileges or cause a denial of service (use-after-free) by making multiple bind system calls without properly ascertaining whether a socket has the SOCK_ZAPPED status, related to net/l2tp/l2tp_ip.c and ne... | https://nvd.nist.gov/vuln/detail/CVE-2016-10200 |
3,089 | libevent | ec65c42052d95d2c23d1d837136d1cf1d9ecef9e | https://github.com/libevent/libevent | https://github.com/libevent/libevent/commit/ec65c42052d95d2c23d1d837136d1cf1d9ecef9e | evdns: fix searching empty hostnames
From #332:
Here follows a bug report by **Guido Vranken** via the _Tor bug bounty program_. Please credit Guido accordingly.
## Bug report
The DNS code of Libevent contains this rather obvious OOB read:
```c
static char *
search_make_new(const struct search_state *co... | 1 | search_make_new(const struct search_state *const state, int n, const char *const base_name) {
const size_t base_len = strlen(base_name);
const char need_to_append_dot = base_name[base_len - 1] == '.' ? 0 : 1;
struct search_domain *dom;
for (dom = state->head; dom; dom = dom->next) {
if (!n--) {
/* this... | 190,898,022,739,224,350,000,000,000,000,000,000,000 | evdns.c | 62,219,741,145,875,580,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2016-10197 | The search_make_new function in evdns.c in libevent before 2.1.6-beta allows attackers to cause a denial of service (out-of-bounds read) via an empty hostname. | https://nvd.nist.gov/vuln/detail/CVE-2016-10197 |
3,090 | libevent | 329acc18a0768c21ba22522f01a5c7f46cacc4d5 | https://github.com/libevent/libevent | https://github.com/libevent/libevent/commit/329acc18a0768c21ba22522f01a5c7f46cacc4d5 | evutil_parse_sockaddr_port(): fix buffer overflow
@asn-the-goblin-slayer:
"Length between '[' and ']' is cast to signed 32 bit integer on line 1815. Is
the length is more than 2<<31 (INT_MAX), len will hold a negative value.
Consequently, it will pass the check at line 1816. Segfault happens at line
1819.
... | 1 | evutil_parse_sockaddr_port(const char *ip_as_string, struct sockaddr *out, int *outlen)
{
int port;
char buf[128];
const char *cp, *addr_part, *port_part;
int is_ipv6;
/* recognized formats are:
* [ipv6]:port
* ipv6
* [ipv6]
* ipv4:port
* ipv4
*/
cp = strchr(ip_as_string, ':');
if (*ip_as_string ... | 297,588,158,023,252,860,000,000,000,000,000,000,000 | evutil.c | 330,918,919,969,703,100,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-10196 | Stack-based buffer overflow in the evutil_parse_sockaddr_port function in evutil.c in libevent before 2.1.6-beta allows attackers to cause a denial of service (segmentation fault) via vectors involving a long string in brackets in the ip_as_string argument. | https://nvd.nist.gov/vuln/detail/CVE-2016-10196 |
3,091 | libevent | 96f64a022014a208105ead6c8a7066018449d86d | https://github.com/libevent/libevent | https://github.com/libevent/libevent/commit/96f64a022014a208105ead6c8a7066018449d86d | evdns: name_parse(): fix remote stack overread
@asn-the-goblin-slayer:
"the name_parse() function in libevent's DNS code is vulnerable to a buffer overread.
971 if (cp != name_out) {
972 if (cp + 1 >= end) return -1;
973 *cp++ = '.';
974 }
975 if (cp + ... | 1 | name_parse(u8 *packet, int length, int *idx, char *name_out, int name_out_len) {
int name_end = -1;
int j = *idx;
int ptr_count = 0;
#define GET32(x) do { if (j + 4 > length) goto err; memcpy(&t32_, packet + j, 4); j += 4; x = ntohl(t32_); } while (0)
#define GET16(x) do { if (j + 2 > length) goto err; memcpy(&t_, p... | 116,803,398,451,156,560,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2016-10195 | The name_parse function in evdns.c in libevent before 2.1.6-beta allows remote attackers to have unspecified impact via vectors involving the label_len variable, which triggers an out-of-bounds stack read. | https://nvd.nist.gov/vuln/detail/CVE-2016-10195 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.