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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
184,429 | openssl | 4924b37ee01f71ae19c94a8934b80eeb2f677932 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/4924b37ee01f71ae19c94a8934b80eeb2f677932 | bn/bn_gf2m.c: avoid infinite loop wich malformed ECParamters.
CVE-2015-1788
Reviewed-by: Matt Caswell <matt@openssl.org> | 0 | int BN_GF2m_mod_inv(BIGNUM *r, const BIGNUM *a, const BIGNUM *p, BN_CTX *ctx)
{
BIGNUM *b, *c = NULL, *u = NULL, *v = NULL, *tmp;
int ret = 0;
bn_check_top(a);
bn_check_top(p);
BN_CTX_start(ctx);
if ((b = BN_CTX_get(ctx)) == NULL)
goto err;
if ((c = BN_CTX_get(ctx)) == NULL)
... | 248,771,703,463,592,570,000,000,000,000,000,000,000 | None | null | [
"CWE-399"
] | CVE-2015-1788 | The BN_GF2m_mod_inv function in crypto/bn/bn_gf2m.c in OpenSSL before 0.9.8s, 1.0.0 before 1.0.0e, 1.0.1 before 1.0.1n, and 1.0.2 before 1.0.2b does not properly handle ECParameters structures in which the curve is over a malformed binary polynomial field, which allows remote attackers to cause a denial of service (inf... | https://nvd.nist.gov/vuln/detail/CVE-2015-1788 |
9,306 | pigz | fdad1406b3ec809f4954ff7cdf9e99eb18c2458f | https://github.com/madler/pigz | https://github.com/madler/pigz/commit/fdad1406b3ec809f4954ff7cdf9e99eb18c2458f | When decompressing with -N or -NT, strip any path from header name.
This uses the path of the compressed file combined with the name
from the header as the name of the decompressed output file. Any
path information in the header name is stripped. This avoids a
possible vulnerability where absolute or descending path... | 1 | local void process(char *path)
{
int method = -1; /* get_header() return value */
size_t len; /* length of base name (minus suffix) */
struct stat st; /* to get file type and mod time */
/* all compressed suffixes for decoding search, in length order */... | 211,054,325,335,456,130,000,000,000,000,000,000,000 | pigz.c | 29,522,447,385,920,444,000,000,000,000,000,000,000 | [
"CWE-22"
] | CVE-2015-1191 | Multiple directory traversal vulnerabilities in pigz 2.3.1 allow remote attackers to write to arbitrary files via a (1) full pathname or (2) .. (dot dot) in an archive. | https://nvd.nist.gov/vuln/detail/CVE-2015-1191 |
184,433 | pigz | fdad1406b3ec809f4954ff7cdf9e99eb18c2458f | https://github.com/madler/pigz | https://github.com/madler/pigz/commit/fdad1406b3ec809f4954ff7cdf9e99eb18c2458f | When decompressing with -N or -NT, strip any path from header name.
This uses the path of the compressed file combined with the name
from the header as the name of the decompressed output file. Any
path information in the header name is stripped. This avoids a
possible vulnerability where absolute or descending path... | 0 | local void process(char *path)
{
int method = -1; /* get_header() return value */
size_t len; /* length of base name (minus suffix) */
struct stat st; /* to get file type and mod time */
/* all compressed suffixes for decoding search, in length order */... | 83,674,661,610,151,320,000,000,000,000,000,000,000 | pigz.c | 2,537,275,398,292,980,200,000,000,000,000,000,000 | [
"CWE-22"
] | CVE-2015-1191 | Multiple directory traversal vulnerabilities in pigz 2.3.1 allow remote attackers to write to arbitrary files via a (1) full pathname or (2) .. (dot dot) in an archive. | https://nvd.nist.gov/vuln/detail/CVE-2015-1191 |
9,307 | linux | 0f2af21aae11972fa924374ddcf52e88347cf5a8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0f2af21aae11972fa924374ddcf52e88347cf5a8 | ext4: allocate entire range in zero range
Currently there is a bug in zero range code which causes zero range
calls to only allocate block aligned portion of the range, while
ignoring the rest in some cases.
In some cases, namely if the end of the range is past i_size, we do
attempt to preallocate the last nonaligned... | 1 | static long ext4_zero_range(struct file *file, loff_t offset,
loff_t len, int mode)
{
struct inode *inode = file_inode(file);
handle_t *handle = NULL;
unsigned int max_blocks;
loff_t new_size = 0;
int ret = 0;
int flags;
int credits;
int partial_begin, partial_end;
loff_t start, end;
ext4_lblk_t lblk;
... | 140,250,258,899,090,150,000,000,000,000,000,000,000 | extents.c | 297,653,654,506,470,950,000,000,000,000,000,000,000 | [
"CWE-17"
] | CVE-2015-0275 | The ext4_zero_range function in fs/ext4/extents.c in the Linux kernel before 4.1 allows local users to cause a denial of service (BUG) via a crafted fallocate zero-range request. | https://nvd.nist.gov/vuln/detail/CVE-2015-0275 |
184,434 | linux | 0f2af21aae11972fa924374ddcf52e88347cf5a8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0f2af21aae11972fa924374ddcf52e88347cf5a8 | ext4: allocate entire range in zero range
Currently there is a bug in zero range code which causes zero range
calls to only allocate block aligned portion of the range, while
ignoring the rest in some cases.
In some cases, namely if the end of the range is past i_size, we do
attempt to preallocate the last nonaligned... | 0 | static long ext4_zero_range(struct file *file, loff_t offset,
loff_t len, int mode)
{
struct inode *inode = file_inode(file);
handle_t *handle = NULL;
unsigned int max_blocks;
loff_t new_size = 0;
int ret = 0;
int flags;
int credits;
int partial_begin, partial_end;
loff_t start, end;
ext4_lblk_t lblk;
... | 181,203,564,234,099,340,000,000,000,000,000,000,000 | extents.c | 219,402,081,205,227,030,000,000,000,000,000,000,000 | [
"CWE-17"
] | CVE-2015-0275 | The ext4_zero_range function in fs/ext4/extents.c in the Linux kernel before 4.1 allows local users to cause a denial of service (BUG) via a crafted fallocate zero-range request. | https://nvd.nist.gov/vuln/detail/CVE-2015-0275 |
9,310 | libsndfile | 725c7dbb95bfaf8b4bb7b04820e3a00cceea9ce6 | https://github.com/erikd/libsndfile | https://github.com/erikd/libsndfile/commit/725c7dbb95bfaf8b4bb7b04820e3a00cceea9ce6 | src/file_io.c : Prevent potential divide-by-zero.
Closes: https://github.com/erikd/libsndfile/issues/92 | 1 | psf_fwrite (const void *ptr, sf_count_t bytes, sf_count_t items, SF_PRIVATE *psf)
{ sf_count_t total = 0 ;
ssize_t count ;
if (psf->virtual_io)
return psf->vio.write (ptr, bytes*items, psf->vio_user_data) / bytes ;
items *= bytes ;
/* Do this check after the multiplication above. */
if (items <= 0)
re... | 168,840,506,501,797,730,000,000,000,000,000,000,000 | file_io.c | 239,890,201,875,820,400,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-9756 | The psf_fwrite function in file_io.c in libsndfile allows attackers to cause a denial of service (divide-by-zero error and application crash) via unspecified vectors related to the headindex variable. | https://nvd.nist.gov/vuln/detail/CVE-2014-9756 |
44,278 | libsndfile | 725c7dbb95bfaf8b4bb7b04820e3a00cceea9ce6 | https://github.com/erikd/libsndfile | https://github.com/erikd/libsndfile/commit/725c7dbb95bfaf8b4bb7b04820e3a00cceea9ce6 | src/file_io.c : Prevent potential divide-by-zero.
Closes: https://github.com/erikd/libsndfile/issues/92 | 0 | psf_fwrite (const void *ptr, sf_count_t bytes, sf_count_t items, SF_PRIVATE *psf)
{ sf_count_t total = 0 ;
ssize_t count ;
if (psf->virtual_io)
return psf->vio.write (ptr, bytes*items, psf->vio_user_data) / bytes ;
items *= bytes ;
/* Do this check after the multiplication above. */
if (items <= 0)
return 0... | 300,658,478,914,303,200,000,000,000,000,000,000,000 | file_io.c | 207,124,311,700,953,700,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-9756 | The psf_fwrite function in file_io.c in libsndfile allows attackers to cause a denial of service (divide-by-zero error and application crash) via unspecified vectors related to the headindex variable. | https://nvd.nist.gov/vuln/detail/CVE-2014-9756 |
9,312 | linux | e159332b9af4b04d882dbcfe1bb0117f0a6d4b58 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e159332b9af4b04d882dbcfe1bb0117f0a6d4b58 | udf: Verify i_size when loading inode
Verify that inode size is sane when loading inode with data stored in
ICB. Otherwise we may get confused later when working with the inode and
inode size is too big.
CC: stable@vger.kernel.org
Reported-by: Carl Henrik Lunde <chlunde@ping.uio.no>
Signed-off-by: Jan Kara <jack@suse... | 1 | static int udf_read_inode(struct inode *inode, bool hidden_inode)
{
struct buffer_head *bh = NULL;
struct fileEntry *fe;
struct extendedFileEntry *efe;
uint16_t ident;
struct udf_inode_info *iinfo = UDF_I(inode);
struct udf_sb_info *sbi = UDF_SB(inode->i_sb);
struct kernel_lb_addr *iloc = &iinfo->i_location;
un... | 164,719,948,166,104,950,000,000,000,000,000,000,000 | inode.c | 333,950,287,295,443,840,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2014-9728 | The UDF filesystem implementation in the Linux kernel before 3.18.2 does not validate certain lengths, which allows local users to cause a denial of service (buffer over-read and system crash) via a crafted filesystem image, related to fs/udf/inode.c and fs/udf/symlink.c. | https://nvd.nist.gov/vuln/detail/CVE-2014-9728 |
184,439 | linux | e159332b9af4b04d882dbcfe1bb0117f0a6d4b58 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e159332b9af4b04d882dbcfe1bb0117f0a6d4b58 | udf: Verify i_size when loading inode
Verify that inode size is sane when loading inode with data stored in
ICB. Otherwise we may get confused later when working with the inode and
inode size is too big.
CC: stable@vger.kernel.org
Reported-by: Carl Henrik Lunde <chlunde@ping.uio.no>
Signed-off-by: Jan Kara <jack@suse... | 0 | static int udf_read_inode(struct inode *inode, bool hidden_inode)
{
struct buffer_head *bh = NULL;
struct fileEntry *fe;
struct extendedFileEntry *efe;
uint16_t ident;
struct udf_inode_info *iinfo = UDF_I(inode);
struct udf_sb_info *sbi = UDF_SB(inode->i_sb);
struct kernel_lb_addr *iloc = &iinfo->i_location;
un... | 54,393,700,335,870,840,000,000,000,000,000,000,000 | inode.c | 12,791,960,363,227,477,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2014-9728 | The UDF filesystem implementation in the Linux kernel before 3.18.2 does not validate certain lengths, which allows local users to cause a denial of service (buffer over-read and system crash) via a crafted filesystem image, related to fs/udf/inode.c and fs/udf/symlink.c. | https://nvd.nist.gov/vuln/detail/CVE-2014-9728 |
9,314 | linux | 5b6698b0e4a37053de35cc24ee695b98a7eb712b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/5b6698b0e4a37053de35cc24ee695b98a7eb712b | batman-adv: Calculate extra tail size based on queued fragments
The fragmentation code was replaced in 610bfc6bc99bc83680d190ebc69359a05fc7f605
("batman-adv: Receive fragmented packets and merge"). The new code provided a
mostly unused parameter skb for the merging function. It is used inside the
function to calculate... | 1 | batadv_frag_merge_packets(struct hlist_head *chain, struct sk_buff *skb)
{
struct batadv_frag_packet *packet;
struct batadv_frag_list_entry *entry;
struct sk_buff *skb_out = NULL;
int size, hdr_size = sizeof(struct batadv_frag_packet);
/* Make sure incoming skb has non-bogus data. */
packet = (struct batadv_frag... | 327,120,903,356,038,720,000,000,000,000,000,000,000 | fragmentation.c | 207,228,498,943,816,330,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-9428 | The batadv_frag_merge_packets function in net/batman-adv/fragmentation.c in the B.A.T.M.A.N. implementation in the Linux kernel through 3.18.1 uses an incorrect length field during a calculation of an amount of memory, which allows remote attackers to cause a denial of service (mesh-node system crash) via fragmented pa... | https://nvd.nist.gov/vuln/detail/CVE-2014-9428 |
184,441 | linux | 5b6698b0e4a37053de35cc24ee695b98a7eb712b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/5b6698b0e4a37053de35cc24ee695b98a7eb712b | batman-adv: Calculate extra tail size based on queued fragments
The fragmentation code was replaced in 610bfc6bc99bc83680d190ebc69359a05fc7f605
("batman-adv: Receive fragmented packets and merge"). The new code provided a
mostly unused parameter skb for the merging function. It is used inside the
function to calculate... | 0 | batadv_frag_merge_packets(struct hlist_head *chain, struct sk_buff *skb)
{
struct batadv_frag_packet *packet;
struct batadv_frag_list_entry *entry;
struct sk_buff *skb_out = NULL;
int size, hdr_size = sizeof(struct batadv_frag_packet);
/* Make sure incoming skb has non-bogus data. */
packet = (struct batadv_frag... | 227,557,021,309,142,630,000,000,000,000,000,000,000 | fragmentation.c | 39,754,377,296,032,180,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-9428 | The batadv_frag_merge_packets function in net/batman-adv/fragmentation.c in the B.A.T.M.A.N. implementation in the Linux kernel through 3.18.1 uses an incorrect length field during a calculation of an amount of memory, which allows remote attackers to cause a denial of service (mesh-node system crash) via fragmented pa... | https://nvd.nist.gov/vuln/detail/CVE-2014-9428 |
9,315 | krb5 | 5bb8a6b9c9eb8dd22bc9526751610aaa255ead9c | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/5bb8a6b9c9eb8dd22bc9526751610aaa255ead9c | Fix gssrpc data leakage [CVE-2014-9423]
[MITKRB5-SA-2015-001] In svcauth_gss_accept_sec_context(), do not copy
bytes from the union context into the handle field we send to the
client. We do not use this handle field, so just supply a fixed
string of "xxxx".
In gss_union_ctx_id_struct, remove the unused "interposer"... | 1 | svcauth_gss_accept_sec_context(struct svc_req *rqst,
struct rpc_gss_init_res *gr)
{
struct svc_rpc_gss_data *gd;
struct rpc_gss_cred *gc;
gss_buffer_desc recv_tok, seqbuf;
gss_OID mech;
OM_uint32 maj_stat = 0, min_stat = 0, ret_flags, seq;
log_debug("in svcauth_gss_accept_context()");
gd = SVC... | 160,165,331,551,633,580,000,000,000,000,000,000,000 | None | null | [
"CWE-200"
] | CVE-2014-9423 | The svcauth_gss_accept_sec_context function in lib/rpc/svc_auth_gss.c in MIT Kerberos 5 (aka krb5) 1.11.x through 1.11.5, 1.12.x through 1.12.2, and 1.13.x before 1.13.1 transmits uninitialized interposer data to clients, which allows remote attackers to obtain sensitive information from process heap memory by sniffing... | https://nvd.nist.gov/vuln/detail/CVE-2014-9423 |
184,442 | krb5 | 5bb8a6b9c9eb8dd22bc9526751610aaa255ead9c | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/5bb8a6b9c9eb8dd22bc9526751610aaa255ead9c | Fix gssrpc data leakage [CVE-2014-9423]
[MITKRB5-SA-2015-001] In svcauth_gss_accept_sec_context(), do not copy
bytes from the union context into the handle field we send to the
client. We do not use this handle field, so just supply a fixed
string of "xxxx".
In gss_union_ctx_id_struct, remove the unused "interposer"... | 0 | svcauth_gss_accept_sec_context(struct svc_req *rqst,
struct rpc_gss_init_res *gr)
{
struct svc_rpc_gss_data *gd;
struct rpc_gss_cred *gc;
gss_buffer_desc recv_tok, seqbuf;
gss_OID mech;
OM_uint32 maj_stat = 0, min_stat = 0, ret_flags, seq;
log_debug("in svcauth_gss_accept_context()");
gd = SVC... | 311,117,843,771,707,250,000,000,000,000,000,000,000 | None | null | [
"CWE-200"
] | CVE-2014-9423 | The svcauth_gss_accept_sec_context function in lib/rpc/svc_auth_gss.c in MIT Kerberos 5 (aka krb5) 1.11.x through 1.11.5, 1.12.x through 1.12.2, and 1.13.x before 1.13.1 transmits uninitialized interposer data to clients, which allows remote attackers to obtain sensitive information from process heap memory by sniffing... | https://nvd.nist.gov/vuln/detail/CVE-2014-9423 |
9,316 | krb5 | 6609658db0799053fbef0d7d0aa2f1fd68ef32d8 | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/6609658db0799053fbef0d7d0aa2f1fd68ef32d8 | Fix kadmind server validation [CVE-2014-9422]
[MITKRB5-SA-2015-001] In kadmind's check_rpcsec_auth(), use
data_eq_string() instead of strncmp() to check components of the
server principal, so that we don't erroneously match left substrings
of "kadmin", "history", or the realm.
ticket: 8057 (new)
target_version: 1.13.... | 1 | check_rpcsec_auth(struct svc_req *rqstp)
{
gss_ctx_id_t ctx;
krb5_context kctx;
OM_uint32 maj_stat, min_stat;
gss_name_t name;
krb5_principal princ;
int ret, success;
krb5_data *c1, *c2, *realm;
gss_buffer_desc gss_str;
kadm5_server_handle_t handle;
size_t slen;
ch... | 94,969,864,754,992,500,000,000,000,000,000,000,000 | kadm_rpc_svc.c | 185,540,932,340,222,600,000,000,000,000,000,000,000 | [
"CWE-284"
] | CVE-2014-9422 | The check_rpcsec_auth function in kadmin/server/kadm_rpc_svc.c in kadmind in MIT Kerberos 5 (aka krb5) through 1.11.5, 1.12.x through 1.12.2, and 1.13.x before 1.13.1 allows remote authenticated users to bypass a kadmin/* authorization check and obtain administrative access by leveraging access to a two-component princ... | https://nvd.nist.gov/vuln/detail/CVE-2014-9422 |
184,443 | krb5 | 6609658db0799053fbef0d7d0aa2f1fd68ef32d8 | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/6609658db0799053fbef0d7d0aa2f1fd68ef32d8 | Fix kadmind server validation [CVE-2014-9422]
[MITKRB5-SA-2015-001] In kadmind's check_rpcsec_auth(), use
data_eq_string() instead of strncmp() to check components of the
server principal, so that we don't erroneously match left substrings
of "kadmin", "history", or the realm.
ticket: 8057 (new)
target_version: 1.13.... | 0 | check_rpcsec_auth(struct svc_req *rqstp)
{
gss_ctx_id_t ctx;
krb5_context kctx;
OM_uint32 maj_stat, min_stat;
gss_name_t name;
krb5_principal princ;
int ret, success;
krb5_data *c1, *c2, *realm;
gss_buffer_desc gss_str;
kadm5_server_handle_t handle;
size_t slen;
ch... | 198,850,176,991,247,300,000,000,000,000,000,000,000 | kadm_rpc_svc.c | 74,095,416,463,421,810,000,000,000,000,000,000,000 | [
"CWE-284"
] | CVE-2014-9422 | The check_rpcsec_auth function in kadmin/server/kadm_rpc_svc.c in kadmind in MIT Kerberos 5 (aka krb5) through 1.11.5, 1.12.x through 1.12.2, and 1.13.x before 1.13.1 allows remote authenticated users to bypass a kadmin/* authorization check and obtain administrative access by leveraging access to a two-component princ... | https://nvd.nist.gov/vuln/detail/CVE-2014-9422 |
9,317 | openssl | cb62ab4b17818fe66d2fed0a7fe71969131c811b | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/cb62ab4b17818fe66d2fed0a7fe71969131c811b | use correct function name
Reviewed-by: Rich Salz <rsalz@openssl.org>
Reviewed-by: Matt Caswell <matt@openssl.org> | 1 | int ASN1_item_verify(const ASN1_ITEM *it, X509_ALGOR *a,
ASN1_BIT_STRING *signature, void *asn, EVP_PKEY *pkey)
{
EVP_MD_CTX ctx;
unsigned char *buf_in=NULL;
int ret= -1,inl;
int mdnid, pknid;
if (!pkey)
{
ASN1err(ASN1_F_ASN1_ITEM_VERIFY, ERR_R_PASSED_NULL_PARAMETER);
return -1;
}
if (signature->t... | 82,007,499,822,031,690,000,000,000,000,000,000,000 | None | null | [
"CWE-310"
] | CVE-2014-8275 | OpenSSL before 0.9.8zd, 1.0.0 before 1.0.0p, and 1.0.1 before 1.0.1k does not enforce certain constraints on certificate data, which allows remote attackers to defeat a fingerprint-based certificate-blacklist protection mechanism by including crafted data within a certificate's unsigned portion, related to crypto/asn1/... | https://nvd.nist.gov/vuln/detail/CVE-2014-8275 |
184,444 | openssl | cb62ab4b17818fe66d2fed0a7fe71969131c811b | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/cb62ab4b17818fe66d2fed0a7fe71969131c811b | use correct function name
Reviewed-by: Rich Salz <rsalz@openssl.org>
Reviewed-by: Matt Caswell <matt@openssl.org> | 0 | int ASN1_item_verify(const ASN1_ITEM *it, X509_ALGOR *a,
ASN1_BIT_STRING *signature, void *asn, EVP_PKEY *pkey)
{
EVP_MD_CTX ctx;
unsigned char *buf_in=NULL;
int ret= -1,inl;
int mdnid, pknid;
if (!pkey)
{
ASN1err(ASN1_F_ASN1_ITEM_VERIFY, ERR_R_PASSED_NULL_PARAMETER);
return -1;
}
if (signature->t... | 333,006,062,626,375,700,000,000,000,000,000,000,000 | None | null | [
"CWE-310"
] | CVE-2014-8275 | OpenSSL before 0.9.8zd, 1.0.0 before 1.0.0p, and 1.0.1 before 1.0.1k does not enforce certain constraints on certificate data, which allows remote attackers to defeat a fingerprint-based certificate-blacklist protection mechanism by including crafted data within a certificate's unsigned portion, related to crypto/asn1/... | https://nvd.nist.gov/vuln/detail/CVE-2014-8275 |
9,322 | krb5 | 82dc33da50338ac84c7b4102dc6513d897d0506a | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/82dc33da50338ac84c7b4102dc6513d897d0506a | Fix gss_process_context_token() [CVE-2014-5352]
[MITKRB5-SA-2015-001] The krb5 gss_process_context_token() should not
actually delete the context; that leaves the caller with a dangling
pointer and no way to know that it is invalid. Instead, mark the
context as terminated, and check for terminated contexts in the GSS... | 1 | krb5_gss_process_context_token(minor_status, context_handle,
token_buffer)
OM_uint32 *minor_status;
gss_ctx_id_t context_handle;
gss_buffer_t token_buffer;
{
krb5_gss_ctx_id_rec *ctx;
OM_uint32 majerr;
ctx = (krb5_gss_ctx_id_t) context_handle;
if (! ctx->e... | 158,561,950,850,829,050,000,000,000,000,000,000,000 | process_context_token.c | 268,638,132,235,201,940,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2014-5352 | The krb5_gss_process_context_token function in lib/gssapi/krb5/process_context_token.c in the libgssapi_krb5 library in MIT Kerberos 5 (aka krb5) through 1.11.5, 1.12.x through 1.12.2, and 1.13.x before 1.13.1 does not properly maintain security-context handles, which allows remote authenticated users to cause a denial... | https://nvd.nist.gov/vuln/detail/CVE-2014-5352 |
184,449 | krb5 | 82dc33da50338ac84c7b4102dc6513d897d0506a | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/82dc33da50338ac84c7b4102dc6513d897d0506a | Fix gss_process_context_token() [CVE-2014-5352]
[MITKRB5-SA-2015-001] The krb5 gss_process_context_token() should not
actually delete the context; that leaves the caller with a dangling
pointer and no way to know that it is invalid. Instead, mark the
context as terminated, and check for terminated contexts in the GSS... | 0 | krb5_gss_process_context_token(minor_status, context_handle,
token_buffer)
OM_uint32 *minor_status;
gss_ctx_id_t context_handle;
gss_buffer_t token_buffer;
{
krb5_gss_ctx_id_rec *ctx;
OM_uint32 majerr;
ctx = (krb5_gss_ctx_id_t) context_handle;
if (ctx->ter... | 105,667,265,428,734,220,000,000,000,000,000,000,000 | process_context_token.c | 127,451,855,086,894,580,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2014-5352 | The krb5_gss_process_context_token function in lib/gssapi/krb5/process_context_token.c in the libgssapi_krb5 library in MIT Kerberos 5 (aka krb5) through 1.11.5, 1.12.x through 1.12.2, and 1.13.x before 1.13.1 does not properly maintain security-context handles, which allows remote authenticated users to cause a denial... | https://nvd.nist.gov/vuln/detail/CVE-2014-5352 |
9,325 | linux | 5d26a105b5a73e5635eae0629b42fa0a90e07b7b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/5d26a105b5a73e5635eae0629b42fa0a90e07b7b | crypto: prefix module autoloading with "crypto-"
This prefixes all crypto module loading with "crypto-" so we never run
the risk of exposing module auto-loading to userspace via a crypto API,
as demonstrated by Mathias Krause:
https://lkml.org/lkml/2013/3/4/70
Signed-off-by: Kees Cook <keescook@chromium.org>
Signed-... | 1 | struct crypto_alg *crypto_larval_lookup(const char *name, u32 type, u32 mask)
{
struct crypto_alg *alg;
if (!name)
return ERR_PTR(-ENOENT);
mask &= ~(CRYPTO_ALG_LARVAL | CRYPTO_ALG_DEAD);
type &= mask;
alg = crypto_alg_lookup(name, type, mask);
if (!alg) {
request_module("%s", name);
if (!((type ^ ... | 324,790,015,319,107,200,000,000,000,000,000,000,000 | api.c | 242,936,207,862,042,000,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-7421 | The Crypto API in the Linux kernel before 3.18.5 allows local users to load arbitrary kernel modules via a bind system call for an AF_ALG socket with a module name in the salg_name field, a different vulnerability than CVE-2014-9644. | https://nvd.nist.gov/vuln/detail/CVE-2013-7421 |
184,451 | linux | 5d26a105b5a73e5635eae0629b42fa0a90e07b7b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/5d26a105b5a73e5635eae0629b42fa0a90e07b7b | crypto: prefix module autoloading with "crypto-"
This prefixes all crypto module loading with "crypto-" so we never run
the risk of exposing module auto-loading to userspace via a crypto API,
as demonstrated by Mathias Krause:
https://lkml.org/lkml/2013/3/4/70
Signed-off-by: Kees Cook <keescook@chromium.org>
Signed-... | 0 | struct crypto_alg *crypto_larval_lookup(const char *name, u32 type, u32 mask)
{
struct crypto_alg *alg;
if (!name)
return ERR_PTR(-ENOENT);
mask &= ~(CRYPTO_ALG_LARVAL | CRYPTO_ALG_DEAD);
type &= mask;
alg = crypto_alg_lookup(name, type, mask);
if (!alg) {
request_module("crypto-%s", name);
if (!((... | 315,710,622,014,312,620,000,000,000,000,000,000,000 | api.c | 293,177,305,671,077,580,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-7421 | The Crypto API in the Linux kernel before 3.18.5 allows local users to load arbitrary kernel modules via a bind system call for an AF_ALG socket with a module name in the salg_name field, a different vulnerability than CVE-2014-9644. | https://nvd.nist.gov/vuln/detail/CVE-2013-7421 |
9,326 | linux | bf911e985d6bbaa328c20c3e05f4eb03de11fdd6 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/bf911e985d6bbaa328c20c3e05f4eb03de11fdd6 | sctp: validate chunk len before actually using it
Andrey Konovalov reported that KASAN detected that SCTP was using a slab
beyond the boundaries. It was caused because when handling out of the
blue packets in function sctp_sf_ootb() it was checking the chunk len
only after already processing the first chunk, validatin... | 1 | sctp_disposition_t sctp_sf_ootb(struct net *net,
const struct sctp_endpoint *ep,
const struct sctp_association *asoc,
const sctp_subtype_t type,
void *arg,
sctp_cmd_seq_t *commands)
{
struct sctp_chunk *chunk = arg;
struct sk_buff *skb = chunk->skb;
sctp_chunkhdr_t *ch;
sctp_errhdr_t *err;
__u8... | 324,777,000,170,628,950,000,000,000,000,000,000,000 | sm_statefuns.c | 57,717,278,456,982,200,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2016-9555 | The sctp_sf_ootb function in net/sctp/sm_statefuns.c in the Linux kernel before 4.8.8 lacks chunk-length checking for the first chunk, which allows remote attackers to cause a denial of service (out-of-bounds slab access) or possibly have unspecified other impact via crafted SCTP data. | https://nvd.nist.gov/vuln/detail/CVE-2016-9555 |
184,452 | linux | bf911e985d6bbaa328c20c3e05f4eb03de11fdd6 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/bf911e985d6bbaa328c20c3e05f4eb03de11fdd6 | sctp: validate chunk len before actually using it
Andrey Konovalov reported that KASAN detected that SCTP was using a slab
beyond the boundaries. It was caused because when handling out of the
blue packets in function sctp_sf_ootb() it was checking the chunk len
only after already processing the first chunk, validatin... | 0 | sctp_disposition_t sctp_sf_ootb(struct net *net,
const struct sctp_endpoint *ep,
const struct sctp_association *asoc,
const sctp_subtype_t type,
void *arg,
sctp_cmd_seq_t *commands)
{
struct sctp_chunk *chunk = arg;
struct sk_buff *skb = chunk->skb;
sctp_chunkhdr_t *ch;
sctp_errhdr_t *err;
__u8... | 339,890,610,459,448,240,000,000,000,000,000,000,000 | sm_statefuns.c | 239,670,809,574,687,900,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2016-9555 | The sctp_sf_ootb function in net/sctp/sm_statefuns.c in the Linux kernel before 4.8.8 lacks chunk-length checking for the first chunk, which allows remote attackers to cause a denial of service (out-of-bounds slab access) or possibly have unspecified other impact via crafted SCTP data. | https://nvd.nist.gov/vuln/detail/CVE-2016-9555 |
9,332 | linux | f5527fffff3f002b0a6b376163613b82f69de073 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f5527fffff3f002b0a6b376163613b82f69de073 | mpi: Fix NULL ptr dereference in mpi_powm() [ver #3]
This fixes CVE-2016-8650.
If mpi_powm() is given a zero exponent, it wants to immediately return
either 1 or 0, depending on the modulus. However, if the result was
initalised with zero limb space, no limbs space is allocated and a
NULL-pointer exception ensues.
... | 1 | int mpi_powm(MPI res, MPI base, MPI exp, MPI mod)
{
mpi_ptr_t mp_marker = NULL, bp_marker = NULL, ep_marker = NULL;
mpi_ptr_t xp_marker = NULL;
mpi_ptr_t tspace = NULL;
mpi_ptr_t rp, ep, mp, bp;
mpi_size_t esize, msize, bsize, rsize;
int esign, msign, bsign, rsign;
mpi_size_t size;
int mod_shift_cnt;
int negat... | 52,745,785,378,836,690,000,000,000,000,000,000,000 | mpi-pow.c | 265,062,024,780,737,600,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-8650 | The mpi_powm function in lib/mpi/mpi-pow.c in the Linux kernel through 4.8.11 does not ensure that memory is allocated for limb data, which allows local users to cause a denial of service (stack memory corruption and panic) via an add_key system call for an RSA key with a zero exponent. | https://nvd.nist.gov/vuln/detail/CVE-2016-8650 |
184,457 | linux | f5527fffff3f002b0a6b376163613b82f69de073 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f5527fffff3f002b0a6b376163613b82f69de073 | mpi: Fix NULL ptr dereference in mpi_powm() [ver #3]
This fixes CVE-2016-8650.
If mpi_powm() is given a zero exponent, it wants to immediately return
either 1 or 0, depending on the modulus. However, if the result was
initalised with zero limb space, no limbs space is allocated and a
NULL-pointer exception ensues.
... | 0 | int mpi_powm(MPI res, MPI base, MPI exp, MPI mod)
{
mpi_ptr_t mp_marker = NULL, bp_marker = NULL, ep_marker = NULL;
mpi_ptr_t xp_marker = NULL;
mpi_ptr_t tspace = NULL;
mpi_ptr_t rp, ep, mp, bp;
mpi_size_t esize, msize, bsize, rsize;
int esign, msign, bsign, rsign;
mpi_size_t size;
int mod_shift_cnt;
int negat... | 80,672,488,438,415,300,000,000,000,000,000,000,000 | mpi-pow.c | 83,154,361,021,688,860,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-8650 | The mpi_powm function in lib/mpi/mpi-pow.c in the Linux kernel through 4.8.11 does not ensure that memory is allocated for limb data, which allows local users to cause a denial of service (stack memory corruption and panic) via an add_key system call for an RSA key with a zero exponent. | https://nvd.nist.gov/vuln/detail/CVE-2016-8650 |
9,333 | linux | 8148a73c9901a8794a50f950083c00ccf97d43b3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8148a73c9901a8794a50f950083c00ccf97d43b3 | proc: prevent accessing /proc/<PID>/environ until it's ready
If /proc/<PID>/environ gets read before the envp[] array is fully set up
in create_{aout,elf,elf_fdpic,flat}_tables(), we might end up trying to
read more bytes than are actually written, as env_start will already be
set but env_end will still be zero, makin... | 1 | static ssize_t environ_read(struct file *file, char __user *buf,
size_t count, loff_t *ppos)
{
char *page;
unsigned long src = *ppos;
int ret = 0;
struct mm_struct *mm = file->private_data;
unsigned long env_start, env_end;
if (!mm)
return 0;
page = (char *)__get_free_page(GFP_TEMPORARY);
if (!page... | 154,024,528,585,163,020,000,000,000,000,000,000,000 | base.c | 174,177,174,530,935,130,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2016-7916 | Race condition in the environ_read function in fs/proc/base.c in the Linux kernel before 4.5.4 allows local users to obtain sensitive information from kernel memory by reading a /proc/*/environ file during a process-setup time interval in which environment-variable copying is incomplete. | https://nvd.nist.gov/vuln/detail/CVE-2016-7916 |
184,458 | linux | 8148a73c9901a8794a50f950083c00ccf97d43b3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8148a73c9901a8794a50f950083c00ccf97d43b3 | proc: prevent accessing /proc/<PID>/environ until it's ready
If /proc/<PID>/environ gets read before the envp[] array is fully set up
in create_{aout,elf,elf_fdpic,flat}_tables(), we might end up trying to
read more bytes than are actually written, as env_start will already be
set but env_end will still be zero, makin... | 0 | static ssize_t environ_read(struct file *file, char __user *buf,
size_t count, loff_t *ppos)
{
char *page;
unsigned long src = *ppos;
int ret = 0;
struct mm_struct *mm = file->private_data;
unsigned long env_start, env_end;
/* Ensure the process spawned far enough to have an environment. */
if (!mm || !mm... | 179,708,708,730,868,570,000,000,000,000,000,000,000 | base.c | 60,592,448,060,544,760,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2016-7916 | Race condition in the environ_read function in fs/proc/base.c in the Linux kernel before 4.5.4 allows local users to obtain sensitive information from kernel memory by reading a /proc/*/environ file during a process-setup time interval in which environment-variable copying is incomplete. | https://nvd.nist.gov/vuln/detail/CVE-2016-7916 |
9,334 | linux | 7bc2b55a5c030685b399bb65b6baa9ccc3d1f167 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7bc2b55a5c030685b399bb65b6baa9ccc3d1f167 | scsi: arcmsr: Buffer overflow in arcmsr_iop_message_xfer()
We need to put an upper bound on "user_len" so the memcpy() doesn't
overflow.
Cc: <stable@vger.kernel.org>
Reported-by: Marco Grassi <marco.gra@gmail.com>
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Reviewed-by: Tomas Henzl <thenzl@redhat.com>
Sig... | 1 | static int arcmsr_iop_message_xfer(struct AdapterControlBlock *acb,
struct scsi_cmnd *cmd)
{
char *buffer;
unsigned short use_sg;
int retvalue = 0, transfer_len = 0;
unsigned long flags;
struct CMD_MESSAGE_FIELD *pcmdmessagefld;
uint32_t controlcode = (uint32_t)cmd->cmnd[5] << 24 |
(uint32_t)cmd->cmnd[6] << 1... | 280,628,888,206,953,260,000,000,000,000,000,000,000 | arcmsr_hba.c | 263,709,549,106,019,150,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-7425 | The arcmsr_iop_message_xfer function in drivers/scsi/arcmsr/arcmsr_hba.c in the Linux kernel through 4.8.2 does not restrict a certain length field, which allows local users to gain privileges or cause a denial of service (heap-based buffer overflow) via an ARCMSR_MESSAGE_WRITE_WQBUFFER control code. | https://nvd.nist.gov/vuln/detail/CVE-2016-7425 |
184,459 | linux | 7bc2b55a5c030685b399bb65b6baa9ccc3d1f167 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7bc2b55a5c030685b399bb65b6baa9ccc3d1f167 | scsi: arcmsr: Buffer overflow in arcmsr_iop_message_xfer()
We need to put an upper bound on "user_len" so the memcpy() doesn't
overflow.
Cc: <stable@vger.kernel.org>
Reported-by: Marco Grassi <marco.gra@gmail.com>
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Reviewed-by: Tomas Henzl <thenzl@redhat.com>
Sig... | 0 | static int arcmsr_iop_message_xfer(struct AdapterControlBlock *acb,
struct scsi_cmnd *cmd)
{
char *buffer;
unsigned short use_sg;
int retvalue = 0, transfer_len = 0;
unsigned long flags;
struct CMD_MESSAGE_FIELD *pcmdmessagefld;
uint32_t controlcode = (uint32_t)cmd->cmnd[5] << 24 |
(uint32_t)cmd->cmnd[6] << 1... | 4,543,714,354,896,753,400,000,000,000,000,000,000 | arcmsr_hba.c | 105,798,901,421,870,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-7425 | The arcmsr_iop_message_xfer function in drivers/scsi/arcmsr/arcmsr_hba.c in the Linux kernel through 4.8.2 does not restrict a certain length field, which allows local users to gain privileges or cause a denial of service (heap-based buffer overflow) via an ARCMSR_MESSAGE_WRITE_WQBUFFER control code. | https://nvd.nist.gov/vuln/detail/CVE-2016-7425 |
9,336 | php-src | b88393f08a558eec14964a55d3c680fe67407712 | https://github.com/php/php-src | https://github.com/php/php-src/commit/b88393f08a558eec14964a55d3c680fe67407712?w=1 | Fix bug #72860: wddx_deserialize use-after-free | 1 | static int wddx_stack_destroy(wddx_stack *stack)
{
register int i;
if (stack->elements) {
for (i = 0; i < stack->top; i++) {
if (((st_entry *)stack->elements[i])->data) {
zval_ptr_dtor(&((st_entry *)stack->elements[i])->data);
}
if (((st_entry *)stack->elements[i])->varname) {
efree(((st_ent... | 167,114,955,492,293,730,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2016-7413 | Use-after-free vulnerability in the wddx_stack_destroy function in ext/wddx/wddx.c in PHP before 5.6.26 and 7.x before 7.0.11 allows remote attackers to cause a denial of service or possibly have unspecified other impact via a wddxPacket XML document that lacks an end-tag for a recordset field element, leading to misha... | https://nvd.nist.gov/vuln/detail/CVE-2016-7413 |
184,461 | php-src | b88393f08a558eec14964a55d3c680fe67407712 | https://github.com/php/php-src | https://github.com/php/php-src/commit/b88393f08a558eec14964a55d3c680fe67407712?w=1 | Fix bug #72860: wddx_deserialize use-after-free | 0 | static int wddx_stack_destroy(wddx_stack *stack)
{
register int i;
if (stack->elements) {
for (i = 0; i < stack->top; i++) {
if (((st_entry *)stack->elements[i])->data
&& ((st_entry *)stack->elements[i])->type != ST_FIELD) {
zval_ptr_dtor(&((st_entry *)stack->elements[i])->data);
}
if (((st... | 91,378,896,002,095,350,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2016-7413 | Use-after-free vulnerability in the wddx_stack_destroy function in ext/wddx/wddx.c in PHP before 5.6.26 and 7.x before 7.0.11 allows remote attackers to cause a denial of service or possibly have unspecified other impact via a wddxPacket XML document that lacks an end-tag for a recordset field element, leading to misha... | https://nvd.nist.gov/vuln/detail/CVE-2016-7413 |
9,337 | charybdis | 818a3fda944b26d4814132cee14cfda4ea4aa824 | https://github.com/charybdis-ircd/charybdis | https://github.com/charybdis-ircd/charybdis/commit/818a3fda944b26d4814132cee14cfda4ea4aa824 | SASL: Disallow beginning : and space anywhere in AUTHENTICATE parameter
This is a FIX FOR A SECURITY VULNERABILITY. All Charybdis users must
apply this fix if you support SASL on your servers, or unload m_sasl.so
in the meantime. | 1 | m_authenticate(struct Client *client_p, struct Client *source_p,
int parc, const char *parv[])
{
struct Client *agent_p = NULL;
struct Client *saslserv_p = NULL;
/* They really should use CAP for their own sake. */
if(!IsCapable(source_p, CLICAP_SASL))
return 0;
if (strlen(client_p->id) == 3)
{
exit_client... | 245,147,725,102,129,400,000,000,000,000,000,000,000 | m_sasl.c | 250,746,651,209,914,400,000,000,000,000,000,000,000 | [
"CWE-285"
] | CVE-2016-7143 | The m_authenticate function in modules/m_sasl.c in Charybdis before 3.5.3 allows remote attackers to spoof certificate fingerprints and consequently log in as another user via a crafted AUTHENTICATE parameter. | https://nvd.nist.gov/vuln/detail/CVE-2016-7143 |
184,462 | charybdis | 818a3fda944b26d4814132cee14cfda4ea4aa824 | https://github.com/charybdis-ircd/charybdis | https://github.com/charybdis-ircd/charybdis/commit/818a3fda944b26d4814132cee14cfda4ea4aa824 | SASL: Disallow beginning : and space anywhere in AUTHENTICATE parameter
This is a FIX FOR A SECURITY VULNERABILITY. All Charybdis users must
apply this fix if you support SASL on your servers, or unload m_sasl.so
in the meantime. | 0 | m_authenticate(struct Client *client_p, struct Client *source_p,
int parc, const char *parv[])
{
struct Client *agent_p = NULL;
struct Client *saslserv_p = NULL;
/* They really should use CAP for their own sake. */
if(!IsCapable(source_p, CLICAP_SASL))
return 0;
if (strlen(client_p->id) == 3)
{
exit_client... | 56,541,943,419,364,145,000,000,000,000,000,000,000 | m_sasl.c | 304,912,785,726,819,350,000,000,000,000,000,000,000 | [
"CWE-285"
] | CVE-2016-7143 | The m_authenticate function in modules/m_sasl.c in Charybdis before 3.5.3 allows remote attackers to spoof certificate fingerprints and consequently log in as another user via a crafted AUTHENTICATE parameter. | https://nvd.nist.gov/vuln/detail/CVE-2016-7143 |
9,343 | libgd | 01c61f8ab110a77ae64b5ca67c244c728c506f03 | https://github.com/libgd/libgd | https://github.com/libgd/libgd/commit/01c61f8ab110a77ae64b5ca67c244c728c506f03 | Proper fix for #248 | 1 | int read_image_tga( gdIOCtx *ctx, oTga *tga )
{
int pixel_block_size = (tga->bits / 8);
int image_block_size = (tga->width * tga->height) * pixel_block_size;
uint8_t* decompression_buffer = NULL;
unsigned char* conversion_buffer = NULL;
int buffer_caret = 0;
int bitmap_caret = 0;
int i = 0;
int j = 0;
uint... | 28,079,061,121,387,740,000,000,000,000,000,000,000 | gd_tga.c | 123,375,562,412,498,340,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2016-6905 | The read_image_tga function in gd_tga.c in the GD Graphics Library (aka libgd) before 2.2.3 allows remote attackers to cause a denial of service (out-of-bounds read) via a crafted TGA image. | https://nvd.nist.gov/vuln/detail/CVE-2016-6905 |
184,466 | libgd | 01c61f8ab110a77ae64b5ca67c244c728c506f03 | https://github.com/libgd/libgd | https://github.com/libgd/libgd/commit/01c61f8ab110a77ae64b5ca67c244c728c506f03 | Proper fix for #248 | 0 | int read_image_tga( gdIOCtx *ctx, oTga *tga )
{
int pixel_block_size = (tga->bits / 8);
int image_block_size = (tga->width * tga->height) * pixel_block_size;
uint8_t* decompression_buffer = NULL;
unsigned char* conversion_buffer = NULL;
int buffer_caret = 0;
int bitmap_caret = 0;
int i = 0;
uint8_t encoded_... | 41,145,075,528,071,100,000,000,000,000,000,000,000 | gd_tga.c | 301,385,883,061,048,700,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2016-6905 | The read_image_tga function in gd_tga.c in the GD Graphics Library (aka libgd) before 2.2.3 allows remote attackers to cause a denial of service (out-of-bounds read) via a crafted TGA image. | https://nvd.nist.gov/vuln/detail/CVE-2016-6905 |
9,348 | linux | 43761473c254b45883a64441dd0bc85a42f3645c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/43761473c254b45883a64441dd0bc85a42f3645c | audit: fix a double fetch in audit_log_single_execve_arg()
There is a double fetch problem in audit_log_single_execve_arg()
where we first check the execve(2) argumnets for any "bad" characters
which would require hex encoding and then re-fetch the arguments for
logging in the audit record[1]. Of course this leaves a... | 1 | static int audit_log_single_execve_arg(struct audit_context *context,
struct audit_buffer **ab,
int arg_num,
size_t *len_sent,
const char __user *p,
char *buf)
{
char arg_num_len_buf[12];
const char __user *tmp_p = p;
/* how many digits are in arg_num? 5 is the length of ' a=""' */
size_t ... | 315,514,706,975,674,840,000,000,000,000,000,000,000 | auditsc.c | 30,820,339,966,201,292,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2016-6136 | Race condition in the audit_log_single_execve_arg function in kernel/auditsc.c in the Linux kernel through 4.7 allows local users to bypass intended character-set restrictions or disrupt system-call auditing by changing a certain string, aka a "double fetch" vulnerability. | https://nvd.nist.gov/vuln/detail/CVE-2016-6136 |
184,470 | linux | 43761473c254b45883a64441dd0bc85a42f3645c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/43761473c254b45883a64441dd0bc85a42f3645c | audit: fix a double fetch in audit_log_single_execve_arg()
There is a double fetch problem in audit_log_single_execve_arg()
where we first check the execve(2) argumnets for any "bad" characters
which would require hex encoding and then re-fetch the arguments for
logging in the audit record[1]. Of course this leaves a... | 0 | static int audit_log_single_execve_arg(struct audit_context *context,
static void audit_log_execve_info(struct audit_context *context,
struct audit_buffer **ab)
{
long len_max;
long len_rem;
long len_full;
long len_buf;
long len_abuf;
long len_tmp;
bool require_data;
bool encode;
unsigned int iter;
uns... | 82,379,677,640,088,730,000,000,000,000,000,000,000 | None | null | [
"CWE-362"
] | CVE-2016-6136 | Race condition in the audit_log_single_execve_arg function in kernel/auditsc.c in the Linux kernel through 4.7 allows local users to bypass intended character-set restrictions or disrupt system-call auditing by changing a certain string, aka a "double fetch" vulnerability. | https://nvd.nist.gov/vuln/detail/CVE-2016-6136 |
9,389 | openssl | 0ed26acce328ec16a3aa635f1ca37365e8c7403a | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/0ed26acce328ec16a3aa635f1ca37365e8c7403a | Fix OOB read in TS_OBJ_print_bio().
TS_OBJ_print_bio() misuses OBJ_txt2obj: it should print the result
as a null terminated buffer. The length value returned is the total
length the complete text reprsentation would need not the amount of
data written.
CVE-2016-2180
Thanks to Shi Lei for reporting this bug.
Reviewe... | 1 | int TS_OBJ_print_bio(BIO *bio, const ASN1_OBJECT *obj)
{
char obj_txt[128];
int len = OBJ_obj2txt(obj_txt, sizeof(obj_txt), obj, 0);
BIO_write(bio, obj_txt, len);
BIO_write(bio, "\n", 1);
return 1;
}
| 23,563,415,281,384,434,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2016-2180 | The TS_OBJ_print_bio function in crypto/ts/ts_lib.c in the X.509 Public Key Infrastructure Time-Stamp Protocol (TSP) implementation in OpenSSL through 1.0.2h allows remote attackers to cause a denial of service (out-of-bounds read and application crash) via a crafted time-stamp file that is mishandled by the "openssl t... | https://nvd.nist.gov/vuln/detail/CVE-2016-2180 |
184,491 | openssl | 0ed26acce328ec16a3aa635f1ca37365e8c7403a | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/0ed26acce328ec16a3aa635f1ca37365e8c7403a | Fix OOB read in TS_OBJ_print_bio().
TS_OBJ_print_bio() misuses OBJ_txt2obj: it should print the result
as a null terminated buffer. The length value returned is the total
length the complete text reprsentation would need not the amount of
data written.
CVE-2016-2180
Thanks to Shi Lei for reporting this bug.
Reviewe... | 0 | int TS_OBJ_print_bio(BIO *bio, const ASN1_OBJECT *obj)
{
char obj_txt[128];
OBJ_obj2txt(obj_txt, sizeof(obj_txt), obj, 0);
BIO_printf(bio, "%s\n", obj_txt);
return 1;
}
| 148,174,202,715,247,570,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2016-2180 | The TS_OBJ_print_bio function in crypto/ts/ts_lib.c in the X.509 Public Key Infrastructure Time-Stamp Protocol (TSP) implementation in OpenSSL through 1.0.2h allows remote attackers to cause a denial of service (out-of-bounds read and application crash) via a crafted time-stamp file that is mishandled by the "openssl t... | https://nvd.nist.gov/vuln/detail/CVE-2016-2180 |
9,390 | linux | 23c8a812dc3c621009e4f0e5342aa4e2ede1ceaa | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/23c8a812dc3c621009e4f0e5342aa4e2ede1ceaa | KEYS: Fix ASN.1 indefinite length object parsing
This fixes CVE-2016-0758.
In the ASN.1 decoder, when the length field of an ASN.1 value is extracted,
it isn't validated against the remaining amount of data before being added
to the cursor. With a sufficiently large size indicated, the check:
datalen - dp < 2
may... | 1 | static int asn1_find_indefinite_length(const unsigned char *data, size_t datalen,
size_t *_dp, size_t *_len,
const char **_errmsg)
{
unsigned char tag, tmp;
size_t dp = *_dp, len, n;
int indef_level = 1;
next_tag:
if (unlikely(datalen - dp < 2)) {
if (datalen == dp)
goto missing_eoc;
g... | 207,849,252,963,623,300,000,000,000,000,000,000,000 | asn1_decoder.c | 194,942,407,892,131,830,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2016-0758 | Integer overflow in lib/asn1_decoder.c in the Linux kernel before 4.6 allows local users to gain privileges via crafted ASN.1 data. | https://nvd.nist.gov/vuln/detail/CVE-2016-0758 |
184,492 | linux | 23c8a812dc3c621009e4f0e5342aa4e2ede1ceaa | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/23c8a812dc3c621009e4f0e5342aa4e2ede1ceaa | KEYS: Fix ASN.1 indefinite length object parsing
This fixes CVE-2016-0758.
In the ASN.1 decoder, when the length field of an ASN.1 value is extracted,
it isn't validated against the remaining amount of data before being added
to the cursor. With a sufficiently large size indicated, the check:
datalen - dp < 2
may... | 0 | static int asn1_find_indefinite_length(const unsigned char *data, size_t datalen,
size_t *_dp, size_t *_len,
const char **_errmsg)
{
unsigned char tag, tmp;
size_t dp = *_dp, len, n;
int indef_level = 1;
next_tag:
if (unlikely(datalen - dp < 2)) {
if (datalen == dp)
goto missing_eoc;
g... | 62,776,827,936,979,040,000,000,000,000,000,000,000 | asn1_decoder.c | 191,323,920,066,634,150,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2016-0758 | Integer overflow in lib/asn1_decoder.c in the Linux kernel before 4.6 allows local users to gain privileges via crafted ASN.1 data. | https://nvd.nist.gov/vuln/detail/CVE-2016-0758 |
9,391 | linux | 5c17c861a357e9458001f021a7afa7aab9937439 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/5c17c861a357e9458001f021a7afa7aab9937439 | tty: Fix unsafe ldisc reference via ioctl(TIOCGETD)
ioctl(TIOCGETD) retrieves the line discipline id directly from the
ldisc because the line discipline id (c_line) in termios is untrustworthy;
userspace may have set termios via ioctl(TCSETS*) without actually
changing the line discipline via ioctl(TIOCSETD).
However... | 1 | long tty_ioctl(struct file *file, unsigned int cmd, unsigned long arg)
{
struct tty_struct *tty = file_tty(file);
struct tty_struct *real_tty;
void __user *p = (void __user *)arg;
int retval;
struct tty_ldisc *ld;
if (tty_paranoia_check(tty, file_inode(file), "tty_ioctl"))
return -EINVAL;
real_tty = tty_pair... | 250,376,623,282,860,260,000,000,000,000,000,000,000 | tty_io.c | 271,836,844,159,911,300,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2016-0723 | Race condition in the tty_ioctl function in drivers/tty/tty_io.c in the Linux kernel through 4.4.1 allows local users to obtain sensitive information from kernel memory or cause a denial of service (use-after-free and system crash) by making a TIOCGETD ioctl call during processing of a TIOCSETD ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2016-0723 |
184,493 | linux | 5c17c861a357e9458001f021a7afa7aab9937439 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/5c17c861a357e9458001f021a7afa7aab9937439 | tty: Fix unsafe ldisc reference via ioctl(TIOCGETD)
ioctl(TIOCGETD) retrieves the line discipline id directly from the
ldisc because the line discipline id (c_line) in termios is untrustworthy;
userspace may have set termios via ioctl(TCSETS*) without actually
changing the line discipline via ioctl(TIOCSETD).
However... | 0 | long tty_ioctl(struct file *file, unsigned int cmd, unsigned long arg)
{
struct tty_struct *tty = file_tty(file);
struct tty_struct *real_tty;
void __user *p = (void __user *)arg;
int retval;
struct tty_ldisc *ld;
if (tty_paranoia_check(tty, file_inode(file), "tty_ioctl"))
return -EINVAL;
real_tty = tty_pair... | 246,115,441,572,782,900,000,000,000,000,000,000,000 | tty_io.c | 209,003,959,513,187,400,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2016-0723 | Race condition in the tty_ioctl function in drivers/tty/tty_io.c in the Linux kernel through 4.4.1 allows local users to obtain sensitive information from kernel memory or cause a denial of service (use-after-free and system crash) by making a TIOCGETD ioctl call during processing of a TIOCSETD ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2016-0723 |
9,392 | dosfstools | 07908124838afcc99c577d1d3e84cef2dbd39cb7 | https://github.com/dosfstools/dosfstools | https://github.com/dosfstools/dosfstools/commit/07908124838afcc99c577d1d3e84cef2dbd39cb7 | set_fat(): Fix off-by-2 error leading to corruption in FAT12
In FAT12 two 12 bit entries are combined to a 24 bit value (three
bytes). Therefore, when an even numbered FAT entry is set in FAT12, it
must be be combined with the following entry. To prevent accessing
beyond the end of the FAT array, it must be checked th... | 1 | void set_fat(DOS_FS * fs, uint32_t cluster, int32_t new)
{
unsigned char *data = NULL;
int size;
loff_t offs;
if (new == -1)
new = FAT_EOF(fs);
else if ((long)new == -2)
new = FAT_BAD(fs);
switch (fs->fat_bits) {
case 12:
data = fs->fat + cluster * 3 / 2;
offs = fs->fat_start + cluster ... | 55,173,971,612,937,990,000,000,000,000,000,000,000 | fat.c | 15,574,431,569,440,080,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2015-8872 | The set_fat function in fat.c in dosfstools before 4.0 might allow attackers to corrupt a FAT12 filesystem or cause a denial of service (invalid memory read and crash) by writing an odd number of clusters to the third to last entry on a FAT12 filesystem, which triggers an "off-by-two error." | https://nvd.nist.gov/vuln/detail/CVE-2015-8872 |
184,494 | dosfstools | 07908124838afcc99c577d1d3e84cef2dbd39cb7 | https://github.com/dosfstools/dosfstools | https://github.com/dosfstools/dosfstools/commit/07908124838afcc99c577d1d3e84cef2dbd39cb7 | set_fat(): Fix off-by-2 error leading to corruption in FAT12
In FAT12 two 12 bit entries are combined to a 24 bit value (three
bytes). Therefore, when an even numbered FAT entry is set in FAT12, it
must be be combined with the following entry. To prevent accessing
beyond the end of the FAT array, it must be checked th... | 0 | void set_fat(DOS_FS * fs, uint32_t cluster, int32_t new)
{
unsigned char *data = NULL;
int size;
loff_t offs;
if (new == -1)
new = FAT_EOF(fs);
else if ((long)new == -2)
new = FAT_BAD(fs);
switch (fs->fat_bits) {
case 12:
data = fs->fat + cluster * 3 / 2;
offs = fs->fat_start + cluster ... | 208,429,240,369,048,840,000,000,000,000,000,000,000 | fat.c | 258,057,985,473,446,600,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2015-8872 | The set_fat function in fat.c in dosfstools before 4.0 might allow attackers to corrupt a FAT12 filesystem or cause a denial of service (invalid memory read and crash) by writing an odd number of clusters to the third to last entry on a FAT12 filesystem, which triggers an "off-by-two error." | https://nvd.nist.gov/vuln/detail/CVE-2015-8872 |
9,394 | linux | e50293ef9775c5f1cf3fcc093037dd6a8c5684ea | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e50293ef9775c5f1cf3fcc093037dd6a8c5684ea | USB: fix invalid memory access in hub_activate()
Commit 8520f38099cc ("USB: change hub initialization sleeps to
delayed_work") changed the hub_activate() routine to make part of it
run in a workqueue. However, the commit failed to take a reference to
the usb_hub structure or to lock the hub interface while doing so. ... | 1 | static void hub_activate(struct usb_hub *hub, enum hub_activation_type type)
{
struct usb_device *hdev = hub->hdev;
struct usb_hcd *hcd;
int ret;
int port1;
int status;
bool need_debounce_delay = false;
unsigned delay;
/* Continue a partial initialization */
if (type == HUB_INIT2)
goto init2;
if (type =... | 70,755,082,858,795,600,000,000,000,000,000,000,000 | hub.c | 290,566,164,472,724,600,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2015-8816 | The hub_activate function in drivers/usb/core/hub.c in the Linux kernel before 4.3.5 does not properly maintain a hub-interface data structure, which allows physically proximate attackers to cause a denial of service (invalid memory access and system crash) or possibly have unspecified other impact by unplugging a USB ... | https://nvd.nist.gov/vuln/detail/CVE-2015-8816 |
184,496 | linux | e50293ef9775c5f1cf3fcc093037dd6a8c5684ea | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e50293ef9775c5f1cf3fcc093037dd6a8c5684ea | USB: fix invalid memory access in hub_activate()
Commit 8520f38099cc ("USB: change hub initialization sleeps to
delayed_work") changed the hub_activate() routine to make part of it
run in a workqueue. However, the commit failed to take a reference to
the usb_hub structure or to lock the hub interface while doing so. ... | 0 | static void hub_activate(struct usb_hub *hub, enum hub_activation_type type)
{
struct usb_device *hdev = hub->hdev;
struct usb_hcd *hcd;
int ret;
int port1;
int status;
bool need_debounce_delay = false;
unsigned delay;
/* Continue a partial initialization */
if (type == HUB_INIT2 || type == HUB_INIT3) {
... | 210,945,061,073,446,920,000,000,000,000,000,000,000 | hub.c | 128,007,697,666,704,870,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2015-8816 | The hub_activate function in drivers/usb/core/hub.c in the Linux kernel before 4.3.5 does not properly maintain a hub-interface data structure, which allows physically proximate attackers to cause a denial of service (invalid memory access and system crash) or possibly have unspecified other impact by unplugging a USB ... | https://nvd.nist.gov/vuln/detail/CVE-2015-8816 |
9,401 | hexchat | c9b63f7f9be01692b03fa15275135a4910a7e02d | https://github.com/hexchat/hexchat | https://github.com/hexchat/hexchat/commit/c9b63f7f9be01692b03fa15275135a4910a7e02d | ssl: Validate hostnames
Closes #524 | 1 | ssl_do_connect (server * serv)
{
char buf[128];
g_sess = serv->server_session;
if (SSL_connect (serv->ssl) <= 0)
{
char err_buf[128];
int err;
g_sess = NULL;
if ((err = ERR_get_error ()) > 0)
{
ERR_error_string (err, err_buf);
snprintf (buf, sizeof (buf), "(%d) %s", err, err_buf);
EMIT_SIGNAL (... | 283,876,863,796,405,900,000,000,000,000,000,000,000 | server.c | 59,660,602,516,359,420,000,000,000,000,000,000,000 | [
"CWE-310"
] | CVE-2013-7449 | The ssl_do_connect function in common/server.c in HexChat before 2.10.2, XChat, and XChat-GNOME does not verify that the server hostname matches a domain name in the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate. | https://nvd.nist.gov/vuln/detail/CVE-2013-7449 |
184,505 | hexchat | c9b63f7f9be01692b03fa15275135a4910a7e02d | https://github.com/hexchat/hexchat | https://github.com/hexchat/hexchat/commit/c9b63f7f9be01692b03fa15275135a4910a7e02d | ssl: Validate hostnames
Closes #524 | 0 | ssl_do_connect (server * serv)
{
char buf[128];
g_sess = serv->server_session;
if (SSL_connect (serv->ssl) <= 0)
{
char err_buf[128];
int err;
g_sess = NULL;
if ((err = ERR_get_error ()) > 0)
{
ERR_error_string (err, err_buf);
snprintf (buf, sizeof (buf), "(%d) %s", err, err_buf);
EMIT_SIGNAL (... | 204,130,839,985,195,200,000,000,000,000,000,000,000 | server.c | 196,415,928,665,548,940,000,000,000,000,000,000,000 | [
"CWE-310"
] | CVE-2013-7449 | The ssl_do_connect function in common/server.c in HexChat before 2.10.2, XChat, and XChat-GNOME does not verify that the server hostname matches a domain name in the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate. | https://nvd.nist.gov/vuln/detail/CVE-2013-7449 |
9,407 | linux | 2b7e8665b4ff51c034c55df3cff76518d1a9ee3a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b7e8665b4ff51c034c55df3cff76518d1a9ee3a | fork: fix incorrect fput of ->exe_file causing use-after-free
Commit 7c051267931a ("mm, fork: make dup_mmap wait for mmap_sem for
write killable") made it possible to kill a forking task while it is
waiting to acquire its ->mmap_sem for write, in dup_mmap().
However, it was overlooked that this introduced an new erro... | 1 | static struct mm_struct *mm_init(struct mm_struct *mm, struct task_struct *p,
struct user_namespace *user_ns)
{
mm->mmap = NULL;
mm->mm_rb = RB_ROOT;
mm->vmacache_seqnum = 0;
atomic_set(&mm->mm_users, 1);
atomic_set(&mm->mm_count, 1);
init_rwsem(&mm->mmap_sem);
INIT_LIST_HEAD(&mm->mmlist);
mm->core_state = NUL... | 266,885,714,175,674,640,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2017-17052 | The mm_init function in kernel/fork.c in the Linux kernel before 4.12.10 does not clear the ->exe_file member of a new process's mm_struct, allowing a local attacker to achieve a use-after-free or possibly have unspecified other impact by running a specially crafted program. | https://nvd.nist.gov/vuln/detail/CVE-2017-17052 |
184,509 | linux | 2b7e8665b4ff51c034c55df3cff76518d1a9ee3a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b7e8665b4ff51c034c55df3cff76518d1a9ee3a | fork: fix incorrect fput of ->exe_file causing use-after-free
Commit 7c051267931a ("mm, fork: make dup_mmap wait for mmap_sem for
write killable") made it possible to kill a forking task while it is
waiting to acquire its ->mmap_sem for write, in dup_mmap().
However, it was overlooked that this introduced an new erro... | 0 | static struct mm_struct *mm_init(struct mm_struct *mm, struct task_struct *p,
struct user_namespace *user_ns)
{
mm->mmap = NULL;
mm->mm_rb = RB_ROOT;
mm->vmacache_seqnum = 0;
atomic_set(&mm->mm_users, 1);
atomic_set(&mm->mm_count, 1);
init_rwsem(&mm->mmap_sem);
INIT_LIST_HEAD(&mm->mmlist);
mm->core_state = NUL... | 339,868,848,667,323,300,000,000,000,000,000,000,000 | fork.c | 338,731,942,757,022,300,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2017-17052 | The mm_init function in kernel/fork.c in the Linux kernel before 4.12.10 does not clear the ->exe_file member of a new process's mm_struct, allowing a local attacker to achieve a use-after-free or possibly have unspecified other impact by running a specially crafted program. | https://nvd.nist.gov/vuln/detail/CVE-2017-17052 |
9,408 | linux | 7c80f9e4a588f1925b07134bb2e3689335f6c6d8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7c80f9e4a588f1925b07134bb2e3689335f6c6d8 | usb: usbtest: fix NULL pointer dereference
If the usbtest driver encounters a device with an IN bulk endpoint but
no OUT bulk endpoint, it will try to dereference a NULL pointer
(out->desc.bEndpointAddress). The problem can be solved by adding a
missing test.
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Rep... | 1 | get_endpoints(struct usbtest_dev *dev, struct usb_interface *intf)
{
int tmp;
struct usb_host_interface *alt;
struct usb_host_endpoint *in, *out;
struct usb_host_endpoint *iso_in, *iso_out;
struct usb_host_endpoint *int_in, *int_out;
struct usb_device *udev;
for (tmp = 0; tmp < intf->num_altsetting; tmp++) ... | 283,507,030,675,456,930,000,000,000,000,000,000,000 | usbtest.c | 52,688,706,411,922,670,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-16532 | The get_endpoints function in drivers/usb/misc/usbtest.c in the Linux kernel through 4.13.11 allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via a crafted USB device. | https://nvd.nist.gov/vuln/detail/CVE-2017-16532 |
184,510 | linux | 7c80f9e4a588f1925b07134bb2e3689335f6c6d8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7c80f9e4a588f1925b07134bb2e3689335f6c6d8 | usb: usbtest: fix NULL pointer dereference
If the usbtest driver encounters a device with an IN bulk endpoint but
no OUT bulk endpoint, it will try to dereference a NULL pointer
(out->desc.bEndpointAddress). The problem can be solved by adding a
missing test.
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Rep... | 0 | get_endpoints(struct usbtest_dev *dev, struct usb_interface *intf)
{
int tmp;
struct usb_host_interface *alt;
struct usb_host_endpoint *in, *out;
struct usb_host_endpoint *iso_in, *iso_out;
struct usb_host_endpoint *int_in, *int_out;
struct usb_device *udev;
for (tmp = 0; tmp < intf->num_altsetting; tmp++) ... | 293,833,094,194,471,500,000,000,000,000,000,000,000 | usbtest.c | 141,427,487,637,288,040,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-16532 | The get_endpoints function in drivers/usb/misc/usbtest.c in the Linux kernel through 4.13.11 allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via a crafted USB device. | https://nvd.nist.gov/vuln/detail/CVE-2017-16532 |
9,409 | linux | 786de92b3cb26012d3d0f00ee37adf14527f35c4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/786de92b3cb26012d3d0f00ee37adf14527f35c4 | USB: uas: fix bug in handling of alternate settings
The uas driver has a subtle bug in the way it handles alternate
settings. The uas_find_uas_alt_setting() routine returns an
altsetting value (the bAlternateSetting number in the descriptor), but
uas_use_uas_driver() then treats that value as an index to the
intf->al... | 1 | static int uas_switch_interface(struct usb_device *udev,
struct usb_interface *intf)
{
int alt;
alt = uas_find_uas_alt_setting(intf);
if (alt < 0)
return alt;
return usb_set_interface(udev,
intf->altsetting[0].desc.bInterfaceNumber, alt);
}
| 140,637,843,410,934,800,000,000,000,000,000,000,000 | uas.c | 20,737,748,293,101,703,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-16530 | The uas driver in the Linux kernel before 4.13.6 allows local users to cause a denial of service (out-of-bounds read and system crash) or possibly have unspecified other impact via a crafted USB device, related to drivers/usb/storage/uas-detect.h and drivers/usb/storage/uas.c. | https://nvd.nist.gov/vuln/detail/CVE-2017-16530 |
184,511 | linux | 786de92b3cb26012d3d0f00ee37adf14527f35c4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/786de92b3cb26012d3d0f00ee37adf14527f35c4 | USB: uas: fix bug in handling of alternate settings
The uas driver has a subtle bug in the way it handles alternate
settings. The uas_find_uas_alt_setting() routine returns an
altsetting value (the bAlternateSetting number in the descriptor), but
uas_use_uas_driver() then treats that value as an index to the
intf->al... | 0 | static int uas_switch_interface(struct usb_device *udev,
struct usb_interface *intf)
{
struct usb_host_interface *alt;
alt = uas_find_uas_alt_setting(intf);
if (!alt)
return -ENODEV;
return usb_set_interface(udev, alt->desc.bInterfaceNumber,
alt->desc.bAlternateSetting);
}
| 256,589,686,740,686,640,000,000,000,000,000,000,000 | uas.c | 242,708,712,057,179,100,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-16530 | The uas driver in the Linux kernel before 4.13.6 allows local users to cause a denial of service (out-of-bounds read and system crash) or possibly have unspecified other impact via a crafted USB device, related to drivers/usb/storage/uas-detect.h and drivers/usb/storage/uas.c. | https://nvd.nist.gov/vuln/detail/CVE-2017-16530 |
9,415 | FFmpeg | c42a1388a6d1bfd8001bf6a4241d8ca27e49326d | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/c42a1388a6d1bfd8001bf6a4241d8ca27e49326d | avformat/rtpdec_h264: Fix heap-buffer-overflow
Fixes: rtp_sdp/poc.sdp
Found-by: Bingchang <l.bing.chang.bc@gmail.com>
Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> | 1 | static int sdp_parse_fmtp_config_h264(AVFormatContext *s,
AVStream *stream,
PayloadContext *h264_data,
const char *attr, const char *value)
{
AVCodecParameters *par = stream->codecpar;
if (!strcmp(... | 3,803,066,890,696,449,000,000,000,000,000,000,000 | rtpdec_h264.c | 222,521,992,068,081,200,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-14767 | The sdp_parse_fmtp_config_h264 function in libavformat/rtpdec_h264.c in FFmpeg before 3.3.4 mishandles empty sprop-parameter-sets values, which allows remote attackers to cause a denial of service (heap buffer overflow) or possibly have unspecified other impact via a crafted sdp file. | https://nvd.nist.gov/vuln/detail/CVE-2017-14767 |
184,516 | FFmpeg | c42a1388a6d1bfd8001bf6a4241d8ca27e49326d | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/c42a1388a6d1bfd8001bf6a4241d8ca27e49326d | avformat/rtpdec_h264: Fix heap-buffer-overflow
Fixes: rtp_sdp/poc.sdp
Found-by: Bingchang <l.bing.chang.bc@gmail.com>
Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> | 0 | static int sdp_parse_fmtp_config_h264(AVFormatContext *s,
AVStream *stream,
PayloadContext *h264_data,
const char *attr, const char *value)
{
AVCodecParameters *par = stream->codecpar;
if (!strcmp(... | 81,620,069,591,139,470,000,000,000,000,000,000,000 | rtpdec_h264.c | 317,657,616,697,484,230,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-14767 | The sdp_parse_fmtp_config_h264 function in libavformat/rtpdec_h264.c in FFmpeg before 3.3.4 mishandles empty sprop-parameter-sets values, which allows remote attackers to cause a denial of service (heap buffer overflow) or possibly have unspecified other impact via a crafted sdp file. | https://nvd.nist.gov/vuln/detail/CVE-2017-14767 |
9,417 | ImageMagick | 4eae304e773bad8a876c3c26fdffac24d4253ae4 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/4eae304e773bad8a876c3c26fdffac24d4253ae4 | None | 1 | static Image *ReadWPGImage(const ImageInfo *image_info,
ExceptionInfo *exception)
{
typedef struct
{
size_t FileId;
MagickOffsetType DataOffset;
unsigned int ProductType;
unsigned int FileType;
unsigned char MajorVersion;
unsigned char MinorVersion;
unsigned int EncryptKey;
unsigne... | 148,171,285,010,940,660,000,000,000,000,000,000,000 | None | null | [
"CWE-400"
] | CVE-2017-14341 | ImageMagick 7.0.6-6 has a large loop vulnerability in ReadWPGImage in coders/wpg.c, causing CPU exhaustion via a crafted wpg image file. | https://nvd.nist.gov/vuln/detail/CVE-2017-14341 |
184,518 | ImageMagick | 4eae304e773bad8a876c3c26fdffac24d4253ae4 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/4eae304e773bad8a876c3c26fdffac24d4253ae4 | None | 0 | static Image *ReadWPGImage(const ImageInfo *image_info,
ExceptionInfo *exception)
{
typedef struct
{
size_t FileId;
MagickOffsetType DataOffset;
unsigned int ProductType;
unsigned int FileType;
unsigned char MajorVersion;
unsigned char MinorVersion;
unsigned int EncryptKey;
unsigne... | 90,789,861,759,395,120,000,000,000,000,000,000,000 | None | null | [
"CWE-400"
] | CVE-2017-14341 | ImageMagick 7.0.6-6 has a large loop vulnerability in ReadWPGImage in coders/wpg.c, causing CPU exhaustion via a crafted wpg image file. | https://nvd.nist.gov/vuln/detail/CVE-2017-14341 |
9,418 | ImageMagick | 8598a497e2d1f556a34458cf54b40ba40674734c | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/8598a497e2d1f556a34458cf54b40ba40674734c | None | 1 | static Image *ReadPSImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
#define BoundingBox "BoundingBox:"
#define BeginDocument "BeginDocument:"
#define BeginXMPPacket "<?xpacket begin="
#define EndXMPPacket "<?xpacket end="
#define ICCProfile "BeginICCProfile:"
#define CMYKCustomColor "CMYKCustomColor:... | 136,311,021,343,540,440,000,000,000,000,000,000,000 | None | null | [
"CWE-834"
] | CVE-2017-14172 | In coders/ps.c in ImageMagick 7.0.7-0 Q16, a DoS in ReadPSImage() due to lack of an EOF (End of File) check might cause huge CPU consumption. When a crafted PSD file, which claims a large "extent" field in the header but does not contain sufficient backing data, is provided, the loop over "length" would consume huge CP... | https://nvd.nist.gov/vuln/detail/CVE-2017-14172 |
184,519 | ImageMagick | 8598a497e2d1f556a34458cf54b40ba40674734c | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/8598a497e2d1f556a34458cf54b40ba40674734c | None | 0 | static Image *ReadPSImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
#define BoundingBox "BoundingBox:"
#define BeginDocument "BeginDocument:"
#define BeginXMPPacket "<?xpacket begin="
#define EndXMPPacket "<?xpacket end="
#define ICCProfile "BeginICCProfile:"
#define CMYKCustomColor "CMYKCustomColor:... | 30,474,061,084,174,295,000,000,000,000,000,000,000 | None | null | [
"CWE-834"
] | CVE-2017-14172 | In coders/ps.c in ImageMagick 7.0.7-0 Q16, a DoS in ReadPSImage() due to lack of an EOF (End of File) check might cause huge CPU consumption. When a crafted PSD file, which claims a large "extent" field in the header but does not contain sufficient backing data, is provided, the loop over "length" would consume huge CP... | https://nvd.nist.gov/vuln/detail/CVE-2017-14172 |
9,422 | ImageMagick | 22e0310345499ffe906c604428f2a3a668942b05 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/22e0310345499ffe906c604428f2a3a668942b05 | None | 1 | static Image *ReadOneMNGImage(MngInfo* mng_info, const ImageInfo *image_info,
ExceptionInfo *exception)
{
char
page_geometry[MaxTextExtent];
Image
*image;
MagickBooleanType
logging;
volatile int
first_mng_object,
object_id,
term_chunk_found,
skip_to_iend;
volatile ssize_t
... | 81,322,809,210,957,050,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2017-13139 | In ImageMagick before 6.9.9-0 and 7.x before 7.0.6-1, the ReadOneMNGImage function in coders/png.c has an out-of-bounds read with the MNG CLIP chunk. | https://nvd.nist.gov/vuln/detail/CVE-2017-13139 |
184,520 | ImageMagick | 22e0310345499ffe906c604428f2a3a668942b05 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/22e0310345499ffe906c604428f2a3a668942b05 | None | 0 | static Image *ReadOneMNGImage(MngInfo* mng_info, const ImageInfo *image_info,
ExceptionInfo *exception)
{
char
page_geometry[MaxTextExtent];
Image
*image;
MagickBooleanType
logging;
volatile int
first_mng_object,
object_id,
term_chunk_found,
skip_to_iend;
volatile ssize_t
... | 307,114,930,302,049,200,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2017-13139 | In ImageMagick before 6.9.9-0 and 7.x before 7.0.6-1, the ReadOneMNGImage function in coders/png.c has an out-of-bounds read with the MNG CLIP chunk. | https://nvd.nist.gov/vuln/detail/CVE-2017-13139 |
9,425 | tcpdump | da6f1a677bfa4476abaeaf9b1afe1c4390f51b41 | https://github.com/the-tcpdump-group/tcpdump | https://github.com/the-tcpdump-group/tcpdump/commit/da6f1a677bfa4476abaeaf9b1afe1c4390f51b41 | CVE-2017-13034/PGM: Add a bounds check.
This fixes a buffer over-read discovered by Bhargava Shastry,
SecT/TU Berlin.
Add a test using the capture file supplied by the reporter(s), modified
so the capture file won't be rejected as an invalid capture.
Move a return to make the code a bit cleaner (i.e., make it more o... | 1 | pgm_print(netdissect_options *ndo,
register const u_char *bp, register u_int length,
register const u_char *bp2)
{
register const struct pgm_header *pgm;
register const struct ip *ip;
register char ch;
uint16_t sport, dport;
u_int nla_afnum;
char nla_buf[INET6_ADDRSTRLEN];
register const stru... | 149,333,147,897,387,360,000,000,000,000,000,000,000 | print-pgm.c | 340,037,039,173,930,900,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-13034 | The PGM parser in tcpdump before 4.9.2 has a buffer over-read in print-pgm.c:pgm_print(). | https://nvd.nist.gov/vuln/detail/CVE-2017-13034 |
184,521 | tcpdump | da6f1a677bfa4476abaeaf9b1afe1c4390f51b41 | https://github.com/the-tcpdump-group/tcpdump | https://github.com/the-tcpdump-group/tcpdump/commit/da6f1a677bfa4476abaeaf9b1afe1c4390f51b41 | CVE-2017-13034/PGM: Add a bounds check.
This fixes a buffer over-read discovered by Bhargava Shastry,
SecT/TU Berlin.
Add a test using the capture file supplied by the reporter(s), modified
so the capture file won't be rejected as an invalid capture.
Move a return to make the code a bit cleaner (i.e., make it more o... | 0 | pgm_print(netdissect_options *ndo,
register const u_char *bp, register u_int length,
register const u_char *bp2)
{
register const struct pgm_header *pgm;
register const struct ip *ip;
register char ch;
uint16_t sport, dport;
u_int nla_afnum;
char nla_buf[INET6_ADDRSTRLEN];
register const stru... | 132,157,298,085,094,960,000,000,000,000,000,000,000 | print-pgm.c | 156,722,559,691,661,720,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-13034 | The PGM parser in tcpdump before 4.9.2 has a buffer over-read in print-pgm.c:pgm_print(). | https://nvd.nist.gov/vuln/detail/CVE-2017-13034 |
9,426 | tcpdump | 1bc78d795cd5cad5525498658f414a11ea0a7e9c | https://github.com/the-tcpdump-group/tcpdump | https://github.com/the-tcpdump-group/tcpdump/commit/1bc78d795cd5cad5525498658f414a11ea0a7e9c | CVE-2017-13032/RADIUS: Check whether a byte exists before testing its value.
Reverse the test in a for loop to test the length before testing whether
we have a null byte.
This fixes a buffer over-read discovered by Bhargava Shastry.
Add a test using the capture file supplied by the reporter(s), modified
so the captu... | 1 | print_attr_string(netdissect_options *ndo,
register const u_char *data, u_int length, u_short attr_code)
{
register u_int i;
ND_TCHECK2(data[0],length);
switch(attr_code)
{
case TUNNEL_PASS:
if (length < 3)
{
ND_PRINT((ndo, "%s", tstr));
... | 248,093,794,910,011,600,000,000,000,000,000,000,000 | print-radius.c | 205,335,897,441,003,700,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-13032 | The RADIUS parser in tcpdump before 4.9.2 has a buffer over-read in print-radius.c:print_attr_string(). | https://nvd.nist.gov/vuln/detail/CVE-2017-13032 |
184,522 | tcpdump | 1bc78d795cd5cad5525498658f414a11ea0a7e9c | https://github.com/the-tcpdump-group/tcpdump | https://github.com/the-tcpdump-group/tcpdump/commit/1bc78d795cd5cad5525498658f414a11ea0a7e9c | CVE-2017-13032/RADIUS: Check whether a byte exists before testing its value.
Reverse the test in a for loop to test the length before testing whether
we have a null byte.
This fixes a buffer over-read discovered by Bhargava Shastry.
Add a test using the capture file supplied by the reporter(s), modified
so the captu... | 0 | print_attr_string(netdissect_options *ndo,
register const u_char *data, u_int length, u_short attr_code)
{
register u_int i;
ND_TCHECK2(data[0],length);
switch(attr_code)
{
case TUNNEL_PASS:
if (length < 3)
goto trunc;
if (*data && (*data <=0... | 279,841,386,576,325,370,000,000,000,000,000,000,000 | print-radius.c | 61,264,973,441,731,000,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-13032 | The RADIUS parser in tcpdump before 4.9.2 has a buffer over-read in print-radius.c:print_attr_string(). | https://nvd.nist.gov/vuln/detail/CVE-2017-13032 |
9,434 | tcpdump | 66df248b49095c261138b5a5e34d341a6bf9ac7f | https://github.com/the-tcpdump-group/tcpdump | https://github.com/the-tcpdump-group/tcpdump/commit/66df248b49095c261138b5a5e34d341a6bf9ac7f | CVE-2017-12985/IPv6: Check for print routines returning -1 when running past the end.
rt6_print(), ah_print(), and esp_print() return -1 if they run up
against the end of the packet while dissecting; if that happens, stop
dissecting, don't try to fetch the next header value, because 1) *it*
might be past the end of th... | 1 | ip6_print(netdissect_options *ndo, const u_char *bp, u_int length)
{
register const struct ip6_hdr *ip6;
register int advance;
u_int len;
const u_char *ipend;
register const u_char *cp;
register u_int payload_len;
int nh;
int fragmented = 0;
u_int flow;
ip6 = (const struct ip6_hdr *)bp;
ND_TCHECK(*ip6);
i... | 263,310,729,271,621,080,000,000,000,000,000,000 | print-ip6.c | 214,404,332,817,975,570,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-12985 | The IPv6 parser in tcpdump before 4.9.2 has a buffer over-read in print-ip6.c:ip6_print(). | https://nvd.nist.gov/vuln/detail/CVE-2017-12985 |
184,525 | tcpdump | 66df248b49095c261138b5a5e34d341a6bf9ac7f | https://github.com/the-tcpdump-group/tcpdump | https://github.com/the-tcpdump-group/tcpdump/commit/66df248b49095c261138b5a5e34d341a6bf9ac7f | CVE-2017-12985/IPv6: Check for print routines returning -1 when running past the end.
rt6_print(), ah_print(), and esp_print() return -1 if they run up
against the end of the packet while dissecting; if that happens, stop
dissecting, don't try to fetch the next header value, because 1) *it*
might be past the end of th... | 0 | ip6_print(netdissect_options *ndo, const u_char *bp, u_int length)
{
register const struct ip6_hdr *ip6;
register int advance;
u_int len;
const u_char *ipend;
register const u_char *cp;
register u_int payload_len;
int nh;
int fragmented = 0;
u_int flow;
ip6 = (const struct ip6_hdr *)bp;
ND_TCHECK(*ip6);
i... | 33,352,515,045,565,447,000,000,000,000,000,000,000 | print-ip6.c | 153,144,531,199,554,750,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-12985 | The IPv6 parser in tcpdump before 4.9.2 has a buffer over-read in print-ip6.c:ip6_print(). | https://nvd.nist.gov/vuln/detail/CVE-2017-12985 |
9,438 | ImageMagick | 45aeda5da9eb328689afc221fa3b7dfa5cdea54d | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/45aeda5da9eb328689afc221fa3b7dfa5cdea54d | None | 1 | static MagickBooleanType WriteINLINEImage(const ImageInfo *image_info,
Image *image)
{
char
*base64,
message[MaxTextExtent];
const MagickInfo
*magick_info;
ExceptionInfo
*exception;
Image
*write_image;
ImageInfo
*write_info;
MagickBooleanType
status;
size_t
blob_len... | 91,114,626,347,775,820,000,000,000,000,000,000,000 | None | null | [
"CWE-772"
] | CVE-2017-12666 | ImageMagick 7.0.6-2 has a memory leak vulnerability in WriteINLINEImage in coders/inline.c. | https://nvd.nist.gov/vuln/detail/CVE-2017-12666 |
184,528 | ImageMagick | 45aeda5da9eb328689afc221fa3b7dfa5cdea54d | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/45aeda5da9eb328689afc221fa3b7dfa5cdea54d | None | 0 | static MagickBooleanType WriteINLINEImage(const ImageInfo *image_info,
Image *image)
{
char
*base64,
message[MaxTextExtent];
const MagickInfo
*magick_info;
ExceptionInfo
*exception;
Image
*write_image;
ImageInfo
*write_info;
MagickBooleanType
status;
size_t
blob_len... | 95,327,956,304,312,400,000,000,000,000,000,000,000 | None | null | [
"CWE-772"
] | CVE-2017-12666 | ImageMagick 7.0.6-2 has a memory leak vulnerability in WriteINLINEImage in coders/inline.c. | https://nvd.nist.gov/vuln/detail/CVE-2017-12666 |
9,439 | ImageMagick | 9f375e7080a2c1044cd546854d0548b4bfb429d0 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/9f375e7080a2c1044cd546854d0548b4bfb429d0 | None | 1 | static Image *ReadDCMImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
#define ThrowDCMException(exception,message) \
{ \
if (data != (unsigned char *) NULL) \
data=(unsigned char *) RelinquishMagickMemory(data); \
if (stream_info != (DCMStreamInfo *) NULL) \
stream_info=(DCMStreamInfo *) Relinq... | 250,223,957,382,125,260,000,000,000,000,000,000,000 | None | null | [
"CWE-772"
] | CVE-2017-12644 | ImageMagick 7.0.6-1 has a memory leak vulnerability in ReadDCMImage in coders\dcm.c. | https://nvd.nist.gov/vuln/detail/CVE-2017-12644 |
184,529 | ImageMagick | 9f375e7080a2c1044cd546854d0548b4bfb429d0 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/9f375e7080a2c1044cd546854d0548b4bfb429d0 | None | 0 | static Image *ReadDCMImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
#define ThrowDCMException(exception,message) \
{ \
if (data != (unsigned char *) NULL) \
data=(unsigned char *) RelinquishMagickMemory(data); \
if (stream_info != (DCMStreamInfo *) NULL) \
stream_info=(DCMStreamInfo *) Relinq... | 85,795,089,399,248,150,000,000,000,000,000,000,000 | None | null | [
"CWE-772"
] | CVE-2017-12644 | ImageMagick 7.0.6-1 has a memory leak vulnerability in ReadDCMImage in coders\dcm.c. | https://nvd.nist.gov/vuln/detail/CVE-2017-12644 |
9,440 | linux | 9e3f7a29694049edd728e2400ab57ad7553e5aa9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9e3f7a29694049edd728e2400ab57ad7553e5aa9 | arm64: KVM: pmu: Fix AArch32 cycle counter access
We're missing the handling code for the cycle counter accessed
from a 32bit guest, leading to unexpected results.
Cc: stable@vger.kernel.org # 4.6+
Signed-off-by: Wei Huang <wei@redhat.com>
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com> | 1 | static bool access_pmu_evcntr(struct kvm_vcpu *vcpu,
struct sys_reg_params *p,
const struct sys_reg_desc *r)
{
u64 idx;
if (!kvm_arm_pmu_v3_ready(vcpu))
return trap_raz_wi(vcpu, p, r);
if (r->CRn == 9 && r->CRm == 13) {
if (r->Op2 == 2) {
/* PMXEVCNTR_EL0 */
if (pmu_access_event_counter... | 109,885,700,626,088,160,000,000,000,000,000,000,000 | sys_regs.c | 47,091,922,259,694,350,000,000,000,000,000,000,000 | [
"CWE-617"
] | CVE-2017-12168 | The access_pmu_evcntr function in arch/arm64/kvm/sys_regs.c in the Linux kernel before 4.8.11 allows privileged KVM guest OS users to cause a denial of service (assertion failure and host OS crash) by accessing the Performance Monitors Cycle Count Register (PMCCNTR). | https://nvd.nist.gov/vuln/detail/CVE-2017-12168 |
184,530 | linux | 9e3f7a29694049edd728e2400ab57ad7553e5aa9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9e3f7a29694049edd728e2400ab57ad7553e5aa9 | arm64: KVM: pmu: Fix AArch32 cycle counter access
We're missing the handling code for the cycle counter accessed
from a 32bit guest, leading to unexpected results.
Cc: stable@vger.kernel.org # 4.6+
Signed-off-by: Wei Huang <wei@redhat.com>
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com> | 0 | static bool access_pmu_evcntr(struct kvm_vcpu *vcpu,
struct sys_reg_params *p,
const struct sys_reg_desc *r)
{
u64 idx;
if (!kvm_arm_pmu_v3_ready(vcpu))
return trap_raz_wi(vcpu, p, r);
if (r->CRn == 9 && r->CRm == 13) {
if (r->Op2 == 2) {
/* PMXEVCNTR_EL0 */
if (pmu_access_event_counter... | 93,704,480,489,885,370,000,000,000,000,000,000,000 | sys_regs.c | 209,078,167,393,227,300,000,000,000,000,000,000,000 | [
"CWE-617"
] | CVE-2017-12168 | The access_pmu_evcntr function in arch/arm64/kvm/sys_regs.c in the Linux kernel before 4.8.11 allows privileged KVM guest OS users to cause a denial of service (assertion failure and host OS crash) by accessing the Performance Monitors Cycle Count Register (PMCCNTR). | https://nvd.nist.gov/vuln/detail/CVE-2017-12168 |
9,443 | FFmpeg | ba4beaf6149f7241c8bd85fe853318c2f6837ad0 | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/ba4beaf6149f7241c8bd85fe853318c2f6837ad0 | avcodec/apedec: Fix integer overflow
Fixes: out of array access
Fixes: PoC.ape and others
Found-by: Bingchang, Liu@VARAS of IIE
Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> | 1 | static int ape_decode_frame(AVCodecContext *avctx, void *data,
int *got_frame_ptr, AVPacket *avpkt)
{
AVFrame *frame = data;
const uint8_t *buf = avpkt->data;
APEContext *s = avctx->priv_data;
uint8_t *sample8;
int16_t *sample16;
int32_t *sample24;
int i, ch... | 225,537,218,437,466,820,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2017-11399 | Integer overflow in the ape_decode_frame function in libavcodec/apedec.c in FFmpeg 2.4 through 3.3.2 allows remote attackers to cause a denial of service (out-of-array access and application crash) or possibly have unspecified other impact via a crafted APE file. | https://nvd.nist.gov/vuln/detail/CVE-2017-11399 |
184,533 | FFmpeg | ba4beaf6149f7241c8bd85fe853318c2f6837ad0 | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/ba4beaf6149f7241c8bd85fe853318c2f6837ad0 | avcodec/apedec: Fix integer overflow
Fixes: out of array access
Fixes: PoC.ape and others
Found-by: Bingchang, Liu@VARAS of IIE
Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> | 0 | static int ape_decode_frame(AVCodecContext *avctx, void *data,
int *got_frame_ptr, AVPacket *avpkt)
{
AVFrame *frame = data;
const uint8_t *buf = avpkt->data;
APEContext *s = avctx->priv_data;
uint8_t *sample8;
int16_t *sample16;
int32_t *sample24;
int i, ch... | 270,911,209,672,469,800,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2017-11399 | Integer overflow in the ape_decode_frame function in libavcodec/apedec.c in FFmpeg 2.4 through 3.3.2 allows remote attackers to cause a denial of service (out-of-array access and application crash) or possibly have unspecified other impact via a crafted APE file. | https://nvd.nist.gov/vuln/detail/CVE-2017-11399 |
9,448 | FFmpeg | 31c1c0b46a7021802c3d1d18039fca30dba5a14e | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/31c1c0b46a7021802c3d1d18039fca30dba5a14e | avcodec/dnxhd_parser: Do not return invalid value from dnxhd_find_frame_end() on error
Fixes: Null pointer dereference
Fixes: CVE-2017-9608
Found-by: Yihan Lian
Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
(cherry picked from commit 611b35627488a8d0763e75c25ee0875c5b7987dd)
Signed-off-by: Michael Niede... | 1 | static int dnxhd_find_frame_end(DNXHDParserContext *dctx,
const uint8_t *buf, int buf_size)
{
ParseContext *pc = &dctx->pc;
uint64_t state = pc->state64;
int pic_found = pc->frame_start_found;
int i = 0;
int interlaced = dctx->interlaced;
int cur_field = dctx->cur... | 28,683,453,471,711,494,000,000,000,000,000,000,000 | dnxhd_parser.c | 78,021,258,009,879,840,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-9608 | The dnxhd decoder in FFmpeg before 3.2.6, and 3.3.x before 3.3.3 allows remote attackers to cause a denial of service (NULL pointer dereference) via a crafted mov file. | https://nvd.nist.gov/vuln/detail/CVE-2017-9608 |
184,538 | FFmpeg | 31c1c0b46a7021802c3d1d18039fca30dba5a14e | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/31c1c0b46a7021802c3d1d18039fca30dba5a14e | avcodec/dnxhd_parser: Do not return invalid value from dnxhd_find_frame_end() on error
Fixes: Null pointer dereference
Fixes: CVE-2017-9608
Found-by: Yihan Lian
Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
(cherry picked from commit 611b35627488a8d0763e75c25ee0875c5b7987dd)
Signed-off-by: Michael Niede... | 0 | static int dnxhd_find_frame_end(DNXHDParserContext *dctx,
const uint8_t *buf, int buf_size)
{
ParseContext *pc = &dctx->pc;
uint64_t state = pc->state64;
int pic_found = pc->frame_start_found;
int i = 0;
int interlaced = dctx->interlaced;
int cur_field = dctx->cur... | 4,205,551,996,619,674,000,000,000,000,000,000,000 | dnxhd_parser.c | 146,591,610,316,261,090,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-9608 | The dnxhd decoder in FFmpeg before 3.2.6, and 3.3.x before 3.3.3 allows remote attackers to cause a denial of service (NULL pointer dereference) via a crafted mov file. | https://nvd.nist.gov/vuln/detail/CVE-2017-9608 |
9,459 | linux | c4baad50297d84bde1a7ad45e50c73adae4a2192 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c4baad50297d84bde1a7ad45e50c73adae4a2192 | virtio-console: avoid DMA from stack
put_chars() stuffs the buffer it gets into an sg, but that buffer may be
on the stack. This breaks with CONFIG_VMAP_STACK=y (for me, it
manifested as printks getting turned into NUL bytes).
Signed-off-by: Omar Sandoval <osandov@fb.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat... | 1 | static int put_chars(u32 vtermno, const char *buf, int count)
{
struct port *port;
struct scatterlist sg[1];
if (unlikely(early_put_chars))
return early_put_chars(vtermno, buf, count);
port = find_port_by_vtermno(vtermno);
if (!port)
return -EPIPE;
sg_init_one(sg, buf, count);
return __send_to_po... | 208,943,279,536,157,350,000,000,000,000,000,000,000 | virtio_console.c | 9,053,507,988,298,926,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-8067 | drivers/char/virtio_console.c in the Linux kernel 4.9.x and 4.10.x before 4.10.12 interacts incorrectly with the CONFIG_VMAP_STACK option, which allows local users to cause a denial of service (system crash or memory corruption) or possibly have unspecified other impact by leveraging use of more than one virtual page f... | https://nvd.nist.gov/vuln/detail/CVE-2017-8067 |
184,547 | linux | c4baad50297d84bde1a7ad45e50c73adae4a2192 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c4baad50297d84bde1a7ad45e50c73adae4a2192 | virtio-console: avoid DMA from stack
put_chars() stuffs the buffer it gets into an sg, but that buffer may be
on the stack. This breaks with CONFIG_VMAP_STACK=y (for me, it
manifested as printks getting turned into NUL bytes).
Signed-off-by: Omar Sandoval <osandov@fb.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat... | 0 | static int put_chars(u32 vtermno, const char *buf, int count)
{
struct port *port;
struct scatterlist sg[1];
void *data;
int ret;
if (unlikely(early_put_chars))
return early_put_chars(vtermno, buf, count);
port = find_port_by_vtermno(vtermno);
if (!port)
return -EPIPE;
data = kmemdup(buf, count,... | 326,461,035,208,927,300,000,000,000,000,000,000,000 | virtio_console.c | 188,802,960,319,308,300,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-8067 | drivers/char/virtio_console.c in the Linux kernel 4.9.x and 4.10.x before 4.10.12 interacts incorrectly with the CONFIG_VMAP_STACK option, which allows local users to cause a denial of service (system crash or memory corruption) or possibly have unspecified other impact by leveraging use of more than one virtual page f... | https://nvd.nist.gov/vuln/detail/CVE-2017-8067 |
9,465 | php-src | bab0b99f376dac9170ac81382a5ed526938d595a | https://github.com/php/php-src | https://github.com/php/php-src/commit/bab0b99f376dac9170ac81382a5ed526938d595a | Detect invalid port in xp_socket parse ip address
For historical reasons, fsockopen() accepts the port and hostname
separately: fsockopen('127.0.0.1', 80)
However, with the introdcution of stream transports in PHP 4.3,
it became possible to include the port in the hostname specifier:
fsockopen('127.0.0.1:80')
Or mor... | 1 | static inline char *parse_ip_address_ex(const char *str, size_t str_len, int *portno, int get_err, zend_string **err)
{
char *colon;
char *host = NULL;
#ifdef HAVE_IPV6
char *p;
if (*(str) == '[' && str_len > 1) {
/* IPV6 notation to specify raw address with port (i.e. [fe80::1]:80) */
p = memchr(str + 1,... | 168,256,484,098,446,520,000,000,000,000,000,000,000 | xp_socket.c | 256,034,985,988,711,000,000,000,000,000,000,000,000 | [
"CWE-918"
] | CVE-2017-7189 | main/streams/xp_socket.c in PHP 7.x before 2017-03-07 misparses fsockopen calls, such as by interpreting fsockopen('127.0.0.1:80', 443) as if the address/port were 127.0.0.1:80:443, which is later truncated to 127.0.0.1:80. This behavior has a security risk if the explicitly provided port number (i.e., 443 in this exam... | https://nvd.nist.gov/vuln/detail/CVE-2017-7189 |
184,553 | php-src | bab0b99f376dac9170ac81382a5ed526938d595a | https://github.com/php/php-src | https://github.com/php/php-src/commit/bab0b99f376dac9170ac81382a5ed526938d595a | Detect invalid port in xp_socket parse ip address
For historical reasons, fsockopen() accepts the port and hostname
separately: fsockopen('127.0.0.1', 80)
However, with the introdcution of stream transports in PHP 4.3,
it became possible to include the port in the hostname specifier:
fsockopen('127.0.0.1:80')
Or mor... | 0 | static inline char *parse_ip_address_ex(const char *str, size_t str_len, int *portno, int get_err, zend_string **err)
{
char *colon;
char *host = NULL;
#ifdef HAVE_IPV6
if (*(str) == '[' && str_len > 1) {
/* IPV6 notation to specify raw address with port (i.e. [fe80::1]:80) */
char *p = memchr(str + 1, ']'... | 103,702,572,413,630,890,000,000,000,000,000,000,000 | xp_socket.c | 31,307,525,326,172,657,000,000,000,000,000,000,000 | [
"CWE-918"
] | CVE-2017-7189 | main/streams/xp_socket.c in PHP 7.x before 2017-03-07 misparses fsockopen calls, such as by interpreting fsockopen('127.0.0.1:80', 443) as if the address/port were 127.0.0.1:80:443, which is later truncated to 127.0.0.1:80. This behavior has a security risk if the explicitly provided port number (i.e., 443 in this exam... | https://nvd.nist.gov/vuln/detail/CVE-2017-7189 |
9,470 | libsndfile | f833c53cb596e9e1792949f762e0b33661822748 | https://github.com/erikd/libsndfile | https://github.com/erikd/libsndfile/commit/f833c53cb596e9e1792949f762e0b33661822748 | src/aiff.c: Fix a buffer read overflow
Secunia Advisory SA76717.
Found by: Laurent Delosieres, Secunia Research at Flexera Software | 1 | aiff_read_chanmap (SF_PRIVATE * psf, unsigned dword)
{ const AIFF_CAF_CHANNEL_MAP * map_info ;
unsigned channel_bitmap, channel_decriptions, bytesread ;
int layout_tag ;
bytesread = psf_binheader_readf (psf, "444", &layout_tag, &channel_bitmap, &channel_decriptions) ;
if ((map_info = aiff_caf_of_channel_layout_ta... | 229,784,367,109,779,380,000,000,000,000,000,000,000 | aiff.c | 100,715,852,571,463,750,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-6892 | In libsndfile version 1.0.28, an error in the "aiff_read_chanmap()" function (aiff.c) can be exploited to cause an out-of-bounds read memory access via a specially crafted AIFF file. | https://nvd.nist.gov/vuln/detail/CVE-2017-6892 |
184,558 | libsndfile | f833c53cb596e9e1792949f762e0b33661822748 | https://github.com/erikd/libsndfile | https://github.com/erikd/libsndfile/commit/f833c53cb596e9e1792949f762e0b33661822748 | src/aiff.c: Fix a buffer read overflow
Secunia Advisory SA76717.
Found by: Laurent Delosieres, Secunia Research at Flexera Software | 0 | aiff_read_chanmap (SF_PRIVATE * psf, unsigned dword)
{ const AIFF_CAF_CHANNEL_MAP * map_info ;
unsigned channel_bitmap, channel_decriptions, bytesread ;
int layout_tag ;
bytesread = psf_binheader_readf (psf, "444", &layout_tag, &channel_bitmap, &channel_decriptions) ;
if ((map_info = aiff_caf_of_channel_layout_ta... | 86,913,205,846,784,100,000,000,000,000,000,000,000 | aiff.c | 159,254,405,386,693,200,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-6892 | In libsndfile version 1.0.28, an error in the "aiff_read_chanmap()" function (aiff.c) can be exploited to cause an out-of-bounds read memory access via a specially crafted AIFF file. | https://nvd.nist.gov/vuln/detail/CVE-2017-6892 |
9,471 | ImageMagick | 65f75a32a93ae4044c528a987a68366ecd4b46b9 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/65f75a32a93ae4044c528a987a68366ecd4b46b9 | None | 1 | static MagickBooleanType WriteTGAImage(const ImageInfo *image_info,Image *image)
{
CompressionType
compression;
const char
*value;
const double
midpoint = QuantumRange/2.0;
MagickBooleanType
status;
QuantumAny
range;
register const IndexPacket
*indexes;
register const P... | 256,636,415,044,259,280,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2017-6498 | An issue was discovered in ImageMagick 6.9.7. Incorrect TGA files could trigger assertion failures, thus leading to DoS. | https://nvd.nist.gov/vuln/detail/CVE-2017-6498 |
184,559 | ImageMagick | 65f75a32a93ae4044c528a987a68366ecd4b46b9 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/65f75a32a93ae4044c528a987a68366ecd4b46b9 | None | 0 | static MagickBooleanType WriteTGAImage(const ImageInfo *image_info,Image *image)
{
CompressionType
compression;
const char
*comment,
*value;
const double
midpoint = QuantumRange/2.0;
MagickBooleanType
status;
QuantumAny
range;
register const IndexPacket
*indexes;
re... | 245,035,315,541,133,450,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2017-6498 | An issue was discovered in ImageMagick 6.9.7. Incorrect TGA files could trigger assertion failures, thus leading to DoS. | https://nvd.nist.gov/vuln/detail/CVE-2017-6498 |
9,473 | radare2 | 252afb1cff9676f3ae1f341a28448bf2c8b6e308 | https://github.com/radare/radare2 | https://github.com/radare/radare2/commit/252afb1cff9676f3ae1f341a28448bf2c8b6e308 | None | 1 | static void dex_parse_debug_item(RBinFile *binfile, RBinDexObj *bin,
RBinDexClass *c, int MI, int MA, int paddr, int ins_size,
int insns_size, char *class_name, int regsz,
int debug_info_off) {
struct r_bin_t *rbin = binfile->rbin;
const ut8 *p4 = r_buf_get_at (binfile->buf, debug_info_off, NULL);
... | 49,497,050,964,486,830,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2017-6415 | The dex_parse_debug_item function in libr/bin/p/bin_dex.c in radare2 1.2.1 allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted DEX file. | https://nvd.nist.gov/vuln/detail/CVE-2017-6415 |
184,561 | radare2 | 252afb1cff9676f3ae1f341a28448bf2c8b6e308 | https://github.com/radare/radare2 | https://github.com/radare/radare2/commit/252afb1cff9676f3ae1f341a28448bf2c8b6e308 | None | 0 | static void dex_parse_debug_item(RBinFile *binfile, RBinDexObj *bin,
RBinDexClass *c, int MI, int MA, int paddr, int ins_size,
int insns_size, char *class_name, int regsz,
int debug_info_off) {
struct r_bin_t *rbin = binfile->rbin;
const ut8 *p4 = r_buf_get_at (binfile->buf, debug_info_off, NULL);
... | 213,958,809,551,227,440,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2017-6415 | The dex_parse_debug_item function in libr/bin/p/bin_dex.c in radare2 1.2.1 allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted DEX file. | https://nvd.nist.gov/vuln/detail/CVE-2017-6415 |
9,475 | tnef | 1a17af1ed0c791aec44dbdc9eab91218cc1e335a | https://github.com/verdammelt/tnef | https://github.com/verdammelt/tnef/commit/1a17af1ed0c791aec44dbdc9eab91218cc1e335a | Use asserts on lengths to prevent invalid reads/writes. | 1 | mapi_attr_read (size_t len, unsigned char *buf)
{
size_t idx = 0;
uint32 i,j;
assert(len > 4);
uint32 num_properties = GETINT32(buf+idx);
MAPI_Attr** attrs = CHECKED_XMALLOC (MAPI_Attr*, (num_properties + 1));
idx += 4;
if (!attrs) return NULL;
for (i = 0; i < num_properties; i++... | 201,006,663,046,884,500,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2017-6307 | An issue was discovered in tnef before 1.4.13. Two OOB Writes have been identified in src/mapi_attr.c:mapi_attr_read(). These might lead to invalid read and write operations, controlled by an attacker. | https://nvd.nist.gov/vuln/detail/CVE-2017-6307 |
184,563 | tnef | 1a17af1ed0c791aec44dbdc9eab91218cc1e335a | https://github.com/verdammelt/tnef | https://github.com/verdammelt/tnef/commit/1a17af1ed0c791aec44dbdc9eab91218cc1e335a | Use asserts on lengths to prevent invalid reads/writes. | 0 | mapi_attr_read (size_t len, unsigned char *buf)
{
size_t idx = 0;
uint32 i,j;
assert(len > 4);
uint32 num_properties = GETINT32(buf+idx);
assert((num_properties+1) != 0);
MAPI_Attr** attrs = CHECKED_XMALLOC (MAPI_Attr*, (num_properties + 1));
idx += 4;
if (!attrs) return NULL;
... | 187,330,868,674,190,620,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2017-6307 | An issue was discovered in tnef before 1.4.13. Two OOB Writes have been identified in src/mapi_attr.c:mapi_attr_read(). These might lead to invalid read and write operations, controlled by an attacker. | https://nvd.nist.gov/vuln/detail/CVE-2017-6307 |
9,479 | yara | ab906da53ff2a68c6fd6d1fa73f2b7c7bf0bc636 | https://github.com/VirusTotal/yara | https://github.com/VirusTotal/yara/commit/ab906da53ff2a68c6fd6d1fa73f2b7c7bf0bc636 | Fix issue #597 | 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... | 120,882,024,126,152,870,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2017-5923 | libyara/grammar.y in YARA 3.5.0 allows remote attackers to cause a denial of service (heap-based out-of-bounds read and application crash) via a crafted rule that is mishandled in the yara_yyparse function. | https://nvd.nist.gov/vuln/detail/CVE-2017-5923 |
184,565 | yara | ab906da53ff2a68c6fd6d1fa73f2b7c7bf0bc636 | https://github.com/VirusTotal/yara | https://github.com/VirusTotal/yara/commit/ab906da53ff2a68c6fd6d1fa73f2b7c7bf0bc636 | Fix issue #597 | 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... | 121,270,495,526,720,510,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2017-5923 | libyara/grammar.y in YARA 3.5.0 allows remote attackers to cause a denial of service (heap-based out-of-bounds read and application crash) via a crafted rule that is mishandled in the yara_yyparse function. | https://nvd.nist.gov/vuln/detail/CVE-2017-5923 |
9,480 | libarchive | 98dcbbf0bf4854bf987557e55e55fff7abbf3ea9 | https://github.com/libarchive/libarchive | https://github.com/libarchive/libarchive/commit/98dcbbf0bf4854bf987557e55e55fff7abbf3ea9 | Fail with negative lha->compsize in lha_read_file_header_1()
Fixes a heap buffer overflow reported in Secunia SA74169 | 1 | lha_read_file_header_1(struct archive_read *a, struct lha *lha)
{
const unsigned char *p;
size_t extdsize;
int i, err, err2;
int namelen, padding;
unsigned char headersum, sum_calculated;
err = ARCHIVE_OK;
if ((p = __archive_read_ahead(a, H1_FIXED_SIZE, NULL)) == NULL)
return (truncated_error(a));
lha->hea... | 48,954,952,310,354,580,000,000,000,000,000,000,000 | archive_read_support_format_lha.c | 200,846,349,839,688,150,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-5601 | An error in the lha_read_file_header_1() function (archive_read_support_format_lha.c) in libarchive 3.2.2 allows remote attackers to trigger an out-of-bounds read memory access and subsequently cause a crash via a specially crafted archive. | https://nvd.nist.gov/vuln/detail/CVE-2017-5601 |
184,566 | libarchive | 98dcbbf0bf4854bf987557e55e55fff7abbf3ea9 | https://github.com/libarchive/libarchive | https://github.com/libarchive/libarchive/commit/98dcbbf0bf4854bf987557e55e55fff7abbf3ea9 | Fail with negative lha->compsize in lha_read_file_header_1()
Fixes a heap buffer overflow reported in Secunia SA74169 | 0 | lha_read_file_header_1(struct archive_read *a, struct lha *lha)
{
const unsigned char *p;
size_t extdsize;
int i, err, err2;
int namelen, padding;
unsigned char headersum, sum_calculated;
err = ARCHIVE_OK;
if ((p = __archive_read_ahead(a, H1_FIXED_SIZE, NULL)) == NULL)
return (truncated_error(a));
lha->hea... | 38,857,243,409,447,520,000,000,000,000,000,000,000 | archive_read_support_format_lha.c | 12,745,854,041,047,408,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-5601 | An error in the lha_read_file_header_1() function (archive_read_support_format_lha.c) in libarchive 3.2.2 allows remote attackers to trigger an out-of-bounds read memory access and subsequently cause a crash via a specially crafted archive. | https://nvd.nist.gov/vuln/detail/CVE-2017-5601 |
9,481 | linux | 6b8ac63847bc2f958dd93c09edc941a0118992d9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6b8ac63847bc2f958dd93c09edc941a0118992d9 | drm/vc4: Return -EINVAL on the overflow checks failing.
By failing to set the errno, we'd continue on to trying to set up the
RCL, and then oops on trying to dereference the tile_bo that binning
validation should have set up.
Reported-by: Ingo Molnar <mingo@kernel.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Fix... | 1 | vc4_get_bcl(struct drm_device *dev, struct vc4_exec_info *exec)
{
struct drm_vc4_submit_cl *args = exec->args;
void *temp = NULL;
void *bin;
int ret = 0;
uint32_t bin_offset = 0;
uint32_t shader_rec_offset = roundup(bin_offset + args->bin_cl_size,
16);
uint32_t uniforms_offset = shader_rec_offset + arg... | 231,214,910,622,587,800,000,000,000,000,000,000,000 | vc4_gem.c | 130,965,582,702,580,360,000,000,000,000,000,000,000 | [
"CWE-388"
] | CVE-2017-5577 | The vc4_get_bcl function in drivers/gpu/drm/vc4/vc4_gem.c in the VideoCore DRM driver in the Linux kernel before 4.9.7 does not set an errno value upon certain overflow detections, which allows local users to cause a denial of service (incorrect pointer dereference and OOPS) via inconsistent size values in a VC4_SUBMIT... | https://nvd.nist.gov/vuln/detail/CVE-2017-5577 |
184,567 | linux | 6b8ac63847bc2f958dd93c09edc941a0118992d9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6b8ac63847bc2f958dd93c09edc941a0118992d9 | drm/vc4: Return -EINVAL on the overflow checks failing.
By failing to set the errno, we'd continue on to trying to set up the
RCL, and then oops on trying to dereference the tile_bo that binning
validation should have set up.
Reported-by: Ingo Molnar <mingo@kernel.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Fix... | 0 | vc4_get_bcl(struct drm_device *dev, struct vc4_exec_info *exec)
{
struct drm_vc4_submit_cl *args = exec->args;
void *temp = NULL;
void *bin;
int ret = 0;
uint32_t bin_offset = 0;
uint32_t shader_rec_offset = roundup(bin_offset + args->bin_cl_size,
16);
uint32_t uniforms_offset = shader_rec_offset + arg... | 220,541,881,910,312,830,000,000,000,000,000,000,000 | vc4_gem.c | 332,138,143,407,800,780,000,000,000,000,000,000,000 | [
"CWE-388"
] | CVE-2017-5577 | The vc4_get_bcl function in drivers/gpu/drm/vc4/vc4_gem.c in the VideoCore DRM driver in the Linux kernel before 4.9.7 does not set an errno value upon certain overflow detections, which allows local users to cause a denial of service (incorrect pointer dereference and OOPS) via inconsistent size values in a VC4_SUBMIT... | https://nvd.nist.gov/vuln/detail/CVE-2017-5577 |
9,496 | libgd | 69d2fd2c597ffc0c217de1238b9bf4d4bceba8e6 | https://github.com/libgd/libgd | https://github.com/libgd/libgd/commit/69d2fd2c597ffc0c217de1238b9bf4d4bceba8e6 | Fix #354: Signed Integer Overflow gd_io.c
GD2 stores the number of horizontal and vertical chunks as words (i.e. 2
byte unsigned). These values are multiplied and assigned to an int when
reading the image, what can cause integer overflows. We have to avoid
that, and also make sure that either chunk count is actually g... | 1 | _gd2GetHeader (gdIOCtxPtr in, int *sx, int *sy,
int *cs, int *vers, int *fmt, int *ncx, int *ncy,
t_chunk_info ** chunkIdx)
{
int i;
int ch;
char id[5];
t_chunk_info *cidx;
int sidx;
int nc;
GD2_DBG (printf ("Reading gd2 header info\n"));
for (i = 0; i < 4; i++) {
ch = gdGetC (... | 204,162,205,224,826,550,000,000,000,000,000,000,000 | None | null | [
"CWE-190"
] | CVE-2016-10168 | Integer overflow in gd_io.c in the GD Graphics Library (aka libgd) before 2.2.4 allows remote attackers to have unspecified impact via vectors involving the number of horizontal and vertical chunks in an image. | https://nvd.nist.gov/vuln/detail/CVE-2016-10168 |
184,581 | libgd | 69d2fd2c597ffc0c217de1238b9bf4d4bceba8e6 | https://github.com/libgd/libgd | https://github.com/libgd/libgd/commit/69d2fd2c597ffc0c217de1238b9bf4d4bceba8e6 | Fix #354: Signed Integer Overflow gd_io.c
GD2 stores the number of horizontal and vertical chunks as words (i.e. 2
byte unsigned). These values are multiplied and assigned to an int when
reading the image, what can cause integer overflows. We have to avoid
that, and also make sure that either chunk count is actually g... | 0 | _gd2GetHeader (gdIOCtxPtr in, int *sx, int *sy,
int *cs, int *vers, int *fmt, int *ncx, int *ncy,
t_chunk_info ** chunkIdx)
{
int i;
int ch;
char id[5];
t_chunk_info *cidx;
int sidx;
int nc;
GD2_DBG (printf ("Reading gd2 header info\n"));
for (i = 0; i < 4; i++) {
ch = gdGetC (... | 215,773,110,339,356,160,000,000,000,000,000,000,000 | None | null | [
"CWE-190"
] | CVE-2016-10168 | Integer overflow in gd_io.c in the GD Graphics Library (aka libgd) before 2.2.4 allows remote attackers to have unspecified impact via vectors involving the number of horizontal and vertical chunks in an image. | https://nvd.nist.gov/vuln/detail/CVE-2016-10168 |
9,510 | ImageMagick | 134463b926fa965571aa4febd61b810be5e7da05 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/134463b926fa965571aa4febd61b810be5e7da05 | https://github.com/ImageMagick/ImageMagick/issues/129 | 1 | static Image *ReadVIFFImage(const ImageInfo *image_info,
ExceptionInfo *exception)
{
#define VFF_CM_genericRGB 15
#define VFF_CM_ntscRGB 1
#define VFF_CM_NONE 0
#define VFF_DEP_DECORDER 0x4
#define VFF_DEP_NSORDER 0x8
#define VFF_DES_RAW 0
#define VFF_LOC_IMPLICIT 1
#define VFF_MAPTYP_NONE 0
#define VFF_MA... | 103,434,257,928,059,800,000,000,000,000,000,000,000 | viff.c | 5,265,972,500,401,776,000,000,000,000,000,000,000 | [
"CWE-284"
] | CVE-2016-10065 | The ReadVIFFImage function in coders/viff.c in ImageMagick before 7.0.1-0 allows remote attackers to cause a denial of service (application crash) or have other unspecified impact via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2016-10065 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.