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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
158,818 | linux | b860d3cc62877fad02863e2a08efff69a19382d2 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b860d3cc62877fad02863e2a08efff69a19382d2 | l2tp: fix info leak in l2tp_ip6_recvmsg()
The L2TP code for IPv6 fails to initialize the l2tp_conn_id member of
struct sockaddr_l2tpip6 and therefore leaks four bytes kernel stack
in l2tp_ip6_recvmsg() in case msg_name is set.
Initialize l2tp_conn_id with 0 to avoid the info leak.
Signed-off-by: Mathias Krause <mini... | 0 | static int l2tp_ip6_recvmsg(struct kiocb *iocb, struct sock *sk,
struct msghdr *msg, size_t len, int noblock,
int flags, int *addr_len)
{
struct ipv6_pinfo *np = inet6_sk(sk);
struct sockaddr_l2tpip6 *lsa = (struct sockaddr_l2tpip6 *)msg->msg_name;
size_t copied = 0;
int err = -EOPNOTSUPP;
struct sk_... | 2,738,390,768,923,815,000,000,000,000,000,000,000 | None | null | [
"CWE-200"
] | CVE-2013-3230 | The l2tp_ip6_recvmsg function in net/l2tp/l2tp_ip6.c in the Linux kernel before 3.9-rc7 does not initialize a certain structure member, 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-3230 |
1,004 | linux | a5598bd9c087dc0efc250a5221e5d0e6f584ee88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a5598bd9c087dc0efc250a5221e5d0e6f584ee88 | iucv: Fix missing msg_namelen update in iucv_sock_recvmsg()
The current code does not fill the msg_name member in case it is set.
It also does not set the msg_namelen member to 0 and therefore makes
net/socket.c leak the local, uninitialized sockaddr_storage variable
to userland -- 128 bytes of kernel stack memory.
F... | 1 | static int iucv_sock_recvmsg(struct kiocb *iocb, struct socket *sock,
struct msghdr *msg, size_t len, int flags)
{
int noblock = flags & MSG_DONTWAIT;
struct sock *sk = sock->sk;
struct iucv_sock *iucv = iucv_sk(sk);
unsigned int copied, rlen;
struct sk_buff *skb, *rskb, *cskb;
int err = 0;
if ((sk-... | 292,835,413,067,186,280,000,000,000,000,000,000,000 | af_iucv.c | 219,701,138,014,006,630,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3229 | The iucv_sock_recvmsg function in net/iucv/af_iucv.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-3229 |
158,819 | linux | a5598bd9c087dc0efc250a5221e5d0e6f584ee88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a5598bd9c087dc0efc250a5221e5d0e6f584ee88 | iucv: Fix missing msg_namelen update in iucv_sock_recvmsg()
The current code does not fill the msg_name member in case it is set.
It also does not set the msg_namelen member to 0 and therefore makes
net/socket.c leak the local, uninitialized sockaddr_storage variable
to userland -- 128 bytes of kernel stack memory.
F... | 0 | static int iucv_sock_recvmsg(struct kiocb *iocb, struct socket *sock,
struct msghdr *msg, size_t len, int flags)
{
int noblock = flags & MSG_DONTWAIT;
struct sock *sk = sock->sk;
struct iucv_sock *iucv = iucv_sk(sk);
unsigned int copied, rlen;
struct sk_buff *skb, *rskb, *cskb;
int err = 0;
msg->msg_... | 168,242,682,143,857,780,000,000,000,000,000,000,000 | af_iucv.c | 26,562,190,649,779,340,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3229 | The iucv_sock_recvmsg function in net/iucv/af_iucv.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-3229 |
1,008 | linux | 4683f42fde3977bdb4e8a09622788cc8b5313778 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4683f42fde3977bdb4e8a09622788cc8b5313778 | Bluetooth: fix possible info leak in bt_sock_recvmsg()
In case the socket is already shutting down, bt_sock_recvmsg() returns
with 0 without updating msg_namelen leading to net/socket.c leaking the
local, uninitialized sockaddr_storage variable to userland -- 128 bytes
of kernel stack memory.
Fix this by moving the m... | 1 | int bt_sock_recvmsg(struct kiocb *iocb, struct socket *sock,
struct msghdr *msg, size_t len, int flags)
{
int noblock = flags & MSG_DONTWAIT;
struct sock *sk = sock->sk;
struct sk_buff *skb;
size_t copied;
int err;
BT_DBG("sock %p sk %p len %zu", sock, sk, len);
if (flags & (MSG_OOB))
return -EOPNOTSUP... | 4,403,052,444,065,820,700,000,000,000,000,000,000 | af_bluetooth.c | 92,794,431,760,555,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3224 | The bt_sock_recvmsg function in net/bluetooth/af_bluetooth.c in the Linux kernel before 3.9-rc7 does not properly 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-3224 |
158,820 | linux | 4683f42fde3977bdb4e8a09622788cc8b5313778 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4683f42fde3977bdb4e8a09622788cc8b5313778 | Bluetooth: fix possible info leak in bt_sock_recvmsg()
In case the socket is already shutting down, bt_sock_recvmsg() returns
with 0 without updating msg_namelen leading to net/socket.c leaking the
local, uninitialized sockaddr_storage variable to userland -- 128 bytes
of kernel stack memory.
Fix this by moving the m... | 0 | int bt_sock_recvmsg(struct kiocb *iocb, struct socket *sock,
struct msghdr *msg, size_t len, int flags)
{
int noblock = flags & MSG_DONTWAIT;
struct sock *sk = sock->sk;
struct sk_buff *skb;
size_t copied;
int err;
BT_DBG("sock %p sk %p len %zu", sock, sk, len);
if (flags & (MSG_OOB))
return -EOPNOTSUP... | 137,008,293,782,107,320,000,000,000,000,000,000,000 | af_bluetooth.c | 26,667,698,022,529,756,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3224 | The bt_sock_recvmsg function in net/bluetooth/af_bluetooth.c in the Linux kernel before 3.9-rc7 does not properly 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-3224 |
1,012 | linux | 12ae030d54ef250706da5642fc7697cc60ad0df7 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/12ae030d54ef250706da5642fc7697cc60ad0df7 | perf/ftrace: Fix paranoid level for enabling function tracer
The current default perf paranoid level is "1" which has
"perf_paranoid_kernel()" return false, and giving any operations that
use it, access to normal users. Unfortunately, this includes function
tracing and normal users should not be allowed to enable func... | 1 | static int perf_trace_event_perm(struct ftrace_event_call *tp_event,
struct perf_event *p_event)
{
/* The ftrace function trace is allowed only for root. */
if (ftrace_event_is_function(tp_event) &&
perf_paranoid_kernel() && !capable(CAP_SYS_ADMIN))
return -EPERM;
/* No tracing, just counting, so ... | 282,170,608,950,902,630,000,000,000,000,000,000,000 | trace_event_perf.c | 103,737,043,602,954,010,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2930 | The perf_trace_event_perm function in kernel/trace/trace_event_perf.c in the Linux kernel before 3.12.2 does not properly restrict access to the perf subsystem, which allows local users to enable function tracing via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2930 |
158,821 | linux | 12ae030d54ef250706da5642fc7697cc60ad0df7 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/12ae030d54ef250706da5642fc7697cc60ad0df7 | perf/ftrace: Fix paranoid level for enabling function tracer
The current default perf paranoid level is "1" which has
"perf_paranoid_kernel()" return false, and giving any operations that
use it, access to normal users. Unfortunately, this includes function
tracing and normal users should not be allowed to enable func... | 0 | static int perf_trace_event_perm(struct ftrace_event_call *tp_event,
struct perf_event *p_event)
{
/* The ftrace function trace is allowed only for root. */
if (ftrace_event_is_function(tp_event) &&
perf_paranoid_tracepoint_raw() && !capable(CAP_SYS_ADMIN))
return -EPERM;
/* No tracing, just count... | 113,078,525,885,039,850,000,000,000,000,000,000,000 | trace_event_perf.c | 17,968,683,985,346,208,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2930 | The perf_trace_event_perm function in kernel/trace/trace_event_perf.c in the Linux kernel before 3.12.2 does not properly restrict access to the perf subsystem, which allows local users to enable function tracing via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2930 |
1,013 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 1 | static int __ptrace_may_access(struct task_struct *task, unsigned int mode)
{
const struct cred *cred = current_cred(), *tcred;
/* May we inspect the given task?
* This check is used both for attaching with ptrace
* and for allowing access to sensitive information in /proc.
*
* ptrace_attach denies several c... | 145,541,299,218,287,470,000,000,000,000,000,000,000 | ptrace.c | 292,077,372,195,169,620,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
158,822 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | static int __ptrace_may_access(struct task_struct *task, unsigned int mode)
{
const struct cred *cred = current_cred(), *tcred;
/* May we inspect the given task?
* This check is used both for attaching with ptrace
* and for allowing access to sensitive information in /proc.
*
* ptrace_attach denies several c... | 215,931,340,294,829,000,000,000,000,000,000,000,000 | ptrace.c | 316,279,739,902,479,560,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
1,014 | linux | cea4dcfdad926a27a18e188720efe0f2c9403456 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cea4dcfdad926a27a18e188720efe0f2c9403456 | iscsi-target: fix heap buffer overflow on error
If a key was larger than 64 bytes, as checked by iscsi_check_key(), the
error response packet, generated by iscsi_add_notunderstood_response(),
would still attempt to copy the entire key into the packet, overflowing
the structure on the heap.
Remote preauthentication ke... | 1 | static int iscsi_add_notunderstood_response(
char *key,
char *value,
struct iscsi_param_list *param_list)
{
struct iscsi_extra_response *extra_response;
if (strlen(value) > VALUE_MAXLEN) {
pr_err("Value for notunderstood key \"%s\" exceeds %d,"
" protocol error.\n", key, VALUE_MAXLEN);
return -1;
}
extr... | 100,762,060,795,839,660,000,000,000,000,000,000,000 | iscsi_target_parameters.c | 259,649,241,332,208,500,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2850 | Heap-based buffer overflow in the iscsi_add_notunderstood_response function in drivers/target/iscsi/iscsi_target_parameters.c in the iSCSI target subsystem in the Linux kernel through 3.9.4 allows remote attackers to cause a denial of service (memory corruption and OOPS) or possibly execute arbitrary code via a long ke... | https://nvd.nist.gov/vuln/detail/CVE-2013-2850 |
158,823 | linux | cea4dcfdad926a27a18e188720efe0f2c9403456 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cea4dcfdad926a27a18e188720efe0f2c9403456 | iscsi-target: fix heap buffer overflow on error
If a key was larger than 64 bytes, as checked by iscsi_check_key(), the
error response packet, generated by iscsi_add_notunderstood_response(),
would still attempt to copy the entire key into the packet, overflowing
the structure on the heap.
Remote preauthentication ke... | 0 | static int iscsi_add_notunderstood_response(
char *key,
char *value,
struct iscsi_param_list *param_list)
{
struct iscsi_extra_response *extra_response;
if (strlen(value) > VALUE_MAXLEN) {
pr_err("Value for notunderstood key \"%s\" exceeds %d,"
" protocol error.\n", key, VALUE_MAXLEN);
return -1;
}
extr... | 336,700,731,731,125,500,000,000,000,000,000,000,000 | iscsi_target_parameters.c | 260,263,344,392,188,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2850 | Heap-based buffer overflow in the iscsi_add_notunderstood_response function in drivers/target/iscsi/iscsi_target_parameters.c in the iSCSI target subsystem in the Linux kernel through 3.9.4 allows remote attackers to cause a denial of service (memory corruption and OOPS) or possibly execute arbitrary code via a long ke... | https://nvd.nist.gov/vuln/detail/CVE-2013-2850 |
1,020 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 1 | static int rtnl_fill_ifinfo(struct sk_buff *skb, struct net_device *dev,
int type, u32 pid, u32 seq, u32 change,
unsigned int flags, u32 ext_filter_mask)
{
struct ifinfomsg *ifm;
struct nlmsghdr *nlh;
struct rtnl_link_stats64 temp;
const struct rtnl_link_stats64 *stats;
struct nlattr *attr, *af_spec;... | 305,591,951,297,307,640,000,000,000,000,000,000,000 | rtnetlink.c | 128,134,176,972,809,380,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
158,825 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | static int rtnl_fill_ifinfo(struct sk_buff *skb, struct net_device *dev,
int type, u32 pid, u32 seq, u32 change,
unsigned int flags, u32 ext_filter_mask)
{
struct ifinfomsg *ifm;
struct nlmsghdr *nlh;
struct rtnl_link_stats64 temp;
const struct rtnl_link_stats64 *stats;
struct nlattr *attr, *af_spec;... | 304,373,100,592,328,530,000,000,000,000,000,000,000 | rtnetlink.c | 84,143,673,137,336,160,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
1,022 | linux | fc9bbca8f650e5f738af8806317c0a041a48ae4a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fc9bbca8f650e5f738af8806317c0a041a48ae4a | vm: convert fb_mmap to vm_iomap_memory() helper
This is my example conversion of a few existing mmap users. The
fb_mmap() case is a good example because it is a bit more complicated
than some: fb_mmap() mmaps one of two different memory areas depending
on the page offset of the mmap (but happily there is never any mi... | 1 | fb_mmap(struct file *file, struct vm_area_struct * vma)
{
struct fb_info *info = file_fb_info(file);
struct fb_ops *fb;
unsigned long off;
unsigned long start;
u32 len;
if (!info)
return -ENODEV;
if (vma->vm_pgoff > (~0UL >> PAGE_SHIFT))
return -EINVAL;
off = vma->vm_pgoff << PAGE_SHIFT;
fb = inf... | 61,607,845,425,516,360,000,000,000,000,000,000,000 | fbmem.c | 127,339,374,413,477,720,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2596 | Integer overflow in the fb_mmap function in drivers/video/fbmem.c in the Linux kernel before 3.8.9, as used in a certain Motorola build of Android 4.1.2 and other products, allows local users to create a read-write memory mapping for the entirety of kernel memory, and consequently gain privileges, via crafted /dev/grap... | https://nvd.nist.gov/vuln/detail/CVE-2013-2596 |
158,827 | linux | fc9bbca8f650e5f738af8806317c0a041a48ae4a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fc9bbca8f650e5f738af8806317c0a041a48ae4a | vm: convert fb_mmap to vm_iomap_memory() helper
This is my example conversion of a few existing mmap users. The
fb_mmap() case is a good example because it is a bit more complicated
than some: fb_mmap() mmaps one of two different memory areas depending
on the page offset of the mmap (but happily there is never any mi... | 0 | fb_mmap(struct file *file, struct vm_area_struct * vma)
{
struct fb_info *info = file_fb_info(file);
struct fb_ops *fb;
unsigned long mmio_pgoff;
unsigned long start;
u32 len;
if (!info)
return -ENODEV;
fb = info->fbops;
if (!fb)
return -ENODEV;
mutex_lock(&info->mm_lock);
if (fb->fb_mmap) {
... | 280,378,351,628,973,440,000,000,000,000,000,000,000 | fbmem.c | 332,990,640,300,605,980,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2596 | Integer overflow in the fb_mmap function in drivers/video/fbmem.c in the Linux kernel before 3.8.9, as used in a certain Motorola build of Android 4.1.2 and other products, allows local users to create a read-write memory mapping for the entirety of kernel memory, and consequently gain privileges, via crafted /dev/grap... | https://nvd.nist.gov/vuln/detail/CVE-2013-2596 |
1,030 | linux | 9a5467bf7b6e9e02ec9c3da4e23747c05faeaac6 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9a5467bf7b6e9e02ec9c3da4e23747c05faeaac6 | crypto: user - fix info leaks in report API
Three errors resulting in kernel memory disclosure:
1/ The structures used for the netlink based crypto algorithm report API
are located on the stack. As snprintf() does not fill the remainder of
the buffer with null bytes, those stack bytes will be disclosed to users
of th... | 1 | static int crypto_report_one(struct crypto_alg *alg,
struct crypto_user_alg *ualg, struct sk_buff *skb)
{
memcpy(&ualg->cru_name, &alg->cra_name, sizeof(ualg->cru_name));
memcpy(&ualg->cru_driver_name, &alg->cra_driver_name,
sizeof(ualg->cru_driver_name));
memcpy(&ualg->cru_module_name, module_nam... | 20,209,587,001,997,520,000,000,000,000,000,000,000 | crypto_user.c | 164,121,594,634,091,500,000,000,000,000,000,000,000 | [
"CWE-310"
] | CVE-2013-2546 | The report API in the crypto user configuration API in the Linux kernel through 3.8.2 uses an incorrect C library function for copying strings, which allows local users to obtain sensitive information from kernel stack memory by leveraging the CAP_NET_ADMIN capability. | https://nvd.nist.gov/vuln/detail/CVE-2013-2546 |
158,835 | linux | 9a5467bf7b6e9e02ec9c3da4e23747c05faeaac6 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9a5467bf7b6e9e02ec9c3da4e23747c05faeaac6 | crypto: user - fix info leaks in report API
Three errors resulting in kernel memory disclosure:
1/ The structures used for the netlink based crypto algorithm report API
are located on the stack. As snprintf() does not fill the remainder of
the buffer with null bytes, those stack bytes will be disclosed to users
of th... | 0 | static int crypto_report_one(struct crypto_alg *alg,
struct crypto_user_alg *ualg, struct sk_buff *skb)
{
strncpy(ualg->cru_name, alg->cra_name, sizeof(ualg->cru_name));
strncpy(ualg->cru_driver_name, alg->cra_driver_name,
sizeof(ualg->cru_driver_name));
strncpy(ualg->cru_module_name, module_name(alg->c... | 125,221,564,629,112,530,000,000,000,000,000,000,000 | crypto_user.c | 217,854,877,621,692,400,000,000,000,000,000,000,000 | [
"CWE-310"
] | CVE-2013-2546 | The report API in the crypto user configuration API in the Linux kernel through 3.8.2 uses an incorrect C library function for copying strings, which allows local users to obtain sensitive information from kernel stack memory by leveraging the CAP_NET_ADMIN capability. | https://nvd.nist.gov/vuln/detail/CVE-2013-2546 |
1,040 | curl | 192c4f788d48f82c03e9cef40013f34370e90737 | https://github.com/curl/curl | https://github.com/bagder/curl/commit/192c4f788d48f82c03e9cef40013f34370e90737 | Curl_urldecode: no peeking beyond end of input buffer
Security problem: CVE-2013-2174
If a program would give a string like "%FF" to curl_easy_unescape() but
ask for it to decode only the first byte, it would still parse and
decode the full hex sequence. The function then not only read beyond the
allowed buffer but i... | 1 | CURLcode Curl_urldecode(struct SessionHandle *data,
const char *string, size_t length,
char **ostring, size_t *olen,
bool reject_ctrl)
{
size_t alloc = (length?length:strlen(string))+1;
char *ns = malloc(alloc);
unsigned char in;
size_t str... | 85,709,973,777,579,240,000,000,000,000,000,000,000 | escape.c | 170,290,579,417,472,230,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2174 | Heap-based buffer overflow in the curl_easy_unescape function in lib/escape.c in cURL and libcurl 7.7 through 7.30.0 allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted string ending in a "%" (percent) character. | https://nvd.nist.gov/vuln/detail/CVE-2013-2174 |
158,839 | curl | 192c4f788d48f82c03e9cef40013f34370e90737 | https://github.com/curl/curl | https://github.com/bagder/curl/commit/192c4f788d48f82c03e9cef40013f34370e90737 | Curl_urldecode: no peeking beyond end of input buffer
Security problem: CVE-2013-2174
If a program would give a string like "%FF" to curl_easy_unescape() but
ask for it to decode only the first byte, it would still parse and
decode the full hex sequence. The function then not only read beyond the
allowed buffer but i... | 0 | CURLcode Curl_urldecode(struct SessionHandle *data,
const char *string, size_t length,
char **ostring, size_t *olen,
bool reject_ctrl)
{
size_t alloc = (length?length:strlen(string))+1;
char *ns = malloc(alloc);
unsigned char in;
size_t str... | 261,717,292,064,389,370,000,000,000,000,000,000,000 | escape.c | 33,651,401,652,734,190,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2174 | Heap-based buffer overflow in the curl_easy_unescape function in lib/escape.c in cURL and libcurl 7.7 through 7.30.0 allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted string ending in a "%" (percent) character. | https://nvd.nist.gov/vuln/detail/CVE-2013-2174 |
1,041 | linux | b9e146d8eb3b9ecae5086d373b50fa0c1f3e7f0f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b9e146d8eb3b9ecae5086d373b50fa0c1f3e7f0f | kernel/signal.c: stop info leak via the tkill and the tgkill syscalls
This fixes a kernel memory contents leak via the tkill and tgkill syscalls
for compat processes.
This is visible in the siginfo_t->_sifields._rt.si_sigval.sival_ptr field
when handling signals delivered from tkill.
The place of the infoleak:
int ... | 1 | static int do_tkill(pid_t tgid, pid_t pid, int sig)
{
struct siginfo info;
info.si_signo = sig;
info.si_errno = 0;
info.si_code = SI_TKILL;
info.si_pid = task_tgid_vnr(current);
info.si_uid = from_kuid_munged(current_user_ns(), current_uid());
return do_send_specific(tgid, pid, sig, &info);
}
| 92,468,020,625,669,770,000,000,000,000,000,000,000 | signal.c | 50,160,511,605,867,340,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2141 | The do_tkill function in kernel/signal.c in the Linux kernel before 3.8.9 does not initialize a certain data structure, which allows local users to obtain sensitive information from kernel memory via a crafted application that makes a (1) tkill or (2) tgkill system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2141 |
33,146 | linux | b9e146d8eb3b9ecae5086d373b50fa0c1f3e7f0f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b9e146d8eb3b9ecae5086d373b50fa0c1f3e7f0f | kernel/signal.c: stop info leak via the tkill and the tgkill syscalls
This fixes a kernel memory contents leak via the tkill and tgkill syscalls
for compat processes.
This is visible in the siginfo_t->_sifields._rt.si_sigval.sival_ptr field
when handling signals delivered from tkill.
The place of the infoleak:
int ... | 0 | SYSCALL_DEFINE2(kill, pid_t, pid, int, sig)
{
struct siginfo info;
info.si_signo = sig;
info.si_errno = 0;
info.si_code = SI_USER;
info.si_pid = task_tgid_vnr(current);
info.si_uid = from_kuid_munged(current_user_ns(), current_uid());
return kill_something_info(sig, &info, pid);
}
| 137,120,236,693,695,100,000,000,000,000,000,000,000 | signal.c | 43,790,563,659,993,175,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2141 | The do_tkill function in kernel/signal.c in the Linux kernel before 3.8.9 does not initialize a certain data structure, which allows local users to obtain sensitive information from kernel memory via a crafted application that makes a (1) tkill or (2) tgkill system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2141 |
1,042 | linux | 604c499cbbcc3d5fe5fb8d53306aa0fae1990109 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/604c499cbbcc3d5fe5fb8d53306aa0fae1990109 | xen/blkback: Check device permissions before allowing OP_DISCARD
We need to make sure that the device is not RO or that
the request is not past the number of sectors we want to
issue the DISCARD operation for.
This fixes CVE-2013-2140.
Cc: stable@vger.kernel.org
Acked-by: Jan Beulich <JBeulich@suse.com>
Acked-by: Ia... | 1 | static int dispatch_discard_io(struct xen_blkif *blkif,
struct blkif_request *req)
{
int err = 0;
int status = BLKIF_RSP_OKAY;
struct block_device *bdev = blkif->vbd.bdev;
unsigned long secure;
blkif->st_ds_req++;
xen_blkif_get(blkif);
secure = (blkif->vbd.discard_secure &&
(req->u.discard.flag &... | 326,182,960,843,920,000,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2013-2140 | The dispatch_discard_io function in drivers/block/xen-blkback/blkback.c in the Xen blkback implementation in the Linux kernel before 3.10.5 allows guest OS users to cause a denial of service (data loss) via filesystem write operations on a read-only disk that supports the (1) BLKIF_OP_DISCARD (aka discard or TRIM) or (... | https://nvd.nist.gov/vuln/detail/CVE-2013-2140 |
158,840 | linux | 604c499cbbcc3d5fe5fb8d53306aa0fae1990109 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/604c499cbbcc3d5fe5fb8d53306aa0fae1990109 | xen/blkback: Check device permissions before allowing OP_DISCARD
We need to make sure that the device is not RO or that
the request is not past the number of sectors we want to
issue the DISCARD operation for.
This fixes CVE-2013-2140.
Cc: stable@vger.kernel.org
Acked-by: Jan Beulich <JBeulich@suse.com>
Acked-by: Ia... | 0 | static int dispatch_discard_io(struct xen_blkif *blkif,
struct blkif_request *req)
{
int err = 0;
int status = BLKIF_RSP_OKAY;
struct block_device *bdev = blkif->vbd.bdev;
unsigned long secure;
struct phys_req preq;
preq.sector_number = req->u.discard.sector_number;
preq.nr_sects = req->u.discard.nr... | 334,984,300,099,464,330,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2013-2140 | The dispatch_discard_io function in drivers/block/xen-blkback/blkback.c in the Xen blkback implementation in the Linux kernel before 3.10.5 allows guest OS users to cause a denial of service (data loss) via filesystem write operations on a read-only disk that supports the (1) BLKIF_OP_DISCARD (aka discard or TRIM) or (... | https://nvd.nist.gov/vuln/detail/CVE-2013-2140 |
1,043 | linux | baff42ab1494528907bf4d5870359e31711746ae | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/baff42ab1494528907bf4d5870359e31711746ae | net: Fix oops from tcp_collapse() when using splice()
tcp_read_sock() can have a eat skbs without immediately advancing copied_seq.
This can cause a panic in tcp_collapse() if it is called as a result
of the recv_actor dropping the socket lock.
A userspace program that splices data from a socket to either another
soc... | 1 | int tcp_read_sock(struct sock *sk, read_descriptor_t *desc,
sk_read_actor_t recv_actor)
{
struct sk_buff *skb;
struct tcp_sock *tp = tcp_sk(sk);
u32 seq = tp->copied_seq;
u32 offset;
int copied = 0;
if (sk->sk_state == TCP_LISTEN)
return -ENOTCONN;
while ((skb = tcp_recv_skb(sk, seq, &offset)) != NULL) {
... | 199,403,613,559,602,620,000,000,000,000,000,000,000 | tcp.c | 12,402,514,951,805,328,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2128 | The tcp_read_sock function in net/ipv4/tcp.c in the Linux kernel before 2.6.34 does not properly manage skb consumption, which allows local users to cause a denial of service (system crash) via a crafted splice system call for a TCP socket. | https://nvd.nist.gov/vuln/detail/CVE-2013-2128 |
158,841 | linux | baff42ab1494528907bf4d5870359e31711746ae | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/baff42ab1494528907bf4d5870359e31711746ae | net: Fix oops from tcp_collapse() when using splice()
tcp_read_sock() can have a eat skbs without immediately advancing copied_seq.
This can cause a panic in tcp_collapse() if it is called as a result
of the recv_actor dropping the socket lock.
A userspace program that splices data from a socket to either another
soc... | 0 | int tcp_read_sock(struct sock *sk, read_descriptor_t *desc,
sk_read_actor_t recv_actor)
{
struct sk_buff *skb;
struct tcp_sock *tp = tcp_sk(sk);
u32 seq = tp->copied_seq;
u32 offset;
int copied = 0;
if (sk->sk_state == TCP_LISTEN)
return -ENOTCONN;
while ((skb = tcp_recv_skb(sk, seq, &offset)) != NULL) {
... | 67,110,211,699,949,060,000,000,000,000,000,000,000 | tcp.c | 163,710,130,416,565,710,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2128 | The tcp_read_sock function in net/ipv4/tcp.c in the Linux kernel before 2.6.34 does not properly manage skb consumption, which allows local users to cause a denial of service (system crash) via a crafted splice system call for a TCP socket. | https://nvd.nist.gov/vuln/detail/CVE-2013-2128 |
1,044 | openvpn | 11d21349a4e7e38a025849479b36ace7c2eec2ee | https://github.com/OpenVPN/openvpn | https://github.com/OpenVPN/openvpn/commit/11d21349a4e7e38a025849479b36ace7c2eec2ee | Use constant time memcmp when comparing HMACs in openvpn_decrypt.
Signed-off-by: Steffan Karger <steffan.karger@fox-it.com>
Acked-by: Gert Doering <gert@greenie.muc.de>
Signed-off-by: Gert Doering <gert@greenie.muc.de> | 1 | openvpn_decrypt (struct buffer *buf, struct buffer work,
const struct crypto_options *opt,
const struct frame* frame)
{
static const char error_prefix[] = "Authenticate/Decrypt packet error";
struct gc_arena gc;
gc_init (&gc);
if (buf->len > 0 && opt->key_ctx_bi)
{
struct key_ctx *ctx = &opt->k... | 289,938,016,318,508,460,000,000,000,000,000,000,000 | crypto.c | 243,766,420,768,321,600,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-2061 | The openvpn_decrypt function in crypto.c in OpenVPN 2.3.0 and earlier, when running in UDP mode, allows remote attackers to obtain sensitive information via a timing attack involving an HMAC comparison function that does not run in constant time and a padding oracle attack on the CBC mode cipher. | https://nvd.nist.gov/vuln/detail/CVE-2013-2061 |
158,842 | openvpn | 11d21349a4e7e38a025849479b36ace7c2eec2ee | https://github.com/OpenVPN/openvpn | https://github.com/OpenVPN/openvpn/commit/11d21349a4e7e38a025849479b36ace7c2eec2ee | Use constant time memcmp when comparing HMACs in openvpn_decrypt.
Signed-off-by: Steffan Karger <steffan.karger@fox-it.com>
Acked-by: Gert Doering <gert@greenie.muc.de>
Signed-off-by: Gert Doering <gert@greenie.muc.de> | 0 | openvpn_decrypt (struct buffer *buf, struct buffer work,
const struct crypto_options *opt,
const struct frame* frame)
{
static const char error_prefix[] = "Authenticate/Decrypt packet error";
struct gc_arena gc;
gc_init (&gc);
if (buf->len > 0 && opt->key_ctx_bi)
{
struct key_ctx *ctx = &opt->k... | 266,680,031,659,370,050,000,000,000,000,000,000,000 | crypto.c | 289,311,636,969,505,400,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-2061 | The openvpn_decrypt function in crypto.c in OpenVPN 2.3.0 and earlier, when running in UDP mode, allows remote attackers to obtain sensitive information via a timing attack involving an HMAC comparison function that does not run in constant time and a padding oracle attack on the CBC mode cipher. | https://nvd.nist.gov/vuln/detail/CVE-2013-2061 |
1,045 | linux | 929473ea05db455ad88cdc081f2adc556b8dc48f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/929473ea05db455ad88cdc081f2adc556b8dc48f | usb: chipidea: Allow disabling streaming not only in udc mode
When running a scp transfer using a USB/Ethernet adapter the following crash
happens:
$ scp test.tar.gz fabio@192.168.1.100:/home/fabio
fabio@192.168.1.100's password:
test.tar.gz 0% 0 0.0KB/s --:-- ETA
-------... | 1 | static int host_start(struct ci13xxx *ci)
{
struct usb_hcd *hcd;
struct ehci_hcd *ehci;
int ret;
if (usb_disabled())
return -ENODEV;
hcd = usb_create_hcd(&ci_ehci_hc_driver, ci->dev, dev_name(ci->dev));
if (!hcd)
return -ENOMEM;
dev_set_drvdata(ci->dev, ci);
hcd->rsrc_start = ci->hw_bank.phys;
hcd->rsrc... | 178,357,202,326,078,400,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2013-2058 | The host_start function in drivers/usb/chipidea/host.c in the Linux kernel before 3.7.4 does not properly support a certain non-streaming option, which allows local users to cause a denial of service (system crash) by sending a large amount of network traffic through a USB/Ethernet adapter. | https://nvd.nist.gov/vuln/detail/CVE-2013-2058 |
158,843 | linux | 929473ea05db455ad88cdc081f2adc556b8dc48f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/929473ea05db455ad88cdc081f2adc556b8dc48f | usb: chipidea: Allow disabling streaming not only in udc mode
When running a scp transfer using a USB/Ethernet adapter the following crash
happens:
$ scp test.tar.gz fabio@192.168.1.100:/home/fabio
fabio@192.168.1.100's password:
test.tar.gz 0% 0 0.0KB/s --:-- ETA
-------... | 0 | static int host_start(struct ci13xxx *ci)
{
struct usb_hcd *hcd;
struct ehci_hcd *ehci;
int ret;
if (usb_disabled())
return -ENODEV;
hcd = usb_create_hcd(&ci_ehci_hc_driver, ci->dev, dev_name(ci->dev));
if (!hcd)
return -ENOMEM;
dev_set_drvdata(ci->dev, ci);
hcd->rsrc_start = ci->hw_bank.phys;
hcd->rsrc... | 202,703,564,392,681,700,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2013-2058 | The host_start function in drivers/usb/chipidea/host.c in the Linux kernel before 3.7.4 does not properly support a certain non-streaming option, which allows local users to cause a denial of service (system crash) by sending a large amount of network traffic through a USB/Ethernet adapter. | https://nvd.nist.gov/vuln/detail/CVE-2013-2058 |
1,047 | linux | 0e9a9a1ad619e7e987815d20262d36a2f95717ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e9a9a1ad619e7e987815d20262d36a2f95717ca | ext4: avoid hang when mounting non-journal filesystems with orphan list
When trying to mount a file system which does not contain a journal,
but which does have a orphan list containing an inode which needs to
be truncated, the mount call with hang forever in
ext4_orphan_cleanup() because ext4_orphan_del() will return... | 1 | int ext4_orphan_del(handle_t *handle, struct inode *inode)
{
struct list_head *prev;
struct ext4_inode_info *ei = EXT4_I(inode);
struct ext4_sb_info *sbi;
__u32 ino_next;
struct ext4_iloc iloc;
int err = 0;
if (!EXT4_SB(inode->i_sb)->s_journal)
return 0;
mutex_lock(&EXT4_SB(inode->i_sb)->s_orphan_lock... | 244,588,647,148,744,640,000,000,000,000,000,000,000 | namei.c | 70,402,644,734,207,050,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2015 | The ext4_orphan_del function in fs/ext4/namei.c in the Linux kernel before 3.7.3 does not properly handle orphan-list entries for non-journal filesystems, which allows physically proximate attackers to cause a denial of service (system hang) via a crafted filesystem on removable media, as demonstrated by the e2fsprogs ... | https://nvd.nist.gov/vuln/detail/CVE-2013-2015 |
158,845 | linux | 0e9a9a1ad619e7e987815d20262d36a2f95717ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e9a9a1ad619e7e987815d20262d36a2f95717ca | ext4: avoid hang when mounting non-journal filesystems with orphan list
When trying to mount a file system which does not contain a journal,
but which does have a orphan list containing an inode which needs to
be truncated, the mount call with hang forever in
ext4_orphan_cleanup() because ext4_orphan_del() will return... | 0 | int ext4_orphan_del(handle_t *handle, struct inode *inode)
{
struct list_head *prev;
struct ext4_inode_info *ei = EXT4_I(inode);
struct ext4_sb_info *sbi;
__u32 ino_next;
struct ext4_iloc iloc;
int err = 0;
if ((!EXT4_SB(inode->i_sb)->s_journal) &&
!(EXT4_SB(inode->i_sb)->s_mount_state & EXT4_ORPHAN_FS)... | 114,208,085,292,493,160,000,000,000,000,000,000,000 | namei.c | 232,123,123,324,503,340,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2015 | The ext4_orphan_del function in fs/ext4/namei.c in the Linux kernel before 3.7.3 does not properly handle orphan-list entries for non-journal filesystems, which allows physically proximate attackers to cause a denial of service (system hang) via a crafted filesystem on removable media, as demonstrated by the e2fsprogs ... | https://nvd.nist.gov/vuln/detail/CVE-2013-2015 |
1,051 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 1 | static struct mount *clone_mnt(struct mount *old, struct dentry *root,
int flag)
{
struct super_block *sb = old->mnt.mnt_sb;
struct mount *mnt;
int err;
mnt = alloc_vfsmnt(old->mnt_devname);
if (!mnt)
return ERR_PTR(-ENOMEM);
if (flag & (CL_SLAVE | CL_PRIVATE | CL_SHARED_TO_SLAVE))
mnt->mnt_group_id = ... | 333,226,396,239,700,840,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
158,847 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static struct mount *clone_mnt(struct mount *old, struct dentry *root,
int flag)
{
struct super_block *sb = old->mnt.mnt_sb;
struct mount *mnt;
int err;
mnt = alloc_vfsmnt(old->mnt_devname);
if (!mnt)
return ERR_PTR(-ENOMEM);
if (flag & (CL_SLAVE | CL_PRIVATE | CL_SHARED_TO_SLAVE))
mnt->mnt_group_id = ... | 145,748,488,629,147,650,000,000,000,000,000,000,000 | namespace.c | 142,988,980,350,645,570,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
1,054 | linux | 3151527ee007b73a0ebd296010f1c0454a919c7d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/3151527ee007b73a0ebd296010f1c0454a919c7d | userns: Don't allow creation if the user is chrooted
Guarantee that the policy of which files may be access that is
established by setting the root directory will not be violated
by user namespaces by verifying that the root directory points
to the root of the mount namespace at the time of user namespace
creation.
... | 1 | int create_user_ns(struct cred *new)
{
struct user_namespace *ns, *parent_ns = new->user_ns;
kuid_t owner = new->euid;
kgid_t group = new->egid;
int ret;
/* The creator needs a mapping in the parent user namespace
* or else we won't be able to reasonably tell userspace who
* created a user_namespace.
... | 62,769,202,323,779,360,000,000,000,000,000,000,000 | user_namespace.c | 60,695,328,771,795,950,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1956 | The create_user_ns function in kernel/user_namespace.c in the Linux kernel before 3.8.6 does not check whether a chroot directory exists that differs from the namespace root directory, which allows local users to bypass intended filesystem restrictions via a crafted clone system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-1956 |
158,850 | linux | 3151527ee007b73a0ebd296010f1c0454a919c7d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/3151527ee007b73a0ebd296010f1c0454a919c7d | userns: Don't allow creation if the user is chrooted
Guarantee that the policy of which files may be access that is
established by setting the root directory will not be violated
by user namespaces by verifying that the root directory points
to the root of the mount namespace at the time of user namespace
creation.
... | 0 | int create_user_ns(struct cred *new)
{
struct user_namespace *ns, *parent_ns = new->user_ns;
kuid_t owner = new->euid;
kgid_t group = new->egid;
int ret;
/*
* Verify that we can not violate the policy of which files
* may be accessed that is specified by the root directory,
* by verifing that the root di... | 239,983,657,945,796,700,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1956 | The create_user_ns function in kernel/user_namespace.c in the Linux kernel before 3.8.6 does not check whether a chroot directory exists that differs from the namespace root directory, which allows local users to bypass intended filesystem restrictions via a crafted clone system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-1956 |
1,056 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 1 | static void tg3_read_vpd(struct tg3 *tp)
{
u8 *vpd_data;
unsigned int block_end, rosize, len;
u32 vpdlen;
int j, i = 0;
vpd_data = (u8 *)tg3_vpd_readblock(tp, &vpdlen);
if (!vpd_data)
goto out_no_vpd;
i = pci_vpd_find_tag(vpd_data, 0, vpdlen, PCI_VPD_LRDT_RO_DATA);
if (i < 0)
goto out_not_found;
rosize ... | 112,924,613,750,397,920,000,000,000,000,000,000,000 | tg3.c | 243,393,128,707,233,270,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
158,853 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 0 | static void tg3_read_vpd(struct tg3 *tp)
{
u8 *vpd_data;
unsigned int block_end, rosize, len;
u32 vpdlen;
int j, i = 0;
vpd_data = (u8 *)tg3_vpd_readblock(tp, &vpdlen);
if (!vpd_data)
goto out_no_vpd;
i = pci_vpd_find_tag(vpd_data, 0, vpdlen, PCI_VPD_LRDT_RO_DATA);
if (i < 0)
goto out_not_found;
rosize ... | 339,368,621,396,240,300,000,000,000,000,000,000,000 | tg3.c | 309,569,115,333,965,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
1,057 | linux | 12176503366885edd542389eed3aaf94be163fdb | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/12176503366885edd542389eed3aaf94be163fdb | fs/compat_ioctl.c: VIDEO_SET_SPU_PALETTE missing error check
The compat ioctl for VIDEO_SET_SPU_PALETTE was missing an error check
while converting ioctl arguments. This could lead to leaking kernel
stack contents into userspace.
Patch extracted from existing fix in grsecurity.
Signed-off-by: Kees Cook <keescook@ch... | 1 | static int do_video_set_spu_palette(unsigned int fd, unsigned int cmd,
struct compat_video_spu_palette __user *up)
{
struct video_spu_palette __user *up_native;
compat_uptr_t palp;
int length, err;
err = get_user(palp, &up->palette);
err |= get_user(length, &up->length);
up_native = compat_alloc_user_sp... | 316,505,203,133,565,640,000,000,000,000,000,000,000 | compat_ioctl.c | 304,637,621,645,556,700,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-1928 | The do_video_set_spu_palette function in fs/compat_ioctl.c in the Linux kernel before 3.6.5 on unspecified architectures lacks a certain error check, which might allow local users to obtain sensitive information from kernel stack memory via a crafted VIDEO_SET_SPU_PALETTE ioctl call on a /dev/dvb device. | https://nvd.nist.gov/vuln/detail/CVE-2013-1928 |
158,854 | linux | 12176503366885edd542389eed3aaf94be163fdb | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/12176503366885edd542389eed3aaf94be163fdb | fs/compat_ioctl.c: VIDEO_SET_SPU_PALETTE missing error check
The compat ioctl for VIDEO_SET_SPU_PALETTE was missing an error check
while converting ioctl arguments. This could lead to leaking kernel
stack contents into userspace.
Patch extracted from existing fix in grsecurity.
Signed-off-by: Kees Cook <keescook@ch... | 0 | static int do_video_set_spu_palette(unsigned int fd, unsigned int cmd,
struct compat_video_spu_palette __user *up)
{
struct video_spu_palette __user *up_native;
compat_uptr_t palp;
int length, err;
err = get_user(palp, &up->palette);
err |= get_user(length, &up->length);
if (err)
return -EFAULT;
up_n... | 276,226,896,291,213,600,000,000,000,000,000,000,000 | compat_ioctl.c | 100,937,621,684,748,480,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-1928 | The do_video_set_spu_palette function in fs/compat_ioctl.c in the Linux kernel before 3.6.5 on unspecified architectures lacks a certain error check, which might allow local users to obtain sensitive information from kernel stack memory via a crafted VIDEO_SET_SPU_PALETTE ioctl call on a /dev/dvb device. | https://nvd.nist.gov/vuln/detail/CVE-2013-1928 |
1,058 | linux | c0f5ecee4e741667b2493c742b60b6218d40b3aa | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c0f5ecee4e741667b2493c742b60b6218d40b3aa | USB: cdc-wdm: fix buffer overflow
The buffer for responses must not overflow.
If this would happen, set a flag, drop the data and return
an error after user space has read all remaining data.
Signed-off-by: Oliver Neukum <oliver@neukum.org>
CC: stable@kernel.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundati... | 1 | static void wdm_in_callback(struct urb *urb)
{
struct wdm_device *desc = urb->context;
int status = urb->status;
spin_lock(&desc->iuspin);
clear_bit(WDM_RESPONDING, &desc->flags);
if (status) {
switch (status) {
case -ENOENT:
dev_dbg(&desc->intf->dev,
"nonzero urb status received: -ENOENT");
... | 263,555,284,317,390,400,000,000,000,000,000,000,000 | cdc-wdm.c | 233,028,530,119,557,450,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1860 | Heap-based buffer overflow in the wdm_in_callback function in drivers/usb/class/cdc-wdm.c in the Linux kernel before 3.8.4 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted cdc-wdm USB device. | https://nvd.nist.gov/vuln/detail/CVE-2013-1860 |
158,855 | linux | c0f5ecee4e741667b2493c742b60b6218d40b3aa | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c0f5ecee4e741667b2493c742b60b6218d40b3aa | USB: cdc-wdm: fix buffer overflow
The buffer for responses must not overflow.
If this would happen, set a flag, drop the data and return
an error after user space has read all remaining data.
Signed-off-by: Oliver Neukum <oliver@neukum.org>
CC: stable@kernel.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundati... | 0 | static void wdm_in_callback(struct urb *urb)
{
struct wdm_device *desc = urb->context;
int status = urb->status;
int length = urb->actual_length;
spin_lock(&desc->iuspin);
clear_bit(WDM_RESPONDING, &desc->flags);
if (status) {
switch (status) {
case -ENOENT:
dev_dbg(&desc->intf->dev,
"nonzero u... | 232,042,914,284,621,120,000,000,000,000,000,000,000 | cdc-wdm.c | 201,237,370,339,956,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1860 | Heap-based buffer overflow in the wdm_in_callback function in drivers/usb/class/cdc-wdm.c in the Linux kernel before 3.8.4 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted cdc-wdm USB device. | https://nvd.nist.gov/vuln/detail/CVE-2013-1860 |
1,065 | linux | 726bc6b092da4c093eb74d13c07184b18c1af0f1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/726bc6b092da4c093eb74d13c07184b18c1af0f1 | net/sctp: Validate parameter size for SCTP_GET_ASSOC_STATS
Building sctp may fail with:
In function ‘copy_from_user’,
inlined from ‘sctp_getsockopt_assoc_stats’ at
net/sctp/socket.c:5656:20:
arch/x86/include/asm/uaccess_32.h:211:26: error: call to
‘copy_from_user_overflow’ declared with attribute error: c... | 1 | static int sctp_getsockopt_assoc_stats(struct sock *sk, int len,
char __user *optval,
int __user *optlen)
{
struct sctp_assoc_stats sas;
struct sctp_association *asoc = NULL;
/* User must provide at least the assoc id */
if (len < sizeof(sctp_assoc_t))
return -EINVAL;
if (copy_from_us... | 170,963,965,115,843,570,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2013-1828 | The sctp_getsockopt_assoc_stats function in net/sctp/socket.c in the Linux kernel before 3.8.4 does not validate a size value before proceeding to a copy_from_user operation, which allows local users to gain privileges via a crafted application that contains an SCTP_GET_ASSOC_STATS getsockopt system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-1828 |
158,861 | linux | 726bc6b092da4c093eb74d13c07184b18c1af0f1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/726bc6b092da4c093eb74d13c07184b18c1af0f1 | net/sctp: Validate parameter size for SCTP_GET_ASSOC_STATS
Building sctp may fail with:
In function ‘copy_from_user’,
inlined from ‘sctp_getsockopt_assoc_stats’ at
net/sctp/socket.c:5656:20:
arch/x86/include/asm/uaccess_32.h:211:26: error: call to
‘copy_from_user_overflow’ declared with attribute error: c... | 0 | static int sctp_getsockopt_assoc_stats(struct sock *sk, int len,
char __user *optval,
int __user *optlen)
{
struct sctp_assoc_stats sas;
struct sctp_association *asoc = NULL;
/* User must provide at least the assoc id */
if (len < sizeof(sctp_assoc_t))
return -EINVAL;
/* Allow the stru... | 318,691,377,843,228,440,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2013-1828 | The sctp_getsockopt_assoc_stats function in net/sctp/socket.c in the Linux kernel before 3.8.4 does not validate a size value before proceeding to a copy_from_user operation, which allows local users to gain privileges via a crafted application that contains an SCTP_GET_ASSOC_STATS getsockopt system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-1828 |
1,066 | linux | 864745d291b5ba80ea0bd0edcbe67273de368836 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/864745d291b5ba80ea0bd0edcbe67273de368836 | xfrm_user: return error pointer instead of NULL
When dump_one_state() returns an error, e.g. because of a too small
buffer to dump the whole xfrm state, xfrm_state_netlink() returns NULL
instead of an error pointer. But its callers expect an error pointer
and therefore continue to operate on a NULL skbuff.
This could... | 1 | static struct sk_buff *xfrm_state_netlink(struct sk_buff *in_skb,
struct xfrm_state *x, u32 seq)
{
struct xfrm_dump_info info;
struct sk_buff *skb;
skb = nlmsg_new(NLMSG_DEFAULT_SIZE, GFP_ATOMIC);
if (!skb)
return ERR_PTR(-ENOMEM);
info.in_skb = in_skb;
info.out_skb = skb;
info.nlmsg_seq = seq;... | 324,377,055,092,562,550,000,000,000,000,000,000,000 | xfrm_user.c | 252,384,883,337,736,730,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2013-1826 | The xfrm_state_netlink function in net/xfrm/xfrm_user.c in the Linux kernel before 3.5.7 does not properly handle error conditions in dump_one_state function calls, which allows local users to gain privileges or cause a denial of service (NULL pointer dereference and system crash) by leveraging the CAP_NET_ADMIN capabi... | https://nvd.nist.gov/vuln/detail/CVE-2013-1826 |
34,398 | linux | 864745d291b5ba80ea0bd0edcbe67273de368836 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/864745d291b5ba80ea0bd0edcbe67273de368836 | xfrm_user: return error pointer instead of NULL
When dump_one_state() returns an error, e.g. because of a too small
buffer to dump the whole xfrm state, xfrm_state_netlink() returns NULL
instead of an error pointer. But its callers expect an error pointer
and therefore continue to operate on a NULL skbuff.
This could... | 0 | static struct sk_buff *xfrm_policy_netlink(struct sk_buff *in_skb,
struct xfrm_policy *xp,
int dir, u32 seq)
{
struct xfrm_dump_info info;
struct sk_buff *skb;
skb = nlmsg_new(NLMSG_DEFAULT_SIZE, GFP_KERNEL);
if (!skb)
return ERR_PTR(-ENOMEM);
info.in_skb = in_skb;
info.out_skb = skb;
info.nlms... | 104,687,477,009,612,440,000,000,000,000,000,000,000 | xfrm_user.c | 146,233,539,701,132,340,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2013-1826 | The xfrm_state_netlink function in net/xfrm/xfrm_user.c in the Linux kernel before 3.5.7 does not properly handle error conditions in dump_one_state function calls, which allows local users to gain privileges or cause a denial of service (NULL pointer dereference and system crash) by leveraging the CAP_NET_ADMIN capabi... | https://nvd.nist.gov/vuln/detail/CVE-2013-1826 |
1,067 | linux | eb178619f930fa2ba2348de332a1ff1c66a31424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/eb178619f930fa2ba2348de332a1ff1c66a31424 | xfs: fix _xfs_buf_find oops on blocks beyond the filesystem end
When _xfs_buf_find is passed an out of range address, it will fail
to find a relevant struct xfs_perag and oops with a null
dereference. This can happen when trying to walk a filesystem with a
metadata inode that has a partially corrupted extent map (i.e.... | 1 | _xfs_buf_find(
struct xfs_buftarg *btp,
struct xfs_buf_map *map,
int nmaps,
xfs_buf_flags_t flags,
xfs_buf_t *new_bp)
{
size_t numbytes;
struct xfs_perag *pag;
struct rb_node **rbp;
struct rb_node *parent;
xfs_buf_t *bp;
xfs_daddr_t blkno = map[0].bm_bn;
int numblks = 0;
int i;
for (i... | 91,424,937,264,814,560,000,000,000,000,000,000,000 | xfs_buf.c | 137,283,063,241,069,840,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-1819 | The _xfs_buf_find function in fs/xfs/xfs_buf.c in the Linux kernel before 3.7.6 does not validate block numbers, which allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact by leveraging the ability to mount an XFS filesystem containing a m... | https://nvd.nist.gov/vuln/detail/CVE-2013-1819 |
158,862 | linux | eb178619f930fa2ba2348de332a1ff1c66a31424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/eb178619f930fa2ba2348de332a1ff1c66a31424 | xfs: fix _xfs_buf_find oops on blocks beyond the filesystem end
When _xfs_buf_find is passed an out of range address, it will fail
to find a relevant struct xfs_perag and oops with a null
dereference. This can happen when trying to walk a filesystem with a
metadata inode that has a partially corrupted extent map (i.e.... | 0 | _xfs_buf_find(
struct xfs_buftarg *btp,
struct xfs_buf_map *map,
int nmaps,
xfs_buf_flags_t flags,
xfs_buf_t *new_bp)
{
size_t numbytes;
struct xfs_perag *pag;
struct rb_node **rbp;
struct rb_node *parent;
xfs_buf_t *bp;
xfs_daddr_t blkno = map[0].bm_bn;
xfs_daddr_t eofs;
int numblks = 0;
... | 325,044,590,263,845,660,000,000,000,000,000,000,000 | xfs_buf.c | 281,802,917,585,970,800,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-1819 | The _xfs_buf_find function in fs/xfs/xfs_buf.c in the Linux kernel before 3.7.6 does not validate block numbers, which allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact by leveraging the ability to mount an XFS filesystem containing a m... | https://nvd.nist.gov/vuln/detail/CVE-2013-1819 |
1,075 | linux | 1ee0a224bc9aad1de496c795f96bc6ba2c394811 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1ee0a224bc9aad1de496c795f96bc6ba2c394811 | USB: io_ti: Fix NULL dereference in chase_port()
The tty is NULL when the port is hanging up.
chase_port() needs to check for this.
This patch is intended for stable series.
The behavior was observed and tested in Linux 3.2 and 3.7.1.
Johan Hovold submitted a more elaborate patch for the mainline kernel.
[ 56.277... | 1 | static void chase_port(struct edgeport_port *port, unsigned long timeout,
int flush)
{
int baud_rate;
struct tty_struct *tty = tty_port_tty_get(&port->port->port);
struct usb_serial *serial = port->port->serial;
wait_queue_t wait;
unsigned long flags;
if (!timeout)
timeout = (HZ * EDGE_CLOSING_WAI... | 45,678,875,671,616,350,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2013-1774 | The chase_port function in drivers/usb/serial/io_ti.c in the Linux kernel before 3.7.4 allows local users to cause a denial of service (NULL pointer dereference and system crash) via an attempted /dev/ttyUSB read or write operation on a disconnected Edgeport USB serial converter. | https://nvd.nist.gov/vuln/detail/CVE-2013-1774 |
158,866 | linux | 1ee0a224bc9aad1de496c795f96bc6ba2c394811 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1ee0a224bc9aad1de496c795f96bc6ba2c394811 | USB: io_ti: Fix NULL dereference in chase_port()
The tty is NULL when the port is hanging up.
chase_port() needs to check for this.
This patch is intended for stable series.
The behavior was observed and tested in Linux 3.2 and 3.7.1.
Johan Hovold submitted a more elaborate patch for the mainline kernel.
[ 56.277... | 0 | static void chase_port(struct edgeport_port *port, unsigned long timeout,
int flush)
{
int baud_rate;
struct tty_struct *tty = tty_port_tty_get(&port->port->port);
struct usb_serial *serial = port->port->serial;
wait_queue_t wait;
unsigned long flags;
if (!tty)
return;
if (!timeout)
timeout = ... | 209,364,999,674,560,930,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2013-1774 | The chase_port function in drivers/usb/serial/io_ti.c in the Linux kernel before 3.7.4 allows local users to cause a denial of service (NULL pointer dereference and system crash) via an attempted /dev/ttyUSB read or write operation on a disconnected Edgeport USB serial converter. | https://nvd.nist.gov/vuln/detail/CVE-2013-1774 |
1,079 | linux | ce0030c00f95cf9110d9cdcd41e901e1fb814417 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ce0030c00f95cf9110d9cdcd41e901e1fb814417 | None | 1 | static void call_console_drivers(unsigned start, unsigned end)
{
unsigned cur_index, start_print;
static int msg_level = -1;
BUG_ON(((int)(start - end)) > 0);
cur_index = start;
start_print = start;
while (cur_index != end) {
if (msg_level < 0 && ((end - cur_index) > 2)) {
/* strip log prefix */
cur... | 150,497,347,424,301,980,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2013-1772 | The log_prefix function in kernel/printk.c in the Linux kernel 3.x before 3.4.33 does not properly remove a prefix string from a syslog header, which allows local users to cause a denial of service (buffer overflow and system crash) by leveraging /dev/kmsg write access and triggering a call_console_drivers function cal... | https://nvd.nist.gov/vuln/detail/CVE-2013-1772 |
158,870 | linux | ce0030c00f95cf9110d9cdcd41e901e1fb814417 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ce0030c00f95cf9110d9cdcd41e901e1fb814417 | None | 0 | static void call_console_drivers(unsigned start, unsigned end)
{
unsigned cur_index, start_print;
static int msg_level = -1;
BUG_ON(((int)(start - end)) > 0);
cur_index = start;
start_print = start;
while (cur_index != end) {
if (msg_level < 0 && ((end - cur_index) > 2)) {
/*
* prepare buf_prefix, a... | 278,336,960,793,883,450,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2013-1772 | The log_prefix function in kernel/printk.c in the Linux kernel 3.x before 3.4.33 does not properly remove a prefix string from a syslog header, which allows local users to cause a denial of service (buffer overflow and system crash) by leveraging /dev/kmsg write access and triggering a call_console_drivers function cal... | https://nvd.nist.gov/vuln/detail/CVE-2013-1772 |
1,080 | tinc | 17a33dfd95b1a29e90db76414eb9622df9632320 | https://github.com/gsliepen/tinc | https://github.com/gsliepen/tinc/commit/17a33dfd95b1a29e90db76414eb9622df9632320 | Drop packets forwarded via TCP if they are too big (CVE-2013-1428).
Normally all requests sent via the meta connections are checked so that they
cannot be larger than the input buffer. However, when packets are forwarded via
meta connections, they are copied into a packet buffer without checking whether
it fits into i... | 1 | void receive_tcppacket(connection_t *c, const char *buffer, int len) {
vpn_packet_t outpkt;
outpkt.len = len;
if(c->options & OPTION_TCPONLY)
outpkt.priority = 0;
else
outpkt.priority = -1;
memcpy(outpkt.data, buffer, len);
receive_packet(c->node, &outpkt);
}
| 130,046,906,967,549,600,000,000,000,000,000,000,000 | net_packet.c | 8,171,485,538,728,046,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1428 | Stack-based buffer overflow in the receive_tcppacket function in net_packet.c in tinc before 1.0.21 and 1.1 before 1.1pre7 allows remote authenticated peers to cause a denial of service (crash) or possibly execute arbitrary code via a large TCP packet. | https://nvd.nist.gov/vuln/detail/CVE-2013-1428 |
158,871 | tinc | 17a33dfd95b1a29e90db76414eb9622df9632320 | https://github.com/gsliepen/tinc | https://github.com/gsliepen/tinc/commit/17a33dfd95b1a29e90db76414eb9622df9632320 | Drop packets forwarded via TCP if they are too big (CVE-2013-1428).
Normally all requests sent via the meta connections are checked so that they
cannot be larger than the input buffer. However, when packets are forwarded via
meta connections, they are copied into a packet buffer without checking whether
it fits into i... | 0 | void receive_tcppacket(connection_t *c, const char *buffer, int len) {
vpn_packet_t outpkt;
if(len > sizeof outpkt.data)
return;
outpkt.len = len;
if(c->options & OPTION_TCPONLY)
outpkt.priority = 0;
else
outpkt.priority = -1;
memcpy(outpkt.data, buffer, len);
receive_packet(c->node, &outpkt);
}
| 237,645,872,547,157,030,000,000,000,000,000,000,000 | net_packet.c | 84,979,222,404,728,470,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1428 | Stack-based buffer overflow in the receive_tcppacket function in net_packet.c in tinc before 1.0.21 and 1.1 before 1.1pre7 allows remote authenticated peers to cause a denial of service (crash) or possibly execute arbitrary code via a large TCP packet. | https://nvd.nist.gov/vuln/detail/CVE-2013-1428 |
1,083 | krb5 | 8ee70ec63931d1e38567905387ab9b1d45734d81 | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/8ee70ec63931d1e38567905387ab9b1d45734d81 | KDC TGS-REQ null deref [CVE-2013-1416]
By sending an unusual but valid TGS-REQ, an authenticated remote
attacker can cause the KDC process to crash by dereferencing a null
pointer.
prep_reprocess_req() can cause a null pointer dereference when
processing a service principal name. Code in this function can
inappropri... | 1 | prep_reprocess_req(krb5_kdc_req *request, krb5_principal *krbtgt_princ)
{
krb5_error_code retval = KRB5KRB_AP_ERR_BADMATCH;
char **realms, **cpp, *temp_buf=NULL;
krb5_data *comp1 = NULL, *comp2 = NULL;
char *comp1_str = NULL;
/* By now we know that server principal name is unknown.
* If CANONI... | 26,445,768,461,799,657,000,000,000,000,000,000,000 | do_tgs_req.c | 132,430,812,994,884,870,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1416 | The prep_reprocess_req function in do_tgs_req.c in the Key Distribution Center (KDC) in MIT Kerberos 5 (aka krb5) before 1.10.5 does not properly perform service-principal realm referral, which allows remote authenticated users to cause a denial of service (NULL pointer dereference and daemon crash) via a crafted TGS-R... | https://nvd.nist.gov/vuln/detail/CVE-2013-1416 |
158,873 | krb5 | 8ee70ec63931d1e38567905387ab9b1d45734d81 | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/8ee70ec63931d1e38567905387ab9b1d45734d81 | KDC TGS-REQ null deref [CVE-2013-1416]
By sending an unusual but valid TGS-REQ, an authenticated remote
attacker can cause the KDC process to crash by dereferencing a null
pointer.
prep_reprocess_req() can cause a null pointer dereference when
processing a service principal name. Code in this function can
inappropri... | 0 | prep_reprocess_req(krb5_kdc_req *request, krb5_principal *krbtgt_princ)
{
krb5_error_code retval = KRB5KRB_AP_ERR_BADMATCH;
char **realms, **cpp, *temp_buf=NULL;
krb5_data *comp1 = NULL, *comp2 = NULL;
char *comp1_str = NULL;
/* By now we know that server principal name is unknown.
* If CANONI... | 167,732,044,059,211,620,000,000,000,000,000,000,000 | do_tgs_req.c | 69,088,724,082,177,510,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1416 | The prep_reprocess_req function in do_tgs_req.c in the Key Distribution Center (KDC) in MIT Kerberos 5 (aka krb5) before 1.10.5 does not properly perform service-principal realm referral, which allows remote authenticated users to cause a denial of service (NULL pointer dereference and daemon crash) via a crafted TGS-R... | https://nvd.nist.gov/vuln/detail/CVE-2013-1416 |
1,084 | krb5 | f249555301940c6df3a2cdda13b56b5674eebc2e | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/f249555301940c6df3a2cdda13b56b5674eebc2e | PKINIT null pointer deref [CVE-2013-1415]
Don't dereference a null pointer when cleaning up.
The KDC plugin for PKINIT can dereference a null pointer when a
malformed packet causes processing to terminate early, leading to
a crash of the KDC process. An attacker would need to have a valid
PKINIT certificate or have ... | 1 | pkinit_check_kdc_pkid(krb5_context context,
pkinit_plg_crypto_context plg_cryptoctx,
pkinit_req_crypto_context req_cryptoctx,
pkinit_identity_crypto_context id_cryptoctx,
unsigned char *pdid_buf,
unsigned int p... | 113,776,654,271,026,500,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2013-1415 | The pkinit_check_kdc_pkid function in plugins/preauth/pkinit/pkinit_crypto_openssl.c in the PKINIT implementation in the Key Distribution Center (KDC) in MIT Kerberos 5 (aka krb5) before 1.10.4 and 1.11.x before 1.11.1 does not properly handle errors during extraction of fields from an X.509 certificate, which allows r... | https://nvd.nist.gov/vuln/detail/CVE-2013-1415 |
158,874 | krb5 | f249555301940c6df3a2cdda13b56b5674eebc2e | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/f249555301940c6df3a2cdda13b56b5674eebc2e | PKINIT null pointer deref [CVE-2013-1415]
Don't dereference a null pointer when cleaning up.
The KDC plugin for PKINIT can dereference a null pointer when a
malformed packet causes processing to terminate early, leading to
a crash of the KDC process. An attacker would need to have a valid
PKINIT certificate or have ... | 0 | pkinit_check_kdc_pkid(krb5_context context,
pkinit_plg_crypto_context plg_cryptoctx,
pkinit_req_crypto_context req_cryptoctx,
pkinit_identity_crypto_context id_cryptoctx,
unsigned char *pdid_buf,
unsigned int p... | 143,213,392,633,765,950,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2013-1415 | The pkinit_check_kdc_pkid function in plugins/preauth/pkinit/pkinit_crypto_openssl.c in the PKINIT implementation in the Key Distribution Center (KDC) in MIT Kerberos 5 (aka krb5) before 1.10.4 and 1.11.x before 1.11.1 does not properly handle errors during extraction of fields from an X.509 certificate, which allows r... | https://nvd.nist.gov/vuln/detail/CVE-2013-1415 |
1,085 | linux | 2ca39528c01a933f6689cd6505ce65bd6d68a530 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2ca39528c01a933f6689cd6505ce65bd6d68a530 | signal: always clear sa_restorer on execve
When the new signal handlers are set up, the location of sa_restorer is
not cleared, leaking a parent process's address space location to
children. This allows for a potential bypass of the parent's ASLR by
examining the sa_restorer value returned when calling sigaction().
... | 1 | flush_signal_handlers(struct task_struct *t, int force_default)
{
int i;
struct k_sigaction *ka = &t->sighand->action[0];
for (i = _NSIG ; i != 0 ; i--) {
if (force_default || ka->sa.sa_handler != SIG_IGN)
ka->sa.sa_handler = SIG_DFL;
ka->sa.sa_flags = 0;
sigemptyset(&ka->sa.sa_mask);
ka++;
}
}
| 300,076,951,675,769,600,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2013-0914 | The flush_signal_handlers function in kernel/signal.c in the Linux kernel before 3.8.4 preserves the value of the sa_restorer field across an exec operation, which makes it easier for local users to bypass the ASLR protection mechanism via a crafted application containing a sigaction system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-0914 |
158,875 | linux | 2ca39528c01a933f6689cd6505ce65bd6d68a530 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2ca39528c01a933f6689cd6505ce65bd6d68a530 | signal: always clear sa_restorer on execve
When the new signal handlers are set up, the location of sa_restorer is
not cleared, leaking a parent process's address space location to
children. This allows for a potential bypass of the parent's ASLR by
examining the sa_restorer value returned when calling sigaction().
... | 0 | flush_signal_handlers(struct task_struct *t, int force_default)
{
int i;
struct k_sigaction *ka = &t->sighand->action[0];
for (i = _NSIG ; i != 0 ; i--) {
if (force_default || ka->sa.sa_handler != SIG_IGN)
ka->sa.sa_handler = SIG_DFL;
ka->sa.sa_flags = 0;
#ifdef SA_RESTORER
ka->sa.sa_restorer = NULL;
#en... | 130,092,903,275,859,960,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2013-0914 | The flush_signal_handlers function in kernel/signal.c in the Linux kernel before 3.8.4 preserves the value of the sa_restorer field across an exec operation, which makes it easier for local users to bypass the ASLR protection mechanism via a crafted application containing a sigaction system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-0914 |
1,089 | linux | 0a9ab9bdb3e891762553f667066190c1d22ad62b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0a9ab9bdb3e891762553f667066190c1d22ad62b | Bluetooth: Fix incorrect strncpy() in hidp_setup_hid()
The length parameter should be sizeof(req->name) - 1 because there is no
guarantee that string provided by userspace will contain the trailing
'\0'.
Can be easily reproduced by manually setting req->name to 128 non-zero
bytes prior to ioctl(HIDPCONNADD) and check... | 1 | static int hidp_setup_hid(struct hidp_session *session,
struct hidp_connadd_req *req)
{
struct hid_device *hid;
int err;
session->rd_data = kzalloc(req->rd_size, GFP_KERNEL);
if (!session->rd_data)
return -ENOMEM;
if (copy_from_user(session->rd_data, req->rd_data, req->rd_size)) {
err = -EFAULT;
goto f... | 293,512,902,537,004,240,000,000,000,000,000,000,000 | core.c | 327,221,048,127,945,550,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-0349 | The hidp_setup_hid function in net/bluetooth/hidp/core.c in the Linux kernel before 3.7.6 does not properly copy a certain name field, which allows local users to obtain sensitive information from kernel memory by setting a long name and making an HIDPCONNADD ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2013-0349 |
158,877 | linux | 0a9ab9bdb3e891762553f667066190c1d22ad62b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0a9ab9bdb3e891762553f667066190c1d22ad62b | Bluetooth: Fix incorrect strncpy() in hidp_setup_hid()
The length parameter should be sizeof(req->name) - 1 because there is no
guarantee that string provided by userspace will contain the trailing
'\0'.
Can be easily reproduced by manually setting req->name to 128 non-zero
bytes prior to ioctl(HIDPCONNADD) and check... | 0 | static int hidp_setup_hid(struct hidp_session *session,
struct hidp_connadd_req *req)
{
struct hid_device *hid;
int err;
session->rd_data = kzalloc(req->rd_size, GFP_KERNEL);
if (!session->rd_data)
return -ENOMEM;
if (copy_from_user(session->rd_data, req->rd_data, req->rd_size)) {
err = -EFAULT;
goto f... | 64,688,095,993,032,210,000,000,000,000,000,000,000 | core.c | 300,142,110,910,201,880,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-0349 | The hidp_setup_hid function in net/bluetooth/hidp/core.c in the Linux kernel before 3.7.6 does not properly copy a certain name field, which allows local users to obtain sensitive information from kernel memory by setting a long name and making an HIDPCONNADD ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2013-0349 |
1,090 | linux | a67adb997419fb53540d4a4f79c6471c60bc69b6 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a67adb997419fb53540d4a4f79c6471c60bc69b6 | evm: checking if removexattr is not a NULL
The following lines of code produce a kernel oops.
fd = socket(PF_FILE, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0);
fchmod(fd, 0666);
[ 139.922364] BUG: unable to handle kernel NULL pointer dereference at (null)
[ 139.924982] IP: [< (null)>] (null)
[ 139.924982] *pd... | 1 | int evm_update_evmxattr(struct dentry *dentry, const char *xattr_name,
const char *xattr_value, size_t xattr_value_len)
{
struct inode *inode = dentry->d_inode;
struct evm_ima_xattr_data xattr_data;
int rc = 0;
rc = evm_calc_hmac(dentry, xattr_name, xattr_value,
xattr_value_len, xattr_data.digest);
if (r... | 305,997,047,583,974,500,000,000,000,000,000,000,000 | evm_crypto.c | 98,288,434,782,980,370,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2013-0313 | The evm_update_evmxattr function in security/integrity/evm/evm_crypto.c in the Linux kernel before 3.7.5, when the Extended Verification Module (EVM) is enabled, allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via an attempted removex... | https://nvd.nist.gov/vuln/detail/CVE-2013-0313 |
158,878 | linux | a67adb997419fb53540d4a4f79c6471c60bc69b6 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a67adb997419fb53540d4a4f79c6471c60bc69b6 | evm: checking if removexattr is not a NULL
The following lines of code produce a kernel oops.
fd = socket(PF_FILE, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0);
fchmod(fd, 0666);
[ 139.922364] BUG: unable to handle kernel NULL pointer dereference at (null)
[ 139.924982] IP: [< (null)>] (null)
[ 139.924982] *pd... | 0 | int evm_update_evmxattr(struct dentry *dentry, const char *xattr_name,
const char *xattr_value, size_t xattr_value_len)
{
struct inode *inode = dentry->d_inode;
struct evm_ima_xattr_data xattr_data;
int rc = 0;
rc = evm_calc_hmac(dentry, xattr_name, xattr_value,
xattr_value_len, xattr_data.digest);
if (r... | 183,523,284,803,485,700,000,000,000,000,000,000,000 | evm_crypto.c | 8,120,758,867,011,354,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2013-0313 | The evm_update_evmxattr function in security/integrity/evm/evm_crypto.c in the Linux kernel before 3.7.5, when the Extended Verification Module (EVM) is enabled, allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via an attempted removex... | https://nvd.nist.gov/vuln/detail/CVE-2013-0313 |
1,092 | linux | 89d7ae34cdda4195809a5a987f697a517a2a3177 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/89d7ae34cdda4195809a5a987f697a517a2a3177 | cipso: don't follow a NULL pointer when setsockopt() is called
As reported by Alan Cox, and verified by Lin Ming, when a user
attempts to add a CIPSO option to a socket using the CIPSO_V4_TAG_LOCAL
tag the kernel dies a terrible death when it attempts to follow a NULL
pointer (the skb argument to cipso_v4_validate() i... | 1 | int cipso_v4_validate(const struct sk_buff *skb, unsigned char **option)
{
unsigned char *opt = *option;
unsigned char *tag;
unsigned char opt_iter;
unsigned char err_offset = 0;
u8 opt_len;
u8 tag_len;
struct cipso_v4_doi *doi_def = NULL;
u32 tag_iter;
/* caller already checks for length values that are too ... | 254,520,361,513,953,370,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2013-0310 | The cipso_v4_validate function in net/ipv4/cipso_ipv4.c in the Linux kernel before 3.4.8 allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via an IPOPT_CIPSO IP_OPTIONS setsockopt system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-0310 |
158,880 | linux | 89d7ae34cdda4195809a5a987f697a517a2a3177 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/89d7ae34cdda4195809a5a987f697a517a2a3177 | cipso: don't follow a NULL pointer when setsockopt() is called
As reported by Alan Cox, and verified by Lin Ming, when a user
attempts to add a CIPSO option to a socket using the CIPSO_V4_TAG_LOCAL
tag the kernel dies a terrible death when it attempts to follow a NULL
pointer (the skb argument to cipso_v4_validate() i... | 0 | int cipso_v4_validate(const struct sk_buff *skb, unsigned char **option)
{
unsigned char *opt = *option;
unsigned char *tag;
unsigned char opt_iter;
unsigned char err_offset = 0;
u8 opt_len;
u8 tag_len;
struct cipso_v4_doi *doi_def = NULL;
u32 tag_iter;
/* caller already checks for length values that are too ... | 203,090,929,831,454,360,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2013-0310 | The cipso_v4_validate function in net/ipv4/cipso_ipv4.c in the Linux kernel before 3.4.8 allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via an IPOPT_CIPSO IP_OPTIONS setsockopt system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-0310 |
1,093 | linux | 77c1090f94d1b0b5186fb13a1b71b47b1343f87f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/77c1090f94d1b0b5186fb13a1b71b47b1343f87f | net: fix infinite loop in __skb_recv_datagram()
Tommi was fuzzing with trinity and reported the following problem :
commit 3f518bf745 (datagram: Add offset argument to __skb_recv_datagram)
missed that a raw socket receive queue can contain skbs with no payload.
We can loop in __skb_recv_datagram() with MSG_PEEK mode... | 1 | struct sk_buff *__skb_recv_datagram(struct sock *sk, unsigned int flags,
int *peeked, int *off, int *err)
{
struct sk_buff *skb;
long timeo;
/*
* Caller is allowed not to check sk->sk_err before skb_recv_datagram()
*/
int error = sock_error(sk);
if (error)
goto no_packet;
timeo = sock_rcvtimeo(sk,... | 89,456,193,869,845,560,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2013-0290 | The __skb_recv_datagram function in net/core/datagram.c in the Linux kernel before 3.8 does not properly handle the MSG_PEEK flag with zero-length data, which allows local users to cause a denial of service (infinite loop and system hang) via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-0290 |
158,881 | linux | 77c1090f94d1b0b5186fb13a1b71b47b1343f87f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/77c1090f94d1b0b5186fb13a1b71b47b1343f87f | net: fix infinite loop in __skb_recv_datagram()
Tommi was fuzzing with trinity and reported the following problem :
commit 3f518bf745 (datagram: Add offset argument to __skb_recv_datagram)
missed that a raw socket receive queue can contain skbs with no payload.
We can loop in __skb_recv_datagram() with MSG_PEEK mode... | 0 | struct sk_buff *__skb_recv_datagram(struct sock *sk, unsigned int flags,
int *peeked, int *off, int *err)
{
struct sk_buff *skb;
long timeo;
/*
* Caller is allowed not to check sk->sk_err before skb_recv_datagram()
*/
int error = sock_error(sk);
if (error)
goto no_packet;
timeo = sock_rcvtimeo(sk,... | 143,881,527,320,364,330,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2013-0290 | The __skb_recv_datagram function in net/core/datagram.c in the Linux kernel before 3.8 does not properly handle the MSG_PEEK flag with zero-length data, which allows local users to cause a denial of service (infinite loop and system hang) via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-0290 |
1,115 | linux | c903f0456bc69176912dee6dd25c6a66ee1aed00 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c903f0456bc69176912dee6dd25c6a66ee1aed00 | x86/msr: Add capabilities check
At the moment the MSR driver only relies upon file system
checks. This means that anything as root with any capability set
can write to MSRs. Historically that wasn't very interesting but
on modern processors the MSRs are such that writing to them
provides several ways to execute arbita... | 1 | static int msr_open(struct inode *inode, struct file *file)
{
unsigned int cpu;
struct cpuinfo_x86 *c;
cpu = iminor(file->f_path.dentry->d_inode);
if (cpu >= nr_cpu_ids || !cpu_online(cpu))
return -ENXIO; /* No such CPU */
c = &cpu_data(cpu);
if (!cpu_has(c, X86_FEATURE_MSR))
return -EIO; /* MSR not s... | 134,954,684,690,763,780,000,000,000,000,000,000,000 | msr.c | 286,103,807,502,299,130,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-0268 | The msr_open function in arch/x86/kernel/msr.c in the Linux kernel before 3.7.6 allows local users to bypass intended capability restrictions by executing a crafted application as root, as demonstrated by msr32.c. | https://nvd.nist.gov/vuln/detail/CVE-2013-0268 |
158,902 | linux | c903f0456bc69176912dee6dd25c6a66ee1aed00 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c903f0456bc69176912dee6dd25c6a66ee1aed00 | x86/msr: Add capabilities check
At the moment the MSR driver only relies upon file system
checks. This means that anything as root with any capability set
can write to MSRs. Historically that wasn't very interesting but
on modern processors the MSRs are such that writing to them
provides several ways to execute arbita... | 0 | static int msr_open(struct inode *inode, struct file *file)
{
unsigned int cpu;
struct cpuinfo_x86 *c;
if (!capable(CAP_SYS_RAWIO))
return -EPERM;
cpu = iminor(file->f_path.dentry->d_inode);
if (cpu >= nr_cpu_ids || !cpu_online(cpu))
return -ENXIO; /* No such CPU */
c = &cpu_data(cpu);
if (!cpu_has(... | 97,547,137,240,082,430,000,000,000,000,000,000,000 | msr.c | 202,214,703,476,074,400,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-0268 | The msr_open function in arch/x86/kernel/msr.c in the Linux kernel before 3.7.6 allows local users to bypass intended capability restrictions by executing a crafted application as root, as demonstrated by msr32.c. | https://nvd.nist.gov/vuln/detail/CVE-2013-0268 |
1,123 | libarchive | 22531545514043e04633e1c015c7540b9de9dbe4 | https://github.com/libarchive/libarchive | https://github.com/libarchive/libarchive/commit/22531545514043e04633e1c015c7540b9de9dbe4 | Limit write requests to at most INT_MAX.
This prevents a certain common programming error (passing -1 to write)
from leading to other problems deeper in the library. | 1 | _archive_write_data(struct archive *_a, const void *buff, size_t s)
{
struct archive_write *a = (struct archive_write *)_a;
archive_check_magic(&a->archive, ARCHIVE_WRITE_MAGIC,
ARCHIVE_STATE_DATA, "archive_write_data");
archive_clear_error(&a->archive);
return ((a->format_write_data)(a, buff, s));
}
| 130,653,882,621,145,300,000,000,000,000,000,000,000 | archive_write.c | 270,035,346,370,556,250,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-0211 | Integer signedness error in the archive_write_zip_data function in archive_write_set_format_zip.c in libarchive 3.1.2 and earlier, when running on 64-bit machines, allows context-dependent attackers to cause a denial of service (crash) via unspecified vectors, which triggers an improper conversion between unsigned and ... | https://nvd.nist.gov/vuln/detail/CVE-2013-0211 |
158,907 | libarchive | 22531545514043e04633e1c015c7540b9de9dbe4 | https://github.com/libarchive/libarchive | https://github.com/libarchive/libarchive/commit/22531545514043e04633e1c015c7540b9de9dbe4 | Limit write requests to at most INT_MAX.
This prevents a certain common programming error (passing -1 to write)
from leading to other problems deeper in the library. | 0 | _archive_write_data(struct archive *_a, const void *buff, size_t s)
{
struct archive_write *a = (struct archive_write *)_a;
const size_t max_write = INT_MAX;
archive_check_magic(&a->archive, ARCHIVE_WRITE_MAGIC,
ARCHIVE_STATE_DATA, "archive_write_data");
/* In particular, this catches attempts to pass ne... | 280,395,881,836,362,560,000,000,000,000,000,000,000 | archive_write.c | 173,125,723,841,928,230,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-0211 | Integer signedness error in the archive_write_zip_data function in archive_write_set_format_zip.c in libarchive 3.1.2 and earlier, when running on 64-bit machines, allows context-dependent attackers to cause a denial of service (crash) via unspecified vectors, which triggers an improper conversion between unsigned and ... | https://nvd.nist.gov/vuln/detail/CVE-2013-0211 |
1,124 | linux | fe685aabf7c8c9f138e5ea900954d295bf229175 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fe685aabf7c8c9f138e5ea900954d295bf229175 | isofs: avoid info leak on export
For type 1 the parent_offset member in struct isofs_fid gets copied
uninitialized to userland. Fix this by initializing it to 0.
Signed-off-by: Mathias Krause <minipli@googlemail.com>
Signed-off-by: Jan Kara <jack@suse.cz> | 1 | isofs_export_encode_fh(struct inode *inode,
__u32 *fh32,
int *max_len,
struct inode *parent)
{
struct iso_inode_info * ei = ISOFS_I(inode);
int len = *max_len;
int type = 1;
__u16 *fh16 = (__u16*)fh32;
/*
* WARNING: max_len is 5 for NFSv2. Because of this
* limitation, we use the l... | 175,765,004,232,940,700,000,000,000,000,000,000,000 | None | null | [
"CWE-200"
] | CVE-2012-6549 | The isofs_export_encode_fh function in fs/isofs/export.c in the Linux kernel before 3.6 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel heap memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2012-6549 |
158,908 | linux | fe685aabf7c8c9f138e5ea900954d295bf229175 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fe685aabf7c8c9f138e5ea900954d295bf229175 | isofs: avoid info leak on export
For type 1 the parent_offset member in struct isofs_fid gets copied
uninitialized to userland. Fix this by initializing it to 0.
Signed-off-by: Mathias Krause <minipli@googlemail.com>
Signed-off-by: Jan Kara <jack@suse.cz> | 0 | isofs_export_encode_fh(struct inode *inode,
__u32 *fh32,
int *max_len,
struct inode *parent)
{
struct iso_inode_info * ei = ISOFS_I(inode);
int len = *max_len;
int type = 1;
__u16 *fh16 = (__u16*)fh32;
/*
* WARNING: max_len is 5 for NFSv2. Because of this
* limitation, we use the l... | 320,978,724,258,404,660,000,000,000,000,000,000,000 | None | null | [
"CWE-200"
] | CVE-2012-6549 | The isofs_export_encode_fh function in fs/isofs/export.c in the Linux kernel before 3.6 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel heap memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2012-6549 |
1,125 | linux | 0143fc5e9f6f5aad4764801015bc8d4b4a278200 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0143fc5e9f6f5aad4764801015bc8d4b4a278200 | udf: avoid info leak on export
For type 0x51 the udf.parent_partref member in struct fid gets copied
uninitialized to userland. Fix this by initializing it to 0.
Signed-off-by: Mathias Krause <minipli@googlemail.com>
Signed-off-by: Jan Kara <jack@suse.cz> | 1 | static int udf_encode_fh(struct inode *inode, __u32 *fh, int *lenp,
struct inode *parent)
{
int len = *lenp;
struct kernel_lb_addr location = UDF_I(inode)->i_location;
struct fid *fid = (struct fid *)fh;
int type = FILEID_UDF_WITHOUT_PARENT;
if (parent && (len < 5)) {
*lenp = 5;
return 255;
} else if (le... | 271,056,274,363,302,500,000,000,000,000,000,000,000 | namei.c | 30,071,079,208,846,090,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2012-6548 | The udf_encode_fh function in fs/udf/namei.c in the Linux kernel before 3.6 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel heap memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2012-6548 |
158,909 | linux | 0143fc5e9f6f5aad4764801015bc8d4b4a278200 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0143fc5e9f6f5aad4764801015bc8d4b4a278200 | udf: avoid info leak on export
For type 0x51 the udf.parent_partref member in struct fid gets copied
uninitialized to userland. Fix this by initializing it to 0.
Signed-off-by: Mathias Krause <minipli@googlemail.com>
Signed-off-by: Jan Kara <jack@suse.cz> | 0 | static int udf_encode_fh(struct inode *inode, __u32 *fh, int *lenp,
struct inode *parent)
{
int len = *lenp;
struct kernel_lb_addr location = UDF_I(inode)->i_location;
struct fid *fid = (struct fid *)fh;
int type = FILEID_UDF_WITHOUT_PARENT;
if (parent && (len < 5)) {
*lenp = 5;
return 255;
} else if (le... | 244,619,496,587,582,150,000,000,000,000,000,000,000 | namei.c | 333,614,401,961,029,570,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2012-6548 | The udf_encode_fh function in fs/udf/namei.c in the Linux kernel before 3.6 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel heap memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2012-6548 |
1,126 | linux | a117dacde0288f3ec60b6e5bcedae8fa37ee0dfc | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a117dacde0288f3ec60b6e5bcedae8fa37ee0dfc | net/tun: fix ioctl() based info leaks
The tun module leaks up to 36 bytes of memory by not fully initializing
a structure located on the stack that gets copied to user memory by the
TUNGETIFF and SIOCGIFHWADDR ioctl()s.
Signed-off-by: Mathias Krause <minipli@googlemail.com>
Signed-off-by: David S. Miller <davem@davem... | 1 | static long __tun_chr_ioctl(struct file *file, unsigned int cmd,
unsigned long arg, int ifreq_len)
{
struct tun_file *tfile = file->private_data;
struct tun_struct *tun;
void __user* argp = (void __user*)arg;
struct sock_fprog fprog;
struct ifreq ifr;
int sndbuf;
int vnet_hdr_sz;
int ret;
if (cmd ==... | 35,869,627,182,032,717,000,000,000,000,000,000,000 | tun.c | 266,233,870,309,545,600,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2012-6547 | The __tun_chr_ioctl function in drivers/net/tun.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-6547 |
158,910 | linux | a117dacde0288f3ec60b6e5bcedae8fa37ee0dfc | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a117dacde0288f3ec60b6e5bcedae8fa37ee0dfc | net/tun: fix ioctl() based info leaks
The tun module leaks up to 36 bytes of memory by not fully initializing
a structure located on the stack that gets copied to user memory by the
TUNGETIFF and SIOCGIFHWADDR ioctl()s.
Signed-off-by: Mathias Krause <minipli@googlemail.com>
Signed-off-by: David S. Miller <davem@davem... | 0 | static long __tun_chr_ioctl(struct file *file, unsigned int cmd,
unsigned long arg, int ifreq_len)
{
struct tun_file *tfile = file->private_data;
struct tun_struct *tun;
void __user* argp = (void __user*)arg;
struct sock_fprog fprog;
struct ifreq ifr;
int sndbuf;
int vnet_hdr_sz;
int ret;
if (cmd ==... | 9,362,178,505,815,067,000,000,000,000,000,000,000 | None | null | [
"CWE-200"
] | CVE-2012-6547 | The __tun_chr_ioctl function in drivers/net/tun.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-6547 |
1,132 | linux | 7b07f8eb75aa3097cdfd4f6eac3da49db787381d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7b07f8eb75aa3097cdfd4f6eac3da49db787381d | dccp: fix info leak via getsockopt(DCCP_SOCKOPT_CCID_TX_INFO)
The CCID3 code fails to initialize the trailing padding bytes of struct
tfrc_tx_info added for alignment on 64 bit architectures. It that for
potentially leaks four bytes kernel stack via the getsockopt() syscall.
Add an explicit memset(0) before filling th... | 1 | static int ccid3_hc_tx_getsockopt(struct sock *sk, const int optname, int len,
u32 __user *optval, int __user *optlen)
{
const struct ccid3_hc_tx_sock *hc = ccid3_hc_tx_sk(sk);
struct tfrc_tx_info tfrc;
const void *val;
switch (optname) {
case DCCP_SOCKOPT_CCID_TX_INFO:
if (len < sizeof(tfrc))
retur... | 8,536,137,024,975,475,000,000,000,000,000,000,000 | ccid3.c | 160,351,560,622,096,350,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2012-6541 | The ccid3_hc_tx_getsockopt function in net/dccp/ccids/ccid3.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-6541 |
158,911 | linux | 7b07f8eb75aa3097cdfd4f6eac3da49db787381d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7b07f8eb75aa3097cdfd4f6eac3da49db787381d | dccp: fix info leak via getsockopt(DCCP_SOCKOPT_CCID_TX_INFO)
The CCID3 code fails to initialize the trailing padding bytes of struct
tfrc_tx_info added for alignment on 64 bit architectures. It that for
potentially leaks four bytes kernel stack via the getsockopt() syscall.
Add an explicit memset(0) before filling th... | 0 | static int ccid3_hc_tx_getsockopt(struct sock *sk, const int optname, int len,
u32 __user *optval, int __user *optlen)
{
const struct ccid3_hc_tx_sock *hc = ccid3_hc_tx_sk(sk);
struct tfrc_tx_info tfrc;
const void *val;
switch (optname) {
case DCCP_SOCKOPT_CCID_TX_INFO:
if (len < sizeof(tfrc))
retur... | 316,593,226,478,784,700,000,000,000,000,000,000,000 | ccid3.c | 100,687,945,022,576,240,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2012-6541 | The ccid3_hc_tx_getsockopt function in net/dccp/ccids/ccid3.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-6541 |
1,133 | linux | 2d8a041b7bfe1097af21441cb77d6af95f4f4680 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2d8a041b7bfe1097af21441cb77d6af95f4f4680 | ipvs: fix info leak in getsockopt(IP_VS_SO_GET_TIMEOUT)
If at least one of CONFIG_IP_VS_PROTO_TCP or CONFIG_IP_VS_PROTO_UDP is
not set, __ip_vs_get_timeouts() does not fully initialize the structure
that gets copied to userland and that for leaks up to 12 bytes of kernel
stack. Add an explicit memset(0) before passing... | 1 | do_ip_vs_get_ctl(struct sock *sk, int cmd, void __user *user, int *len)
{
unsigned char arg[128];
int ret = 0;
unsigned int copylen;
struct net *net = sock_net(sk);
struct netns_ipvs *ipvs = net_ipvs(net);
BUG_ON(!net);
if (!capable(CAP_NET_ADMIN))
return -EPERM;
if (cmd < IP_VS_BASE_CTL || cmd > IP_VS_SO_G... | 267,941,661,112,975,060,000,000,000,000,000,000,000 | ip_vs_ctl.c | 289,258,931,771,187,420,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2012-6540 | The do_ip_vs_get_ctl function in net/netfilter/ipvs/ip_vs_ctl.c in the Linux kernel before 3.6 does not initialize a certain structure for IP_VS_SO_GET_TIMEOUT commands, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2012-6540 |
158,912 | linux | 2d8a041b7bfe1097af21441cb77d6af95f4f4680 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2d8a041b7bfe1097af21441cb77d6af95f4f4680 | ipvs: fix info leak in getsockopt(IP_VS_SO_GET_TIMEOUT)
If at least one of CONFIG_IP_VS_PROTO_TCP or CONFIG_IP_VS_PROTO_UDP is
not set, __ip_vs_get_timeouts() does not fully initialize the structure
that gets copied to userland and that for leaks up to 12 bytes of kernel
stack. Add an explicit memset(0) before passing... | 0 | do_ip_vs_get_ctl(struct sock *sk, int cmd, void __user *user, int *len)
{
unsigned char arg[128];
int ret = 0;
unsigned int copylen;
struct net *net = sock_net(sk);
struct netns_ipvs *ipvs = net_ipvs(net);
BUG_ON(!net);
if (!capable(CAP_NET_ADMIN))
return -EPERM;
if (cmd < IP_VS_BASE_CTL || cmd > IP_VS_SO_G... | 276,892,604,779,127,200,000,000,000,000,000,000,000 | ip_vs_ctl.c | 198,232,056,816,623,300,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2012-6540 | The do_ip_vs_get_ctl function in net/netfilter/ipvs/ip_vs_ctl.c in the Linux kernel before 3.6 does not initialize a certain structure for IP_VS_SO_GET_TIMEOUT commands, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2012-6540 |
1,134 | linux | f778a636713a435d3a922c60b1622a91136560c1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f778a636713a435d3a922c60b1622a91136560c1 | xfrm_user: fix info leak in copy_to_user_state()
The memory reserved to dump the xfrm state includes the padding bytes of
struct xfrm_usersa_info added by the compiler for alignment (7 for
amd64, 3 for i386). Add an explicit memset(0) before filling the buffer
to avoid the info leak.
Signed-off-by: Mathias Krause <mi... | 1 | static void copy_to_user_state(struct xfrm_state *x, struct xfrm_usersa_info *p)
{
memcpy(&p->id, &x->id, sizeof(p->id));
memcpy(&p->sel, &x->sel, sizeof(p->sel));
memcpy(&p->lft, &x->lft, sizeof(p->lft));
memcpy(&p->curlft, &x->curlft, sizeof(p->curlft));
memcpy(&p->stats, &x->stats, sizeof(p->stats));
memc... | 144,112,786,017,541,910,000,000,000,000,000,000,000 | xfrm_user.c | 38,362,585,315,635,697,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2012-6537 | net/xfrm/xfrm_user.c in the Linux kernel before 3.6 does not initialize certain structures, which allows local users to obtain sensitive information from kernel memory by leveraging the CAP_NET_ADMIN capability. | https://nvd.nist.gov/vuln/detail/CVE-2012-6537 |
158,913 | linux | f778a636713a435d3a922c60b1622a91136560c1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f778a636713a435d3a922c60b1622a91136560c1 | xfrm_user: fix info leak in copy_to_user_state()
The memory reserved to dump the xfrm state includes the padding bytes of
struct xfrm_usersa_info added by the compiler for alignment (7 for
amd64, 3 for i386). Add an explicit memset(0) before filling the buffer
to avoid the info leak.
Signed-off-by: Mathias Krause <mi... | 0 | static void copy_to_user_state(struct xfrm_state *x, struct xfrm_usersa_info *p)
{
memset(p, 0, sizeof(*p));
memcpy(&p->id, &x->id, sizeof(p->id));
memcpy(&p->sel, &x->sel, sizeof(p->sel));
memcpy(&p->lft, &x->lft, sizeof(p->lft));
memcpy(&p->curlft, &x->curlft, sizeof(p->curlft));
memcpy(&p->stats, &x->stat... | 36,744,037,473,184,592,000,000,000,000,000,000,000 | xfrm_user.c | 86,195,625,117,642,060,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2012-6537 | net/xfrm/xfrm_user.c in the Linux kernel before 3.6 does not initialize certain structures, which allows local users to obtain sensitive information from kernel memory by leveraging the CAP_NET_ADMIN capability. | https://nvd.nist.gov/vuln/detail/CVE-2012-6537 |
1,142 | linux | b66c5984017533316fd1951770302649baf1aa33 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b66c5984017533316fd1951770302649baf1aa33 | exec: do not leave bprm->interp on stack
If a series of scripts are executed, each triggering module loading via
unprintable bytes in the script header, kernel stack contents can leak
into the command line.
Normally execution of binfmt_script and binfmt_misc happens recursively.
However, when modules are enabled, and... | 1 | static int load_script(struct linux_binprm *bprm)
{
const char *i_arg, *i_name;
char *cp;
struct file *file;
char interp[BINPRM_BUF_SIZE];
int retval;
if ((bprm->buf[0] != '#') || (bprm->buf[1] != '!'))
return -ENOEXEC;
/*
* This section does the #! interpretation.
* Sorta complicated, but hopefully it wi... | 328,383,916,190,717,060,000,000,000,000,000,000,000 | None | null | [
"CWE-200"
] | CVE-2012-4530 | The load_script function in fs/binfmt_script.c in the Linux kernel before 3.7.2 does not properly handle recursion, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2012-4530 |
158,920 | linux | b66c5984017533316fd1951770302649baf1aa33 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b66c5984017533316fd1951770302649baf1aa33 | exec: do not leave bprm->interp on stack
If a series of scripts are executed, each triggering module loading via
unprintable bytes in the script header, kernel stack contents can leak
into the command line.
Normally execution of binfmt_script and binfmt_misc happens recursively.
However, when modules are enabled, and... | 0 | static int load_script(struct linux_binprm *bprm)
{
const char *i_arg, *i_name;
char *cp;
struct file *file;
char interp[BINPRM_BUF_SIZE];
int retval;
if ((bprm->buf[0] != '#') || (bprm->buf[1] != '!'))
return -ENOEXEC;
/*
* This section does the #! interpretation.
* Sorta complicated, but hopefully it wi... | 214,694,254,699,035,900,000,000,000,000,000,000,000 | None | null | [
"CWE-200"
] | CVE-2012-4530 | The load_script function in fs/binfmt_script.c in the Linux kernel before 3.7.2 does not properly handle recursion, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2012-4530 |
1,150 | krb5 | db64ca25d661a47b996b4e2645998b5d7f0eb52c | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/db64ca25d661a47b996b4e2645998b5d7f0eb52c | PKINIT (draft9) null ptr deref [CVE-2012-1016]
Don't check for an agility KDF identifier in the non-draft9 reply
structure when we're building a draft9 reply, because it'll be NULL.
The KDC plugin for PKINIT can dereference a null pointer when handling
a draft9 request, leading to a crash of the KDC process. An atta... | 1 | pkinit_server_return_padata(krb5_context context,
krb5_pa_data * padata,
krb5_data *req_pkt,
krb5_kdc_req * request,
krb5_kdc_rep * reply,
krb5_keyblock * encrypting_key,
... | 76,503,992,088,312,030,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2012-1016 | The pkinit_server_return_padata function in plugins/preauth/pkinit/pkinit_srv.c in the PKINIT implementation in the Key Distribution Center (KDC) in MIT Kerberos 5 (aka krb5) before 1.10.4 attempts to find an agility KDF identifier in inappropriate circumstances, which allows remote attackers to cause a denial of servi... | https://nvd.nist.gov/vuln/detail/CVE-2012-1016 |
158,927 | krb5 | db64ca25d661a47b996b4e2645998b5d7f0eb52c | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/db64ca25d661a47b996b4e2645998b5d7f0eb52c | PKINIT (draft9) null ptr deref [CVE-2012-1016]
Don't check for an agility KDF identifier in the non-draft9 reply
structure when we're building a draft9 reply, because it'll be NULL.
The KDC plugin for PKINIT can dereference a null pointer when handling
a draft9 request, leading to a crash of the KDC process. An atta... | 0 | pkinit_server_return_padata(krb5_context context,
krb5_pa_data * padata,
krb5_data *req_pkt,
krb5_kdc_req * request,
krb5_kdc_rep * reply,
krb5_keyblock * encrypting_key,
... | 254,088,971,941,613,450,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2012-1016 | The pkinit_server_return_padata function in plugins/preauth/pkinit/pkinit_srv.c in the PKINIT implementation in the Key Distribution Center (KDC) in MIT Kerberos 5 (aka krb5) before 1.10.4 attempts to find an agility KDF identifier in inappropriate circumstances, which allows remote attackers to cause a denial of servi... | https://nvd.nist.gov/vuln/detail/CVE-2012-1016 |
1,151 | linux | b5a1eeef04cc7859f34dec9b72ea1b28e4aba07c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b5a1eeef04cc7859f34dec9b72ea1b28e4aba07c | batman-adv: Only write requested number of byte to user buffer
Don't write more than the requested number of bytes of an batman-adv icmp
packet to the userspace buffer. Otherwise unrelated userspace memory might get
overridden by the kernel.
Signed-off-by: Sven Eckelmann <sven@narfation.org>
Signed-off-by: Marek Lind... | 1 | static ssize_t bat_socket_read(struct file *file, char __user *buf,
size_t count, loff_t *ppos)
{
struct socket_client *socket_client = file->private_data;
struct socket_packet *socket_packet;
size_t packet_len;
int error;
if ((file->f_flags & O_NONBLOCK) && (socket_client->queue_len == 0))
return -EA... | 85,869,577,016,758,350,000,000,000,000,000,000,000 | icmp_socket.c | 220,335,110,825,043,840,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4604 | The bat_socket_read function in net/batman-adv/icmp_socket.c in the Linux kernel before 3.3 allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via a crafted batman-adv ICMP packet. | https://nvd.nist.gov/vuln/detail/CVE-2011-4604 |
158,928 | linux | b5a1eeef04cc7859f34dec9b72ea1b28e4aba07c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b5a1eeef04cc7859f34dec9b72ea1b28e4aba07c | batman-adv: Only write requested number of byte to user buffer
Don't write more than the requested number of bytes of an batman-adv icmp
packet to the userspace buffer. Otherwise unrelated userspace memory might get
overridden by the kernel.
Signed-off-by: Sven Eckelmann <sven@narfation.org>
Signed-off-by: Marek Lind... | 0 | static ssize_t bat_socket_read(struct file *file, char __user *buf,
size_t count, loff_t *ppos)
{
struct socket_client *socket_client = file->private_data;
struct socket_packet *socket_packet;
size_t packet_len;
int error;
if ((file->f_flags & O_NONBLOCK) && (socket_client->queue_len == 0))
return -EA... | 146,563,344,002,856,950,000,000,000,000,000,000,000 | icmp_socket.c | 218,189,560,527,124,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4604 | The bat_socket_read function in net/batman-adv/icmp_socket.c in the Linux kernel before 3.3 allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via a crafted batman-adv ICMP packet. | https://nvd.nist.gov/vuln/detail/CVE-2011-4604 |
1,152 | linux | ae53b5bd77719fed58086c5be60ce4f22bffe1c6 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ae53b5bd77719fed58086c5be60ce4f22bffe1c6 | sctp: Fix another socket race during accept/peeloff
There is a race between sctp_rcv() and sctp_accept() where we
have moved the association from the listening socket to the
accepted socket, but sctp_rcv() processing cached the old
socket and continues to use it.
The easy solution is to check for the socket mismatch ... | 1 | int sctp_rcv(struct sk_buff *skb)
{
struct sock *sk;
struct sctp_association *asoc;
struct sctp_endpoint *ep = NULL;
struct sctp_ep_common *rcvr;
struct sctp_transport *transport = NULL;
struct sctp_chunk *chunk;
struct sctphdr *sh;
union sctp_addr src;
union sctp_addr dest;
int family;
struct sctp_af *af;
... | 173,020,335,186,799,700,000,000,000,000,000,000,000 | input.c | 44,064,972,847,145,270,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-4348 | Race condition in the sctp_rcv function in net/sctp/input.c in the Linux kernel before 2.6.29 allows remote attackers to cause a denial of service (system hang) via SCTP packets. NOTE: in some environments, this issue exists because of an incomplete fix for CVE-2011-2482. | https://nvd.nist.gov/vuln/detail/CVE-2011-4348 |
158,929 | linux | ae53b5bd77719fed58086c5be60ce4f22bffe1c6 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ae53b5bd77719fed58086c5be60ce4f22bffe1c6 | sctp: Fix another socket race during accept/peeloff
There is a race between sctp_rcv() and sctp_accept() where we
have moved the association from the listening socket to the
accepted socket, but sctp_rcv() processing cached the old
socket and continues to use it.
The easy solution is to check for the socket mismatch ... | 0 | int sctp_rcv(struct sk_buff *skb)
{
struct sock *sk;
struct sctp_association *asoc;
struct sctp_endpoint *ep = NULL;
struct sctp_ep_common *rcvr;
struct sctp_transport *transport = NULL;
struct sctp_chunk *chunk;
struct sctphdr *sh;
union sctp_addr src;
union sctp_addr dest;
int family;
struct sctp_af *af;
... | 285,205,648,314,530,200,000,000,000,000,000,000,000 | input.c | 9,836,562,687,727,890,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-4348 | Race condition in the sctp_rcv function in net/sctp/input.c in the Linux kernel before 2.6.29 allows remote attackers to cause a denial of service (system hang) via SCTP packets. NOTE: in some environments, this issue exists because of an incomplete fix for CVE-2011-2482. | https://nvd.nist.gov/vuln/detail/CVE-2011-4348 |
1,153 | linux | c4e7f9022e506c6635a5037713c37118e23193e4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c4e7f9022e506c6635a5037713c37118e23193e4 | None | 1 | static int kvm_vm_ioctl_assign_device(struct kvm *kvm,
struct kvm_assigned_pci_dev *assigned_dev)
{
int r = 0, idx;
struct kvm_assigned_dev_kernel *match;
struct pci_dev *dev;
if (!(assigned_dev->flags & KVM_DEV_ASSIGN_ENABLE_IOMMU))
return -EINVAL;
mutex_lock(&kvm->lock);
idx = srcu_read_l... | 272,600,557,570,379,850,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2011-4347 | The kvm_vm_ioctl_assign_device function in virt/kvm/assigned-dev.c in the KVM subsystem in the Linux kernel before 3.1.10 does not verify permission to access PCI configuration space and BAR resources, which allows host OS users to assign PCI devices and cause a denial of service (host OS crash) via a KVM_ASSIGN_PCI_DE... | https://nvd.nist.gov/vuln/detail/CVE-2011-4347 |
158,930 | linux | c4e7f9022e506c6635a5037713c37118e23193e4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c4e7f9022e506c6635a5037713c37118e23193e4 | None | 0 | static int kvm_vm_ioctl_assign_device(struct kvm *kvm,
struct kvm_assigned_pci_dev *assigned_dev)
{
int r = 0, idx;
struct kvm_assigned_dev_kernel *match;
struct pci_dev *dev;
u8 header_type;
if (!(assigned_dev->flags & KVM_DEV_ASSIGN_ENABLE_IOMMU))
return -EINVAL;
mutex_lock(&kvm->lock);
... | 5,526,983,120,748,632,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2011-4347 | The kvm_vm_ioctl_assign_device function in virt/kvm/assigned-dev.c in the KVM subsystem in the Linux kernel before 3.1.10 does not verify permission to access PCI configuration space and BAR resources, which allows host OS users to assign PCI devices and cause a denial of service (host OS crash) via a KVM_ASSIGN_PCI_DE... | https://nvd.nist.gov/vuln/detail/CVE-2011-4347 |
1,160 | linux | f8e9881c2aef1e982e5abc25c046820cd0b7cf64 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f8e9881c2aef1e982e5abc25c046820cd0b7cf64 | bridge: reset IPCB in br_parse_ip_options
Commit 462fb2af9788a82 (bridge : Sanitize skb before it enters the IP
stack), missed one IPCB init before calling ip_options_compile()
Thanks to Scot Doyle for his tests and bug reports.
Reported-by: Scot Doyle <lkml@scotdoyle.com>
Signed-off-by: Eric Dumazet <eric.dumazet@g... | 1 | static int br_parse_ip_options(struct sk_buff *skb)
{
struct ip_options *opt;
struct iphdr *iph;
struct net_device *dev = skb->dev;
u32 len;
iph = ip_hdr(skb);
opt = &(IPCB(skb)->opt);
/* Basic sanity checks */
if (iph->ihl < 5 || iph->version != 4)
goto inhdr_error;
if (!pskb_may_pull(skb, iph->ihl*4))
... | 126,955,592,485,195,450,000,000,000,000,000,000,000 | br_netfilter.c | 318,634,080,555,349,820,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2011-4087 | The br_parse_ip_options function in net/bridge/br_netfilter.c in the Linux kernel before 2.6.39 does not properly initialize a certain data structure, which allows remote attackers to cause a denial of service by leveraging connectivity to a network interface that uses an Ethernet bridge device. | https://nvd.nist.gov/vuln/detail/CVE-2011-4087 |
158,937 | linux | f8e9881c2aef1e982e5abc25c046820cd0b7cf64 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f8e9881c2aef1e982e5abc25c046820cd0b7cf64 | bridge: reset IPCB in br_parse_ip_options
Commit 462fb2af9788a82 (bridge : Sanitize skb before it enters the IP
stack), missed one IPCB init before calling ip_options_compile()
Thanks to Scot Doyle for his tests and bug reports.
Reported-by: Scot Doyle <lkml@scotdoyle.com>
Signed-off-by: Eric Dumazet <eric.dumazet@g... | 0 | static int br_parse_ip_options(struct sk_buff *skb)
{
struct ip_options *opt;
struct iphdr *iph;
struct net_device *dev = skb->dev;
u32 len;
iph = ip_hdr(skb);
opt = &(IPCB(skb)->opt);
/* Basic sanity checks */
if (iph->ihl < 5 || iph->version != 4)
goto inhdr_error;
if (!pskb_may_pull(skb, iph->ihl*4))
... | 278,765,479,813,232,630,000,000,000,000,000,000,000 | br_netfilter.c | 229,107,498,176,349,860,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2011-4087 | The br_parse_ip_options function in net/bridge/br_netfilter.c in the Linux kernel before 2.6.39 does not properly initialize a certain data structure, which allows remote attackers to cause a denial of service by leveraging connectivity to a network interface that uses an Ethernet bridge device. | https://nvd.nist.gov/vuln/detail/CVE-2011-4087 |
1,163 | linux | a5b2c5b2ad5853591a6cac6134cd0f599a720865 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a5b2c5b2ad5853591a6cac6134cd0f599a720865 | AppArmor: fix oops in apparmor_setprocattr
When invalid parameters are passed to apparmor_setprocattr a NULL deref
oops occurs when it tries to record an audit message. This is because
it is passing NULL for the profile parameter for aa_audit. But aa_audit
now requires that the profile passed is not NULL.
Fix this by... | 1 | static int apparmor_setprocattr(struct task_struct *task, char *name,
void *value, size_t size)
{
char *command, *args = value;
size_t arg_size;
int error;
if (size == 0)
return -EINVAL;
/* args points to a PAGE_SIZE buffer, AppArmor requires that
* the buffer must be null terminated or have size <= PAGE_... | 198,478,101,125,261,500,000,000,000,000,000,000,000 | lsm.c | 86,780,604,940,296,660,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3619 | The apparmor_setprocattr function in security/apparmor/lsm.c in the Linux kernel before 3.0 does not properly handle invalid parameters, which allows local users to cause a denial of service (NULL pointer dereference and OOPS) or possibly have unspecified other impact by writing to a /proc/#####/attr/current file. | https://nvd.nist.gov/vuln/detail/CVE-2011-3619 |
158,939 | linux | a5b2c5b2ad5853591a6cac6134cd0f599a720865 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a5b2c5b2ad5853591a6cac6134cd0f599a720865 | AppArmor: fix oops in apparmor_setprocattr
When invalid parameters are passed to apparmor_setprocattr a NULL deref
oops occurs when it tries to record an audit message. This is because
it is passing NULL for the profile parameter for aa_audit. But aa_audit
now requires that the profile passed is not NULL.
Fix this by... | 0 | static int apparmor_setprocattr(struct task_struct *task, char *name,
void *value, size_t size)
{
char *command, *args = value;
size_t arg_size;
int error;
if (size == 0)
return -EINVAL;
/* args points to a PAGE_SIZE buffer, AppArmor requires that
* the buffer must be null terminated or have size <= PAGE_... | 100,934,072,516,030,160,000,000,000,000,000,000,000 | lsm.c | 251,075,127,368,936,700,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3619 | The apparmor_setprocattr function in security/apparmor/lsm.c in the Linux kernel before 3.0 does not properly handle invalid parameters, which allows local users to cause a denial of service (NULL pointer dereference and OOPS) or possibly have unspecified other impact by writing to a /proc/#####/attr/current file. | https://nvd.nist.gov/vuln/detail/CVE-2011-3619 |
1,164 | linux | aba8d056078e47350d85b06a9cabd5afcc4b72ea | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/aba8d056078e47350d85b06a9cabd5afcc4b72ea | perf tools: do not look at ./config for configuration
In addition to /etc/perfconfig and $HOME/.perfconfig, perf looks for
configuration in the file ./config, imitating git which looks at
$GIT_DIR/config. If ./config is not a perf configuration file, it
fails, or worse, treats it as a configuration file and changes b... | 1 | int perf_config(config_fn_t fn, void *data)
{
int ret = 0, found = 0;
char *repo_config = NULL;
const char *home = NULL;
/* Setting $PERF_CONFIG makes perf read _only_ the given config file. */
if (config_exclusive_filename)
return perf_config_from_file(fn, config_exclusive_filename, data);
if (perf_conf... | 291,567,066,678,415,750,000,000,000,000,000,000,000 | config.c | 300,265,789,152,003,100,000,000,000,000,000,000,000 | [
"CWE-94"
] | CVE-2011-2905 | Untrusted search path vulnerability in the perf_config function in tools/perf/util/config.c in perf, as distributed in the Linux kernel before 3.1, allows local users to overwrite arbitrary files via a crafted config file in the current working directory. | https://nvd.nist.gov/vuln/detail/CVE-2011-2905 |
158,940 | linux | aba8d056078e47350d85b06a9cabd5afcc4b72ea | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/aba8d056078e47350d85b06a9cabd5afcc4b72ea | perf tools: do not look at ./config for configuration
In addition to /etc/perfconfig and $HOME/.perfconfig, perf looks for
configuration in the file ./config, imitating git which looks at
$GIT_DIR/config. If ./config is not a perf configuration file, it
fails, or worse, treats it as a configuration file and changes b... | 0 | int perf_config(config_fn_t fn, void *data)
{
int ret = 0, found = 0;
const char *home = NULL;
/* Setting $PERF_CONFIG makes perf read _only_ the given config file. */
if (config_exclusive_filename)
return perf_config_from_file(fn, config_exclusive_filename, data);
if (perf_config_system() && !access(perf... | 173,002,454,094,245,940,000,000,000,000,000,000,000 | config.c | 89,272,209,983,932,730,000,000,000,000,000,000,000 | [
"CWE-94"
] | CVE-2011-2905 | Untrusted search path vulnerability in the perf_config function in tools/perf/util/config.c in perf, as distributed in the Linux kernel before 3.1, allows local users to overwrite arbitrary files via a crafted config file in the current working directory. | https://nvd.nist.gov/vuln/detail/CVE-2011-2905 |
1,167 | linux | ea2bc483ff5caada7c4aa0d5fbf87d3a6590273d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ea2bc483ff5caada7c4aa0d5fbf87d3a6590273d | [SCTP]: Fix assertion (!atomic_read(&sk->sk_rmem_alloc)) failed message
In current implementation, LKSCTP does receive buffer accounting for
data in sctp_receive_queue and pd_lobby. However, LKSCTP don't do
accounting for data in frag_list when data is fragmented. In addition,
LKSCTP doesn't do accounting for data in ... | 1 | static void sctp_sock_migrate(struct sock *oldsk, struct sock *newsk,
struct sctp_association *assoc,
sctp_socket_type_t type)
{
struct sctp_sock *oldsp = sctp_sk(oldsk);
struct sctp_sock *newsp = sctp_sk(newsk);
struct sctp_bind_bucket *pp; /* hash list port iterator */
struct sctp_endpoint *newe... | 245,295,386,150,735,570,000,000,000,000,000,000,000 | socket.c | 237,855,478,219,647,640,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2011-2482 | A certain Red Hat patch to the sctp_sock_migrate function in net/sctp/socket.c in the Linux kernel before 2.6.21, as used in Red Hat Enterprise Linux (RHEL) 5, allows remote attackers to cause a denial of service (NULL pointer dereference and OOPS) via a crafted SCTP packet. | https://nvd.nist.gov/vuln/detail/CVE-2011-2482 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.