idx int64 | project string | commit_id string | project_url string | commit_url string | commit_message string | target int64 | func string | func_hash float64 | file_name string | file_hash float64 | cwe list | cve string | cve_desc string | nvd_url string |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
160,313 | 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... | 0 | static void put_ucounts(struct ucounts *ucounts)
{
unsigned long flags;
spin_lock_irqsave(&ucounts_lock, flags);
ucounts->count -= 1;
if (!ucounts->count)
hlist_del_init(&ucounts->node);
else
ucounts = NULL;
spin_unlock_irqrestore(&ucounts_lock, flags);
kfree(ucounts);
}
| 64,776,964,745,445,170,000,000,000,000,000,000,000 | ucount.c | 158,829,112,655,061,700,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 |
160,324 | ImageMagick | 126c7c98ea788241922c30df4a5633ea692cf8df | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/126c7c98ea788241922c30df4a5633ea692cf8df | None | 0 | 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
... | 46,317,742,934,442,890,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 |
160,325 | ImageMagick | d31fec57e9dfb0516deead2053a856e3c71e9751 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/d31fec57e9dfb0516deead2053a856e3c71e9751 | None | 0 | 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... | 333,919,329,295,391,230,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 |
160,326 | ImageMagick | 3007531bfd326c5c1e29cd41d2cd80c166de8528 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/3007531bfd326c5c1e29cd41d2cd80c166de8528 | None | 0 | 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,
... | 56,297,669,153,592,730,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 |
160,327 | ImageMagick | 7f2dc7a1afc067d0c89f12c82bcdec0445fb1b94 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/7f2dc7a1afc067d0c89f12c82bcdec0445fb1b94 | None | 0 | 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... | 125,483,886,699,136,160,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 |
160,329 | 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... | 0 | 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) {
... | 88,029,244,865,751,710,000,000,000,000,000,000,000 | bplist.c | 126,259,277,784,274,980,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,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 |
160,330 | ettercap | 626dc56686f15f2dda13c48f78c2a666cb6d8506 | https://github.com/Ettercap/ettercap | https://github.com/LocutusOfBorg/ettercap/commit/626dc56686f15f2dda13c48f78c2a666cb6d8506 | Exit gracefully in case of corrupted filters (Closes issue #782) | 0 | size_t compile_tree(struct filter_op **fop)
{
int i = 1;
struct filter_op *array = NULL;
struct unfold_elm *ue;
// invalid file
if (tree_root == NULL)
return 0;
fprintf(stdout, " Unfolding the meta-tree ");
fflush(stdout);
/* start the recursion on the tree */
unfold_blk... | 229,608,753,726,102,740,000,000,000,000,000,000,000 | ef_compiler.c | 318,507,594,985,548,100,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 |
160,332 | 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 | 0 | 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 ... | 144,139,494,756,665,900,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 |
160,334 | 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-... | 0 | 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(&hashbin->hb_spinlock, f... | 64,660,640,597,584,570,000,000,000,000,000,000,000 | irqueue.c | 157,010,212,132,212,380,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 |
160,335 | 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... | 0 | 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) {
int tend_off = skb_transport_offset(skb) + tlen;
csum = csum_sub(csum, skb_checksum(skb, tend_off, offset, 0... | 229,534,613,435,565,370,000,000,000,000,000,000,000 | ip_sockglue.c | 330,575,274,490,289,900,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 |
160,339 | tnef | 8dccf79857ceeb7a6d3e42c1e762e7b865d5344d | https://github.com/verdammelt/tnef | https://github.com/verdammelt/tnef/commit/8dccf79857ceeb7a6d3e42c1e762e7b865d5344d | Check types to avoid invalid reads/writes. | 0 | 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:
assert(a->type == szMAPI_STRING);
if (file->name) XFREE(file->name);
file->name = strdup( ... | 40,408,306,451,199,757,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 |
160,341 | tnef | 8dccf79857ceeb7a6d3e42c1e762e7b865d5344d | https://github.com/verdammelt/tnef | https://github.com/verdammelt/tnef/commit/8dccf79857ceeb7a6d3e42c1e762e7b865d5344d | Check types to avoid invalid reads/writes. | 0 | 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... | 308,009,555,072,284,620,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,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 |
160,347 | radare2 | 72794dc3523bbd5bb370de3c5857cb736c387e18 | https://github.com/radare/radare2 | https://github.com/radare/radare2/commit/72794dc3523bbd5bb370de3c5857cb736c387e18 | Fix #6829 oob write because of using wrong struct | 0 | 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... | 167,225,180,540,732,740,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 |
160,349 | 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... | 0 | 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,... | 16,028,697,172,893,430,000,000,000,000,000,000,000 | input.c | 151,429,764,324,567,950,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 |
160,350 | 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... | 0 | 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_... | 216,206,337,907,284,830,000,000,000,000,000,000,000 | core.c | 304,500,610,601,399,240,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 |
160,351 | 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... | 0 | static int rename_in_ns(int pid, char *oldname, char **newnamep)
{
uid_t ruid, suid, euid;
int fret = -1;
int fd = -1, ifindex = -1, ofd = -1, ret;
bool grab_newname = false;
ofd = lxc_preserve_ns(getpid(), "net");
if (ofd < 0) {
usernic_error("Failed opening network namespace path for '%d'.", getpid());... | 60,066,448,029,034,640,000,000,000,000,000,000,000 | lxc_user_nic.c | 250,159,130,258,728,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,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 |
160,357 | 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 | 0 | 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... | 144,021,527,902,697,510,000,000,000,000,000,000,000 | gstasfdemux.c | 214,761,137,771,976,270,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,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 |
160,359 | 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) | 0 | 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 =... | 154,082,361,588,877,430,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,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 |
160,360 | 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... | 0 | int simple_set_acl(struct inode *inode, struct posix_acl *acl, int type)
{
int error;
if (type == ACL_TYPE_ACCESS) {
error = posix_acl_update_mode(inode,
&inode->i_mode, &acl);
if (error)
return error;
}
inode->i_ctime = current_time(inode);
set_cached_acl(inode, type, acl);
return 0;
}
| 97,105,092,151,650,700,000,000,000,000,000,000,000 | posix_acl.c | 212,069,061,966,734,470,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 |
160,362 | 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 ... | 0 | static void pipe_advance(struct iov_iter *i, size_t size)
{
struct pipe_inode_info *pipe = i->pipe;
if (unlikely(i->count < size))
size = i->count;
if (size) {
struct pipe_buffer *buf;
size_t off = i->iov_offset, left = size;
int idx = i->idx;
if (off) /* make it relative to the beginning of buffer ... | 112,113,890,551,327,200,000,000,000,000,000,000,000 | iov_iter.c | 84,353,330,888,787,750,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 |
160,363 | 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... | 0 | 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] =... | 326,272,481,567,770,550,000,000,000,000,000,000,000 | kl5kusb105.c | 33,420,840,777,140,907,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,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 |
160,375 | ImageMagick | c073a7712d82476b5fbee74856c46b88af9c3175 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/c073a7712d82476b5fbee74856c46b88af9c3175 | None | 0 | 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... | 59,453,450,457,173,670,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 |
160,376 | ImageMagick | 4493d9ca1124564da17f9b628ef9d0f1a6be9738 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/4493d9ca1124564da17f9b628ef9d0f1a6be9738 | None | 0 | 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... | 17,910,870,352,937,750,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 |
160,377 | ImageMagick | 6235f1f7a9f7b0f83b197f6cd0073dbb6602d0fb | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/6235f1f7a9f7b0f83b197f6cd0073dbb6602d0fb | None | 0 | 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
... | 254,408,591,185,305,850,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 |
160,378 | 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. | 0 | 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->nTableMa... | 145,309,287,967,237,800,000,000,000,000,000,000,000 | zend_hash.c | 80,515,936,791,057,170,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 |
160,379 | 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 | 0 | 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... | 128,117,677,299,478,650,000,000,000,000,000,000,000 | bubblewrap.c | 233,358,618,089,574,770,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 |
160,382 | 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 | 0 | tiffcp(TIFF* in, TIFF* out)
{
uint16 bitspersample = 1, 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_BITSPERSAMP... | 230,811,703,316,219,500,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 |
160,383 | libplist | 3a55ddd3c4c11ce75a86afbefd085d8d397ff957 | https://github.com/libimobiledevice/libplist | https://github.com/libimobiledevice/libplist/commit/3a55ddd3c4c11ce75a86afbefd085d8d397ff957 | base64: Rework base64decode to handle split encoded data correctly | 0 | 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;
int wv, w1, w2, w3, w4;
int tmpval[4];
int... | 271,416,576,582,958,820,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 |
160,385 | firejail | 5d43fdcd215203868d440ffc42036f5f5ffc89fc | https://github.com/netblue30/firejail | https://github.com/netblue30/firejail/commit/5d43fdcd215203868d440ffc42036f5f5ffc89fc | security fix | 0 | 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... | 32,432,197,062,967,760,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 |
172,604 | firejail | 6b8dba29d73257311564ee7f27b9b14758cc693e | https://github.com/netblue30/firejail | https://github.com/netblue30/firejail/commit/6b8dba29d73257311564ee7f27b9b14758cc693e | security fix | 0 | static void detect_quiet(int argc, char **argv) {
int i;
for (i = 1; i < argc; i++) {
if (strcmp(argv[i], "--quiet") == 0) {
arg_quiet = 1;
break;
}
if (strcmp(argv[i], "--") == 0)
break;
if (strncmp(argv[i], "--", 2) != 0)
break;
}
}
| 100,962,745,453,299,500,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,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 |
160,409 | 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 | 0 | 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... | 4,032,488,277,405,945,300,000,000,000,000,000,000 | rendservice.c | 160,969,707,532,241,080,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 |
160,410 | 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 ... | 0 | 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.
// Only one kind of restriction exists right now: excluding an exit
// ID and all of its family.
const... | 196,282,652,159,466,300,000,000,000,000,000,000,000 | entrynodes.c | 159,942,685,939,478,040,000,000,000,000,000,000,000 | [
"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 |
160,411 | 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.
... | 0 | 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 = ... | 66,986,936,371,270,080,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 |
160,412 | 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... | 0 | 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;
origin_circuit_t *origin_circ = NULL;
crypt_path_t *layer_hint = NULL;
const or_options_t *options = get_options();
be... | 299,271,952,944,700,330,000,000,000,000,000,000,000 | connection_edge.c | 27,745,521,130,031,020,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,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 |
160,413 | 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 | 0 | 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... | 10,556,146,193,382,831,000,000,000,000,000,000,000 | pi.c | 196,331,120,543,022,600,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 |
160,414 | 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 | 0 | 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;
... | 83,067,064,142,559,950,000,000,000,000,000,000,000 | pi.c | 196,331,120,543,022,600,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 |
9,489 | 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_cprl(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 {
pi->first = 0;
}
for (pi->compno = pi->poc.compno... | 271,427,417,647,316,780,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 |
184,574 | 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 | 0 | static OPJ_BOOL opj_pi_next_cprl(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 {
pi->first = 0;
}
for (pi->compno = pi->poc.compno... | 246,397,794,907,537,700,000,000,000,000,000,000,000 | pi.c | 196,331,120,543,022,600,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,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 |
160,415 | 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 | 0 | 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;
... | 326,776,403,012,537,100,000,000,000,000,000,000,000 | queuepush.c | 5,990,812,577,634,449,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 |
160,416 | 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 ... | 0 | int fscrypt_process_policy(struct inode *inode,
const struct fscrypt_policy *policy)
{
if (!inode_owner_or_capable(inode))
return -EACCES;
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... | 71,182,011,548,280,390,000,000,000,000,000,000,000 | policy.c | 202,758,888,549,972,560,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 |
160,417 | 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 | 0 | 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, &... | 34,150,410,170,692,767,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,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 |
160,423 | 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 | 0 | 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((... | 153,689,795,773,008,740,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,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 |
160,424 | 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. | 0 | 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;
}
// Mark the box data as never having been constructed... | 197,303,767,499,977,520,000,000,000,000,000,000,000 | jp2_cod.c | 233,396,642,819,954,440,000,000,000,000,000,000,000 | [
"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 |
160,428 | 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). | 0 | int jpc_tsfb_synthesize(jpc_tsfb_t *tsfb, jas_seq2d_t *a)
{
return (tsfb->numlvls > 0 && jas_seq2d_size(a)) ?
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... | 167,624,567,335,881,300,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 |
160,431 | yara | 890c3f850293176c0e996a602ffa88b315f4e98f | https://github.com/VirusTotal/yara | https://github.com/VirusTotal/yara/commit/890c3f850293176c0e996a602ffa88b315f4e98f | Fix issue #575 | 0 | 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... | 197,412,535,643,782,370,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 |
160,432 | 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 ... | 0 | 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 || text[1] == 0)
return 0;
if (text[1] == 'x')
{
text[2] = RE_YY_INPUT(yyscanner);
if (!isxdigit(text[2]))
... | 150,218,527,312,276,800,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 |
160,433 | 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)... | 0 | 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... | 79,194,532,584,267,290,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 |
160,434 | 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... | 0 | 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 (addr_len < sizeof(struct sockaddr_l2tpip))
return -EINVAL;
... | 211,936,237,253,166,150,000,000,000,000,000,000,000 | l2tp_ip.c | 189,368,109,179,598,530,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 |
160,435 | 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... | 0 | 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 (add... | 124,031,159,716,821,550,000,000,000,000,000,000,000 | l2tp_ip6.c | 283,527,582,540,524,700,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 |
160,436 | 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... | 0 | search_make_new(const struct search_state *const state, int n, const char *const base_name) {
const size_t base_len = strlen(base_name);
char need_to_append_dot;
struct search_domain *dom;
if (!base_len) return NULL;
need_to_append_dot = base_name[base_len - 1] == '.' ? 0 : 1;
for (dom = state->head; dom; ... | 274,276,755,662,782,160,000,000,000,000,000,000,000 | evdns.c | 115,534,086,427,827,900,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 |
160,437 | 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.
... | 0 | 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 ... | 48,276,417,416,350,850,000,000,000,000,000,000,000 | evutil.c | 307,507,185,056,542,270,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.