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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
33,363 | linux | 8176cced706b5e5d15887584150764894e94e02f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8176cced706b5e5d15887584150764894e94e02f | perf: Treat attr.config as u64 in perf_swevent_init()
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed... | 0 | void perf_output_sample(struct perf_output_handle *handle,
struct perf_event_header *header,
struct perf_sample_data *data,
struct perf_event *event)
{
u64 sample_type = data->type;
perf_output_put(handle, *header);
if (sample_type & PERF_SAMPLE_IP)
perf_output_put(handle, data->ip);
if (sample_type &... | 303,596,639,483,001,800,000,000,000,000,000,000,000 | core.c | 11,140,413,320,282,108,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2094 | The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2094 |
33,364 | linux | 8176cced706b5e5d15887584150764894e94e02f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8176cced706b5e5d15887584150764894e94e02f | perf: Treat attr.config as u64 in perf_swevent_init()
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed... | 0 | perf_output_sample_regs(struct perf_output_handle *handle,
struct pt_regs *regs, u64 mask)
{
int bit;
for_each_set_bit(bit, (const unsigned long *) &mask,
sizeof(mask) * BITS_PER_BYTE) {
u64 val;
val = perf_reg_value(regs, bit);
perf_output_put(handle, val);
}
}
| 103,248,054,497,231,750,000,000,000,000,000,000,000 | core.c | 336,324,934,668,837,200,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2094 | The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2094 |
33,365 | linux | 8176cced706b5e5d15887584150764894e94e02f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8176cced706b5e5d15887584150764894e94e02f | perf: Treat attr.config as u64 in perf_swevent_init()
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed... | 0 | perf_output_sample_ustack(struct perf_output_handle *handle, u64 dump_size,
struct pt_regs *regs)
{
/* Case of a kernel thread, nothing to dump */
if (!regs) {
u64 size = 0;
perf_output_put(handle, size);
} else {
unsigned long sp;
unsigned int rem;
u64 dyn_size;
/*
* We dump:
* static size
... | 28,582,937,767,483,197,000,000,000,000,000,000,000 | core.c | 304,500,610,601,399,240,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2094 | The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2094 |
33,366 | linux | 8176cced706b5e5d15887584150764894e94e02f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8176cced706b5e5d15887584150764894e94e02f | perf: Treat attr.config as u64 in perf_swevent_init()
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed... | 0 | void perf_pmu_migrate_context(struct pmu *pmu, int src_cpu, int dst_cpu)
{
struct perf_event_context *src_ctx;
struct perf_event_context *dst_ctx;
struct perf_event *event, *tmp;
LIST_HEAD(events);
src_ctx = &per_cpu_ptr(pmu->pmu_cpu_context, src_cpu)->ctx;
dst_ctx = &per_cpu_ptr(pmu->pmu_cpu_context, dst_cpu)->... | 145,058,634,197,795,800,000,000,000,000,000,000,000 | core.c | 11,140,413,320,282,108,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2094 | The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2094 |
33,367 | linux | 8176cced706b5e5d15887584150764894e94e02f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8176cced706b5e5d15887584150764894e94e02f | perf: Treat attr.config as u64 in perf_swevent_init()
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed... | 0 | int perf_pmu_register(struct pmu *pmu, char *name, int type)
{
int cpu, ret;
mutex_lock(&pmus_lock);
ret = -ENOMEM;
pmu->pmu_disable_count = alloc_percpu(int);
if (!pmu->pmu_disable_count)
goto unlock;
pmu->type = -1;
if (!name)
goto skip_type;
pmu->name = name;
if (type < 0) {
type = idr_alloc(&pmu_i... | 114,484,322,389,244,120,000,000,000,000,000,000,000 | core.c | 11,140,413,320,282,108,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2094 | The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2094 |
33,368 | linux | 8176cced706b5e5d15887584150764894e94e02f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8176cced706b5e5d15887584150764894e94e02f | perf: Treat attr.config as u64 in perf_swevent_init()
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed... | 0 | static unsigned int perf_poll(struct file *file, poll_table *wait)
{
struct perf_event *event = file->private_data;
struct ring_buffer *rb;
unsigned int events = POLL_HUP;
/*
* Race between perf_event_set_output() and perf_poll(): perf_poll()
* grabs the rb reference but perf_event_set_output() overrides it.
... | 125,161,258,278,450,100,000,000,000,000,000,000,000 | core.c | 11,140,413,320,282,108,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2094 | The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2094 |
33,369 | linux | 8176cced706b5e5d15887584150764894e94e02f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8176cced706b5e5d15887584150764894e94e02f | perf: Treat attr.config as u64 in perf_swevent_init()
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed... | 0 | void perf_prepare_sample(struct perf_event_header *header,
struct perf_sample_data *data,
struct perf_event *event,
struct pt_regs *regs)
{
u64 sample_type = event->attr.sample_type;
header->type = PERF_RECORD_SAMPLE;
header->size = sizeof(*header) + event->header_size;
header->misc = 0;
header->misc... | 207,698,989,723,010,500,000,000,000,000,000,000,000 | core.c | 11,140,413,320,282,108,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2094 | The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2094 |
33,370 | linux | 8176cced706b5e5d15887584150764894e94e02f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8176cced706b5e5d15887584150764894e94e02f | perf: Treat attr.config as u64 in perf_swevent_init()
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed... | 0 | static int perf_release(struct inode *inode, struct file *file)
{
put_event(file->private_data);
return 0;
}
| 151,551,671,006,541,370,000,000,000,000,000,000,000 | core.c | 336,324,934,668,837,200,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2094 | The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2094 |
33,371 | linux | 8176cced706b5e5d15887584150764894e94e02f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8176cced706b5e5d15887584150764894e94e02f | perf: Treat attr.config as u64 in perf_swevent_init()
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed... | 0 | static void perf_rotate_context(struct perf_cpu_context *cpuctx)
{
struct perf_event_context *ctx = NULL;
int rotate = 0, remove = 1;
if (cpuctx->ctx.nr_events) {
remove = 0;
if (cpuctx->ctx.nr_events != cpuctx->ctx.nr_active)
rotate = 1;
}
ctx = cpuctx->task_ctx;
if (ctx && ctx->nr_events) {
remove = ... | 285,287,021,152,782,570,000,000,000,000,000,000,000 | core.c | 11,140,413,320,282,108,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2094 | The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2094 |
33,372 | linux | 8176cced706b5e5d15887584150764894e94e02f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8176cced706b5e5d15887584150764894e94e02f | perf: Treat attr.config as u64 in perf_swevent_init()
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed... | 0 | static void perf_sample_regs_user(struct perf_regs_user *regs_user,
struct pt_regs *regs)
{
if (!user_mode(regs)) {
if (current->mm)
regs = task_pt_regs(current);
else
regs = NULL;
}
if (regs) {
regs_user->regs = regs;
regs_user->abi = perf_reg_abi(current);
}
}
| 185,899,327,513,321,880,000,000,000,000,000,000,000 | core.c | 11,140,413,320,282,108,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2094 | The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2094 |
33,373 | linux | 8176cced706b5e5d15887584150764894e94e02f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8176cced706b5e5d15887584150764894e94e02f | perf: Treat attr.config as u64 in perf_swevent_init()
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed... | 0 | perf_sample_ustack_size(u16 stack_size, u16 header_size,
struct pt_regs *regs)
{
u64 task_size;
/* No regs, no stack pointer, no dump. */
if (!regs)
return 0;
/*
* Check if we fit in with the requested stack size into the:
* - TASK_SIZE
* If we don't, we limit the size to the TASK_SIZE.
*
* - rem... | 44,917,806,629,542,560,000,000,000,000,000,000,000 | core.c | 304,500,610,601,399,240,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2094 | The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2094 |
33,374 | linux | 8176cced706b5e5d15887584150764894e94e02f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8176cced706b5e5d15887584150764894e94e02f | perf: Treat attr.config as u64 in perf_swevent_init()
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed... | 0 | static void perf_swevent_event(struct perf_event *event, u64 nr,
struct perf_sample_data *data,
struct pt_regs *regs)
{
struct hw_perf_event *hwc = &event->hw;
local64_add(nr, &event->count);
if (!regs)
return;
if (!is_sampling_event(event))
return;
if ((event->attr.sample_type & PERF_S... | 272,554,582,348,777,740,000,000,000,000,000,000,000 | core.c | 304,500,610,601,399,240,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2094 | The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2094 |
33,375 | linux | 8176cced706b5e5d15887584150764894e94e02f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8176cced706b5e5d15887584150764894e94e02f | perf: Treat attr.config as u64 in perf_swevent_init()
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed... | 0 | static int perf_swevent_event_idx(struct perf_event *event)
{
return 0;
}
| 40,168,390,270,222,510,000,000,000,000,000,000,000 | core.c | 11,140,413,320,282,108,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2094 | The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2094 |
33,376 | linux | 8176cced706b5e5d15887584150764894e94e02f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8176cced706b5e5d15887584150764894e94e02f | perf: Treat attr.config as u64 in perf_swevent_init()
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed... | 0 | static enum hrtimer_restart perf_swevent_hrtimer(struct hrtimer *hrtimer)
{
enum hrtimer_restart ret = HRTIMER_RESTART;
struct perf_sample_data data;
struct pt_regs *regs;
struct perf_event *event;
u64 period;
event = container_of(hrtimer, struct perf_event, hw.hrtimer);
if (event->state != PERF_EVENT_STATE_AC... | 85,162,722,736,909,460,000,000,000,000,000,000,000 | core.c | 304,500,610,601,399,240,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2094 | The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2094 |
33,377 | linux | 8176cced706b5e5d15887584150764894e94e02f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8176cced706b5e5d15887584150764894e94e02f | perf: Treat attr.config as u64 in perf_swevent_init()
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed... | 0 | static void perf_swevent_init_hrtimer(struct perf_event *event)
{
struct hw_perf_event *hwc = &event->hw;
if (!is_sampling_event(event))
return;
hrtimer_init(&hwc->hrtimer, CLOCK_MONOTONIC, HRTIMER_MODE_REL);
hwc->hrtimer.function = perf_swevent_hrtimer;
/*
* Since hrtimers have a fixed rate, we can do a st... | 56,321,142,216,221,850,000,000,000,000,000,000,000 | core.c | 304,500,610,601,399,240,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2094 | The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2094 |
33,378 | linux | 8176cced706b5e5d15887584150764894e94e02f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8176cced706b5e5d15887584150764894e94e02f | perf: Treat attr.config as u64 in perf_swevent_init()
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed... | 0 | static void perf_swevent_overflow(struct perf_event *event, u64 overflow,
struct perf_sample_data *data,
struct pt_regs *regs)
{
struct hw_perf_event *hwc = &event->hw;
int throttle = 0;
if (!overflow)
overflow = perf_swevent_set_period(event);
if (hwc->interrupts == MAX_INTERRUPTS)
return;
... | 59,373,044,637,350,980,000,000,000,000,000,000,000 | core.c | 304,500,610,601,399,240,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2094 | The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2094 |
33,379 | linux | 8176cced706b5e5d15887584150764894e94e02f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8176cced706b5e5d15887584150764894e94e02f | perf: Treat attr.config as u64 in perf_swevent_init()
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed... | 0 | void perf_tp_event(u64 addr, u64 count, void *record, int entry_size,
struct pt_regs *regs, struct hlist_head *head, int rctx,
struct task_struct *task)
{
struct perf_sample_data data;
struct perf_event *event;
struct perf_raw_record raw = {
.size = entry_size,
.data = record,
};
perf_sample_data_i... | 40,045,914,113,341,783,000,000,000,000,000,000,000 | core.c | 336,324,934,668,837,200,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2094 | The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2094 |
33,380 | linux | 8176cced706b5e5d15887584150764894e94e02f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8176cced706b5e5d15887584150764894e94e02f | perf: Treat attr.config as u64 in perf_swevent_init()
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed... | 0 | static int perf_tp_event_init(struct perf_event *event)
{
int err;
if (event->attr.type != PERF_TYPE_TRACEPOINT)
return -ENOENT;
/*
* no branch sampling for tracepoint events
*/
if (has_branch_stack(event))
return -EOPNOTSUPP;
err = perf_trace_init(event);
if (err)
return err;
event->destroy = tp_p... | 338,775,361,232,506,260,000,000,000,000,000,000,000 | core.c | 304,500,610,601,399,240,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2094 | The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2094 |
33,381 | linux | 8176cced706b5e5d15887584150764894e94e02f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8176cced706b5e5d15887584150764894e94e02f | perf: Treat attr.config as u64 in perf_swevent_init()
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed... | 0 | static inline bool perf_tryget_cgroup(struct perf_event *event)
{
return css_tryget(&event->cgrp->css);
}
| 339,052,538,621,474,080,000,000,000,000,000,000,000 | core.c | 11,140,413,320,282,108,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2094 | The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2094 |
33,382 | linux | 8176cced706b5e5d15887584150764894e94e02f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8176cced706b5e5d15887584150764894e94e02f | perf: Treat attr.config as u64 in perf_swevent_init()
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed... | 0 | static u64 perf_ustack_task_size(struct pt_regs *regs)
{
unsigned long addr = perf_user_stack_pointer(regs);
if (!addr || addr >= TASK_SIZE)
return 0;
return TASK_SIZE - addr;
}
| 227,127,289,841,552,670,000,000,000,000,000,000,000 | core.c | 304,500,610,601,399,240,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2094 | The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2094 |
33,383 | linux | 8176cced706b5e5d15887584150764894e94e02f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8176cced706b5e5d15887584150764894e94e02f | perf: Treat attr.config as u64 in perf_swevent_init()
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed... | 0 | static int pmu_dev_alloc(struct pmu *pmu)
{
int ret = -ENOMEM;
pmu->dev = kzalloc(sizeof(struct device), GFP_KERNEL);
if (!pmu->dev)
goto out;
pmu->dev->groups = pmu->attr_groups;
device_initialize(pmu->dev);
ret = dev_set_name(pmu->dev, "%s", pmu->name);
if (ret)
goto free_dev;
dev_set_drvdata(pmu->dev,... | 113,972,373,443,535,300,000,000,000,000,000,000,000 | core.c | 336,324,934,668,837,200,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2094 | The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2094 |
33,384 | linux | 8176cced706b5e5d15887584150764894e94e02f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8176cced706b5e5d15887584150764894e94e02f | perf: Treat attr.config as u64 in perf_swevent_init()
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed... | 0 | static void put_event(struct perf_event *event)
{
struct task_struct *owner;
if (!atomic_long_dec_and_test(&event->refcount))
return;
rcu_read_lock();
owner = ACCESS_ONCE(event->owner);
/*
* Matches the smp_wmb() in perf_event_exit_task(). If we observe
* !owner it means the list deletion is complete and w... | 54,969,243,308,256,800,000,000,000,000,000,000,000 | core.c | 11,140,413,320,282,108,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2094 | The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2094 |
33,385 | linux | 8176cced706b5e5d15887584150764894e94e02f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8176cced706b5e5d15887584150764894e94e02f | perf: Treat attr.config as u64 in perf_swevent_init()
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed... | 0 | static void ring_buffer_attach(struct perf_event *event,
struct ring_buffer *rb)
{
unsigned long flags;
if (!list_empty(&event->rb_entry))
return;
spin_lock_irqsave(&rb->event_lock, flags);
if (!list_empty(&event->rb_entry))
goto unlock;
list_add(&event->rb_entry, &rb->event_list);
unlock:
spin_u... | 121,295,179,358,915,820,000,000,000,000,000,000,000 | core.c | 11,140,413,320,282,108,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2094 | The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2094 |
33,386 | linux | 8176cced706b5e5d15887584150764894e94e02f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8176cced706b5e5d15887584150764894e94e02f | perf: Treat attr.config as u64 in perf_swevent_init()
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed... | 0 | static void ring_buffer_put(struct ring_buffer *rb)
{
struct perf_event *event, *n;
unsigned long flags;
if (!atomic_dec_and_test(&rb->refcount))
return;
spin_lock_irqsave(&rb->event_lock, flags);
list_for_each_entry_safe(event, n, &rb->event_list, rb_entry) {
list_del_init(&event->rb_entry);
wake_up_all(&... | 256,668,682,962,204,850,000,000,000,000,000,000,000 | core.c | 11,140,413,320,282,108,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2094 | The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2094 |
33,387 | linux | 8176cced706b5e5d15887584150764894e94e02f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8176cced706b5e5d15887584150764894e94e02f | perf: Treat attr.config as u64 in perf_swevent_init()
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed... | 0 | static void ring_buffer_wakeup(struct perf_event *event)
{
struct ring_buffer *rb;
rcu_read_lock();
rb = rcu_dereference(event->rb);
if (!rb)
goto unlock;
list_for_each_entry_rcu(event, &rb->event_list, rb_entry)
wake_up_all(&event->waitq);
unlock:
rcu_read_unlock();
}
| 321,108,508,596,632,900,000,000,000,000,000,000,000 | core.c | 11,140,413,320,282,108,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2094 | The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2094 |
33,388 | linux | 8176cced706b5e5d15887584150764894e94e02f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8176cced706b5e5d15887584150764894e94e02f | perf: Treat attr.config as u64 in perf_swevent_init()
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed... | 0 | static void sw_perf_event_destroy(struct perf_event *event)
{
u64 event_id = event->attr.config;
WARN_ON(event->parent);
static_key_slow_dec(&perf_swevent_enabled[event_id]);
swevent_hlist_put(event);
}
| 103,427,292,439,513,000,000,000,000,000,000,000,000 | core.c | 336,324,934,668,837,200,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2094 | The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2094 |
33,389 | linux | 8176cced706b5e5d15887584150764894e94e02f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8176cced706b5e5d15887584150764894e94e02f | perf: Treat attr.config as u64 in perf_swevent_init()
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed... | 0 | static void sync_child_event(struct perf_event *child_event,
struct task_struct *child)
{
struct perf_event *parent_event = child_event->parent;
u64 child_val;
if (child_event->attr.inherit_stat)
perf_event_read_event(child_event, child);
child_val = perf_event_count(child_event);
/*
* Add back th... | 188,240,921,460,794,600,000,000,000,000,000,000,000 | core.c | 11,140,413,320,282,108,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2094 | The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2094 |
33,390 | linux | 8176cced706b5e5d15887584150764894e94e02f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8176cced706b5e5d15887584150764894e94e02f | perf: Treat attr.config as u64 in perf_swevent_init()
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed... | 0 | static int task_clock_event_init(struct perf_event *event)
{
if (event->attr.type != PERF_TYPE_SOFTWARE)
return -ENOENT;
if (event->attr.config != PERF_COUNT_SW_TASK_CLOCK)
return -ENOENT;
/*
* no branch sampling for software events
*/
if (has_branch_stack(event))
return -EOPNOTSUPP;
perf_swevent_init... | 219,703,363,073,810,770,000,000,000,000,000,000,000 | core.c | 304,500,610,601,399,240,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2094 | The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2094 |
33,391 | linux | 8176cced706b5e5d15887584150764894e94e02f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8176cced706b5e5d15887584150764894e94e02f | perf: Treat attr.config as u64 in perf_swevent_init()
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed... | 0 | static void update_pmu_context(struct pmu *pmu, struct pmu *old_pmu)
{
int cpu;
for_each_possible_cpu(cpu) {
struct perf_cpu_context *cpuctx;
cpuctx = per_cpu_ptr(pmu->pmu_cpu_context, cpu);
if (cpuctx->unique_pmu == old_pmu)
cpuctx->unique_pmu = pmu;
}
}
| 98,864,870,519,882,460,000,000,000,000,000,000,000 | core.c | 304,500,610,601,399,240,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-2094 | The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-2094 |
33,392 | 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 | cfb_ofb_mode (const struct key_type* kt)
{
if (kt && kt->cipher) {
const unsigned int mode = cipher_kt_mode (kt->cipher);
return mode == OPENVPN_MODE_CFB || mode == OPENVPN_MODE_OFB;
}
return false;
}
| 322,513,798,732,649,060,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 |
33,393 | 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 | check_key (struct key *key, const struct key_type *kt)
{
if (kt->cipher)
{
/*
* Check for zero key
*/
if (key_is_zero(key, kt))
return false;
/*
* Check for weak or semi-weak DES keys.
*/
{
const int ndc = key_des_num_cblocks (kt->cipher);
if (ndc)
return... | 279,762,234,302,090,540,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 |
33,394 | 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 | check_replay_iv_consistency (const struct key_type *kt, bool packet_id, bool use_iv)
{
if (cfb_ofb_mode (kt) && !(packet_id && use_iv))
msg (M_FATAL, "--no-replay or --no-iv cannot be used with a CFB or OFB mode cipher");
}
| 179,576,200,136,300,820,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 |
33,395 | 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 | crypto_adjust_frame_parameters(struct frame *frame,
const struct key_type* kt,
bool cipher_defined,
bool use_iv,
bool packet_id,
bool packet_id_long_form)
{
frame_add_to_extra_frame (frame,
(packet_id ? packet_id_size (packet_id_long_form) : 0) +
((ciphe... | 116,137,130,043,152,500,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 |
33,396 | 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 | fixup_key (struct key *key, const struct key_type *kt)
{
struct gc_arena gc = gc_new ();
if (kt->cipher)
{
#ifdef ENABLE_DEBUG
const struct key orig = *key;
#endif
const int ndc = key_des_num_cblocks (kt->cipher);
if (ndc)
key_des_fixup (key->cipher, kt->cipher_length, ndc);
#ifdef ENABLE_D... | 210,709,804,755,756,500,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 |
33,397 | 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 | free_key_ctx (struct key_ctx *ctx)
{
if (ctx->cipher)
{
cipher_ctx_cleanup(ctx->cipher);
free(ctx->cipher);
ctx->cipher = NULL;
}
if (ctx->hmac)
{
hmac_ctx_cleanup(ctx->hmac);
free(ctx->hmac);
ctx->hmac = NULL;
}
}
| 28,882,432,168,915,106,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 |
33,398 | 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 | free_key_ctx_bi (struct key_ctx_bi *ctx)
{
free_key_ctx(&ctx->encrypt);
free_key_ctx(&ctx->decrypt);
}
| 146,104,061,651,632,740,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 |
33,399 | 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 | free_ssl_lib (void)
{
crypto_uninit_lib ();
prng_uninit();
}
| 105,362,693,928,925,270,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 |
33,400 | 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 | generate_key_random (struct key *key, const struct key_type *kt)
{
int cipher_len = MAX_CIPHER_KEY_LENGTH;
int hmac_len = MAX_HMAC_KEY_LENGTH;
struct gc_arena gc = gc_new ();
do {
CLEAR (*key);
if (kt)
{
if (kt->cipher && kt->cipher_length > 0 && kt->cipher_length <= cipher_len)
cipher_len =... | 215,075,095,527,045,200,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 |
33,401 | 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 | get_random()
{
long int l;
prng_bytes ((unsigned char *)&l, sizeof(l));
if (l < 0)
l = -l;
return l;
}
| 38,288,565,047,569,590,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 |
33,402 | 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 | get_tls_handshake_key (const struct key_type *key_type,
struct key_ctx_bi *ctx,
const char *passphrase_file,
const int key_direction,
const unsigned int flags)
{
if (passphrase_file && key_type->hmac_length)
{
struct key2 key2;
struct key_type kt = *key_type;
... | 326,378,160,388,373,340,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 |
33,403 | 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 | init_ssl_lib (void)
{
crypto_init_lib ();
}
| 154,430,320,332,170,760,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 |
33,404 | 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 | key2_print (const struct key2* k,
const struct key_type *kt,
const char* prefix0,
const char* prefix1)
{
struct gc_arena gc = gc_new ();
ASSERT (k->n == 2);
dmsg (D_SHOW_KEY_SOURCE, "%s (cipher): %s",
prefix0,
format_hex (k->keys[0].cipher, kt->cipher_length, 0, &gc));
dmsg (D_SHOW_... | 196,499,815,593,835,370,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 |
33,405 | 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 | key_direction_state_init (struct key_direction_state *kds, int key_direction)
{
CLEAR (*kds);
switch (key_direction)
{
case KEY_DIRECTION_NORMAL:
kds->out_key = 0;
kds->in_key = 1;
kds->need_keys = 2;
break;
case KEY_DIRECTION_INVERSE:
kds->out_key = 1;
kds->in_key = ... | 30,224,512,589,185,394,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 |
33,406 | 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 | key_is_zero (struct key *key, const struct key_type *kt)
{
int i;
for (i = 0; i < kt->cipher_length; ++i)
if (key->cipher[i])
return false;
msg (D_CRYPT_ERRORS, "CRYPTO INFO: WARNING: zero key detected");
return true;
}
| 82,995,434,025,209,500,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 |
33,407 | 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 | keydirection2ascii (int kd, bool remote)
{
if (kd == KEY_DIRECTION_BIDIRECTIONAL)
return NULL;
else if (kd == KEY_DIRECTION_NORMAL)
return remote ? "1" : "0";
else if (kd == KEY_DIRECTION_INVERSE)
return remote ? "0" : "1";
else
{
ASSERT (0);
}
return NULL; /* NOTREACHED */
}
| 259,416,069,375,615,900,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 |
33,408 | 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 | md5_digest_clear (struct md5_digest *digest)
{
CLEAR (*digest);
}
| 70,462,437,302,676,070,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 |
33,409 | 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 | md5_digest_defined (const struct md5_digest *digest)
{
int i;
for (i = 0; i < MD5_DIGEST_LENGTH; ++i)
if (digest->digest[i])
return true;
return false;
}
| 99,422,923,229,606,060,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 |
33,410 | 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 | md5_digest_equal (const struct md5_digest *d1, const struct md5_digest *d2)
{
return memcmp(d1->digest, d2->digest, MD5_DIGEST_LENGTH) == 0;
}
| 317,166,246,541,587,400,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 |
33,411 | 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 | md5_state_final (struct md5_state *s, struct md5_digest *out)
{
md_ctx_final(&s->ctx, out->digest);
md_ctx_cleanup(&s->ctx);
}
| 199,587,579,042,197,500,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 |
33,412 | 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 | md5_state_init (struct md5_state *s)
{
const md_kt_t *md5_kt = md_kt_get("MD5");
md_ctx_init(&s->ctx, md5_kt);
}
| 256,890,633,971,297,800,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 |
33,413 | 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 | must_have_n_keys (const char *filename, const char *option, const struct key2 *key2, int n)
{
if (key2->n < n)
{
#ifdef ENABLE_SMALL
msg (M_FATAL, "Key file '%s' used in --%s contains insufficient key material [keys found=%d required=%d]", filename, option, key2->n, n);
#else
msg (M_FATAL, "Key file '... | 247,761,752,287,745,370,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 |
33,414 | 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_encrypt (struct buffer *buf, struct buffer work,
const struct crypto_options *opt,
const struct frame* frame)
{
struct gc_arena gc;
gc_init (&gc);
if (buf->len > 0 && opt->key_ctx_bi)
{
struct key_ctx *ctx = &opt->key_ctx_bi->encrypt;
/* Do Encrypt from buf -> work */
if (c... | 49,675,899,270,737,540,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 |
33,415 | 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 | prng_bytes (uint8_t *output, int len)
{
static size_t processed = 0;
if (nonce_md)
{
const int md_size = md_kt_size (nonce_md);
while (len > 0)
{
unsigned int outlen = 0;
const int blen = min_int (len, md_size);
md_full(nonce_md, nonce_data, md_size + nonce_secret_len, nonce_data);
mem... | 180,396,243,618,755,100,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 |
33,416 | 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 | prng_init (const char *md_name, const int nonce_secret_len_parm)
{
prng_uninit ();
nonce_md = md_name ? md_kt_get (md_name) : NULL;
if (nonce_md)
{
ASSERT (nonce_secret_len_parm >= NONCE_SECRET_LEN_MIN && nonce_secret_len_parm <= NONCE_SECRET_LEN_MAX);
nonce_secret_len = nonce_secret_len_parm;
... | 32,271,990,190,632,112,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 |
33,417 | 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 | prng_reset_nonce ()
{
const int size = md_kt_size (nonce_md) + nonce_secret_len;
#if 1 /* Must be 1 for real usage */
if (!rand_bytes (nonce_data, size))
msg (M_FATAL, "ERROR: Random number generator cannot obtain entropy for PRNG");
#else
/* Only for testing -- will cause a predictable PRNG sequence */
... | 234,193,384,677,023,060,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 |
33,418 | 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 | prng_uninit (void)
{
free (nonce_data);
nonce_data = NULL;
nonce_md = NULL;
nonce_secret_len = 0;
}
| 64,442,603,205,458,880,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 |
33,419 | 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 | read_key_file (struct key2 *key2, const char *file, const unsigned int flags)
{
struct gc_arena gc = gc_new ();
struct buffer in;
int fd, size;
uint8_t hex_byte[3] = {0, 0, 0};
const char *error_filename = file;
/* parse info */
const unsigned char *cp;
int hb_index = 0;
int line_num = 1;
int line_... | 167,112,212,734,613,920,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 |
33,420 | 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 | read_passphrase_hash (const char *passphrase_file,
const md_kt_t *digest,
uint8_t *output,
int len)
{
unsigned int outlen = 0;
md_ctx_t md;
ASSERT (len >= md_kt_size(digest));
memset (output, 0, len);
md_ctx_init(&md, digest);
/* read passphrase file */
{
const int min_passp... | 329,200,473,531,705,250,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 |
33,421 | 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 | test_crypto (const struct crypto_options *co, struct frame* frame)
{
int i, j;
struct gc_arena gc = gc_new ();
struct buffer src = alloc_buf_gc (TUN_MTU_SIZE (frame), &gc);
struct buffer work = alloc_buf_gc (BUF_SIZE (frame), &gc);
struct buffer encrypt_workspace = alloc_buf_gc (BUF_SIZE (frame), &gc);
stru... | 191,891,271,651,653,000,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 |
33,422 | 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 | verify_fix_key2 (struct key2 *key2, const struct key_type *kt, const char *shared_secret_file)
{
int i;
for (i = 0; i < key2->n; ++i)
{
/* Fix parity for DES keys and make sure not a weak key */
fixup_key (&key2->keys[i], kt);
/* This should be a very improbable failure */
if (!check_k... | 37,157,531,917,935,404,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 |
33,423 | 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 | write_key (const struct key *key, const struct key_type *kt,
struct buffer *buf)
{
ASSERT (kt->cipher_length <= MAX_CIPHER_KEY_LENGTH
&& kt->hmac_length <= MAX_HMAC_KEY_LENGTH);
if (!buf_write (buf, &kt->cipher_length, 1))
return false;
if (!buf_write (buf, &kt->hmac_length, 1))
return false;
if... | 142,467,446,096,947,880,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 |
33,424 | 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 | write_key_file (const int nkeys, const char *filename)
{
struct gc_arena gc = gc_new ();
int fd, i;
int nbits = 0;
/* must be large enough to hold full key file */
struct buffer out = alloc_buf_gc (2048, &gc);
struct buffer nbits_head_text = alloc_buf_gc (128, &gc);
/* how to format the ascii file repr... | 165,495,944,535,982,100,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 |
33,425 | 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 | int ci_hdrc_host_init(struct ci13xxx *ci)
{
struct ci_role_driver *rdrv;
if (!hw_read(ci, CAP_DCCPARAMS, DCCPARAMS_HC))
return -ENXIO;
rdrv = devm_kzalloc(ci->dev, sizeof(struct ci_role_driver), GFP_KERNEL);
if (!rdrv)
return -ENOMEM;
rdrv->start = host_start;
rdrv->stop = host_stop;
rdrv->irq = host_irq;... | 277,579,454,163,482,620,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 |
33,426 | 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 irqreturn_t host_irq(struct ci13xxx *ci)
{
return usb_hcd_irq(ci->irq, ci->hcd);
}
| 119,230,414,121,500,660,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 |
33,427 | 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 void host_stop(struct ci13xxx *ci)
{
struct usb_hcd *hcd = ci->hcd;
usb_remove_hcd(hcd);
usb_put_hcd(hcd);
}
| 187,770,547,920,330,900,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 |
33,603 | 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 | static int add_dirent_to_buf(handle_t *handle, struct dentry *dentry,
struct inode *inode, struct ext4_dir_entry_2 *de,
struct buffer_head *bh)
{
struct inode *dir = dentry->d_parent->d_inode;
const char *name = dentry->d_name.name;
int namelen = dentry->d_name.len;
unsigned int blocksize = dir->i_... | 188,293,117,380,673,850,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 |
33,604 | 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 | static struct ext4_dir_entry_2 *do_split(handle_t *handle, struct inode *dir,
struct buffer_head **bh,struct dx_frame *frame,
struct dx_hash_info *hinfo, int *error)
{
unsigned blocksize = dir->i_sb->s_blocksize;
unsigned count, continued;
struct buffer_head *bh2;
ext4_lblk_t newblock;
u32 hash2;
struct dx_... | 204,049,438,096,179,800,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 |
33,605 | 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 | static inline ext4_lblk_t dx_get_block(struct dx_entry *entry)
{
return le32_to_cpu(entry->block) & 0x00ffffff;
}
| 154,897,259,698,726,900,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 |
33,606 | 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 | static inline unsigned dx_get_count(struct dx_entry *entries)
{
return le16_to_cpu(((struct dx_countlimit *) entries)->count);
}
| 22,118,713,410,193,980,000,000,000,000,000,000,000 | namei.c | 113,178,550,349,909,030,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 |
33,607 | 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 | static inline unsigned dx_get_hash(struct dx_entry *entry)
{
return le32_to_cpu(entry->hash);
}
| 98,544,205,958,955,200,000,000,000,000,000,000,000 | namei.c | 113,178,550,349,909,030,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 |
33,608 | 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 | static void dx_insert_block(struct dx_frame *frame, u32 hash, ext4_lblk_t block)
{
struct dx_entry *entries = frame->entries;
struct dx_entry *old = frame->at, *new = old + 1;
int count = dx_get_count(entries);
assert(count < dx_get_limit(entries));
assert(old < entries + count);
memmove(new + 1, new, (char *)(e... | 223,018,841,451,063,200,000,000,000,000,000,000,000 | namei.c | 113,178,550,349,909,030,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 |
33,609 | 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 | static int dx_make_map(struct ext4_dir_entry_2 *de, unsigned blocksize,
struct dx_hash_info *hinfo,
struct dx_map_entry *map_tail)
{
int count = 0;
char *base = (char *) de;
struct dx_hash_info h = *hinfo;
while ((char *) de < base + blocksize) {
if (de->name_len && de->inode) {
ext4fs_dirha... | 42,467,272,806,976,600,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 |
33,610 | 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 | static inline unsigned dx_node_limit(struct inode *dir)
{
unsigned entry_space = dir->i_sb->s_blocksize - EXT4_DIR_REC_LEN(0);
if (EXT4_HAS_RO_COMPAT_FEATURE(dir->i_sb,
EXT4_FEATURE_RO_COMPAT_METADATA_CSUM))
entry_space -= sizeof(struct dx_tail);
return entry_space / sizeof(struct dx_entry);
}
| 248,037,681,111,827,070,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 |
33,611 | 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 | static struct ext4_dir_entry_2* dx_pack_dirents(char *base, unsigned blocksize)
{
struct ext4_dir_entry_2 *next, *to, *prev, *de = (struct ext4_dir_entry_2 *) base;
unsigned rec_len = 0;
prev = to = de;
while ((char*)de < base + blocksize) {
next = ext4_next_entry(de, blocksize);
if (de->inode && de->name_len)... | 22,836,969,824,157,703,000,000,000,000,000,000,000 | namei.c | 113,178,550,349,909,030,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 |
33,612 | 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 | dx_probe(const struct qstr *d_name, struct inode *dir,
struct dx_hash_info *hinfo, struct dx_frame *frame_in, int *err)
{
unsigned count, indirect;
struct dx_entry *at, *entries, *p, *q, *m;
struct dx_root *root;
struct buffer_head *bh;
struct dx_frame *frame = frame_in;
u32 hash;
frame->bh = NULL;
if (!(bh ... | 307,519,041,714,020,670,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 |
33,613 | 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 | static void dx_release (struct dx_frame *frames)
{
if (frames[0].bh == NULL)
return;
if (((struct dx_root *) frames[0].bh->b_data)->info.indirect_levels)
brelse(frames[1].bh);
brelse(frames[0].bh);
}
| 254,429,145,414,133,100,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 |
33,614 | 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 | static inline unsigned dx_root_limit(struct inode *dir, unsigned infosize)
{
unsigned entry_space = dir->i_sb->s_blocksize - EXT4_DIR_REC_LEN(1) -
EXT4_DIR_REC_LEN(2) - infosize;
if (EXT4_HAS_RO_COMPAT_FEATURE(dir->i_sb,
EXT4_FEATURE_RO_COMPAT_METADATA_CSUM))
entry_space -= sizeof(struct dx_tail);
re... | 228,864,338,792,079,040,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 |
33,615 | 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 | static inline void dx_set_count(struct dx_entry *entries, unsigned value)
{
((struct dx_countlimit *) entries)->count = cpu_to_le16(value);
}
| 321,021,184,596,677,700,000,000,000,000,000,000,000 | namei.c | 113,178,550,349,909,030,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 |
33,616 | 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 | static inline void dx_set_hash(struct dx_entry *entry, unsigned value)
{
entry->hash = cpu_to_le32(value);
}
| 194,864,089,752,501,370,000,000,000,000,000,000,000 | namei.c | 113,178,550,349,909,030,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 |
33,617 | 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 | struct stats dx_show_entries(struct dx_hash_info *hinfo, struct inode *dir,
struct dx_entry *entries, int levels)
{
unsigned blocksize = dir->i_sb->s_blocksize;
unsigned count = dx_get_count(entries), names = 0, space = 0, i;
unsigned bcount = 0;
struct buffer_head *bh;
int err;
printk("%i indexed blocks.... | 70,412,904,236,210,350,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 |
33,618 | 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 | static void dx_show_index(char * label, struct dx_entry *entries)
{
int i, n = dx_get_count (entries);
printk(KERN_DEBUG "%s index ", label);
for (i = 0; i < n; i++) {
printk("%x->%lu ", i ? dx_get_hash(entries + i) :
0, (unsigned long)dx_get_block(entries + i));
}
printk("\n");
}
| 173,944,468,410,008,500,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 |
33,619 | 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 | static struct stats dx_show_leaf(struct dx_hash_info *hinfo, struct ext4_dir_entry_2 *de,
int size, int show_names)
{
unsigned names = 0, space = 0;
char *base = (char *) de;
struct dx_hash_info h = *hinfo;
printk("names: ");
while ((char *) de < base + size)
{
if (de->inode)
{
if (show_names)
{
... | 140,544,124,113,624,100,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 |
33,620 | 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 | static void dx_sort_map (struct dx_map_entry *map, unsigned count)
{
struct dx_map_entry *p, *q, *top = map + count - 1;
int more;
/* Combsort until bubble sort doesn't suck */
while (count > 2) {
count = count*10/13;
if (count - 9 < 2) /* 9, 10 -> 11 */
count = 11;
for (p = top, q = p - count; q >= map; p... | 5,753,550,533,079,050,000,000,000,000,000,000,000 | namei.c | 113,178,550,349,909,030,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 |
33,621 | 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 | static int empty_dir(struct inode *inode)
{
unsigned int offset;
struct buffer_head *bh;
struct ext4_dir_entry_2 *de, *de1;
struct super_block *sb;
int err = 0;
if (ext4_has_inline_data(inode)) {
int has_inline_data = 1;
err = empty_inline_dir(inode, &has_inline_data);
if (has_inline_data)
return err;
... | 139,620,580,257,502,780,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 |
33,622 | 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 | static int ext4_add_entry(handle_t *handle, struct dentry *dentry,
struct inode *inode)
{
struct inode *dir = dentry->d_parent->d_inode;
struct buffer_head *bh;
struct ext4_dir_entry_2 *de;
struct ext4_dir_entry_tail *t;
struct super_block *sb;
int retval;
int dx_fallback=0;
unsigned blocksize;
ext4_lblk_... | 56,569,261,572,609,500,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 |
33,623 | 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 | static int ext4_add_nondir(handle_t *handle,
struct dentry *dentry, struct inode *inode)
{
int err = ext4_add_entry(handle, dentry, inode);
if (!err) {
ext4_mark_inode_dirty(handle, inode);
unlock_new_inode(inode);
d_instantiate(dentry, inode);
return 0;
}
drop_nlink(inode);
unlock_new_inode(inode);
ipu... | 25,101,550,190,246,260,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 |
33,624 | 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 | static struct buffer_head *ext4_append(handle_t *handle,
struct inode *inode,
ext4_lblk_t *block, int *err)
{
struct buffer_head *bh;
if (unlikely(EXT4_SB(inode->i_sb)->s_max_dir_size_kb &&
((inode->i_size >> 10) >=
EXT4_SB(inode->i_sb)->s_max_dir_size_kb))) {
*err = -ENOSPC;
return NULL... | 246,506,935,351,303,640,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 |
33,625 | 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 | static int ext4_create(struct inode *dir, struct dentry *dentry, umode_t mode,
bool excl)
{
handle_t *handle;
struct inode *inode;
int err, retries = 0;
dquot_initialize(dir);
retry:
handle = ext4_journal_start(dir, EXT4_DATA_TRANS_BLOCKS(dir->i_sb) +
EXT4_INDEX_EXTRA_TRANS_BLOCKS + 3 +
EXT4_M... | 2,312,524,823,411,751,700,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 |
33,626 | 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 | static void ext4_dec_count(handle_t *handle, struct inode *inode)
{
if (!S_ISDIR(inode->i_mode) || inode->i_nlink > 2)
drop_nlink(inode);
}
| 279,841,697,756,492,260,000,000,000,000,000,000,000 | namei.c | 113,178,550,349,909,030,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 |
33,627 | 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 | static int ext4_delete_entry(handle_t *handle,
struct inode *dir,
struct ext4_dir_entry_2 *de_del,
struct buffer_head *bh)
{
int err, csum_size = 0;
if (ext4_has_inline_data(dir)) {
int has_inline_data = 1;
err = ext4_delete_inline_entry(handle, dir, de_del, bh,
&has_inline_da... | 178,702,896,644,669,250,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 |
33,628 | 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 | static __le32 ext4_dirent_csum(struct inode *inode,
struct ext4_dir_entry *dirent, int size)
{
struct ext4_sb_info *sbi = EXT4_SB(inode->i_sb);
struct ext4_inode_info *ei = EXT4_I(inode);
__u32 csum;
csum = ext4_chksum(sbi, ei->i_csum_seed, (__u8 *)dirent, size);
return cpu_to_le32(csum);
}
| 322,342,169,086,703,780,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 |
33,629 | 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 | static void ext4_dirent_csum_set(struct inode *inode,
struct ext4_dir_entry *dirent)
{
struct ext4_dir_entry_tail *t;
if (!EXT4_HAS_RO_COMPAT_FEATURE(inode->i_sb,
EXT4_FEATURE_RO_COMPAT_METADATA_CSUM))
return;
t = get_dirent_tail(inode, dirent);
if (!t) {
warn_no_space_for_csum(inode);
return;
}
... | 323,746,917,758,709,000,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 |
33,630 | 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_dirent_csum_verify(struct inode *inode, struct ext4_dir_entry *dirent)
{
struct ext4_dir_entry_tail *t;
if (!EXT4_HAS_RO_COMPAT_FEATURE(inode->i_sb,
EXT4_FEATURE_RO_COMPAT_METADATA_CSUM))
return 1;
t = get_dirent_tail(inode, dirent);
if (!t) {
warn_no_space_for_csum(inode);
return 0;
}
if (... | 303,100,204,381,040,540,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 |
33,631 | 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 | static __le32 ext4_dx_csum(struct inode *inode, struct ext4_dir_entry *dirent,
int count_offset, int count, struct dx_tail *t)
{
struct ext4_sb_info *sbi = EXT4_SB(inode->i_sb);
struct ext4_inode_info *ei = EXT4_I(inode);
__u32 csum, old_csum;
int size;
size = count_offset + (count * sizeof(struct dx_entry)... | 180,257,514,315,834,940,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 |
33,632 | 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 | static void ext4_dx_csum_set(struct inode *inode, struct ext4_dir_entry *dirent)
{
struct dx_countlimit *c;
struct dx_tail *t;
int count_offset, limit, count;
if (!EXT4_HAS_RO_COMPAT_FEATURE(inode->i_sb,
EXT4_FEATURE_RO_COMPAT_METADATA_CSUM))
return;
c = get_dx_countlimit(inode, dirent, &count_offset);
i... | 266,383,406,168,032,050,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 |
33,633 | 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 | static int ext4_dx_csum_verify(struct inode *inode,
struct ext4_dir_entry *dirent)
{
struct dx_countlimit *c;
struct dx_tail *t;
int count_offset, limit, count;
if (!EXT4_HAS_RO_COMPAT_FEATURE(inode->i_sb,
EXT4_FEATURE_RO_COMPAT_METADATA_CSUM))
return 1;
c = get_dx_countlimit(inode, dirent, &cou... | 75,577,368,414,829,810,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 |
33,634 | 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 | static struct buffer_head * ext4_dx_find_entry(struct inode *dir, const struct qstr *d_name,
struct ext4_dir_entry_2 **res_dir, int *err)
{
struct super_block * sb = dir->i_sb;
struct dx_hash_info hinfo;
struct dx_frame frames[2], *frame;
struct buffer_head *bh;
ext4_lblk_t block;
int retval;
if (!(fra... | 40,416,839,061,472,413,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 |
33,635 | 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_find_dest_de(struct inode *dir, struct inode *inode,
struct buffer_head *bh,
void *buf, int buf_size,
const char *name, int namelen,
struct ext4_dir_entry_2 **dest_de)
{
struct ext4_dir_entry_2 *de;
unsigned short reclen = EXT4_DIR_REC_LEN(namelen);
int nlen, rlen;
unsigned ... | 50,817,794,438,385,570,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 |
33,636 | 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 | static struct buffer_head * ext4_find_entry (struct inode *dir,
const struct qstr *d_name,
struct ext4_dir_entry_2 **res_dir,
int *inlined)
{
struct super_block *sb;
struct buffer_head *bh_use[NAMEI_RA_SIZE];
struct buffer_head *bh, *ret = NULL;
ext4_lblk_t start, block, b;
const u8 *name = d_name->... | 243,858,537,017,659,870,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 |
33,637 | 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_generic_delete_entry(handle_t *handle,
struct inode *dir,
struct ext4_dir_entry_2 *de_del,
struct buffer_head *bh,
void *entry_buf,
int buf_size,
int csum_size)
{
struct ext4_dir_entry_2 *de, *pde;
unsigned int blocksize = dir->i_sb->s_blocksize;
int i;
... | 274,649,983,299,421,300,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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.