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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
9,233 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 1 | int unshare_userns(unsigned long unshare_flags, struct cred **new_cred)
{
struct cred *cred;
if (!(unshare_flags & CLONE_NEWUSER))
return 0;
cred = prepare_creds();
if (!cred)
return -ENOMEM;
*new_cred = cred;
return create_user_ns(cred);
}
| 11,304,749,673,525,120,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
9,235 | linux | c8c499175f7d295ef867335bceb9a76a2c3cdc38 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c8c499175f7d295ef867335bceb9a76a2c3cdc38 | Bluetooth: SCO - Fix missing msg_namelen update in sco_sock_recvmsg()
If the socket is in state BT_CONNECT2 and BT_SK_DEFER_SETUP is set in
the flags, sco_sock_recvmsg() returns early with 0 without updating the
possibly set msg_namelen member. This, in turn, leads to a 128 byte
kernel stack leak in net/socket.c.
Fix... | 1 | static int sco_sock_recvmsg(struct kiocb *iocb, struct socket *sock,
struct msghdr *msg, size_t len, int flags)
{
struct sock *sk = sock->sk;
struct sco_pinfo *pi = sco_pi(sk);
lock_sock(sk);
if (sk->sk_state == BT_CONNECT2 &&
test_bit(BT_SK_DEFER_SETUP, &bt_sk(sk)->flags)) {
hci_conn_accept(pi->c... | 241,725,848,163,111,900,000,000,000,000,000,000,000 | sco.c | 26,587,629,362,037,386,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3226 | The sco_sock_recvmsg function in net/bluetooth/sco.c in the Linux kernel before 3.9-rc7 does not initialize a certain length variable, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-3226 |
9,236 | linux | 72a763d805a48ac8c0bf48fdb510e84c12de51fe | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/72a763d805a48ac8c0bf48fdb510e84c12de51fe | crypto: algif - suppress sending source address information in recvmsg
The current code does not set the msg_namelen member to 0 and therefore
makes net/socket.c leak the local sockaddr_storage variable to userland
-- 128 bytes of kernel stack memory. Fix that.
Cc: <stable@vger.kernel.org> # 2.6.38
Signed-off-by: Mat... | 1 | static int hash_recvmsg(struct kiocb *unused, struct socket *sock,
struct msghdr *msg, size_t len, int flags)
{
struct sock *sk = sock->sk;
struct alg_sock *ask = alg_sk(sk);
struct hash_ctx *ctx = ask->private;
unsigned ds = crypto_ahash_digestsize(crypto_ahash_reqtfm(&ctx->req));
int err;
if (len > ds)
le... | 223,283,461,660,244,750,000,000,000,000,000,000,000 | algif_hash.c | 274,659,569,534,280,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3076 | The crypto API in the Linux kernel through 3.9-rc8 does not initialize certain length variables, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call, related to the hash_recvmsg function in crypto/algif_hash.c and the skcipher_recvmsg function ... | https://nvd.nist.gov/vuln/detail/CVE-2013-3076 |
9,241 | linux | f1923820c447e986a9da0fc6bf60c1dccdf0408e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f1923820c447e986a9da0fc6bf60c1dccdf0408e | perf/x86: Fix offcore_rsp valid mask for SNB/IVB
The valid mask for both offcore_response_0 and
offcore_response_1 was wrong for SNB/SNB-EP,
IVB/IVB-EP. It was possible to write to
reserved bit and cause a GP fault crashing
the kernel.
This patch fixes the problem by correctly marking the
reserved bits in the valid m... | 1 | __init int intel_pmu_init(void)
{
union cpuid10_edx edx;
union cpuid10_eax eax;
union cpuid10_ebx ebx;
struct event_constraint *c;
unsigned int unused;
int version;
if (!cpu_has(&boot_cpu_data, X86_FEATURE_ARCH_PERFMON)) {
switch (boot_cpu_data.x86) {
case 0x6:
return p6_pmu_init();
case 0xb:
return... | 168,687,725,266,084,830,000,000,000,000,000,000,000 | perf_event_intel.c | 333,137,357,155,144,160,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-2146 | arch/x86/kernel/cpu/perf_event_intel.c in the Linux kernel before 3.8.9, when the Performance Events Subsystem is enabled, specifies an incorrect bitmask, which allows local users to cause a denial of service (general protection fault and system crash) by attempting to set a reserved bit. | https://nvd.nist.gov/vuln/detail/CVE-2013-2146 |
9,242 | linux | 8176cced706b5e5d15887584150764894e94e02f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8176cced706b5e5d15887584150764894e94e02f | perf: Treat attr.config as u64 in perf_swevent_init()
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed... | 1 | static int perf_swevent_init(struct perf_event *event)
{
int event_id = event->attr.config;
if (event->attr.type != PERF_TYPE_SOFTWARE)
return -ENOENT;
/*
* no branch sampling for software events
*/
if (has_branch_stack(event))
return -EOPNOTSUPP;
switch (event_id) {
case PERF_COUNT_SW_CPU_CLOCK:
... | 19,870,798,287,114,217,000,000,000,000,000,000,000 | core.c | 25,070,996,430,960,593,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2094 | The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2094 |
9,246 | linux | 5f00110f7273f9ff04ac69a5f85bb535a4fd0987 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/5f00110f7273f9ff04ac69a5f85bb535a4fd0987 | tmpfs: fix use-after-free of mempolicy object
The tmpfs remount logic preserves filesystem mempolicy if the mpol=M
option is not specified in the remount request. A new policy can be
specified if mpol=M is given.
Before this patch remounting an mpol bound tmpfs without specifying
mpol= mount option in the remount re... | 1 | static int shmem_remount_fs(struct super_block *sb, int *flags, char *data)
{
struct shmem_sb_info *sbinfo = SHMEM_SB(sb);
struct shmem_sb_info config = *sbinfo;
unsigned long inodes;
int error = -EINVAL;
if (shmem_parse_options(data, &config, true))
return error;
spin_lock(&sbinfo->stat_lock);
inodes ... | 69,198,739,652,828,040,000,000,000,000,000,000,000 | shmem.c | 324,391,302,440,655,720,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-1767 | Use-after-free vulnerability in the shmem_remount_fs function in mm/shmem.c in the Linux kernel before 3.7.10 allows local users to gain privileges or cause a denial of service (system crash) by remounting a tmpfs filesystem without specifying a required mpol (aka mempolicy) mount option. | https://nvd.nist.gov/vuln/detail/CVE-2013-1767 |
9,247 | linux | 6e601a53566d84e1ffd25e7b6fe0b6894ffd79c0 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6e601a53566d84e1ffd25e7b6fe0b6894ffd79c0 | sock_diag: Fix out-of-bounds access to sock_diag_handlers[]
Userland can send a netlink message requesting SOCK_DIAG_BY_FAMILY
with a family greater or equal then AF_MAX -- the array size of
sock_diag_handlers[]. The current code does not test for this
condition therefore is vulnerable to an out-of-bound access openin... | 1 | static int __sock_diag_rcv_msg(struct sk_buff *skb, struct nlmsghdr *nlh)
{
int err;
struct sock_diag_req *req = nlmsg_data(nlh);
const struct sock_diag_handler *hndl;
if (nlmsg_len(nlh) < sizeof(*req))
return -EINVAL;
hndl = sock_diag_lock_handler(req->sdiag_family);
if (hndl == NULL)
err = -ENOENT;
... | 81,691,601,596,043,680,000,000,000,000,000,000,000 | sock_diag.c | 5,227,707,971,742,808,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-1763 | Array index error in the __sock_diag_rcv_msg function in net/core/sock_diag.c in the Linux kernel before 3.7.10 allows local users to gain privileges via a large family value in a Netlink message. | https://nvd.nist.gov/vuln/detail/CVE-2013-1763 |
9,252 | linux | 43da5f2e0d0c69ded3d51907d9552310a6b545e8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/43da5f2e0d0c69ded3d51907d9552310a6b545e8 | net: fix info leak in compat dev_ifconf()
The implementation of dev_ifconf() for the compat ioctl interface uses
an intermediate ifc structure allocated in userland for the duration of
the syscall. Though, it fails to initialize the padding bytes inserted
for alignment and that for leaks four bytes of kernel stack. Ad... | 1 | static int dev_ifconf(struct net *net, struct compat_ifconf __user *uifc32)
{
struct compat_ifconf ifc32;
struct ifconf ifc;
struct ifconf __user *uifc;
struct compat_ifreq __user *ifr32;
struct ifreq __user *ifr;
unsigned int i, j;
int err;
if (copy_from_user(&ifc32, uifc32, sizeof(struct compat_ifconf)))
... | 260,748,882,966,970,700,000,000,000,000,000,000,000 | socket.c | 117,057,233,606,366,900,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2012-6539 | The dev_ifconf function in net/socket.c in the Linux kernel before 3.6 does not initialize a certain structure, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2012-6539 |
9,253 | linux | 4c87308bdea31a7b4828a51f6156e6f721a1fcc9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4c87308bdea31a7b4828a51f6156e6f721a1fcc9 | xfrm_user: fix info leak in copy_to_user_auth()
copy_to_user_auth() fails to initialize the remainder of alg_name and
therefore discloses up to 54 bytes of heap memory via netlink to
userland.
Use strncpy() instead of strcpy() to fill the trailing bytes of alg_name
with null bytes.
Signed-off-by: Mathias Krause <min... | 1 | static int copy_to_user_auth(struct xfrm_algo_auth *auth, struct sk_buff *skb)
{
struct xfrm_algo *algo;
struct nlattr *nla;
nla = nla_reserve(skb, XFRMA_ALG_AUTH,
sizeof(*algo) + (auth->alg_key_len + 7) / 8);
if (!nla)
return -EMSGSIZE;
algo = nla_data(nla);
strcpy(algo->alg_name, auth->alg_name);
... | 16,551,793,964,917,886,000,000,000,000,000,000,000 | xfrm_user.c | 146,233,539,701,132,340,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2012-6538 | The copy_to_user_auth function in net/xfrm/xfrm_user.c in the Linux kernel before 3.6 uses an incorrect C library function for copying a string, which allows local users to obtain sensitive information from kernel heap memory by leveraging the CAP_NET_ADMIN capability. | https://nvd.nist.gov/vuln/detail/CVE-2012-6538 |
9,258 | krb5 | d1f707024f1d0af6e54a18885322d70fa15ec4d3 | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/d1f707024f1d0af6e54a18885322d70fa15ec4d3 | Fix LDAP misused policy name crash [CVE-2014-5353]
In krb5_ldap_get_password_policy_from_dn, if LDAP_SEARCH returns
successfully with no results, return KRB5_KDB_NOENTRY instead of
returning success with a zeroed-out policy object. This fixes a null
dereference when an admin attempts to use an LDAP ticket policy name... | 1 | krb5_ldap_get_password_policy_from_dn(krb5_context context, char *pol_name,
char *pol_dn, osa_policy_ent_t *policy)
{
krb5_error_code st=0, tempst=0;
LDAP *ld=NULL;
LDAPMessage *result=NULL,*ent=NULL;
kdb5_dal_handl... | 312,745,617,712,492,800,000,000,000,000,000,000,000 | ldap_pwd_policy.c | 258,732,680,614,208,330,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2014-5353 | The krb5_ldap_get_password_policy_from_dn function in plugins/kdb/ldap/libkdb_ldap/ldap_pwd_policy.c in MIT Kerberos 5 (aka krb5) before 1.13.1, when the KDC uses LDAP, allows remote authenticated users to cause a denial of service (daemon crash) via a successful LDAP query with no results, as demonstrated by using an ... | https://nvd.nist.gov/vuln/detail/CVE-2014-5353 |
9,260 | linux | 07f4d9d74a04aa7c72c5dae0ef97565f28f17b92 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/07f4d9d74a04aa7c72c5dae0ef97565f28f17b92 | ALSA: control: Protect user controls against concurrent access
The user-control put and get handlers as well as the tlv do not protect against
concurrent access from multiple threads. Since the state of the control is not
updated atomically it is possible that either two write operations or a write
and a read operatio... | 1 | static int snd_ctl_elem_user_tlv(struct snd_kcontrol *kcontrol,
int op_flag,
unsigned int size,
unsigned int __user *tlv)
{
struct user_element *ue = kcontrol->private_data;
int change = 0;
void *new_data;
if (op_flag > 0) {
if (size > 1024 * 128) /* sane value */
return -EINVAL;
new_data =... | 95,140,620,080,426,880,000,000,000,000,000,000,000 | None | null | [
"CWE-362"
] | CVE-2014-4652 | Race condition in the tlv handler functionality in the snd_ctl_elem_user_tlv function in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allows local users to obtain sensitive information from kernel memory by leveraging /dev/snd/controlCX access. | https://nvd.nist.gov/vuln/detail/CVE-2014-4652 |
9,262 | krb5 | dc7ed55c689d57de7f7408b34631bf06fec9dab1 | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/dc7ed55c689d57de7f7408b34631bf06fec9dab1 | Fix LDAP key data segmentation [CVE-2014-4345]
For principal entries having keys with multiple kvnos (due to use of
-keepold), the LDAP KDB module makes an attempt to store all the keys
having the same kvno into a single krbPrincipalKey attribute value.
There is a fencepost error in the loop, causing currkvno to be se... | 1 | krb5_encode_krbsecretkey(krb5_key_data *key_data_in, int n_key_data,
krb5_kvno mkvno) {
struct berval **ret = NULL;
int currkvno;
int num_versions = 1;
int i, j, last;
krb5_error_code err = 0;
krb5_key_data *key_data;
if (n_key_data <= 0)
return NULL;
/... | 106,082,474,012,218,960,000,000,000,000,000,000,000 | ldap_principal2.c | 270,009,798,351,028,000,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-4345 | Off-by-one error in the krb5_encode_krbsecretkey function in plugins/kdb/ldap/libkdb_ldap/ldap_principal2.c in the LDAP KDB module in kadmind in MIT Kerberos 5 (aka krb5) 1.6.x through 1.11.x before 1.11.6 and 1.12.x before 1.12.2 allows remote authenticated users to cause a denial of service (buffer overflow) or possi... | https://nvd.nist.gov/vuln/detail/CVE-2014-4345 |
9,267 | linux | a642fc305053cc1c6e47e4f4df327895747ab485 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a642fc305053cc1c6e47e4f4df327895747ab485 | kvm: vmx: handle invvpid vm exit gracefully
On systems with invvpid instruction support (corresponding bit in
IA32_VMX_EPT_VPID_CAP MSR is set) guest invocation of invvpid
causes vm exit, which is currently not handled and results in
propagation of unknown exit to userspace.
Fix this by installing an invvpid vm exit ... | 1 | static bool nested_vmx_exit_handled(struct kvm_vcpu *vcpu)
{
u32 intr_info = vmcs_read32(VM_EXIT_INTR_INFO);
struct vcpu_vmx *vmx = to_vmx(vcpu);
struct vmcs12 *vmcs12 = get_vmcs12(vcpu);
u32 exit_reason = vmx->exit_reason;
trace_kvm_nested_vmexit(kvm_rip_read(vcpu), exit_reason,
vmcs_readl(EXIT_QUALIFICATION... | 25,917,898,868,493,210,000,000,000,000,000,000,000 | vmx.c | 276,794,831,116,419,260,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3646 | arch/x86/kvm/vmx.c in the KVM subsystem in the Linux kernel through 3.17.2 does not have an exit handler for the INVVPID instruction, which allows guest OS users to cause a denial of service (guest OS crash) via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2014-3646 |
9,268 | linux | 854e8bb1aa06c578c2c9145fa6bfe3680ef63b23 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/854e8bb1aa06c578c2c9145fa6bfe3680ef63b23 | KVM: x86: Check non-canonical addresses upon WRMSR
Upon WRMSR, the CPU should inject #GP if a non-canonical value (address) is
written to certain MSRs. The behavior is "almost" identical for AMD and Intel
(ignoring MSRs that are not implemented in either architecture since they would
anyhow #GP). However, IA32_SYSENTE... | 1 | static int wrmsr_interception(struct vcpu_svm *svm)
{
struct msr_data msr;
u32 ecx = svm->vcpu.arch.regs[VCPU_REGS_RCX];
u64 data = (svm->vcpu.arch.regs[VCPU_REGS_RAX] & -1u)
| ((u64)(svm->vcpu.arch.regs[VCPU_REGS_RDX] & -1u) << 32);
msr.data = data;
msr.index = ecx;
msr.host_initiated = false;
svm->next_... | 142,189,173,362,958,500,000,000,000,000,000,000,000 | svm.c | 123,664,188,883,176,400,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3610 | The WRMSR processing functionality in the KVM subsystem in the Linux kernel through 3.17.2 does not properly handle the writing of a non-canonical address to a model-specific register, which allows guest OS users to cause a denial of service (host OS crash) by leveraging guest OS privileges, related to the wrmsr_interc... | https://nvd.nist.gov/vuln/detail/CVE-2014-3610 |
9,271 | linux | 05ab8f2647e4221cbdb3856dd7d32bd5407316b3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/05ab8f2647e4221cbdb3856dd7d32bd5407316b3 | filter: prevent nla extensions to peek beyond the end of the message
The BPF_S_ANC_NLATTR and BPF_S_ANC_NLATTR_NEST extensions fail to check
for a minimal message length before testing the supplied offset to be
within the bounds of the message. This allows the subtraction of the nla
header to underflow and therefore -... | 1 | static u64 __skb_get_nlattr(u64 ctx, u64 A, u64 X, u64 r4, u64 r5)
{
struct sk_buff *skb = (struct sk_buff *)(long) ctx;
struct nlattr *nla;
if (skb_is_nonlinear(skb))
return 0;
if (A > skb->len - sizeof(struct nlattr))
return 0;
nla = nla_find((struct nlattr *) &skb->data[A], skb->len - A, X);
if (n... | 257,641,762,135,738,580,000,000,000,000,000,000,000 | filter.c | 228,552,301,451,129,950,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-3144 | The (1) BPF_S_ANC_NLATTR and (2) BPF_S_ANC_NLATTR_NEST extension implementations in the sk_run_filter function in net/core/filter.c in the Linux kernel through 3.14.3 do not check whether a certain length value is sufficiently large, which allows local users to cause a denial of service (integer underflow and system cr... | https://nvd.nist.gov/vuln/detail/CVE-2014-3144 |
9,275 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 1 | static int security_context_to_sid_core(const char *scontext, u32 scontext_len,
u32 *sid, u32 def_sid, gfp_t gfp_flags,
int force)
{
char *scontext2, *str = NULL;
struct context context;
int rc = 0;
if (!ss_initialized) {
int i;
for (i = 1; i < SECINITSID_NUM; i++) {
if (!strcmp(initial_sid... | 25,979,071,260,218,318,000,000,000,000,000,000,000 | services.c | 171,658,659,208,984,150,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
9,276 | linux | ef87dbe7614341c2e7bfe8d32fcb7028cc97442c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ef87dbe7614341c2e7bfe8d32fcb7028cc97442c | floppy: ignore kernel-only members in FDRAWCMD ioctl input
Always clear out these floppy_raw_cmd struct members after copying the
entire structure from userspace so that the in-kernel version is always
valid and never left in an interdeterminate state.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: L... | 1 | static int raw_cmd_copyin(int cmd, void __user *param,
struct floppy_raw_cmd **rcmd)
{
struct floppy_raw_cmd *ptr;
int ret;
int i;
*rcmd = NULL;
loop:
ptr = kmalloc(sizeof(struct floppy_raw_cmd), GFP_USER);
if (!ptr)
return -ENOMEM;
*rcmd = ptr;
ret = copy_from_user(ptr, param, sizeof(*ptr));
if (r... | 116,582,411,855,757,030,000,000,000,000,000,000,000 | floppy.c | 12,289,325,460,874,707,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1737 | The raw_cmd_copyin function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly handle error conditions during processing of an FDRAWCMD ioctl call, which allows local users to trigger kfree operations and gain privileges by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1737 |
9,277 | torque | 3ed749263abe3d69fa3626d142a5789dcb5a5684 | https://github.com/adaptivecomputing/torque | https://github.com/adaptivecomputing/torque/commit/3ed749263abe3d69fa3626d142a5789dcb5a5684 | Merge pull request #171 into 2.5-fixes. | 1 | int disrsi_(
int stream,
int *negate,
unsigned *value,
unsigned count)
{
int c;
unsigned locval;
unsigned ndigs;
char *cp;
char scratch[DIS_BUFSIZ+1];
assert(negate != NULL);
assert(value != NULL);
assert(count);
assert(stream >= 0);
assert(dis_getc != NULL);
assert(dis... | 119,468,526,822,998,800,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-0749 | Stack-based buffer overflow in lib/Libdis/disrsi_.c in Terascale Open-Source Resource and Queue Manager (aka TORQUE Resource Manager) 2.5.x through 2.5.13 allows remote attackers to execute arbitrary code via a large count value. | https://nvd.nist.gov/vuln/detail/CVE-2014-0749 |
9,279 | linux | edfbbf388f293d70bf4b7c0bc38774d05e6f711a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/edfbbf388f293d70bf4b7c0bc38774d05e6f711a | aio: fix kernel memory disclosure in io_getevents() introduced in v3.10
A kernel memory disclosure was introduced in aio_read_events_ring() in v3.10
by commit a31ad380bed817aa25f8830ad23e1a0480fef797. The changes made to
aio_read_events_ring() failed to correctly limit the index into
ctx->ring_pages[], allowing an at... | 1 | static long aio_read_events_ring(struct kioctx *ctx,
struct io_event __user *event, long nr)
{
struct aio_ring *ring;
unsigned head, tail, pos;
long ret = 0;
int copy_ret;
mutex_lock(&ctx->ring_lock);
/* Access to ->ring_pages here is protected by ctx->ring_lock. */
ring = kmap_atomic(ctx->ring_pages[0]);... | 175,931,741,530,477,530,000,000,000,000,000,000,000 | aio.c | 192,927,533,272,323,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2014-0206 | Array index error in the aio_read_events_ring function in fs/aio.c in the Linux kernel through 3.15.1 allows local users to obtain sensitive information from kernel memory via a large head value. | https://nvd.nist.gov/vuln/detail/CVE-2014-0206 |
9,281 | linux | 1fd819ecb90cc9b822cd84d3056ddba315d3340f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1fd819ecb90cc9b822cd84d3056ddba315d3340f | skbuff: skb_segment: orphan frags before copying
skb_segment copies frags around, so we need
to copy them carefully to avoid accessing
user memory after reporting completion to userspace
through a callback.
skb_segment doesn't normally happen on datapath:
TSO needs to be disabled - so disabling zero copy
in this case... | 1 | struct sk_buff *skb_segment(struct sk_buff *head_skb,
netdev_features_t features)
{
struct sk_buff *segs = NULL;
struct sk_buff *tail = NULL;
struct sk_buff *list_skb = skb_shinfo(head_skb)->frag_list;
skb_frag_t *frag = skb_shinfo(head_skb)->frags;
unsigned int mss = skb_shinfo(head_skb)->gso_size;
uns... | 183,173,230,648,926,970,000,000,000,000,000,000,000 | skbuff.c | 97,493,718,567,580,850,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2014-0131 | Use-after-free vulnerability in the skb_segment function in net/core/skbuff.c in the Linux kernel through 3.13.6 allows attackers to obtain sensitive information from kernel memory by leveraging the absence of a certain orphaning operation. | https://nvd.nist.gov/vuln/detail/CVE-2014-0131 |
9,282 | linux | ec0223ec48a90cb605244b45f7c62de856403729 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ec0223ec48a90cb605244b45f7c62de856403729 | net: sctp: fix sctp_sf_do_5_1D_ce to verify if we/peer is AUTH capable
RFC4895 introduced AUTH chunks for SCTP; during the SCTP
handshake RANDOM; CHUNKS; HMAC-ALGO are negotiated (CHUNKS
being optional though):
---------- INIT[RANDOM; CHUNKS; HMAC-ALGO] ---------->
<------- INIT-ACK[RANDOM; CHUNKS; HMAC-ALGO] ---... | 1 | sctp_disposition_t sctp_sf_do_5_1D_ce(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 sctp_association *new_asoc;
sctp_init_chunk_t *p... | 212,126,296,819,801,930,000,000,000,000,000,000,000 | sm_statefuns.c | 46,353,273,935,311,330,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0101 | The sctp_sf_do_5_1D_ce function in net/sctp/sm_statefuns.c in the Linux kernel through 3.13.6 does not validate certain auth_enable and auth_capable fields before making an sctp_sf_authenticate call, which allows remote attackers to cause a denial of service (NULL pointer dereference and system crash) via an SCTP hands... | https://nvd.nist.gov/vuln/detail/CVE-2014-0101 |
9,283 | linux | d8316f3991d207fe32881a9ac20241be8fa2bad0 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d8316f3991d207fe32881a9ac20241be8fa2bad0 | vhost: fix total length when packets are too short
When mergeable buffers are disabled, and the
incoming packet is too large for the rx buffer,
get_rx_bufs returns success.
This was intentional in order for make recvmsg
truncate the packet and then handle_rx would
detect err != sock_len and drop it.
Unfortunately we... | 1 | static int get_rx_bufs(struct vhost_virtqueue *vq,
struct vring_used_elem *heads,
int datalen,
unsigned *iovcount,
struct vhost_log *log,
unsigned *log_num,
unsigned int quota)
{
unsigned int out, in;
int seg = 0;
int headcount = 0;
unsigned d;
int r, nlogs = 0... | 91,983,981,836,047,390,000,000,000,000,000,000,000 | net.c | 340,076,013,592,583,200,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0077 | drivers/vhost/net.c in the Linux kernel before 3.13.10, when mergeable buffers are disabled, does not properly validate packet lengths, which allows guest OS users to cause a denial of service (memory corruption and host OS crash) or possibly gain privileges on the host OS via crafted packets, related to the handle_rx ... | https://nvd.nist.gov/vuln/detail/CVE-2014-0077 |
9,288 | linux | 0305cd5f7fca85dae392b9ba85b116896eb7c1c7 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0305cd5f7fca85dae392b9ba85b116896eb7c1c7 | Btrfs: fix truncation of compressed and inlined extents
When truncating a file to a smaller size which consists of an inline
extent that is compressed, we did not discard (or made unusable) the
data between the new file size and the old file size, wasting metadata
space and allowing for the truncated data to be leaked... | 1 | int btrfs_truncate_inode_items(struct btrfs_trans_handle *trans,
struct btrfs_root *root,
struct inode *inode,
u64 new_size, u32 min_type)
{
struct btrfs_path *path;
struct extent_buffer *leaf;
struct btrfs_file_extent_item *fi;
struct btrfs_key key;
struct btrfs_key found_key;
u64 e... | 202,426,911,853,200,160,000,000,000,000,000,000,000 | inode.c | 165,350,596,384,609,150,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2015-8374 | fs/btrfs/inode.c in the Linux kernel before 4.3.3 mishandles compressed inline extents, which allows local users to obtain sensitive pre-truncation information from a file via a clone action. | https://nvd.nist.gov/vuln/detail/CVE-2015-8374 |
9,292 | linux | 451a2886b6bf90e2fb378f7c46c655450fb96e81 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/451a2886b6bf90e2fb378f7c46c655450fb96e81 | sg_start_req(): make sure that there's not too many elements in iovec
unfortunately, allowing an arbitrary 16bit value means a possibility of
overflow in the calculation of total number of pages in bio_map_user_iov() -
we rely on there being no more than PAGE_SIZE members of sum in the
first loop there. If that sum w... | 1 | sg_start_req(Sg_request *srp, unsigned char *cmd)
{
int res;
struct request *rq;
Sg_fd *sfp = srp->parentfp;
sg_io_hdr_t *hp = &srp->header;
int dxfer_len = (int) hp->dxfer_len;
int dxfer_dir = hp->dxfer_direction;
unsigned int iov_count = hp->iovec_count;
Sg_scatter_hold *req_schp = &srp->data;
Sg_scatter_hol... | 199,085,659,186,409,220,000,000,000,000,000,000,000 | sg.c | 259,994,801,544,706,120,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2015-5707 | Integer overflow in the sg_start_req function in drivers/scsi/sg.c in the Linux kernel 2.6.x through 4.x before 4.1 allows local users to cause a denial of service or possibly have unspecified other impact via a large iov_count value in a write request. | https://nvd.nist.gov/vuln/detail/CVE-2015-5707 |
9,293 | linux | 59c816c1f24df0204e01851431d3bab3eb76719c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/59c816c1f24df0204e01851431d3bab3eb76719c | vhost/scsi: potential memory corruption
This code in vhost_scsi_make_tpg() is confusing because we limit "tpgt"
to UINT_MAX but the data type of "tpg->tport_tpgt" and that is a u16.
I looked at the context and it turns out that in
vhost_scsi_set_endpoint(), "tpg->tport_tpgt" is used as an offset into
the vs_tpg[] arr... | 1 | vhost_scsi_make_tpg(struct se_wwn *wwn,
struct config_group *group,
const char *name)
{
struct vhost_scsi_tport *tport = container_of(wwn,
struct vhost_scsi_tport, tport_wwn);
struct vhost_scsi_tpg *tpg;
unsigned long tpgt;
int ret;
if (strstr(name, "tpgt_") != name)
return ERR_PTR(-EINVAL)... | 138,793,578,128,477,900,000,000,000,000,000,000,000 | scsi.c | 220,191,379,760,540,220,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-4036 | Array index error in the tcm_vhost_make_tpg function in drivers/vhost/scsi.c in the Linux kernel before 4.0 might allow guest OS users to cause a denial of service (memory corruption) or possibly have unspecified other impact via a crafted VHOST_SCSI_SET_ENDPOINT ioctl call. NOTE: the affected function was renamed to ... | https://nvd.nist.gov/vuln/detail/CVE-2015-4036 |
9,294 | linux | ee73f656a604d5aa9df86a97102e4e462dd79924 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ee73f656a604d5aa9df86a97102e4e462dd79924 | KVM: PIT: control word is write-only
PIT control word (address 0x43) is write-only, reads are undefined.
Cc: stable@kernel.org
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com> | 1 | static int pit_ioport_read(struct kvm_io_device *this,
gpa_t addr, int len, void *data)
{
struct kvm_pit *pit = dev_to_pit(this);
struct kvm_kpit_state *pit_state = &pit->pit_state;
struct kvm *kvm = pit->kvm;
int ret, count;
struct kvm_kpit_channel_state *s;
if (!pit_in_range(addr))
return -EOPNOTSUPP;
... | 56,541,777,842,879,500,000,000,000,000,000,000,000 | i8254.c | 206,424,261,813,794,500,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-3214 | The pit_ioport_read in i8254.c in the Linux kernel before 2.6.33 and QEMU before 2.3.1 does not distinguish between read lengths and write lengths, which might allow guest OS users to execute arbitrary code on the host OS by triggering use of an invalid index. | https://nvd.nist.gov/vuln/detail/CVE-2015-3214 |
9,302 | 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> | 1 | 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)
... | 302,254,574,823,175,280,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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
9,318 | krb5 | 102bb6ebf20f9174130c85c3b052ae104e5073ec | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/102bb6ebf20f9174130c85c3b052ae104e5073ec | Fix krb5_read_message handling [CVE-2014-5355]
In recvauth_common, do not use strcmp against the data fields of
krb5_data objects populated by krb5_read_message(), as there is no
guarantee that they are C strings. Instead, create an expected
krb5_data value and use data_eq().
In the sample user-to-user server applic... | 1 | recvauth_common(krb5_context context,
krb5_auth_context * auth_context,
/* IN */
krb5_pointer fd,
char *appl_version,
krb5_principal server,
krb5_int32 flags,
krb5_keytab keytab,
/* OUT */
... | 146,562,876,660,269,340,000,000,000,000,000,000,000 | recvauth.c | 238,692,121,563,403,830,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2014-5355 | MIT Kerberos 5 (aka krb5) through 1.13.1 incorrectly expects that a krb5_read_message data field is represented as a string ending with a '\0' character, which allows remote attackers to (1) cause a denial of service (NULL pointer dereference) via a zero-byte version string or (2) cause a denial of service (out-of-boun... | https://nvd.nist.gov/vuln/detail/CVE-2014-5355 |
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 |
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 |
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 |
9,328 | libtiff | 83a4b92815ea04969d494416eaae3d4c6b338e4a | https://github.com/vadz/libtiff | https://github.com/vadz/libtiff/commit/83a4b92815ea04969d494416eaae3d4c6b338e4a#diff-5be5ce02d0dea67050d5b2a10102d1ba | * tools/tiffcrop.c: fix various out-of-bounds write vulnerabilities
in heap or stack allocated buffers. Reported as MSVR 35093,
MSVR 35096 and MSVR 35097. Discovered by Axel Souchet and Vishal
Chauhan from the MSRC Vulnerabilities & Mitigations team.
* tools/tiff2pdf.c: fix out-of-bounds write vulnerabilities in
heap a... | 1 | TIFFFlushData1(TIFF* tif)
{
if (tif->tif_rawcc > 0 && tif->tif_flags & TIFF_BUF4WRITE ) {
if (!isFillOrder(tif, tif->tif_dir.td_fillorder) &&
(tif->tif_flags & TIFF_NOBITREV) == 0)
TIFFReverseBits((uint8*)tif->tif_rawdata,
tif->tif_rawcc);
if (!TIFFAppendToStrip(tif,
isTiled(tif) ? tif->tif... | 323,177,524,682,187,800,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2016-9534 | tif_write.c in libtiff 4.0.6 has an issue in the error code path of TIFFFlushData1() that didn't reset the tif_rawcc and tif_rawcp members. Reported as MSVR 35095, aka "TIFFFlushData1 heap-buffer-overflow." | https://nvd.nist.gov/vuln/detail/CVE-2016-9534 |
9,330 | linux | 05692d7005a364add85c6e25a6c4447ce08f913a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/05692d7005a364add85c6e25a6c4447ce08f913a | vfio/pci: Fix integer overflows, bitmask check
The VFIO_DEVICE_SET_IRQS ioctl did not sufficiently sanitize
user-supplied integers, potentially allowing memory corruption. This
patch adds appropriate integer overflow checks, checks the range bounds
for VFIO_IRQ_SET_DATA_NONE, and also verifies that only single element... | 1 | static int vfio_msi_enable(struct vfio_pci_device *vdev, int nvec, bool msix)
{
struct pci_dev *pdev = vdev->pdev;
unsigned int flag = msix ? PCI_IRQ_MSIX : PCI_IRQ_MSI;
int ret;
if (!is_irq_none(vdev))
return -EINVAL;
vdev->ctx = kzalloc(nvec * sizeof(struct vfio_pci_irq_ctx), GFP_KERNEL);
if (!vdev->ctx... | 265,085,938,067,485,300,000,000,000,000,000,000,000 | vfio_pci_intrs.c | 317,782,573,120,508,840,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2016-9083 | drivers/vfio/pci/vfio_pci.c in the Linux kernel through 4.8.11 allows local users to bypass integer overflow checks, and cause a denial of service (memory corruption) or have unspecified other impact, by leveraging access to a vfio PCI device file for a VFIO_DEVICE_SET_IRQS ioctl call, aka a "state machine confusion bu... | https://nvd.nist.gov/vuln/detail/CVE-2016-9083 |
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 |
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 |
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 |
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 |
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 |
9,341 | php-src | 20ce2fe8e3c211a42fee05a461a5881be9a8790e | https://github.com/php/php-src | https://github.com/php/php-src/commit/20ce2fe8e3c211a42fee05a461a5881be9a8790e?w=1 | Fix bug #72663 - destroy broken object when unserializing
(cherry picked from commit 448c9be157f4147e121f1a2a524536c75c9c6059) | 1 | static int php_var_unserialize_internal(UNSERIALIZE_PARAMETER)
{
const unsigned char *cursor, *limit, *marker, *start;
zval *rval_ref;
limit = max;
cursor = *p;
if (YYCURSOR >= YYLIMIT) {
return 0;
}
if (var_hash && (*p)[0] != 'R') {
var_push(var_hash, rval);
}
start = cursor;
#line 554 "ext/standard... | 270,468,889,219,152,030,000,000,000,000,000,000,000 | var_unserializer.c | 166,352,165,499,312,480,000,000,000,000,000,000,000 | [
"CWE-502"
] | CVE-2016-7124 | ext/standard/var_unserializer.c in PHP before 5.6.25 and 7.x before 7.0.10 mishandles certain invalid objects, which allows remote attackers to cause a denial of service or possibly have unspecified other impact via crafted serialized data that leads to a (1) __destruct call or (2) magic method call. | https://nvd.nist.gov/vuln/detail/CVE-2016-7124 |
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 |
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 |
9,349 | php-src | f6aef68089221c5ea047d4a74224ee3deead99a6 | https://github.com/php/php-src | http://github.com/php/php-src/commit/f6aef68089221c5ea047d4a74224ee3deead99a6?w=1 | Fix bug #72434: ZipArchive class Use After Free Vulnerability in PHP's GC algorithm and unserialize | 1 | static PHP_MINIT_FUNCTION(zip)
{
#ifdef PHP_ZIP_USE_OO
zend_class_entry ce;
memcpy(&zip_object_handlers, zend_get_std_object_handlers(), sizeof(zend_object_handlers));
zip_object_handlers.clone_obj = NULL;
zip_object_handlers.get_property_ptr_ptr = php_zip_get_property_ptr_ptr;
zip_object_handlers.get_prope... | 132,104,834,997,612,040,000,000,000,000,000,000,000 | php_zip.c | 89,169,305,548,046,970,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2016-5773 | php_zip.c in the zip extension in PHP before 5.5.37, 5.6.x before 5.6.23, and 7.x before 7.0.8 improperly interacts with the unserialize implementation and garbage collection, which allows remote attackers to execute arbitrary code or cause a denial of service (use-after-free and application crash) via crafted serializ... | https://nvd.nist.gov/vuln/detail/CVE-2016-5773 |
9,372 | linux | 1f461dcdd296eecedaffffc6bae2bfa90bd7eb89 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1f461dcdd296eecedaffffc6bae2bfa90bd7eb89 | ppp: take reference on channels netns
Let channels hold a reference on their network namespace.
Some channel types, like ppp_async and ppp_synctty, can have their
userspace controller running in a different namespace. Therefore they
can't rely on them to preclude their netns from being removed from
under them.
======... | 1 | ppp_unregister_channel(struct ppp_channel *chan)
{
struct channel *pch = chan->ppp;
struct ppp_net *pn;
if (!pch)
return; /* should never happen */
chan->ppp = NULL;
/*
* This ensures that we have returned from any calls into the
* the channel's start_xmit or ioctl routine before we proceed.
*/
down_w... | 219,099,927,735,173,400,000,000,000,000,000,000,000 | ppp_generic.c | 33,074,513,998,217,310,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2016-4805 | Use-after-free vulnerability in drivers/net/ppp/ppp_generic.c in the Linux kernel before 4.5.2 allows local users to cause a denial of service (memory corruption and system crash, or spinlock) or possibly have unspecified other impact by removing a network namespace, related to the ppp_register_net_channel and ppp_unre... | https://nvd.nist.gov/vuln/detail/CVE-2016-4805 |
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 |
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 |
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 |
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 |
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 |
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 |
9,402 | linux | 712f4aad406bb1ed67f3f98d04c044191f0ff593 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/712f4aad406bb1ed67f3f98d04c044191f0ff593 | unix: properly account for FDs passed over unix sockets
It is possible for a process to allocate and accumulate far more FDs than
the process' limit by sending them over a unix socket then closing them
to keep the process' fd count low.
This change addresses this problem by keeping track of the number of FDs
in fligh... | 1 | static int unix_attach_fds(struct scm_cookie *scm, struct sk_buff *skb)
{
int i;
unsigned char max_level = 0;
int unix_sock_count = 0;
for (i = scm->fp->count - 1; i >= 0; i--) {
struct sock *sk = unix_get_socket(scm->fp->fp[i]);
if (sk) {
unix_sock_count++;
max_level = max(max_level,
unix_s... | 129,468,171,766,962,700,000,000,000,000,000,000,000 | af_unix.c | 94,301,712,041,177,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-2550 | The Linux kernel before 4.5 allows local users to bypass file-descriptor limits and cause a denial of service (memory consumption) by leveraging incorrect tracking of descriptor ownership and sending each descriptor over a UNIX socket before closing it. NOTE: this vulnerability exists because of an incorrect fix for CV... | https://nvd.nist.gov/vuln/detail/CVE-2016-2550 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
9,428 | tcpdump | 7029d15f148ef24bb7c6668bc640f5470d085e5a | https://github.com/the-tcpdump-group/tcpdump | https://github.com/the-tcpdump-group/tcpdump/commit/7029d15f148ef24bb7c6668bc640f5470d085e5a | CVE-2017-13029/PPP: Fix a bounds check, and clean up other bounds checks.
For configuration protocol options, use ND_TCHECK() and
ND_TCHECK_nBITS() macros, passing them the appropriate pointer argument.
This fixes one case where the ND_TCHECK2() call they replace was not
checking enough bytes.
This fixes a buffer ove... | 1 | print_ccp_config_options(netdissect_options *ndo,
const u_char *p, int length)
{
int len, opt;
if (length < 2)
return 0;
ND_TCHECK2(*p, 2);
len = p[1];
opt = p[0];
if (length < len)
return 0;
if (len < 2) {
ND_PRINT((ndo, "\n\t %s Option (0x%02x), length %u (length bogus, should ... | 201,333,923,056,790,370,000,000,000,000,000,000,000 | print-ppp.c | 86,948,591,370,272,700,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-13029 | The PPP parser in tcpdump before 4.9.2 has a buffer over-read in print-ppp.c:print_ccp_config_options(). | https://nvd.nist.gov/vuln/detail/CVE-2017-13029 |
9,429 | tcpdump | 5edf405d7ed9fc92f4f43e8a3d44baa4c6387562 | https://github.com/the-tcpdump-group/tcpdump | https://github.com/the-tcpdump-group/tcpdump/commit/5edf405d7ed9fc92f4f43e8a3d44baa4c6387562 | CVE-2017-13008/IEEE 802.11: Fix TIM bitmap copy to copy from p + offset.
offset has already been advanced to point to the bitmap; we shouldn't
add the amount to advance again.
This fixes a buffer over-read discovered by Brian 'geeknik' Carpenter.
Add a test using the capture file supplied by the reporter(s).
While ... | 1 | parse_elements(netdissect_options *ndo,
struct mgmt_body_t *pbody, const u_char *p, int offset,
u_int length)
{
u_int elementlen;
struct ssid_t ssid;
struct challenge_t challenge;
struct rates_t rates;
struct ds_t ds;
struct cf_t cf;
struct tim_t tim;
/*
* We haven't seen any el... | 92,553,270,014,305,060,000,000,000,000,000,000,000 | print-802_11.c | 126,620,455,302,702,500,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-13008 | The IEEE 802.11 parser in tcpdump before 4.9.2 has a buffer over-read in print-802_11.c:parse_elements(). | https://nvd.nist.gov/vuln/detail/CVE-2017-13008 |
9,431 | tcpdump | 3b32029db354cbc875127869d9b12a9addc75b50 | https://github.com/the-tcpdump-group/tcpdump | https://github.com/the-tcpdump-group/tcpdump/commit/3b32029db354cbc875127869d9b12a9addc75b50 | CVE-2017-12999/IS-IS: Add a missing length check.
This fixes a buffer over-read discovered by Forcepoint's security
researchers Otto Airamo & Antti Levomäki.
Add tests using the capture files supplied by the reporter(s). | 1 | isis_print(netdissect_options *ndo,
const uint8_t *p, u_int length)
{
const struct isis_common_header *isis_header;
const struct isis_iih_lan_header *header_iih_lan;
const struct isis_iih_ptp_header *header_iih_ptp;
const struct isis_lsp_header *header_lsp;
const struct isis_csnp_header ... | 297,281,792,744,887,980,000,000,000,000,000,000,000 | print-isoclns.c | 89,784,539,627,020,220,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-12999 | The IS-IS parser in tcpdump before 4.9.2 has a buffer over-read in print-isoclns.c:isis_print(). | https://nvd.nist.gov/vuln/detail/CVE-2017-12999 |
9,432 | tcpdump | 34cec721d39c76be1e0a600829a7b17bdfb832b6 | https://github.com/the-tcpdump-group/tcpdump | https://github.com/the-tcpdump-group/tcpdump/commit/34cec721d39c76be1e0a600829a7b17bdfb832b6 | CVE-2017-12997/LLDP: Don't use an 8-bit loop counter.
If you have a
for (i = 0; i < N; i++)
loop, you'd better make sure that i is big enough to hold N - not N-1,
N.
The TLV length here is 9 bits long, not 8 bits long, so an 8-bit loop
counter will overflow and you can loop infinitely.
This fixes an infinite loop... | 1 | lldp_private_8021_print(netdissect_options *ndo,
const u_char *tptr, u_int tlv_len)
{
int subtype, hexdump = FALSE;
u_int sublen;
u_int tval;
uint8_t i;
if (tlv_len < 4) {
return hexdump;
}
subtype = *(tptr+3);
ND_PRINT((ndo, "\n\t %s Subtype (%u)... | 206,271,957,265,320,640,000,000,000,000,000,000,000 | print-lldp.c | 67,823,449,492,692,070,000,000,000,000,000,000,000 | [
"CWE-835"
] | CVE-2017-12997 | The LLDP parser in tcpdump before 4.9.2 could enter an infinite loop due to a bug in print-lldp.c:lldp_private_8021_print(). | https://nvd.nist.gov/vuln/detail/CVE-2017-12997 |
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 |
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 |
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 |
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 |
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 |
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 |
9,449 | yara | 925bcf3c3b0a28b5b78e25d9efda5c0bf27ae699 | https://github.com/VirusTotal/yara | https://github.com/VirusTotal/yara/commit/925bcf3c3b0a28b5b78e25d9efda5c0bf27ae699 | Fix issue #674. Move regexp limits to limits.h. | 1 | int yr_re_ast_create(
RE_AST** re_ast)
{
*re_ast = (RE_AST*) yr_malloc(sizeof(RE_AST));
if (*re_ast == NULL)
return ERROR_INSUFFICIENT_MEMORY;
(*re_ast)->flags = 0;
(*re_ast)->root_node = NULL;
return ERROR_SUCCESS;
}
| 28,548,031,463,136,045,000,000,000,000,000,000,000 | re.c | 312,264,943,192,667,120,000,000,000,000,000,000,000 | [
"CWE-674"
] | CVE-2017-9304 | libyara/re.c in the regexp module in YARA 3.5.0 allows remote attackers to cause a denial of service (stack consumption) via a crafted rule that is mishandled in the _yr_re_emit function. | https://nvd.nist.gov/vuln/detail/CVE-2017-9304 |
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 |
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 |
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 |
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 |
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 |
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 |
9,477 | linux | 2dcab598484185dea7ec22219c76dcdd59e3cb90 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2dcab598484185dea7ec22219c76dcdd59e3cb90 | sctp: avoid BUG_ON on sctp_wait_for_sndbuf
Alexander Popov reported that an application may trigger a BUG_ON in
sctp_wait_for_sndbuf if the socket tx buffer is full, a thread is
waiting on it to queue more data and meanwhile another thread peels off
the association being used by the first thread.
This patch replaces ... | 1 | static int sctp_wait_for_sndbuf(struct sctp_association *asoc, long *timeo_p,
size_t msg_len)
{
struct sock *sk = asoc->base.sk;
int err = 0;
long current_timeo = *timeo_p;
DEFINE_WAIT(wait);
pr_debug("%s: asoc:%p, timeo:%ld, msg_len:%zu\n", __func__, asoc,
*timeo_p, msg_len);
/* Increment the associatio... | 77,742,281,099,885,130,000,000,000,000,000,000,000 | socket.c | 35,503,354,525,738,835,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2017-5986 | Race condition in the sctp_wait_for_sndbuf function in net/sctp/socket.c in the Linux kernel before 4.9.11 allows local users to cause a denial of service (assertion failure and panic) via a multithreaded application that peels off an association in a certain buffer-full state. | https://nvd.nist.gov/vuln/detail/CVE-2017-5986 |
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 |
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 |
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 |
9,482 | ImageMagick | 91cc3f36f2ccbd485a0456bab9aebe63b635da88 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/91cc3f36f2ccbd485a0456bab9aebe63b635da88 | https://github.com/ImageMagick/ImageMagick/issues/348 | 1 | static size_t WritePSDChannel(const PSDInfo *psd_info,
const ImageInfo *image_info,Image *image,Image *next_image,
const QuantumType quantum_type, unsigned char *compact_pixels,
MagickOffsetType size_offset,const MagickBooleanType separate,
ExceptionInfo *exception)
{
int
y;
MagickBooleanType
monoc... | 118,935,701,709,361,370,000,000,000,000,000,000,000 | psd.c | 178,433,933,849,726,840,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2017-5510 | coders/psd.c in ImageMagick allows remote attackers to have unspecified impact via a crafted PSD file, which triggers an out-of-bounds write. | https://nvd.nist.gov/vuln/detail/CVE-2017-5510 |
9,489 | openjpeg | d27ccf01c68a31ad62b33d2dc1ba2bb1eeaafe7b | https://github.com/uclouvain/openjpeg | https://github.com/uclouvain/openjpeg/commit/d27ccf01c68a31ad62b33d2dc1ba2bb1eeaafe7b | Avoid division by zero in opj_pi_next_rpcl, opj_pi_next_pcrl and opj_pi_next_cprl (#938)
Fixes issues with id:000026,sig:08,src:002419,op:int32,pos:60,val:+32 and
id:000019,sig:08,src:001098,op:flip1,pos:49 | 1 | static OPJ_BOOL opj_pi_next_cprl(opj_pi_iterator_t * pi)
{
opj_pi_comp_t *comp = NULL;
opj_pi_resolution_t *res = NULL;
OPJ_UINT32 index = 0;
if (!pi->first) {
comp = &pi->comps[pi->compno];
goto LABEL_SKIP;
} else {
pi->first = 0;
}
for (pi->compno = pi->poc.compno... | 271,427,417,647,316,780,000,000,000,000,000,000,000 | pi.c | 270,132,454,060,460,450,000,000,000,000,000,000,000 | [
"CWE-369"
] | CVE-2016-10506 | Division-by-zero vulnerabilities in the functions opj_pi_next_cprl, opj_pi_next_pcrl, and opj_pi_next_rpcl in pi.c in OpenJPEG before 2.2.0 allow remote attackers to cause a denial of service (application crash) via crafted j2k files. | https://nvd.nist.gov/vuln/detail/CVE-2016-10506 |
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 |
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 |
9,511 | ImageMagick | 10b3823a7619ed22d42764733eb052c4159bc8c1 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/10b3823a7619ed22d42764733eb052c4159bc8c1 | None | 1 | MagickBooleanType sixel_decode(unsigned char /* in */ *p, /* sixel bytes */
unsigned char /* out */ **pixels, /* decoded pixels */
size_t /* out */ *pwidth, /* image width */
... | 35,991,042,325,313,126,000,000,000,000,000,000,000 | sixel.c | 213,717,042,796,677,070,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-10054 | Buffer overflow in the WriteMAPImage function in coders/map.c in ImageMagick before 6.9.5-8 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-10054 |
9,512 | ImageMagick | 9e187b73a8a1290bb0e1a1c878f8be1917aa8742 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/9e187b73a8a1290bb0e1a1c878f8be1917aa8742 | None | 1 | static void WriteProfile(j_compress_ptr jpeg_info,Image *image)
{
const char
*name;
const StringInfo
*profile;
MagickBooleanType
iptc;
register ssize_t
i;
size_t
length,
tag_length;
StringInfo
*custom_profile;
/*
Save image profile as a APP marker.
*/
iptc=MagickF... | 203,461,117,257,884,900,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2016-10052 | Buffer overflow in the WriteProfile function in coders/jpeg.c in ImageMagick before 6.9.5-6 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-10052 |
9,516 | php-src | 863d37ea66d5c960db08d6f4a2cbd2518f0f80d1 | https://github.com/php/php-src | https://github.com/php/php-src/commit/863d37ea66d5c960db08d6f4a2cbd2518f0f80d1 | Fix #72696: imagefilltoborder stackoverflow on truecolor images
We must not allow negative color values be passed to
gdImageFillToBorder(), because that can lead to infinite recursion
since the recursion termination condition will not necessarily be met. | 1 | void gdImageFillToBorder (gdImagePtr im, int x, int y, int border, int color)
{
int lastBorder;
/* Seek left */
int leftLimit = -1, rightLimit;
int i, restoreAlphaBlending = 0;
if (border < 0) {
/* Refuse to fill to a non-solid border */
return;
}
if (!im->trueColor) {
if ((color > (im->colorsTotal... | 199,950,444,190,713,360,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2016-9933 | Stack consumption vulnerability in the gdImageFillToBorder function in gd.c in the GD Graphics Library (aka libgd) before 2.2.2, as used in PHP before 5.6.28 and 7.x before 7.0.13, allows remote attackers to cause a denial of service (segmentation violation) via a crafted imagefilltoborder call that triggers use of a n... | https://nvd.nist.gov/vuln/detail/CVE-2016-9933 |
9,517 | jasper | 1abc2e5a401a4bf1d5ca4df91358ce5df111f495 | https://github.com/mdadams/jasper | https://github.com/mdadams/jasper/commit/1abc2e5a401a4bf1d5ca4df91358ce5df111f495 | Fixed an array overflow problem in the JPC decoder. | 1 | static int jpc_dec_tileinit(jpc_dec_t *dec, jpc_dec_tile_t *tile)
{
jpc_dec_tcomp_t *tcomp;
int compno;
int rlvlno;
jpc_dec_rlvl_t *rlvl;
jpc_dec_band_t *band;
jpc_dec_prc_t *prc;
int bndno;
jpc_tsfb_band_t *bnd;
int bandno;
jpc_dec_ccp_t *ccp;
int prccnt;
jpc_dec_cblk_t *cblk;
int cblkcnt;
uint_fast32_t ... | 152,611,857,864,829,500,000,000,000,000,000,000,000 | jpc_dec.c | 9,904,405,345,613,609,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-9560 | Stack-based buffer overflow in the jpc_tsfb_getbands2 function in jpc_tsfb.c in JasPer before 1.900.30 allows remote attackers to have unspecified impact via a crafted image. | https://nvd.nist.gov/vuln/detail/CVE-2016-9560 |
9,524 | jasper | d8c2604cd438c41ec72aff52c16ebd8183068020 | https://github.com/mdadams/jasper | https://github.com/mdadams/jasper/commit/d8c2604cd438c41ec72aff52c16ebd8183068020 | Added range check on XRsiz and YRsiz fields of SIZ marker segment. | 1 | static int jpc_siz_getparms(jpc_ms_t *ms, jpc_cstate_t *cstate,
jas_stream_t *in)
{
jpc_siz_t *siz = &ms->parms.siz;
unsigned int i;
uint_fast8_t tmp;
/* Eliminate compiler warning about unused variables. */
cstate = 0;
if (jpc_getuint16(in, &siz->caps) ||
jpc_getuint32(in, &siz->width) ||
jpc_getuint32... | 10,991,172,644,452,336,000,000,000,000,000,000,000 | jpc_cs.c | 109,966,816,698,492,500,000,000,000,000,000,000,000 | [
"CWE-369"
] | CVE-2016-8692 | The jpc_dec_process_siz function in libjasper/jpc/jpc_dec.c in JasPer before 1.900.4 allows remote attackers to cause a denial of service (divide-by-zero error and application crash) via a crafted YRsiz value in a BMP image to the imginfo command. | https://nvd.nist.gov/vuln/detail/CVE-2016-8692 |
9,525 | libarchive | eec077f52bfa2d3f7103b4b74d52572ba8a15aca | https://github.com/libarchive/libarchive | https://github.com/libarchive/libarchive/commit/eec077f52bfa2d3f7103b4b74d52572ba8a15aca | Issue 747 (and others?): Avoid OOB read when parsing multiple long lines
The mtree bidder needs to look several lines ahead
in the input. It does this by extending the read-ahead
and parsing subsequent lines from the same growing buffer.
A bookkeeping error when extending the read-ahead would
sometimes lead it to si... | 1 | next_line(struct archive_read *a,
const char **b, ssize_t *avail, ssize_t *ravail, ssize_t *nl)
{
ssize_t len;
int quit;
quit = 0;
if (*avail == 0) {
*nl = 0;
len = 0;
} else
len = get_line_size(*b, *avail, nl);
/*
* Read bytes more while it does not reach the end of line.
*/
while (*nl == 0 &&... | 62,295,156,973,029,730,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2016-8688 | The mtree bidder in libarchive 3.2.1 does not keep track of line sizes when extending the read-ahead, which allows remote attackers to cause a denial of service (crash) via a crafted file, which triggers an invalid read in the (1) detect_form or (2) bid_entry function in libarchive/archive_read_support_format_mtree.c. | https://nvd.nist.gov/vuln/detail/CVE-2016-8688 |
9,526 | ImageMagick | 6e48aa92ff4e6e95424300ecd52a9ea453c19c60 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/6e48aa92ff4e6e95424300ecd52a9ea453c19c60 | https://github.com/ImageMagick/ImageMagick/issues/268 | 1 | static Image *ReadTIFFImage(const ImageInfo *image_info,
ExceptionInfo *exception)
{
const char
*option;
float
*chromaticity,
x_position,
y_position,
x_resolution,
y_resolution;
Image
*image;
int
tiff_status;
MagickBooleanType
status;
MagickSizeType
number_pixe... | 280,343,953,088,806,580,000,000,000,000,000,000,000 | tiff.c | 223,604,198,693,155,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-8677 | The AcquireQuantumPixels function in MagickCore/quantum.c in ImageMagick before 7.0.3-1 allows remote attackers to have unspecified impact via a crafted image file, which triggers a memory allocation failure. | https://nvd.nist.gov/vuln/detail/CVE-2016-8677 |
9,527 | libav | e5b019725f53b79159931d3a7317107cbbfd0860 | https://github.com/libav/libav | https://github.com/libav/libav/commit/e5b019725f53b79159931d3a7317107cbbfd0860 | m4vdec: Check for non-startcode 00 00 00 sequences in probe
This makes the m4v detection less trigger-happy.
Bug-Id: 949
Signed-off-by: Diego Biurrun <diego@biurrun.de> | 1 | static int mpeg4video_probe(AVProbeData *probe_packet)
{
uint32_t temp_buffer = -1;
int VO = 0, VOL = 0, VOP = 0, VISO = 0, res = 0;
int i;
for (i = 0; i < probe_packet->buf_size; i++) {
temp_buffer = (temp_buffer << 8) + probe_packet->buf[i];
if ((temp_buffer & 0xffffff00) != 0x100)... | 296,504,819,383,989,060,000,000,000,000,000,000,000 | m4vdec.c | 292,188,987,403,181,880,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2016-8675 | The get_vlc2 function in get_bits.h in Libav before 11.9 allows remote attackers to cause a denial of service (NULL pointer dereference and crash) via a crafted mp3 file, possibly related to startcode sequences during m4v detection. | https://nvd.nist.gov/vuln/detail/CVE-2016-8675 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.