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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
517,126 | mjg59_linux | a4a5ed2835e8ea042868b7401dced3f517cafa76 | None | None | acpi: Disable ACPI table override if securelevel is set
From the kernel documentation (initrd_table_override.txt):
If the ACPI_INITRD_TABLE_OVERRIDE compile option is true, it is possible
to override nearly any ACPI table provided by the BIOS with an
instrumented, modified one.
When securelevel is set, the ker... | 0 | void acpi_os_printf(const char *fmt, ...)
{
va_list args;
va_start(args, fmt);
acpi_os_vprintf(fmt, args);
va_end(args);
} | 252,763,057,755,940,550,000,000,000,000,000,000,000 | None | null | [] | None | None | https://nvd.nist.gov/vuln/detail/None |
517,127 | mjg59_linux | a4a5ed2835e8ea042868b7401dced3f517cafa76 | None | None | acpi: Disable ACPI table override if securelevel is set
From the kernel documentation (initrd_table_override.txt):
If the ACPI_INITRD_TABLE_OVERRIDE compile option is true, it is possible
to override nearly any ACPI table provided by the BIOS with an
instrumented, modified one.
When securelevel is set, the ker... | 0 | u64 acpi_os_get_timer(void)
{
u64 time_ns = ktime_to_ns(ktime_get());
do_div(time_ns, 100);
return time_ns;
} | 304,730,012,290,322,360,000,000,000,000,000,000,000 | None | null | [] | None | None | https://nvd.nist.gov/vuln/detail/None |
517,128 | mjg59_linux | a4a5ed2835e8ea042868b7401dced3f517cafa76 | None | None | acpi: Disable ACPI table override if securelevel is set
From the kernel documentation (initrd_table_override.txt):
If the ACPI_INITRD_TABLE_OVERRIDE compile option is true, it is possible
to override nearly any ACPI table provided by the BIOS with an
instrumented, modified one.
When securelevel is set, the ker... | 0 | int acpi_debugger_notify_command_complete(void)
{
int ret;
int (*func)(void);
struct module *owner;
if (!acpi_debugger_initialized)
return -ENODEV;
mutex_lock(&acpi_debugger.lock);
if (!acpi_debugger.ops) {
ret = -ENODEV;
goto err_lock;
}
if (!try_module_get(acpi_debugger.owner)) {
ret = -ENODEV;
got... | 89,529,054,752,834,000,000,000,000,000,000,000,000 | None | null | [] | None | None | https://nvd.nist.gov/vuln/detail/None |
517,129 | mjg59_linux | a4a5ed2835e8ea042868b7401dced3f517cafa76 | None | None | acpi: Disable ACPI table override if securelevel is set
From the kernel documentation (initrd_table_override.txt):
If the ACPI_INITRD_TABLE_OVERRIDE compile option is true, it is possible
to override nearly any ACPI table provided by the BIOS with an
instrumented, modified one.
When securelevel is set, the ker... | 0 | acpi_map_lookup(acpi_physical_address phys, acpi_size size)
{
struct acpi_ioremap *map;
list_for_each_entry_rcu(map, &acpi_ioremaps, list)
if (map->phys <= phys &&
phys + size <= map->phys + map->size)
return map;
return NULL;
} | 90,461,473,498,353,150,000,000,000,000,000,000,000 | None | null | [] | None | None | https://nvd.nist.gov/vuln/detail/None |
517,130 | mjg59_linux | a4a5ed2835e8ea042868b7401dced3f517cafa76 | None | None | acpi: Disable ACPI table override if securelevel is set
From the kernel documentation (initrd_table_override.txt):
If the ACPI_INITRD_TABLE_OVERRIDE compile option is true, it is possible
to override nearly any ACPI table provided by the BIOS with an
instrumented, modified one.
When securelevel is set, the ker... | 0 | void __init acpi_initrd_override(void *data, size_t size)
{
int sig, no, table_nr = 0, total_offset = 0;
long offset = 0;
struct acpi_table_header *table;
char cpio_path[32] = "kernel/firmware/acpi/";
struct cpio_data file;
if (data == NULL || size == 0)
return;
for (no = 0; no < ACPI_OVERRIDE_TABLES; no++) ... | 23,918,808,107,707,700,000,000,000,000,000,000,000 | None | null | [] | None | None | https://nvd.nist.gov/vuln/detail/None |
517,131 | mjg59_linux | a4a5ed2835e8ea042868b7401dced3f517cafa76 | None | None | acpi: Disable ACPI table override if securelevel is set
From the kernel documentation (initrd_table_override.txt):
If the ACPI_INITRD_TABLE_OVERRIDE compile option is true, it is possible
to override nearly any ACPI table provided by the BIOS with an
instrumented, modified one.
When securelevel is set, the ker... | 0 | void __init acpi_initrd_initialize_tables(void)
{
} | 225,041,146,393,883,720,000,000,000,000,000,000,000 | None | null | [] | None | None | https://nvd.nist.gov/vuln/detail/None |
517,132 | mjg59_linux | a4a5ed2835e8ea042868b7401dced3f517cafa76 | None | None | acpi: Disable ACPI table override if securelevel is set
From the kernel documentation (initrd_table_override.txt):
If the ACPI_INITRD_TABLE_OVERRIDE compile option is true, it is possible
to override nearly any ACPI table provided by the BIOS with an
instrumented, modified one.
When securelevel is set, the ker... | 0 | void __init acpi_dmi_osi_linux(int enable, const struct dmi_system_id *d)
{
printk(KERN_NOTICE PREFIX "DMI detected: %s\n", d->ident);
if (enable == -1)
return;
osi_linux.dmi = 1; /* DMI knows that this box asks OSI(Linux) */
set_osi_linux(enable);
return;
} | 78,030,894,625,757,810,000,000,000,000,000,000,000 | None | null | [] | None | None | https://nvd.nist.gov/vuln/detail/None |
517,133 | mjg59_linux | a4a5ed2835e8ea042868b7401dced3f517cafa76 | None | None | acpi: Disable ACPI table override if securelevel is set
From the kernel documentation (initrd_table_override.txt):
If the ACPI_INITRD_TABLE_OVERRIDE compile option is true, it is possible
to override nearly any ACPI table provided by the BIOS with an
instrumented, modified one.
When securelevel is set, the ker... | 0 | acpi_status acpi_os_terminate(void)
{
if (acpi_irq_handler) {
acpi_os_remove_interrupt_handler(acpi_gbl_FADT.sci_interrupt,
acpi_irq_handler);
}
acpi_os_unmap_generic_address(&acpi_gbl_FADT.xgpe1_block);
acpi_os_unmap_generic_address(&acpi_gbl_FADT.xgpe0_block);
acpi_os_unmap_generic_address(&acpi_gbl_FA... | 73,361,721,288,865,860,000,000,000,000,000,000,000 | None | null | [] | None | None | https://nvd.nist.gov/vuln/detail/None |
517,134 | mjg59_linux | a4a5ed2835e8ea042868b7401dced3f517cafa76 | None | None | acpi: Disable ACPI table override if securelevel is set
From the kernel documentation (initrd_table_override.txt):
If the ACPI_INITRD_TABLE_OVERRIDE compile option is true, it is possible
to override nearly any ACPI table provided by the BIOS with an
instrumented, modified one.
When securelevel is set, the ker... | 0 | void __iomem *acpi_os_get_iomem(acpi_physical_address phys, unsigned int size)
{
struct acpi_ioremap *map;
void __iomem *virt = NULL;
mutex_lock(&acpi_ioremap_lock);
map = acpi_map_lookup(phys, size);
if (map) {
virt = map->virt + (phys - map->phys);
map->refcount++;
}
mutex_unlock(&acpi_ioremap_lock);
ret... | 35,403,248,841,521,403,000,000,000,000,000,000,000 | None | null | [] | None | None | https://nvd.nist.gov/vuln/detail/None |
517,135 | mjg59_linux | a4a5ed2835e8ea042868b7401dced3f517cafa76 | None | None | acpi: Disable ACPI table override if securelevel is set
From the kernel documentation (initrd_table_override.txt):
If the ACPI_INITRD_TABLE_OVERRIDE compile option is true, it is possible
to override nearly any ACPI table provided by the BIOS with an
instrumented, modified one.
When securelevel is set, the ker... | 0 | void __ref acpi_os_unmap_memory(void *virt, acpi_size size)
{
return acpi_os_unmap_iomem((void __iomem *)virt, size);
} | 149,478,984,193,158,440,000,000,000,000,000,000,000 | None | null | [] | None | None | https://nvd.nist.gov/vuln/detail/None |
517,136 | mjg59_linux | a4a5ed2835e8ea042868b7401dced3f517cafa76 | None | None | acpi: Disable ACPI table override if securelevel is set
From the kernel documentation (initrd_table_override.txt):
If the ACPI_INITRD_TABLE_OVERRIDE compile option is true, it is possible
to override nearly any ACPI table provided by the BIOS with an
instrumented, modified one.
When securelevel is set, the ker... | 0 | static void __init acpi_request_region (struct acpi_generic_address *gas,
unsigned int length, char *desc)
{
u64 addr;
/* Handle possible alignment issues */
memcpy(&addr, &gas->address, sizeof(addr));
if (!addr || !length)
return;
/* Resources are never freed */
if (gas->space_id == ACPI_ADR_SPACE_SYSTEM_IO... | 156,246,188,293,164,070,000,000,000,000,000,000,000 | None | null | [] | None | None | https://nvd.nist.gov/vuln/detail/None |
517,137 | mjg59_linux | a4a5ed2835e8ea042868b7401dced3f517cafa76 | None | None | acpi: Disable ACPI table override if securelevel is set
From the kernel documentation (initrd_table_override.txt):
If the ACPI_INITRD_TABLE_OVERRIDE compile option is true, it is possible
to override nearly any ACPI table provided by the BIOS with an
instrumented, modified one.
When securelevel is set, the ker... | 0 | acpi_os_table_override(struct acpi_table_header *existing_table,
struct acpi_table_header **new_table)
{
if (!existing_table || !new_table)
return AE_BAD_PARAMETER;
*new_table = NULL;
#ifdef CONFIG_ACPI_CUSTOM_DSDT
if (strncmp(existing_table->signature, "DSDT", 4) == 0)
*new_table = (struct acpi_table... | 215,317,147,356,817,450,000,000,000,000,000,000,000 | None | null | [] | None | None | https://nvd.nist.gov/vuln/detail/None |
517,138 | mjg59_linux | a4a5ed2835e8ea042868b7401dced3f517cafa76 | None | None | acpi: Disable ACPI table override if securelevel is set
From the kernel documentation (initrd_table_override.txt):
If the ACPI_INITRD_TABLE_OVERRIDE compile option is true, it is possible
to override nearly any ACPI table provided by the BIOS with an
instrumented, modified one.
When securelevel is set, the ker... | 0 | static void __iomem *acpi_map(acpi_physical_address pg_off, unsigned long pg_sz)
{
unsigned long pfn;
pfn = pg_off >> PAGE_SHIFT;
if (should_use_kmap(pfn)) {
if (pg_sz > PAGE_SIZE)
return NULL;
return (void __iomem __force *)kmap(pfn_to_page(pfn));
} else
return acpi_os_ioremap(pg_off, pg_sz);
} | 258,732,286,030,003,500,000,000,000,000,000,000,000 | None | null | [] | None | None | https://nvd.nist.gov/vuln/detail/None |
517,139 | mjg59_linux | a4a5ed2835e8ea042868b7401dced3f517cafa76 | None | None | acpi: Disable ACPI table override if securelevel is set
From the kernel documentation (initrd_table_override.txt):
If the ACPI_INITRD_TABLE_OVERRIDE compile option is true, it is possible
to override nearly any ACPI table provided by the BIOS with an
instrumented, modified one.
When securelevel is set, the ker... | 0 | static int __init acpi_reserve_resources(void)
{
acpi_request_region(&acpi_gbl_FADT.xpm1a_event_block, acpi_gbl_FADT.pm1_event_length,
"ACPI PM1a_EVT_BLK");
acpi_request_region(&acpi_gbl_FADT.xpm1b_event_block, acpi_gbl_FADT.pm1_event_length,
"ACPI PM1b_EVT_BLK");
acpi_request_region(&acpi_gbl_FADT.xpm1a_contr... | 72,913,605,658,307,910,000,000,000,000,000,000,000 | None | null | [] | None | None | https://nvd.nist.gov/vuln/detail/None |
517,140 | mjg59_linux | a4a5ed2835e8ea042868b7401dced3f517cafa76 | None | None | acpi: Disable ACPI table override if securelevel is set
From the kernel documentation (initrd_table_override.txt):
If the ACPI_INITRD_TABLE_OVERRIDE compile option is true, it is possible
to override nearly any ACPI table provided by the BIOS with an
instrumented, modified one.
When securelevel is set, the ker... | 0 | acpi_status acpi_os_remove_interrupt_handler(u32 gsi, acpi_osd_handler handler)
{
if (gsi != acpi_gbl_FADT.sci_interrupt || !acpi_sci_irq_valid())
return AE_BAD_PARAMETER;
free_irq(acpi_sci_irq, acpi_irq);
acpi_irq_handler = NULL;
acpi_sci_irq = INVALID_ACPI_IRQ;
return AE_OK;
} | 220,001,499,434,713,640,000,000,000,000,000,000,000 | None | null | [] | None | None | https://nvd.nist.gov/vuln/detail/None |
517,141 | mjg59_linux | a4a5ed2835e8ea042868b7401dced3f517cafa76 | None | None | acpi: Disable ACPI table override if securelevel is set
From the kernel documentation (initrd_table_override.txt):
If the ACPI_INITRD_TABLE_OVERRIDE compile option is true, it is possible
to override nearly any ACPI table provided by the BIOS with an
instrumented, modified one.
When securelevel is set, the ker... | 0 | bool acpi_queue_hotplug_work(struct work_struct *work)
{
return queue_work(kacpi_hotplug_wq, work);
} | 245,387,609,846,345,600,000,000,000,000,000,000,000 | None | null | [] | None | None | https://nvd.nist.gov/vuln/detail/None |
517,142 | mjg59_linux | a4a5ed2835e8ea042868b7401dced3f517cafa76 | None | None | acpi: Disable ACPI table override if securelevel is set
From the kernel documentation (initrd_table_override.txt):
If the ACPI_INITRD_TABLE_OVERRIDE compile option is true, it is possible
to override nearly any ACPI table provided by the BIOS with an
instrumented, modified one.
When securelevel is set, the ker... | 0 | acpi_status acpi_os_delete_cache(acpi_cache_t * cache)
{
kmem_cache_destroy(cache);
return (AE_OK);
} | 177,850,978,229,829,470,000,000,000,000,000,000,000 | None | null | [] | None | None | https://nvd.nist.gov/vuln/detail/None |
517,143 | mjg59_linux | a4a5ed2835e8ea042868b7401dced3f517cafa76 | None | None | acpi: Disable ACPI table override if securelevel is set
From the kernel documentation (initrd_table_override.txt):
If the ACPI_INITRD_TABLE_OVERRIDE compile option is true, it is possible
to override nearly any ACPI table provided by the BIOS with an
instrumented, modified one.
When securelevel is set, the ker... | 0 | int acpi_register_debugger(struct module *owner,
const struct acpi_debugger_ops *ops)
{
int ret = 0;
mutex_lock(&acpi_debugger.lock);
if (acpi_debugger.ops) {
ret = -EBUSY;
goto err_lock;
}
acpi_debugger.owner = owner;
acpi_debugger.ops = ops;
err_lock:
mutex_unlock(&acpi_debugger.lock);
return ret... | 195,066,723,945,306,800,000,000,000,000,000,000,000 | None | null | [] | None | None | https://nvd.nist.gov/vuln/detail/None |
517,144 | mjg59_linux | a4a5ed2835e8ea042868b7401dced3f517cafa76 | None | None | acpi: Disable ACPI table override if securelevel is set
From the kernel documentation (initrd_table_override.txt):
If the ACPI_INITRD_TABLE_OVERRIDE compile option is true, it is possible
to override nearly any ACPI table provided by the BIOS with an
instrumented, modified one.
When securelevel is set, the ker... | 0 | int acpi_debugger_create_thread(acpi_osd_exec_callback function, void *context)
{
int ret;
int (*func)(acpi_osd_exec_callback, void *);
struct module *owner;
if (!acpi_debugger_initialized)
return -ENODEV;
mutex_lock(&acpi_debugger.lock);
if (!acpi_debugger.ops) {
ret = -ENODEV;
goto err_lock;
}
if (!try... | 209,400,751,258,666,650,000,000,000,000,000,000,000 | None | null | [] | None | None | https://nvd.nist.gov/vuln/detail/None |
517,145 | mjg59_linux | a4a5ed2835e8ea042868b7401dced3f517cafa76 | None | None | acpi: Disable ACPI table override if securelevel is set
From the kernel documentation (initrd_table_override.txt):
If the ACPI_INITRD_TABLE_OVERRIDE compile option is true, it is possible
to override nearly any ACPI table provided by the BIOS with an
instrumented, modified one.
When securelevel is set, the ker... | 0 | static int __init osi_setup(char *str)
{
if (str && !strcmp("Linux", str))
acpi_cmdline_osi_linux(1);
else if (str && !strcmp("!Linux", str))
acpi_cmdline_osi_linux(0);
else
acpi_osi_setup(str);
return 1;
} | 86,014,015,430,699,150,000,000,000,000,000,000,000 | None | null | [] | None | None | https://nvd.nist.gov/vuln/detail/None |
517,146 | mjg59_linux | a4a5ed2835e8ea042868b7401dced3f517cafa76 | None | None | acpi: Disable ACPI table override if securelevel is set
From the kernel documentation (initrd_table_override.txt):
If the ACPI_INITRD_TABLE_OVERRIDE compile option is true, it is possible
to override nearly any ACPI table provided by the BIOS with an
instrumented, modified one.
When securelevel is set, the ker... | 0 | int acpi_check_resource_conflict(const struct resource *res)
{
acpi_adr_space_type space_id;
acpi_size length;
u8 warn = 0;
int clash = 0;
if (acpi_enforce_resources == ENFORCE_RESOURCES_NO)
return 0;
if (!(res->flags & IORESOURCE_IO) && !(res->flags & IORESOURCE_MEM))
return 0;
if (res->flags & IORESOURCE... | 32,558,252,171,953,832,000,000,000,000,000,000,000 | None | null | [] | None | None | https://nvd.nist.gov/vuln/detail/None |
517,147 | mjg59_linux | a4a5ed2835e8ea042868b7401dced3f517cafa76 | None | None | acpi: Disable ACPI table override if securelevel is set
From the kernel documentation (initrd_table_override.txt):
If the ACPI_INITRD_TABLE_OVERRIDE compile option is true, it is possible
to override nearly any ACPI table provided by the BIOS with an
instrumented, modified one.
When securelevel is set, the ker... | 0 | acpi_status acpi_hotplug_schedule(struct acpi_device *adev, u32 src)
{
struct acpi_hp_work *hpw;
ACPI_DEBUG_PRINT((ACPI_DB_EXEC,
"Scheduling hotplug event (%p, %u) for deferred execution.\n",
adev, src));
hpw = kmalloc(sizeof(*hpw), GFP_KERNEL);
if (!hpw)
return AE_NO_MEMORY;
INIT_WORK(&hpw->work, acp... | 110,879,561,096,260,320,000,000,000,000,000,000,000 | None | null | [] | None | None | https://nvd.nist.gov/vuln/detail/None |
517,148 | mjg59_linux | a4a5ed2835e8ea042868b7401dced3f517cafa76 | None | None | acpi: Disable ACPI table override if securelevel is set
From the kernel documentation (initrd_table_override.txt):
If the ACPI_INITRD_TABLE_OVERRIDE compile option is true, it is possible
to override nearly any ACPI table provided by the BIOS with an
instrumented, modified one.
When securelevel is set, the ker... | 0 | acpi_os_read_memory(acpi_physical_address phys_addr, u64 *value, u32 width)
{
void __iomem *virt_addr;
unsigned int size = width / 8;
bool unmap = false;
u64 dummy;
rcu_read_lock();
virt_addr = acpi_map_vaddr_lookup(phys_addr, size);
if (!virt_addr) {
rcu_read_unlock();
virt_addr = acpi_os_ioremap(phys_addr... | 129,616,207,551,317,730,000,000,000,000,000,000,000 | None | null | [] | None | None | https://nvd.nist.gov/vuln/detail/None |
517,168 | pam_radius | 01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | https://github.com/FreeRADIUS/pam_radius | https://github.com/FreeRADIUS/pam_radius/commit/01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | Use "length", which has been limited in size | 0 | PAM_EXTERN int pam_sm_chauthtok(pam_handle_t *pamh, int flags, int argc, CONST char **argv)
{
CONST char *user;
char *password = NULL;
char *new_password = NULL;
char *check_password = NULL;
int ctrl;
int retval = PAM_AUTHTOK_ERR;
int attempts;
char recv_buffer[4096];
char send_buffer[4096];
AUTH_HDR *reques... | 76,097,103,322,706,460,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2015-9542 | add_password in pam_radius_auth.c in pam_radius 1.4.0 does not correctly check the length of the input password, and is vulnerable to a stack-based buffer overflow during memcpy(). An attacker could send a crafted password to an application (loading the pam_radius library) and crash it. Arbitrary code execution might b... | https://nvd.nist.gov/vuln/detail/CVE-2015-9542 |
517,169 | pam_radius | 01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | https://github.com/FreeRADIUS/pam_radius | https://github.com/FreeRADIUS/pam_radius/commit/01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | Use "length", which has been limited in size | 0 | static int _pam_parse(int argc, CONST char **argv, radius_conf_t *conf)
{
int ctrl=0;
memset(conf, 0, sizeof(radius_conf_t)); /* ensure it's initialized */
strcpy(conf_file, CONF_FILE);
/* set the default prompt */
snprintf(conf->prompt, MAXPROMPT, "%s: ", DEFAULT_PROMPT);
/*
* If either is not there, then ... | 235,048,926,088,024,770,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2015-9542 | add_password in pam_radius_auth.c in pam_radius 1.4.0 does not correctly check the length of the input password, and is vulnerable to a stack-based buffer overflow during memcpy(). An attacker could send a crafted password to an application (loading the pam_radius library) and crash it. Arbitrary code execution might b... | https://nvd.nist.gov/vuln/detail/CVE-2015-9542 |
517,170 | pam_radius | 01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | https://github.com/FreeRADIUS/pam_radius | https://github.com/FreeRADIUS/pam_radius/commit/01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | Use "length", which has been limited in size | 0 | static int verify_packet(char *secret, AUTH_HDR *response, AUTH_HDR *request)
{
MD5_CTX my_md5;
unsigned char calculated[AUTH_VECTOR_LEN];
unsigned char reply[AUTH_VECTOR_LEN];
/*
* We could dispense with the memcpy, and do MD5's of the packet
* + vector piece by piece. This is easier understand, and maybe fas... | 62,182,153,545,706,220,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2015-9542 | add_password in pam_radius_auth.c in pam_radius 1.4.0 does not correctly check the length of the input password, and is vulnerable to a stack-based buffer overflow during memcpy(). An attacker could send a crafted password to an application (loading the pam_radius library) and crash it. Arbitrary code execution might b... | https://nvd.nist.gov/vuln/detail/CVE-2015-9542 |
517,171 | pam_radius | 01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | https://github.com/FreeRADIUS/pam_radius | https://github.com/FreeRADIUS/pam_radius/commit/01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | Use "length", which has been limited in size | 0 | static void cleanup(radius_server_t *server)
{
radius_server_t *next;
while (server) {
next = server->next;
_pam_drop(server->hostname);
_pam_forget(server->secret);
_pam_drop(server);
server = next;
}
} | 332,048,750,631,102,730,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2015-9542 | add_password in pam_radius_auth.c in pam_radius 1.4.0 does not correctly check the length of the input password, and is vulnerable to a stack-based buffer overflow during memcpy(). An attacker could send a crafted password to an application (loading the pam_radius library) and crash it. Arbitrary code execution might b... | https://nvd.nist.gov/vuln/detail/CVE-2015-9542 |
517,172 | pam_radius | 01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | https://github.com/FreeRADIUS/pam_radius | https://github.com/FreeRADIUS/pam_radius/commit/01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | Use "length", which has been limited in size | 0 | static uint32_t get_ipaddr(char *host) {
struct hostent *hp;
if (good_ipaddr(host) == 0) {
return ipstr2long(host);
} else if ((hp = gethostbyname(host)) == (struct hostent *)NULL) {
return (uint32_t)0;
}
return ntohl(*(uint32_t *)hp->h_addr);
} | 109,900,176,676,289,040,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2015-9542 | add_password in pam_radius_auth.c in pam_radius 1.4.0 does not correctly check the length of the input password, and is vulnerable to a stack-based buffer overflow during memcpy(). An attacker could send a crafted password to an application (loading the pam_radius library) and crash it. Arbitrary code execution might b... | https://nvd.nist.gov/vuln/detail/CVE-2015-9542 |
517,173 | pam_radius | 01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | https://github.com/FreeRADIUS/pam_radius | https://github.com/FreeRADIUS/pam_radius/commit/01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | Use "length", which has been limited in size | 0 | static int rad_converse(pam_handle_t *pamh, int msg_style, char *message, char **password)
{
CONST struct pam_conv *conv;
struct pam_message resp_msg;
CONST struct pam_message *msg[1];
struct pam_response *resp = NULL;
int retval;
resp_msg.msg_style = msg_style;
resp_msg.msg = message;
msg[0] = &resp_msg;
/*... | 201,930,132,387,218,280,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2015-9542 | add_password in pam_radius_auth.c in pam_radius 1.4.0 does not correctly check the length of the input password, and is vulnerable to a stack-based buffer overflow during memcpy(). An attacker could send a crafted password to an application (loading the pam_radius library) and crash it. Arbitrary code execution might b... | https://nvd.nist.gov/vuln/detail/CVE-2015-9542 |
517,174 | pam_radius | 01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | https://github.com/FreeRADIUS/pam_radius | https://github.com/FreeRADIUS/pam_radius/commit/01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | Use "length", which has been limited in size | 0 | static int good_ipaddr(char *addr) {
int dot_count;
int digit_count;
dot_count = 0;
digit_count = 0;
while(*addr != '\0' && *addr != ' ') {
if (*addr == '.') {
dot_count++;
digit_count = 0;
} else if (!isdigit(*addr)) {
dot_count = 5;
} else {
digit_count++;
if (digit_count > 3) {
dot_cou... | 21,853,919,757,367,240,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2015-9542 | add_password in pam_radius_auth.c in pam_radius 1.4.0 does not correctly check the length of the input password, and is vulnerable to a stack-based buffer overflow during memcpy(). An attacker could send a crafted password to an application (loading the pam_radius library) and crash it. Arbitrary code execution might b... | https://nvd.nist.gov/vuln/detail/CVE-2015-9542 |
517,175 | pam_radius | 01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | https://github.com/FreeRADIUS/pam_radius | https://github.com/FreeRADIUS/pam_radius/commit/01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | Use "length", which has been limited in size | 0 | static void get_random_vector(unsigned char *vector)
{
#ifdef linux
int fd = open("/dev/urandom",O_RDONLY); /* Linux: get *real* random numbers */
int total = 0;
if (fd >= 0) {
while (total < AUTH_VECTOR_LEN) {
int bytes = read(fd, vector + total, AUTH_VECTOR_LEN - total);
if (bytes <= 0)
break; /* oop... | 321,916,320,714,731,140,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2015-9542 | add_password in pam_radius_auth.c in pam_radius 1.4.0 does not correctly check the length of the input password, and is vulnerable to a stack-based buffer overflow during memcpy(). An attacker could send a crafted password to an application (loading the pam_radius library) and crash it. Arbitrary code execution might b... | https://nvd.nist.gov/vuln/detail/CVE-2015-9542 |
517,176 | pam_radius | 01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | https://github.com/FreeRADIUS/pam_radius | https://github.com/FreeRADIUS/pam_radius/commit/01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | Use "length", which has been limited in size | 0 | static attribute_t *find_attribute(AUTH_HDR *response, unsigned char type)
{
attribute_t *attr = (attribute_t *) &response->data;
int len = ntohs(response->length) - AUTH_HDR_LEN;
while (attr->attribute != type) {
if ((len -= attr->length) <= 0) {
return NULL; /* not found */
}
attr = (attribute_t *) ((c... | 98,690,024,748,178,180,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2015-9542 | add_password in pam_radius_auth.c in pam_radius 1.4.0 does not correctly check the length of the input password, and is vulnerable to a stack-based buffer overflow during memcpy(). An attacker could send a crafted password to an application (loading the pam_radius library) and crash it. Arbitrary code execution might b... | https://nvd.nist.gov/vuln/detail/CVE-2015-9542 |
517,177 | pam_radius | 01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | https://github.com/FreeRADIUS/pam_radius | https://github.com/FreeRADIUS/pam_radius/commit/01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | Use "length", which has been limited in size | 0 | static void add_attribute(AUTH_HDR *request, unsigned char type, CONST unsigned char *data, int length)
{
attribute_t *p;
p = (attribute_t *) ((unsigned char *)request + ntohs(request->length));
p->attribute = type;
p->length = length + 2; /* the total size of the attribute */
request->length = htons(ntohs(reque... | 247,750,604,005,317,280,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2015-9542 | add_password in pam_radius_auth.c in pam_radius 1.4.0 does not correctly check the length of the input password, and is vulnerable to a stack-based buffer overflow during memcpy(). An attacker could send a crafted password to an application (loading the pam_radius library) and crash it. Arbitrary code execution might b... | https://nvd.nist.gov/vuln/detail/CVE-2015-9542 |
517,178 | pam_radius | 01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | https://github.com/FreeRADIUS/pam_radius | https://github.com/FreeRADIUS/pam_radius/commit/01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | Use "length", which has been limited in size | 0 | static unsigned char * xor(unsigned char *p, unsigned char *q, int length)
{
int i;
unsigned char *retval = p;
for (i = 0; i < length; i++) {
*(p++) ^= *(q++);
}
return retval;
} | 63,879,229,354,166,900,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2015-9542 | add_password in pam_radius_auth.c in pam_radius 1.4.0 does not correctly check the length of the input password, and is vulnerable to a stack-based buffer overflow during memcpy(). An attacker could send a crafted password to an application (loading the pam_radius library) and crash it. Arbitrary code execution might b... | https://nvd.nist.gov/vuln/detail/CVE-2015-9542 |
517,179 | pam_radius | 01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | https://github.com/FreeRADIUS/pam_radius | https://github.com/FreeRADIUS/pam_radius/commit/01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | Use "length", which has been limited in size | 0 | static int talk_radius(radius_conf_t *conf, AUTH_HDR *request, AUTH_HDR *response,
char *password, char *old_password, int tries)
{
socklen_t salen;
int total_length;
fd_set set;
struct timeval tv;
time_t now, end;
int rcode;
struct sockaddr saremote;
struct sockaddr_in *s_in = (struct sockaddr_in *) &... | 204,873,572,493,404,400,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2015-9542 | add_password in pam_radius_auth.c in pam_radius 1.4.0 does not correctly check the length of the input password, and is vulnerable to a stack-based buffer overflow during memcpy(). An attacker could send a crafted password to an application (loading the pam_radius library) and crash it. Arbitrary code execution might b... | https://nvd.nist.gov/vuln/detail/CVE-2015-9542 |
517,180 | pam_radius | 01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | https://github.com/FreeRADIUS/pam_radius | https://github.com/FreeRADIUS/pam_radius/commit/01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | Use "length", which has been limited in size | 0 | PAM_EXTERN int pam_sm_setcred(pam_handle_t *pamh,int flags,int argc,CONST char **argv)
{
int retval, *pret;
retval = PAM_SUCCESS;
pret = &retval;
pam_get_data(pamh, "rad_setcred_return", (CONST void **) &pret);
return *pret;
} | 284,170,686,661,482,700,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2015-9542 | add_password in pam_radius_auth.c in pam_radius 1.4.0 does not correctly check the length of the input password, and is vulnerable to a stack-based buffer overflow during memcpy(). An attacker could send a crafted password to an application (loading the pam_radius library) and crash it. Arbitrary code execution might b... | https://nvd.nist.gov/vuln/detail/CVE-2015-9542 |
517,181 | pam_radius | 01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | https://github.com/FreeRADIUS/pam_radius | https://github.com/FreeRADIUS/pam_radius/commit/01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | Use "length", which has been limited in size | 0 | static int pam_private_session(pam_handle_t *pamh, int flags, int argc, CONST char **argv, int status)
{
CONST char *user;
int ctrl;
int retval = PAM_AUTH_ERR;
char recv_buffer[4096];
char send_buffer[4096];
AUTH_HDR *request = (AUTH_HDR *) send_buffer;
AUTH_HDR *response = (AUTH_HDR *) recv_buffer;
radius_con... | 306,649,450,925,057,100,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2015-9542 | add_password in pam_radius_auth.c in pam_radius 1.4.0 does not correctly check the length of the input password, and is vulnerable to a stack-based buffer overflow during memcpy(). An attacker could send a crafted password to an application (loading the pam_radius library) and crash it. Arbitrary code execution might b... | https://nvd.nist.gov/vuln/detail/CVE-2015-9542 |
517,182 | pam_radius | 01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | https://github.com/FreeRADIUS/pam_radius | https://github.com/FreeRADIUS/pam_radius/commit/01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | Use "length", which has been limited in size | 0 | static uint32_t ipstr2long(char *ip_str) {
char buf[6];
char *ptr;
int i;
int count;
uint32_t ipaddr;
int cur_byte;
ipaddr = (uint32_t)0;
for(i = 0;i < 4;i++) {
ptr = buf;
count = 0;
*ptr = '\0';
while(*ip_str != '.' && *ip_str != '\0' && count < 4) {
if (!isdigit(*ip_str)) {
return (uint32_t)... | 29,564,257,894,363,846,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2015-9542 | add_password in pam_radius_auth.c in pam_radius 1.4.0 does not correctly check the length of the input password, and is vulnerable to a stack-based buffer overflow during memcpy(). An attacker could send a crafted password to an application (loading the pam_radius library) and crash it. Arbitrary code execution might b... | https://nvd.nist.gov/vuln/detail/CVE-2015-9542 |
517,183 | pam_radius | 01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | https://github.com/FreeRADIUS/pam_radius | https://github.com/FreeRADIUS/pam_radius/commit/01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | Use "length", which has been limited in size | 0 | PAM_EXTERN int pam_sm_close_session(pam_handle_t *pamh, int flags, int argc, CONST char **argv)
{
return pam_private_session(pamh, flags, argc, argv, PW_STATUS_STOP);
} | 136,528,483,501,528,920,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2015-9542 | add_password in pam_radius_auth.c in pam_radius 1.4.0 does not correctly check the length of the input password, and is vulnerable to a stack-based buffer overflow during memcpy(). An attacker could send a crafted password to an application (loading the pam_radius library) and crash it. Arbitrary code execution might b... | https://nvd.nist.gov/vuln/detail/CVE-2015-9542 |
517,184 | pam_radius | 01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | https://github.com/FreeRADIUS/pam_radius | https://github.com/FreeRADIUS/pam_radius/commit/01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | Use "length", which has been limited in size | 0 | static void _pam_log(int err, CONST char *format, ...)
{
va_list args;
char buffer[BUFFER_SIZE];
va_start(args, format);
vsprintf(buffer, format, args);
/* don't do openlog or closelog, but put our name in to be friendly */
syslog(err, "%s: %s", pam_module_name, buffer);
va_end(args);
} | 192,076,949,102,933,000,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2015-9542 | add_password in pam_radius_auth.c in pam_radius 1.4.0 does not correctly check the length of the input password, and is vulnerable to a stack-based buffer overflow during memcpy(). An attacker could send a crafted password to an application (loading the pam_radius library) and crash it. Arbitrary code execution might b... | https://nvd.nist.gov/vuln/detail/CVE-2015-9542 |
517,185 | pam_radius | 01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | https://github.com/FreeRADIUS/pam_radius | https://github.com/FreeRADIUS/pam_radius/commit/01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | Use "length", which has been limited in size | 0 | static void get_accounting_vector(AUTH_HDR *request, radius_server_t *server)
{
MD5_CTX my_md5;
int secretlen = strlen(server->secret);
int len = ntohs(request->length);
memset(request->vector, 0, AUTH_VECTOR_LEN);
MD5Init(&my_md5);
memcpy(((char *)request) + len, server->secret, secretlen);
MD5Update(&my_md5,... | 101,109,207,781,756,550,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2015-9542 | add_password in pam_radius_auth.c in pam_radius 1.4.0 does not correctly check the length of the input password, and is vulnerable to a stack-based buffer overflow during memcpy(). An attacker could send a crafted password to an application (loading the pam_radius library) and crash it. Arbitrary code execution might b... | https://nvd.nist.gov/vuln/detail/CVE-2015-9542 |
517,186 | pam_radius | 01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | https://github.com/FreeRADIUS/pam_radius | https://github.com/FreeRADIUS/pam_radius/commit/01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | Use "length", which has been limited in size | 0 | PAM_EXTERN int pam_sm_authenticate(pam_handle_t *pamh,int flags,int argc,CONST char **argv)
{
CONST char *user;
CONST char *userinfo;
char *password = NULL;
CONST char *rhost;
char *resp2challenge = NULL;
int ctrl;
int retval = PAM_AUTH_ERR;
int num_challenge = 0;
char recv_buffer[4096];
char send_buffer[409... | 45,559,752,610,656,070,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2015-9542 | add_password in pam_radius_auth.c in pam_radius 1.4.0 does not correctly check the length of the input password, and is vulnerable to a stack-based buffer overflow during memcpy(). An attacker could send a crafted password to an application (loading the pam_radius library) and crash it. Arbitrary code execution might b... | https://nvd.nist.gov/vuln/detail/CVE-2015-9542 |
517,187 | pam_radius | 01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | https://github.com/FreeRADIUS/pam_radius | https://github.com/FreeRADIUS/pam_radius/commit/01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | Use "length", which has been limited in size | 0 | PAM_EXTERN int pam_sm_open_session(pam_handle_t *pamh, int flags, int argc, CONST char **argv)
{
return pam_private_session(pamh, flags, argc, argv, PW_STATUS_START);
} | 218,666,988,838,564,000,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2015-9542 | add_password in pam_radius_auth.c in pam_radius 1.4.0 does not correctly check the length of the input password, and is vulnerable to a stack-based buffer overflow during memcpy(). An attacker could send a crafted password to an application (loading the pam_radius library) and crash it. Arbitrary code execution might b... | https://nvd.nist.gov/vuln/detail/CVE-2015-9542 |
517,188 | pam_radius | 01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | https://github.com/FreeRADIUS/pam_radius | https://github.com/FreeRADIUS/pam_radius/commit/01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | Use "length", which has been limited in size | 0 | static void add_int_attribute(AUTH_HDR *request, unsigned char type, int data)
{
int value = htonl(data);
add_attribute(request, type, (unsigned char *) &value, sizeof(int));
} | 16,533,020,030,283,797,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2015-9542 | add_password in pam_radius_auth.c in pam_radius 1.4.0 does not correctly check the length of the input password, and is vulnerable to a stack-based buffer overflow during memcpy(). An attacker could send a crafted password to an application (loading the pam_radius library) and crash it. Arbitrary code execution might b... | https://nvd.nist.gov/vuln/detail/CVE-2015-9542 |
517,189 | pam_radius | 01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | https://github.com/FreeRADIUS/pam_radius | https://github.com/FreeRADIUS/pam_radius/commit/01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | Use "length", which has been limited in size | 0 | static void add_password(AUTH_HDR *request, unsigned char type, CONST char *password, char *secret)
{
MD5_CTX md5_secret, my_md5;
unsigned char misc[AUTH_VECTOR_LEN];
int i;
int length = strlen(password);
unsigned char hashed[256 + AUTH_PASS_LEN]; /* can't be longer than this */
unsigned char *vector;
attribute_... | 53,245,594,408,979,590,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2015-9542 | add_password in pam_radius_auth.c in pam_radius 1.4.0 does not correctly check the length of the input password, and is vulnerable to a stack-based buffer overflow during memcpy(). An attacker could send a crafted password to an application (loading the pam_radius library) and crash it. Arbitrary code execution might b... | https://nvd.nist.gov/vuln/detail/CVE-2015-9542 |
517,190 | pam_radius | 01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | https://github.com/FreeRADIUS/pam_radius | https://github.com/FreeRADIUS/pam_radius/commit/01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | Use "length", which has been limited in size | 0 | static int host2server(radius_server_t *server)
{
char *p;
if ((p = strchr(server->hostname, ':')) != NULL) {
*(p++) = '\0'; /* split the port off from the host name */
}
if ((server->ip.s_addr = get_ipaddr(server->hostname)) == ((uint32_t)0)) {
DPRINT(LOG_DEBUG, "DEBUG: get_ipaddr(%s) returned 0.\n", server... | 314,589,421,798,581,040,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2015-9542 | add_password in pam_radius_auth.c in pam_radius 1.4.0 does not correctly check the length of the input password, and is vulnerable to a stack-based buffer overflow during memcpy(). An attacker could send a crafted password to an application (loading the pam_radius library) and crash it. Arbitrary code execution might b... | https://nvd.nist.gov/vuln/detail/CVE-2015-9542 |
517,191 | pam_radius | 01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | https://github.com/FreeRADIUS/pam_radius | https://github.com/FreeRADIUS/pam_radius/commit/01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | Use "length", which has been limited in size | 0 | PAM_EXTERN int pam_sm_acct_mgmt(pam_handle_t *pamh,int flags,int argc,CONST char **argv)
{
int retval;
retval = PAM_SUCCESS;
return retval;
} | 7,055,147,549,102,110,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2015-9542 | add_password in pam_radius_auth.c in pam_radius 1.4.0 does not correctly check the length of the input password, and is vulnerable to a stack-based buffer overflow during memcpy(). An attacker could send a crafted password to an application (loading the pam_radius library) and crash it. Arbitrary code execution might b... | https://nvd.nist.gov/vuln/detail/CVE-2015-9542 |
517,192 | pam_radius | 01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | https://github.com/FreeRADIUS/pam_radius | https://github.com/FreeRADIUS/pam_radius/commit/01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | Use "length", which has been limited in size | 0 | static void build_radius_packet(AUTH_HDR *request, CONST char *user, CONST char *password, radius_conf_t *conf)
{
char hostname[256];
uint32_t ipaddr;
hostname[0] = '\0';
gethostname(hostname, sizeof(hostname) - 1);
request->length = htons(AUTH_HDR_LEN);
if (password) { /* make a random authentication req vec... | 11,706,963,842,758,054,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2015-9542 | add_password in pam_radius_auth.c in pam_radius 1.4.0 does not correctly check the length of the input password, and is vulnerable to a stack-based buffer overflow during memcpy(). An attacker could send a crafted password to an application (loading the pam_radius library) and crash it. Arbitrary code execution might b... | https://nvd.nist.gov/vuln/detail/CVE-2015-9542 |
517,193 | pam_radius | 01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | https://github.com/FreeRADIUS/pam_radius | https://github.com/FreeRADIUS/pam_radius/commit/01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | Use "length", which has been limited in size | 0 | static int initialize(radius_conf_t *conf, int accounting)
{
struct sockaddr salocal;
char hostname[BUFFER_SIZE];
char secret[BUFFER_SIZE];
char buffer[BUFFER_SIZE];
char *p;
FILE *fserver;
radius_server_t *server = NULL;
struct sockaddr_in * s_in;
int timeout;
int line = 0;
/* the first time around, read ... | 297,788,666,648,090,970,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2015-9542 | add_password in pam_radius_auth.c in pam_radius 1.4.0 does not correctly check the length of the input password, and is vulnerable to a stack-based buffer overflow during memcpy(). An attacker could send a crafted password to an application (loading the pam_radius library) and crash it. Arbitrary code execution might b... | https://nvd.nist.gov/vuln/detail/CVE-2015-9542 |
517,194 | pam_radius | 01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | https://github.com/FreeRADIUS/pam_radius | https://github.com/FreeRADIUS/pam_radius/commit/01173ec2426627dbb1e0d96c06c3ffa0b14d36d0 | Use "length", which has been limited in size | 0 | void _int_free(pam_handle_t * pamh, void *x, int error_status)
{
free(x);
} | 330,477,114,292,909,830,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2015-9542 | add_password in pam_radius_auth.c in pam_radius 1.4.0 does not correctly check the length of the input password, and is vulnerable to a stack-based buffer overflow during memcpy(). An attacker could send a crafted password to an application (loading the pam_radius library) and crash it. Arbitrary code execution might b... | https://nvd.nist.gov/vuln/detail/CVE-2015-9542 |
517,195 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | option_value2string (
vimoption_T *opp,
int opt_flags /* OPT_GLOBAL and/or OPT_LOCAL */
)
{
char_u *varp;
varp = get_varp_scope(opp, opt_flags);
if (opp->flags & P_NUM) {
long wc = 0;
if (wc_use_keyname(varp, &wc)) {
STRLCPY(NameBuff, get_special_key_name((in... | 35,888,457,671,088,085,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,196 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | void set_init_1(void)
{
int opt_idx;
langmap_init();
/* Be nocompatible */
p_cp = FALSE;
/*
* Find default value for 'shell' option.
* Don't use it if it is empty.
*/
{
const char *shell = os_getenv("SHELL");
if (shell != NULL) {
set_string_default("sh", (char *) shell, false);
... | 104,304,198,535,599,300,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,197 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | int langmap_adjust_mb(int c)
{
langmap_entry_T *entries = (langmap_entry_T *)(langmap_mapga.ga_data);
int a = 0;
int b = langmap_mapga.ga_len;
while (a != b) {
int i = (a + b) / 2;
int d = entries[i].from - c;
if (d == 0)
return entries[i].to; /* found matching entry */
if (d < 0)... | 151,063,787,428,969,190,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,198 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | static void langmap_set(void)
{
char_u *p;
char_u *p2;
int from, to;
ga_clear(&langmap_mapga); /* clear the previous map first */
langmap_init(); /* back to one-to-one map */
for (p = p_langmap; p[0] != NUL; ) {
for (p2 = p; p2[0] != NUL && p2[0] != ',' && p... | 13,714,220,068,711,830,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,199 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | bool is_tty_option(char *name)
{
return (name[0] == 't' && name[1] == '_') || !strcmp((char *)name, "term");
} | 204,970,952,233,460,140,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,200 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | bool set_tty_option(char *name, char *value)
{
if (!strcmp(name, "t_Co")) {
int colors = atoi(value);
// Only reinitialize colors if t_Co value has really changed to
// avoid expensive reload of colorscheme if t_Co is set to the
// same value multiple times
if (colors != t_colors) {
t_color... | 204,014,158,326,343,840,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,201 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | int makefoldset(FILE *fd)
{
if (put_setstring(fd, "setlocal", "fdm", &curwin->w_p_fdm, FALSE) == FAIL
|| put_setstring(fd, "setlocal", "fde", &curwin->w_p_fde, FALSE)
== FAIL
|| put_setstring(fd, "setlocal", "fmr", &curwin->w_p_fmr, FALSE)
== FAIL
|| put_setstring(fd, "setlocal", "fdi", ... | 141,882,210,289,562,560,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,202 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | set_bool_option (
int opt_idx, /* index in options[] table */
char_u *varp, /* pointer to the option variable */
int value, /* new value */
int opt_flags /* OPT_LOCAL and/or OPT_GLOBAL */
)
{
int old_... | 50,661,785,552,087,560,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,203 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | static char_u *get_varp(vimoption_T *p)
{
/* hidden option, always return NULL */
if (p->var == NULL)
return NULL;
switch ((int)p->indir) {
case PV_NONE: return p->var;
/* global option with local value: use local value if it's been set */
case PV_EP: return *curbuf->b_p_ep != NUL
? (... | 186,181,685,720,899,350,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,204 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | void find_mps_values(int *initc, int *findc, int *backwards, int switchit)
{
char_u *ptr;
ptr = curbuf->b_p_mps;
while (*ptr != NUL) {
if (has_mbyte) {
char_u *prev;
if (mb_ptr2char(ptr) == *initc) {
if (switchit) {
*findc = *initc;
*initc = mb_ptr2char(ptr + mb_... | 73,129,250,305,918,680,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,205 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | bool shortmess(int x)
{
return (p_shm != NULL
&& (vim_strchr(p_shm, x) != NULL
|| (vim_strchr(p_shm, 'a') != NULL
&& vim_strchr((char_u *)SHM_ALL_ABBREVIATIONS, x) != NULL)));
} | 330,616,825,184,206,370,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,206 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | static int check_opt_wim(void)
{
char_u new_wim_flags[4];
char_u *p;
int i;
int idx = 0;
for (i = 0; i < 4; ++i)
new_wim_flags[i] = 0;
for (p = p_wim; *p; ++p) {
for (i = 0; ASCII_ISALPHA(p[i]); ++i)
;
if (p[i] != NUL && p[i] != ',' && p[i] != ':')
return FAIL;
if (i == 7 ... | 65,549,742,633,369,480,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,207 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | int has_format_option(int x)
{
if (p_paste)
return FALSE;
return vim_strchr(curbuf->b_p_fo, x) != NULL;
} | 188,123,922,399,372,300,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,208 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | static void didset_options(void)
{
/* initialize the table for 'iskeyword' et.al. */
(void)init_chartab();
(void)opt_strings_flags(p_cmp, p_cmp_values, &cmp_flags, true);
(void)opt_strings_flags(p_bkc, p_bkc_values, &bkc_flags, true);
(void)opt_strings_flags(p_bo, p_bo_values, &bo_flags, true);
(void)opt_s... | 252,637,108,724,418,000,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,209 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | for (size_t i = 0; i < len; i++) {
if (src[i] == ',') {
dest[i + shift++] = '\\';
}
dest[i + shift] = src[i];
} | 246,605,175,877,704,560,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,210 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | if (dir != NULL && dir_len > 0) {
ret += ((dir_len + memcnt(dir, ',', dir_len) + common_suf_len
+ !after_pathsep(dir, dir + dir_len)) * 2
+ single_suf_len);
} | 236,993,263,674,127,480,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,211 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | FUNC_ATTR_NONNULL_RET FUNC_ATTR_NONNULL_ARG(1) FUNC_ATTR_WARN_UNUSED_RESULT
{
if (dir == NULL || dir_len == 0) {
return dest;
}
dest = strcpy_comma_escaped(dest, dir, dir_len);
if (append_nvim) {
if (!after_pathsep(dest - 1, dest)) {
*dest++ = PATHSEP;
}
memmove(dest, "nvim", NVIM_SIZE);... | 337,123,073,215,311,100,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,212 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | char_u *get_highlight_default(void)
{
int i;
i = findoption((char_u *)"hl");
if (i >= 0)
return options[i].def_val[VI_DEFAULT];
return (char_u *)NULL;
} | 143,293,698,873,262,570,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,213 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | bool get_tty_option(char *name, char **value)
{
if (!strcmp(name, "t_Co")) {
if (value) {
if (t_colors <= 1) {
*value = xstrdup("");
} else {
*value = xmalloc(TCO_BUFFER_SIZE);
snprintf(*value, TCO_BUFFER_SIZE, "%d", t_colors);
}
}
return true;
}
if (!strcmp(... | 250,975,059,480,297,370,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,214 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | void check_buf_options(buf_T *buf)
{
check_string_option(&buf->b_p_bh);
check_string_option(&buf->b_p_bt);
check_string_option(&buf->b_p_fenc);
check_string_option(&buf->b_p_ff);
check_string_option(&buf->b_p_def);
check_string_option(&buf->b_p_inc);
check_string_option(&buf->b_p_inex);
check_string_opt... | 92,530,435,412,469,790,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,215 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | set_num_option (
int opt_idx, /* index in options[] table */
char_u *varp, /* pointer to the option variable */
long value, /* new value */
char_u *errbuf, /* buffer for error messages */
size_t errbuflen,... | 144,930,177,425,275,470,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,216 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | int ExpandSettings(expand_T *xp, regmatch_T *regmatch, int *num_file, char_u ***file)
{
int num_normal = 0; // Nr of matching non-term-code settings
int match;
int count = 0;
char_u *str;
int loop;
static char *(names[]) = {"all", "termcap"};
int ic = regmatch->rm_ic; /* remember the ign... | 76,923,060,327,253,270,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,217 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | set_option_default (
int opt_idx,
int opt_flags, /* OPT_FREE, OPT_LOCAL and/or OPT_GLOBAL */
int compatible /* use Vi default value */
)
{
char_u *varp; /* pointer to variable for current option */
int dvi; /* index in def_val[] */
... | 297,086,184,606,235,060,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,218 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | void buf_copy_options(buf_T *buf, int flags)
{
int should_copy = TRUE;
char_u *save_p_isk = NULL; /* init for GCC */
int dont_do_help;
int did_isk = FALSE;
/*
* Don't do anything if the buffer is invalid.
*/
if (buf == NULL || !buf_valid(buf))
return;
/*
* Skip this when the ... | 213,813,363,438,648,660,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,219 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | int check_ff_value(char_u *p)
{
return check_opt_strings(p, p_ff_values, FALSE);
} | 199,529,963,878,283,600,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,220 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | void comp_col(void)
{
int last_has_status = (p_ls == 2 || (p_ls == 1 && firstwin != lastwin));
sc_col = 0;
ru_col = 0;
if (p_ru) {
ru_col = (ru_wid ? ru_wid : COL_RULER) + 1;
/* no last status line, adjust sc_col */
if (!last_has_status)
sc_col = ru_col;
}
if (p_sc) {
sc_col += SHOWCM... | 335,976,190,384,640,520,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,221 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | did_set_option (
int opt_idx,
int opt_flags, /* possibly with OPT_MODELINE */
int new_value /* value was replaced completely */
)
{
options[opt_idx].flags |= P_WAS_SET;
/* When an option is set in the sandbox, from a modeline or in secure mode
* set the P_INSECURE flag. Ot... | 309,495,228,533,320,660,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,222 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | static void set_option_scriptID_idx(int opt_idx, int opt_flags, int id)
{
int both = (opt_flags & (OPT_LOCAL | OPT_GLOBAL)) == 0;
int indir = (int)options[opt_idx].indir;
/* Remember where the option was set. For local options need to do that
* in the buffer or window structure. */
if (both || (opt_flags &... | 222,183,503,301,140,670,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,223 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | void clear_winopt(winopt_T *wop)
{
clear_string_option(&wop->wo_fdi);
clear_string_option(&wop->wo_fdm);
clear_string_option(&wop->wo_fdm_save);
clear_string_option(&wop->wo_fde);
clear_string_option(&wop->wo_fdt);
clear_string_option(&wop->wo_fmr);
clear_string_option(&wop->wo_rlc);
clear_string_option... | 216,518,524,637,274,760,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,224 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | void save_file_ff(buf_T *buf)
{
buf->b_start_ffc = *buf->b_p_ff;
buf->b_start_eol = buf->b_p_eol;
buf->b_start_bomb = buf->b_p_bomb;
/* Only use free/alloc when necessary, they take time. */
if (buf->b_start_fenc == NULL
|| STRCMP(buf->b_start_fenc, buf->b_p_fenc) != 0) {
xfree(buf->b_start_fenc);
... | 303,272,028,572,360,420,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,225 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | void set_init_2(void)
{
int idx;
/*
* 'scroll' defaults to half the window height. Note that this default is
* wrong when the window height changes.
*/
set_number_default("scroll", Rows / 2);
idx = findoption((char_u *)"scroll");
if (idx >= 0 && !(options[idx].flags & P_WAS_SET))
set_option_defa... | 170,209,327,206,190,270,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,226 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | void clear_string_option(char_u **pp)
{
if (*pp != empty_option)
xfree(*pp);
*pp = empty_option;
} | 240,786,635,230,462,280,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,227 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | void ExpandOldSetting(int *num_file, char_u ***file)
{
char_u *var = NULL;
*num_file = 0;
*file = (char_u **)xmalloc(sizeof(char_u *));
/*
* For a terminal key code expand_option_idx is < 0.
*/
if (expand_option_idx < 0) {
expand_option_idx = findoption(expand_option_name);
}
if (expand_optio... | 235,244,358,267,376,000,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,228 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | static void set_runtimepath_default(void)
{
size_t rtp_size = 0;
char *const data_home = stdpaths_get_xdg_var(kXDGDataHome);
char *const config_home = stdpaths_get_xdg_var(kXDGConfigHome);
char *const vimruntime = vim_getenv("VIMRUNTIME");
char *const data_dirs = stdpaths_get_xdg_var(kXDGDataDirs);
char *co... | 110,527,235,116,467,170,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,229 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | set_string_option_direct (
char_u *name,
int opt_idx,
char_u *val,
int opt_flags, /* OPT_FREE, OPT_LOCAL and/or OPT_GLOBAL */
int set_sid
)
{
char_u *s;
char_u **varp;
int both = (opt_flags & (OPT_LOCAL | OPT_GLOBAL)) == 0;
int idx = opt_idx;
if (idx == -1) { ... | 320,196,687,175,850,800,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,230 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | static int check_opt_strings(
char_u *val,
char **values,
int list /* when TRUE: accept a list of values */
)
{
return opt_strings_flags(val, values, NULL, list);
} | 373,151,040,068,215,760,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,231 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | int csh_like_shell(void)
{
return strstr((char *)path_tail(p_sh), "csh") != NULL;
} | 190,731,574,728,902,360,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,232 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | void win_copy_options(win_T *wp_from, win_T *wp_to)
{
copy_winopt(&wp_from->w_onebuf_opt, &wp_to->w_onebuf_opt);
copy_winopt(&wp_from->w_allbuf_opt, &wp_to->w_allbuf_opt);
/* Is this right? */
wp_to->w_farsi = wp_from->w_farsi;
briopt_check(wp_to);
} | 316,201,155,493,069,200,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,233 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | static uint32_t *insecure_flag(int opt_idx, int opt_flags)
{
if (opt_flags & OPT_LOCAL)
switch ((int)options[opt_idx].indir) {
case PV_STL: return &curwin->w_p_stl_flags;
case PV_FDE: return &curwin->w_p_fde_flags;
case PV_FDT: return &curwin->w_p_fdt_flags;
case PV_INDE: ... | 19,196,647,158,910,894,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,234 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | static void set_string_default(const char *name, char *val, bool allocated)
FUNC_ATTR_NONNULL_ALL
{
int opt_idx = findoption((char_u *)name);
if (opt_idx >= 0) {
if (options[opt_idx].flags & P_DEF_ALLOCED) {
xfree(options[opt_idx].def_val[VI_DEFAULT]);
}
options[opt_idx].def_val[VI_DEFAULT] = (... | 156,122,647,010,969,500,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,235 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | set_options_default (
int opt_flags /* OPT_FREE, OPT_LOCAL and/or OPT_GLOBAL */
)
{
for (int i = 0; options[i].fullname; i++) {
if (!(options[i].flags & P_NODEFAULT)) {
set_option_default(i, opt_flags, p_cp);
}
}
/* The 'scroll' option must be computed for all windows. */
FOR... | 198,729,218,075,914,780,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,236 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | void check_win_options(win_T *win)
{
check_winopt(&win->w_onebuf_opt);
check_winopt(&win->w_allbuf_opt);
} | 164,501,252,197,676,560,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,237 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | char_u *check_stl_option(char_u *s)
{
int itemcnt = 0;
int groupdepth = 0;
static char_u errbuf[80];
while (*s && itemcnt < STL_MAX_ITEM) {
/* Check for valid keys after % sequences */
while (*s && *s != '%')
s++;
if (!*s)
break;
s++;
if (*s != '%' && *s != ')') {
itemcnt+... | 279,105,393,763,309,200,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,238 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | static char_u *did_set_spell_option(bool is_spellfile)
{
char_u *errmsg = NULL;
if (is_spellfile) {
int l = (int)STRLEN(curwin->w_s->b_p_spf);
if (l > 0
&& (l < 4 || STRCMP(curwin->w_s->b_p_spf + l - 4, ".add") != 0)) {
errmsg = e_invarg;
}
}
if (errmsg == NULL) {
FOR_ALL_WINDOW... | 11,477,756,979,790,090,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,239 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | static bool briopt_check(win_T *wp)
{
int bri_shift = 0;
int bri_min = 20;
bool bri_sbr = false;
char_u *p = wp->w_p_briopt;
while (*p != NUL)
{
if (STRNCMP(p, "shift:", 6) == 0
&& ((p[6] == '-' && ascii_isdigit(p[7])) || ascii_isdigit(p[6])))
{
p += 6;
bri_shift = getdigits_int... | 36,557,794,796,790,138,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,240 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | static void redraw_titles(void) {
need_maketitle = TRUE;
redraw_tabline = TRUE;
} | 265,161,551,159,884,470,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,241 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | did_set_title (
int icon /* Did set icon instead of title */
)
{
if (starting != NO_SCREEN) {
maketitle();
if (icon) {
if (!p_icon) {
ui_set_icon(NULL);
}
} else {
if (!p_title) {
ui_set_title(NULL);
}
}
}
} | 323,418,571,028,108,200,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,242 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | static int findoption(char_u *arg)
{
return findoption_len(arg, STRLEN(arg));
} | 295,684,973,755,982,060,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,243 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | static int int_cmp(const void *a, const void *b)
{
return *(const int *)a - *(const int *)b;
} | 240,059,129,799,463,100,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
517,244 | neovim | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 0 | showoptions (
int all,
int opt_flags /* OPT_LOCAL and/or OPT_GLOBAL */
)
{
vimoption_T *p;
int col;
char_u *varp;
int item_count;
int run;
int row, rows;
int cols;
int i;
int len;
#define INC 20
#define GAP 3
vimoption_T **items = xmalloc(sizeof(vimoption_T... | 239,937,805,894,646,400,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.