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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
12,513 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | void red_channel_client_push(RedChannelClient *rcc)
{
PipeItem *pipe_item;
if (!rcc->during_send) {
rcc->during_send = TRUE;
} else {
return;
}
red_channel_client_ref(rcc);
if (rcc->send_data.blocked) {
red_channel_client_send(rcc);
}
if (!red_channel_client_no_... | 200,629,282,118,683,300,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,514 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | static void red_channel_client_push_ping(RedChannelClient *rcc)
{
spice_assert(rcc->latency_monitor.state == PING_STATE_NONE);
rcc->latency_monitor.state = PING_STATE_WARMUP;
rcc->latency_monitor.warmup_was_sent = FALSE;
rcc->latency_monitor.id = rand();
red_channel_client_pipe_add_type(rcc, PIPE_IT... | 287,586,455,236,945,330,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,515 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | void red_channel_client_push_set_ack(RedChannelClient *rcc)
{
red_channel_client_pipe_add_type(rcc, PIPE_ITEM_TYPE_SET_ACK);
}
| 124,948,032,223,289,760,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,516 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | void red_channel_client_receive(RedChannelClient *rcc)
{
red_channel_client_ref(rcc);
red_peer_handle_incoming(rcc->stream, &rcc->incoming);
red_channel_client_unref(rcc);
}
| 23,387,347,746,903,637,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,517 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | static void red_channel_client_release_item(RedChannelClient *rcc, PipeItem *item, int item_pushed)
{
int handled = TRUE;
switch (item->type) {
case PIPE_ITEM_TYPE_SET_ACK:
case PIPE_ITEM_TYPE_EMPTY_MSG:
case PIPE_ITEM_TYPE_MIGRATE:
case PIPE_ITEM_TYPE_PING:
free(ite... | 233,232,438,958,174,520,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,518 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | static inline void red_channel_client_release_sent_item(RedChannelClient *rcc)
{
if (rcc->send_data.item) {
red_channel_client_release_item(rcc,
rcc->send_data.item, TRUE);
rcc->send_data.item = NULL;
}
}
| 91,131,402,320,835,700,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,519 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | static void red_channel_client_restart_ping_timer(RedChannelClient *rcc)
{
struct timespec ts;
uint64_t passed, timeout;
clock_gettime(CLOCK_MONOTONIC, &ts);
passed = ts.tv_sec * 1000000000LL + ts.tv_nsec;
passed = passed - rcc->latency_monitor.last_pong_time;
passed /= 1000*1000;
timeout ... | 42,324,557,255,066,920,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,520 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | static void red_channel_client_restore_main_sender(RedChannelClient *rcc)
{
spice_marshaller_reset(rcc->send_data.urgent.marshaller);
rcc->send_data.marshaller = rcc->send_data.main.marshaller;
rcc->send_data.header.data = rcc->send_data.main.header_data;
if (!rcc->is_mini_header) {
rcc->send_da... | 336,070,840,931,849,970,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,521 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | void red_channel_client_send(RedChannelClient *rcc)
{
red_channel_client_ref(rcc);
red_peer_handle_outgoing(rcc->stream, &rcc->outgoing);
red_channel_client_unref(rcc);
}
| 263,573,522,620,107,800,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,522 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | static void red_channel_client_send_empty_msg(RedChannelClient *rcc, PipeItem *base)
{
EmptyMsgPipeItem *msg_pipe_item = SPICE_CONTAINEROF(base, EmptyMsgPipeItem, base);
red_channel_client_init_send_data(rcc, msg_pipe_item->msg, NULL);
red_channel_client_begin_send_message(rcc);
}
| 111,484,224,880,135,160,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,523 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | static void red_channel_client_send_item(RedChannelClient *rcc, PipeItem *item)
{
int handled = TRUE;
spice_assert(red_channel_client_no_item_being_sent(rcc));
red_channel_client_reset_send_data(rcc);
switch (item->type) {
case PIPE_ITEM_TYPE_SET_ACK:
red_channel_client_send_set_ack... | 140,239,143,666,874,740,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,524 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | int red_channel_client_send_message_pending(RedChannelClient *rcc)
{
return rcc->send_data.header.get_msg_type(&rcc->send_data.header) != 0;
}
| 126,875,648,302,744,330,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,525 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | static void red_channel_client_send_migrate(RedChannelClient *rcc)
{
SpiceMsgMigrate migrate;
red_channel_client_init_send_data(rcc, SPICE_MSG_MIGRATE, NULL);
migrate.flags = rcc->channel->migration_flags;
spice_marshall_msg_migrate(rcc->send_data.marshaller, &migrate);
if (rcc->channel->migration_... | 119,783,338,488,392,070,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,526 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | static void red_channel_client_send_ping(RedChannelClient *rcc)
{
SpiceMsgPing ping;
struct timespec ts;
if (!rcc->latency_monitor.warmup_was_sent) { // latency test start
int delay_val;
socklen_t opt_size = sizeof(delay_val);
rcc->latency_monitor.warmup_was_sent = TRUE;
/*... | 338,975,790,626,838,840,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,527 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | static void red_channel_client_send_set_ack(RedChannelClient *rcc)
{
SpiceMsgSetAck ack;
spice_assert(rcc);
red_channel_client_init_send_data(rcc, SPICE_MSG_SET_ACK, NULL);
ack.generation = ++rcc->ack_data.generation;
ack.window = rcc->ack_data.client_window;
rcc->ack_data.messages_window = 0;
... | 220,028,754,355,311,300,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,528 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | void red_channel_client_set_message_serial(RedChannelClient *rcc, uint64_t serial)
{
rcc->send_data.last_sent_serial = serial;
rcc->send_data.serial = serial;
}
| 333,652,373,756,030,750,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,529 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | static void red_channel_client_set_migration_seamless(RedChannelClient *rcc)
{
spice_assert(rcc->client->during_target_migrate && rcc->client->seamless_migrate);
if (rcc->channel->migration_flags & SPICE_MIGRATE_NEED_DATA_TRANSFER) {
rcc->wait_migrate_data = TRUE;
rcc->client->num_migrated_chan... | 18,874,892,864,046,733,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,530 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | static void red_channel_client_set_remote_caps(RedChannelClient* rcc,
int num_common_caps, uint32_t *common_caps,
int num_caps, uint32_t *caps)
{
rcc->remote_caps.num_common_caps = num_common_caps;
rcc->remote_caps.com... | 175,926,471,653,704,770,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,531 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | static void red_channel_client_start_ping_timer(RedChannelClient *rcc, uint32_t timeout)
{
if (!rcc->latency_monitor.timer) {
return;
}
if (rcc->latency_monitor.state != PING_STATE_NONE) {
return;
}
rcc->latency_monitor.state = PING_STATE_TIMER;
rcc->channel->core->timer_start(rc... | 35,716,001,855,740,136,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,532 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | int red_channel_client_test_remote_cap(RedChannelClient *rcc, uint32_t cap)
{
return test_capabilty(rcc->remote_caps.caps,
rcc->remote_caps.num_caps,
cap);
}
| 267,655,586,889,197,900,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,533 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | int red_channel_client_test_remote_common_cap(RedChannelClient *rcc, uint32_t cap)
{
return test_capabilty(rcc->remote_caps.common_caps,
rcc->remote_caps.num_common_caps,
cap);
}
| 313,043,257,500,073,100,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,534 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | static void red_channel_client_unref(RedChannelClient *rcc)
{
if (!--rcc->refs) {
if (rcc->send_data.main.marshaller) {
spice_marshaller_destroy(rcc->send_data.main.marshaller);
}
if (rcc->send_data.urgent.marshaller) {
spice_marshaller_destroy(rcc->send_data.urgent.... | 46,340,103,187,900,790,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,535 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | static inline int red_channel_client_urgent_marshaller_is_active(RedChannelClient *rcc)
{
return (rcc->send_data.marshaller == rcc->send_data.urgent.marshaller);
}
| 105,910,283,935,387,400,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,536 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | static inline int red_channel_client_waiting_for_ack(RedChannelClient *rcc)
{
return (rcc->channel->handle_acks &&
(rcc->ack_data.messages_window > rcc->ack_data.client_window * 2));
}
| 238,956,215,530,179,400,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,537 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | int red_channel_client_waits_for_migrate_data(RedChannelClient *rcc)
{
return rcc->wait_migrate_data;
}
| 97,859,630,013,639,680,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,538 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | RedChannel *red_channel_create(int size,
SpiceCoreInterface *core,
uint32_t type, uint32_t id,
int handle_acks,
channel_handle_message_proc handle_message,
ChannelCb... | 54,835,027,982,850,000,000,000,000,000,000,000,000 | None | null | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,539 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | RedChannel *red_channel_create_dummy(int size, uint32_t type, uint32_t id)
{
RedChannel *channel;
ClientCbs client_cbs = { NULL, };
spice_assert(size >= sizeof(*channel));
channel = spice_malloc0(size);
channel->type = type;
channel->id = id;
channel->refs = 1;
channel->core = &dummy_co... | 252,900,038,205,076,600,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,540 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | RedChannel *red_channel_create_parser(int size,
SpiceCoreInterface *core,
uint32_t type, uint32_t id,
int handle_acks,
spice_parse_channel_func_t parser,
channel_han... | 293,908,157,397,617,870,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,541 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | void red_channel_destroy(RedChannel *channel)
{
RingItem *link;
RingItem *next;
if (!channel) {
return;
}
RING_FOREACH_SAFE(link, next, &channel->clients) {
red_channel_client_destroy(
SPICE_CONTAINEROF(link, RedChannelClient, channel_link));
}
red_channel_unref... | 297,622,806,879,232,460,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,542 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | static void red_channel_handle_migrate_data(RedChannelClient *rcc, uint32_t size, void *message)
{
spice_debug("channel type %d id %d rcc %p size %u",
rcc->channel->type, rcc->channel->id, rcc, size);
if (!rcc->channel->channel_cbs.handle_migrate_data) {
return;
}
if (!red_channe... | 5,767,856,774,549,702,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,543 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | static void red_channel_handle_migrate_flush_mark(RedChannelClient *rcc)
{
if (rcc->channel->channel_cbs.handle_migrate_flush_mark) {
rcc->channel->channel_cbs.handle_migrate_flush_mark(rcc);
}
}
| 210,253,878,530,436,920,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,544 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | void red_channel_init_outgoing_messages_window(RedChannel *channel)
{
RingItem *link;
RingItem *next;
RING_FOREACH_SAFE(link, next, &channel->clients) {
red_channel_client_init_outgoing_messages_window(
SPICE_CONTAINEROF(link, RedChannelClient, channel_link));
}
}
| 334,975,406,098,808,920,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,545 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | uint32_t red_channel_min_pipe_size(RedChannel *channel)
{
RingItem *link;
RedChannelClient *rcc;
uint32_t pipe_size = ~0;
RING_FOREACH(link, &channel->clients) {
rcc = SPICE_CONTAINEROF(link, RedChannelClient, channel_link);
pipe_size = pipe_size < rcc->pipe_size ? pipe_size : rcc->pipe... | 176,442,985,003,791,930,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,546 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | int red_channel_no_item_being_sent(RedChannel *channel)
{
RingItem *link;
RedChannelClient *rcc;
RING_FOREACH(link, &channel->clients) {
rcc = SPICE_CONTAINEROF(link, RedChannelClient, channel_link);
if (!red_channel_client_no_item_being_sent(rcc)) {
return FALSE;
}
... | 11,965,183,038,308,166,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,547 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | void red_channel_pipe_item_init(RedChannel *channel, PipeItem *item, int type)
{
ring_item_init(&item->link);
item->type = type;
}
| 331,959,602,365,877,330,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,548 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | void red_channel_pipes_new_add(RedChannel *channel, new_pipe_item_t creator, void *data)
{
red_channel_pipes_create_batch(channel, creator, data,
red_channel_client_pipe_add);
}
| 103,025,597,834,196,470,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,549 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | void red_channel_pipes_new_add_push(RedChannel *channel,
new_pipe_item_t creator, void *data)
{
red_channel_pipes_create_batch(channel, creator, data,
red_channel_client_pipe_add);
red_channel_push(channel);
}
| 239,479,517,237,043,600,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,550 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | void red_channel_push(RedChannel *channel)
{
RingItem *link;
RingItem *next;
RedChannelClient *rcc;
if (!channel) {
return;
}
RING_FOREACH_SAFE(link, next, &channel->clients) {
rcc = SPICE_CONTAINEROF(link, RedChannelClient, channel_link);
red_channel_client_push(rcc);
... | 114,439,448,224,540,300,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,551 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | void red_channel_receive(RedChannel *channel)
{
RingItem *link;
RingItem *next;
RedChannelClient *rcc;
RING_FOREACH_SAFE(link, next, &channel->clients) {
rcc = SPICE_CONTAINEROF(link, RedChannelClient, channel_link);
red_channel_client_receive(rcc);
}
}
| 204,689,296,702,642,650,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,552 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | static void red_channel_ref(RedChannel *channel)
{
channel->refs++;
}
| 220,779,958,993,770,830,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,553 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | void red_channel_register_client_cbs(RedChannel *channel, ClientCbs *client_cbs)
{
spice_assert(client_cbs->connect || channel->type == SPICE_CHANNEL_MAIN);
channel->client_cbs.connect = client_cbs->connect;
if (client_cbs->disconnect) {
channel->client_cbs.disconnect = client_cbs->disconnect;
... | 229,213,062,250,391,450,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,554 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | static void red_channel_remove_client(RedChannelClient *rcc)
{
if (!pthread_equal(pthread_self(), rcc->channel->thread_id)) {
spice_warning("channel type %d id %d - "
"channel->thread_id (0x%lx) != pthread_self (0x%lx)."
"If one of the threads is != io-thread && !... | 92,429,403,216,911,540,000,000,000,000,000,000,000 | None | null | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,555 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | void red_channel_send(RedChannel *channel)
{
RingItem *link;
RingItem *next;
RING_FOREACH_SAFE(link, next, &channel->clients) {
red_channel_client_send(SPICE_CONTAINEROF(link, RedChannelClient, channel_link));
}
}
| 177,662,869,470,296,130,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,556 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | void red_channel_set_cap(RedChannel *channel, uint32_t cap)
{
add_capability(&channel->local_caps.caps, &channel->local_caps.num_caps, cap);
}
| 89,179,074,656,586,500,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,557 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | void red_channel_set_data(RedChannel *channel, void *data)
{
spice_assert(channel);
channel->data = data;
}
| 126,913,446,103,668,740,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,558 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | uint32_t red_channel_sum_pipes_size(RedChannel *channel)
{
RingItem *link;
RedChannelClient *rcc;
uint32_t sum = 0;
RING_FOREACH(link, &channel->clients) {
rcc = SPICE_CONTAINEROF(link, RedChannelClient, channel_link);
sum += rcc->pipe_size;
}
return sum;
}
| 229,707,971,744,110,060,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,559 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | int red_channel_test_remote_cap(RedChannel *channel, uint32_t cap)
{
RingItem *link;
RING_FOREACH(link, &channel->clients) {
RedChannelClient *rcc = SPICE_CONTAINEROF(link, RedChannelClient, channel_link);
if (!red_channel_client_test_remote_cap(rcc, cap)) {
return FALSE;
}... | 72,425,594,046,635,720,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,560 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | int red_channel_test_remote_common_cap(RedChannel *channel, uint32_t cap)
{
RingItem *link;
RING_FOREACH(link, &channel->clients) {
RedChannelClient *rcc = SPICE_CONTAINEROF(link, RedChannelClient, channel_link);
if (!red_channel_client_test_remote_common_cap(rcc, cap)) {
return FA... | 311,572,290,763,414,420,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,561 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | static void red_channel_unref(RedChannel *channel)
{
if (!--channel->refs) {
if (channel->local_caps.num_common_caps) {
free(channel->local_caps.common_caps);
}
if (channel->local_caps.num_caps) {
free(channel->local_caps.caps);
}
free(channel);
... | 146,452,876,954,865,930,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,562 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | int red_channel_waits_for_migrate_data(RedChannel *channel)
{
RedChannelClient *rcc;
if (!red_channel_is_connected(channel)) {
return FALSE;
}
if (channel->clients_num > 1) {
return FALSE;
}
spice_assert(channel->clients_num == 1);
rcc = SPICE_CONTAINEROF(ring_get_head(&cha... | 187,002,055,935,134,950,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,563 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | static void red_client_add_channel(RedClient *client, RedChannelClient *rcc)
{
spice_assert(rcc && client);
ring_add(&client->channels, &rcc->client_link);
if (client->during_target_migrate && client->seamless_migrate) {
red_channel_client_set_migration_seamless(rcc);
}
client->channels_num+... | 103,304,816,233,578,030,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,564 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | void red_client_destroy(RedClient *client)
{
RingItem *link, *next;
RedChannelClient *rcc;
spice_printerr("destroy client with #channels %d", client->channels_num);
if (!pthread_equal(pthread_self(), client->thread_id)) {
spice_warning("client->thread_id (0x%lx) != pthread_self (0x%lx)."
... | 39,713,263,073,954,397,000,000,000,000,000,000,000 | None | null | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,565 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | int red_client_during_migrate_at_target(RedClient *client)
{
int ret;
pthread_mutex_lock(&client->lock);
ret = client->during_target_migrate;
pthread_mutex_unlock(&client->lock);
return ret;
}
| 110,639,191,543,275,090,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,566 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | static RedChannelClient *red_client_get_channel(RedClient *client, int type, int id)
{
RingItem *link;
RedChannelClient *rcc;
RedChannelClient *ret = NULL;
RING_FOREACH(link, &client->channels) {
rcc = SPICE_CONTAINEROF(link, RedChannelClient, client_link);
if (rcc->channel->type == typ... | 245,337,931,316,319,600,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,567 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | MainChannelClient *red_client_get_main(RedClient *client) {
return client->mcc;
}
| 199,524,170,780,823,800,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,568 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | void red_client_migrate(RedClient *client)
{
RingItem *link, *next;
RedChannelClient *rcc;
spice_printerr("migrate client with #channels %d", client->channels_num);
if (!pthread_equal(pthread_self(), client->thread_id)) {
spice_warning("client->thread_id (0x%lx) != pthread_self (0x%lx)."
... | 137,972,210,053,449,630,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,569 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | RedClient *red_client_new(int migrated)
{
RedClient *client;
client = spice_malloc0(sizeof(RedClient));
ring_init(&client->channels);
pthread_mutex_init(&client->lock, NULL);
client->thread_id = pthread_self();
client->during_target_migrate = migrated;
return client;
}
| 300,969,726,879,090,860,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,570 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | static void red_client_remove_channel(RedChannelClient *rcc)
{
pthread_mutex_lock(&rcc->client->lock);
ring_remove(&rcc->client_link);
rcc->client->channels_num--;
pthread_mutex_unlock(&rcc->client->lock);
}
| 120,816,244,854,140,050,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,571 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | void red_client_semi_seamless_migrate_complete(RedClient *client)
{
RingItem *link;
pthread_mutex_lock(&client->lock);
if (!client->during_target_migrate || client->seamless_migrate) {
spice_error("unexpected");
pthread_mutex_unlock(&client->lock);
return;
}
client->during_t... | 35,108,736,732,040,500,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,572 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | void red_client_set_migration_seamless(RedClient *client) // dest
{
RingItem *link;
pthread_mutex_lock(&client->lock);
client->seamless_migrate = TRUE;
/* update channel clients that got connected before the migration
* type was set. red_client_add_channel will handle newer channel clients */
R... | 22,273,518,261,898,524,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,573 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | static void red_peer_handle_outgoing(RedsStream *stream, OutgoingHandler *handler)
{
ssize_t n;
if (!stream) {
return;
}
if (handler->size == 0) {
handler->vec = handler->vec_buf;
handler->size = handler->cb->get_msg_size(handler->opaque);
if (!handler->size) { // noth... | 266,010,055,500,513,780,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,574 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | static int red_peer_receive(RedsStream *stream, uint8_t *buf, uint32_t size)
{
uint8_t *pos = buf;
while (size) {
int now;
if (stream->shutdown) {
return -1;
}
now = reds_stream_read(stream, pos, size);
if (now <= 0) {
if (now == 0) {
... | 223,655,969,181,937,900,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,575 | spice | 53488f0275d6c8a121af49f7ac817d09ce68090d | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d | Use RING_FOREACH_SAFE in red_channel.c functions which are missing it
Currently, both red_channel_pipes_add_type() and
red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not
safe versus removals from the ring within the loop body.
Although it's rare, such a removal can occur in both cases. In the c... | 0 | int test_capabilty(uint32_t *caps, int num_caps, uint32_t cap)
{
uint32_t index = cap / 32;
if (num_caps < index + 1) {
return FALSE;
}
return (caps[index] & (1 << (cap % 32))) != 0;
}
| 55,459,836,844,780,850,000,000,000,000,000,000,000 | red_channel.c | 327,785,878,310,762,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4130 | The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error. | https://nvd.nist.gov/vuln/detail/CVE-2013-4130 |
12,576 | poppler | da63c35549e8852a410946ab016a3f25ac701bdf | https://github.com/freedesktop/poppler | https://cgit.freedesktop.org/poppler/poppler/commit/?id=da63c35549e8852a410946ab016a3f25ac701bdf | FoFiType1C::convertToType0: Fix crash in broken files
Bug #102724 | 0 | FoFiType1C::FoFiType1C(char *fileA, int lenA, GBool freeFileDataA):
FoFiBase(fileA, lenA, freeFileDataA)
{
name = NULL;
encoding = NULL;
privateDicts = NULL;
fdSelect = NULL;
charset = NULL;
charsetLength = 0;
}
| 132,930,680,239,200,210,000,000,000,000,000,000,000 | FoFiType1C.cc | 149,976,149,896,113,630,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-14976 | The FoFiType1C::convertToType0 function in FoFiType1C.cc in Poppler 0.59.0 has a heap-based buffer over-read vulnerability if an out-of-bounds font dictionary index is encountered, which allows an attacker to launch a denial of service attack. | https://nvd.nist.gov/vuln/detail/CVE-2017-14976 |
12,577 | poppler | da63c35549e8852a410946ab016a3f25ac701bdf | https://github.com/freedesktop/poppler | https://cgit.freedesktop.org/poppler/poppler/commit/?id=da63c35549e8852a410946ab016a3f25ac701bdf | FoFiType1C::convertToType0: Fix crash in broken files
Bug #102724 | 0 | void FoFiType1C::buildEncoding() {
char buf[256];
int nCodes, nRanges, encFormat;
int pos, c, sid, nLeft, nSups, i, j;
if (topDict.encodingOffset == 0) {
encoding = (char **)fofiType1StandardEncoding;
} else if (topDict.encodingOffset == 1) {
encoding = (char **)fofiType1ExpertEncoding;
} else {
... | 162,671,353,550,294,700,000,000,000,000,000,000,000 | FoFiType1C.cc | 149,976,149,896,113,630,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-14976 | The FoFiType1C::convertToType0 function in FoFiType1C.cc in Poppler 0.59.0 has a heap-based buffer over-read vulnerability if an out-of-bounds font dictionary index is encountered, which allows an attacker to launch a denial of service attack. | https://nvd.nist.gov/vuln/detail/CVE-2017-14976 |
12,578 | poppler | da63c35549e8852a410946ab016a3f25ac701bdf | https://github.com/freedesktop/poppler | https://cgit.freedesktop.org/poppler/poppler/commit/?id=da63c35549e8852a410946ab016a3f25ac701bdf | FoFiType1C::convertToType0: Fix crash in broken files
Bug #102724 | 0 | void FoFiType1C::convertToCIDType0(char *psName, int *codeMap, int nCodes,
FoFiOutputFunc outputFunc,
void *outputStream) {
int *cidMap;
GooString *charStrings;
int *charStringOffsets;
Type1CIndex subrIdx;
Type1CIndexVal val;
int nCIDs, gdBytes;
GooString *buf;
char buf2[256];
GBool ok;
... | 97,095,882,244,718,160,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2017-14976 | The FoFiType1C::convertToType0 function in FoFiType1C.cc in Poppler 0.59.0 has a heap-based buffer over-read vulnerability if an out-of-bounds font dictionary index is encountered, which allows an attacker to launch a denial of service attack. | https://nvd.nist.gov/vuln/detail/CVE-2017-14976 |
12,579 | poppler | da63c35549e8852a410946ab016a3f25ac701bdf | https://github.com/freedesktop/poppler | https://cgit.freedesktop.org/poppler/poppler/commit/?id=da63c35549e8852a410946ab016a3f25ac701bdf | FoFiType1C::convertToType0: Fix crash in broken files
Bug #102724 | 0 | void FoFiType1C::convertToType1(char *psName, const char **newEncoding, GBool ascii,
FoFiOutputFunc outputFunc,
void *outputStream) {
int psNameLen;
Type1CEexecBuf eb;
Type1CIndex subrIdx;
Type1CIndexVal val;
GooString *buf;
char buf2[256];
const char **enc;
GBool ok;
int i;
if (psName) {
... | 9,038,964,464,295,006,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2017-14976 | The FoFiType1C::convertToType0 function in FoFiType1C.cc in Poppler 0.59.0 has a heap-based buffer over-read vulnerability if an out-of-bounds font dictionary index is encountered, which allows an attacker to launch a denial of service attack. | https://nvd.nist.gov/vuln/detail/CVE-2017-14976 |
12,580 | poppler | da63c35549e8852a410946ab016a3f25ac701bdf | https://github.com/freedesktop/poppler | https://cgit.freedesktop.org/poppler/poppler/commit/?id=da63c35549e8852a410946ab016a3f25ac701bdf | FoFiType1C::convertToType0: Fix crash in broken files
Bug #102724 | 0 | void FoFiType1C::cvtGlyph(int offset, int nBytes, GooString *charBuf,
Type1CIndex *subrIdx, Type1CPrivateDict *pDict,
GBool top) {
Type1CIndexVal val;
GBool ok, dFP;
double d, dx, dy;
Gushort r2;
Guchar byte;
int pos, subrBias, start, i, k;
start = charBuf->getLength();
if (top) {
charBuf... | 113,411,388,115,967,360,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2017-14976 | The FoFiType1C::convertToType0 function in FoFiType1C.cc in Poppler 0.59.0 has a heap-based buffer over-read vulnerability if an out-of-bounds font dictionary index is encountered, which allows an attacker to launch a denial of service attack. | https://nvd.nist.gov/vuln/detail/CVE-2017-14976 |
12,581 | poppler | da63c35549e8852a410946ab016a3f25ac701bdf | https://github.com/freedesktop/poppler | https://cgit.freedesktop.org/poppler/poppler/commit/?id=da63c35549e8852a410946ab016a3f25ac701bdf | FoFiType1C::convertToType0: Fix crash in broken files
Bug #102724 | 0 | void FoFiType1C::cvtNum(double x, GBool isFP, GooString *charBuf) {
Guchar buf[12];
int y, n;
n = 0;
if (isFP) {
if (x >= -32768 && x < 32768) {
y = (int)(x * 256.0);
buf[0] = 255;
buf[1] = (Guchar)(y >> 24);
buf[2] = (Guchar)(y >> 16);
buf[3] = (Guchar)(y >> 8);
buf[4] ... | 7,610,209,460,544,788,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2017-14976 | The FoFiType1C::convertToType0 function in FoFiType1C.cc in Poppler 0.59.0 has a heap-based buffer over-read vulnerability if an out-of-bounds font dictionary index is encountered, which allows an attacker to launch a denial of service attack. | https://nvd.nist.gov/vuln/detail/CVE-2017-14976 |
12,582 | poppler | da63c35549e8852a410946ab016a3f25ac701bdf | https://github.com/freedesktop/poppler | https://cgit.freedesktop.org/poppler/poppler/commit/?id=da63c35549e8852a410946ab016a3f25ac701bdf | FoFiType1C::convertToType0: Fix crash in broken files
Bug #102724 | 0 | void FoFiType1C::eexecWrite(Type1CEexecBuf *eb, const char *s) {
Guchar *p;
Guchar x;
for (p = (Guchar *)s; *p; ++p) {
x = *p ^ (eb->r1 >> 8);
eb->r1 = (x + eb->r1) * 52845 + 22719;
if (eb->ascii) {
(*eb->outputFunc)(eb->outputStream, &hexChars[x >> 4], 1);
(*eb->outputFunc)(eb->outputStr... | 149,382,853,591,758,970,000,000,000,000,000,000,000 | FoFiType1C.cc | 149,976,149,896,113,630,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-14976 | The FoFiType1C::convertToType0 function in FoFiType1C.cc in Poppler 0.59.0 has a heap-based buffer over-read vulnerability if an out-of-bounds font dictionary index is encountered, which allows an attacker to launch a denial of service attack. | https://nvd.nist.gov/vuln/detail/CVE-2017-14976 |
12,583 | poppler | da63c35549e8852a410946ab016a3f25ac701bdf | https://github.com/freedesktop/poppler | https://cgit.freedesktop.org/poppler/poppler/commit/?id=da63c35549e8852a410946ab016a3f25ac701bdf | FoFiType1C::convertToType0: Fix crash in broken files
Bug #102724 | 0 | void FoFiType1C::eexecWriteCharstring(Type1CEexecBuf *eb,
Guchar *s, int n) {
Guchar x;
int i;
for (i = 0; i < n; ++i) {
x = s[i] ^ (eb->r1 >> 8);
eb->r1 = (x + eb->r1) * 52845 + 22719;
if (eb->ascii) {
(*eb->outputFunc)(eb->outputStream, &hexChars[x >> 4], 1);
(*eb->outputFunc)... | 73,552,302,461,561,650,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2017-14976 | The FoFiType1C::convertToType0 function in FoFiType1C.cc in Poppler 0.59.0 has a heap-based buffer over-read vulnerability if an out-of-bounds font dictionary index is encountered, which allows an attacker to launch a denial of service attack. | https://nvd.nist.gov/vuln/detail/CVE-2017-14976 |
12,584 | poppler | da63c35549e8852a410946ab016a3f25ac701bdf | https://github.com/freedesktop/poppler | https://cgit.freedesktop.org/poppler/poppler/commit/?id=da63c35549e8852a410946ab016a3f25ac701bdf | FoFiType1C::convertToType0: Fix crash in broken files
Bug #102724 | 0 | int *FoFiType1C::getCIDToGIDMap(int *nCIDs) {
int *map;
int n, i;
if (topDict.firstOp != 0x0c1e) {
*nCIDs = 0;
return NULL;
}
n = 0;
for (i = 0; i < nGlyphs && i < charsetLength; ++i) {
if (charset[i] > n) {
n = charset[i];
}
}
++n;
map = (int *)gmallocn(n, sizeof(int));
mems... | 300,988,775,507,354,640,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2017-14976 | The FoFiType1C::convertToType0 function in FoFiType1C.cc in Poppler 0.59.0 has a heap-based buffer over-read vulnerability if an out-of-bounds font dictionary index is encountered, which allows an attacker to launch a denial of service attack. | https://nvd.nist.gov/vuln/detail/CVE-2017-14976 |
12,585 | poppler | da63c35549e8852a410946ab016a3f25ac701bdf | https://github.com/freedesktop/poppler | https://cgit.freedesktop.org/poppler/poppler/commit/?id=da63c35549e8852a410946ab016a3f25ac701bdf | FoFiType1C::convertToType0: Fix crash in broken files
Bug #102724 | 0 | int FoFiType1C::getDeltaIntArray(int *arr, int maxLen) {
int x;
int n, i;
if ((n = nOps) > maxLen) {
n = maxLen;
}
x = 0;
for (i = 0; i < n; ++i) {
x += (int)ops[i].num;
arr[i] = x;
}
return n;
}
| 337,870,466,405,912,370,000,000,000,000,000,000,000 | FoFiType1C.cc | 149,976,149,896,113,630,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-14976 | The FoFiType1C::convertToType0 function in FoFiType1C.cc in Poppler 0.59.0 has a heap-based buffer over-read vulnerability if an out-of-bounds font dictionary index is encountered, which allows an attacker to launch a denial of service attack. | https://nvd.nist.gov/vuln/detail/CVE-2017-14976 |
12,586 | poppler | da63c35549e8852a410946ab016a3f25ac701bdf | https://github.com/freedesktop/poppler | https://cgit.freedesktop.org/poppler/poppler/commit/?id=da63c35549e8852a410946ab016a3f25ac701bdf | FoFiType1C::convertToType0: Fix crash in broken files
Bug #102724 | 0 | char **FoFiType1C::getEncoding() {
return encoding;
}
| 269,867,170,584,341,800,000,000,000,000,000,000,000 | FoFiType1C.cc | 149,976,149,896,113,630,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-14976 | The FoFiType1C::convertToType0 function in FoFiType1C.cc in Poppler 0.59.0 has a heap-based buffer over-read vulnerability if an out-of-bounds font dictionary index is encountered, which allows an attacker to launch a denial of service attack. | https://nvd.nist.gov/vuln/detail/CVE-2017-14976 |
12,587 | poppler | da63c35549e8852a410946ab016a3f25ac701bdf | https://github.com/freedesktop/poppler | https://cgit.freedesktop.org/poppler/poppler/commit/?id=da63c35549e8852a410946ab016a3f25ac701bdf | FoFiType1C::convertToType0: Fix crash in broken files
Bug #102724 | 0 | void FoFiType1C::getFontMatrix(double *mat) {
int i;
if (topDict.firstOp == 0x0c1e && privateDicts[0].hasFontMatrix) {
if (topDict.hasFontMatrix) {
mat[0] = topDict.fontMatrix[0] * privateDicts[0].fontMatrix[0] +
topDict.fontMatrix[1] * privateDicts[0].fontMatrix[2];
mat[1] = topDict.fontMa... | 273,950,030,922,165,450,000,000,000,000,000,000,000 | FoFiType1C.cc | 149,976,149,896,113,630,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-14976 | The FoFiType1C::convertToType0 function in FoFiType1C.cc in Poppler 0.59.0 has a heap-based buffer over-read vulnerability if an out-of-bounds font dictionary index is encountered, which allows an attacker to launch a denial of service attack. | https://nvd.nist.gov/vuln/detail/CVE-2017-14976 |
12,588 | poppler | da63c35549e8852a410946ab016a3f25ac701bdf | https://github.com/freedesktop/poppler | https://cgit.freedesktop.org/poppler/poppler/commit/?id=da63c35549e8852a410946ab016a3f25ac701bdf | FoFiType1C::convertToType0: Fix crash in broken files
Bug #102724 | 0 | GooString *FoFiType1C::getGlyphName(int gid) {
char buf[256];
GBool ok;
ok = gTrue;
if (gid < 0 || gid >= charsetLength)
return NULL;
getString(charset[gid], buf, &ok);
if (!ok) {
return NULL;
}
return new GooString(buf);
}
| 243,259,455,817,763,900,000,000,000,000,000,000,000 | FoFiType1C.cc | 149,976,149,896,113,630,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-14976 | The FoFiType1C::convertToType0 function in FoFiType1C.cc in Poppler 0.59.0 has a heap-based buffer over-read vulnerability if an out-of-bounds font dictionary index is encountered, which allows an attacker to launch a denial of service attack. | https://nvd.nist.gov/vuln/detail/CVE-2017-14976 |
12,589 | poppler | da63c35549e8852a410946ab016a3f25ac701bdf | https://github.com/freedesktop/poppler | https://cgit.freedesktop.org/poppler/poppler/commit/?id=da63c35549e8852a410946ab016a3f25ac701bdf | FoFiType1C::convertToType0: Fix crash in broken files
Bug #102724 | 0 | void FoFiType1C::getIndex(int pos, Type1CIndex *idx, GBool *ok) {
idx->pos = pos;
idx->len = getU16BE(pos, ok);
if (idx->len == 0) {
idx->offSize = 0;
idx->startPos = idx->endPos = pos + 2;
} else {
idx->offSize = getU8(pos + 2, ok);
if (idx->offSize < 1 || idx->offSize > 4) {
*ok = gFalse... | 107,461,941,489,488,180,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2017-14976 | The FoFiType1C::convertToType0 function in FoFiType1C.cc in Poppler 0.59.0 has a heap-based buffer over-read vulnerability if an out-of-bounds font dictionary index is encountered, which allows an attacker to launch a denial of service attack. | https://nvd.nist.gov/vuln/detail/CVE-2017-14976 |
12,590 | poppler | da63c35549e8852a410946ab016a3f25ac701bdf | https://github.com/freedesktop/poppler | https://cgit.freedesktop.org/poppler/poppler/commit/?id=da63c35549e8852a410946ab016a3f25ac701bdf | FoFiType1C::convertToType0: Fix crash in broken files
Bug #102724 | 0 | void FoFiType1C::getIndexVal(Type1CIndex *idx, int i,
Type1CIndexVal *val, GBool *ok) {
int pos0, pos1;
if (i < 0 || i >= idx->len) {
*ok = gFalse;
return;
}
pos0 = idx->startPos + getUVarBE(idx->pos + 3 + i * idx->offSize,
idx->offSize, ok);
pos1 = idx->startPos + getUVarBE(idx->pos +... | 218,758,403,661,259,420,000,000,000,000,000,000,000 | FoFiType1C.cc | 149,976,149,896,113,630,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-14976 | The FoFiType1C::convertToType0 function in FoFiType1C.cc in Poppler 0.59.0 has a heap-based buffer over-read vulnerability if an out-of-bounds font dictionary index is encountered, which allows an attacker to launch a denial of service attack. | https://nvd.nist.gov/vuln/detail/CVE-2017-14976 |
12,591 | poppler | da63c35549e8852a410946ab016a3f25ac701bdf | https://github.com/freedesktop/poppler | https://cgit.freedesktop.org/poppler/poppler/commit/?id=da63c35549e8852a410946ab016a3f25ac701bdf | FoFiType1C::convertToType0: Fix crash in broken files
Bug #102724 | 0 | char *FoFiType1C::getName() {
return name ? name->getCString() : (char *)NULL;
}
| 269,534,378,516,702,570,000,000,000,000,000,000,000 | FoFiType1C.cc | 149,976,149,896,113,630,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-14976 | The FoFiType1C::convertToType0 function in FoFiType1C.cc in Poppler 0.59.0 has a heap-based buffer over-read vulnerability if an out-of-bounds font dictionary index is encountered, which allows an attacker to launch a denial of service attack. | https://nvd.nist.gov/vuln/detail/CVE-2017-14976 |
12,592 | poppler | da63c35549e8852a410946ab016a3f25ac701bdf | https://github.com/freedesktop/poppler | https://cgit.freedesktop.org/poppler/poppler/commit/?id=da63c35549e8852a410946ab016a3f25ac701bdf | FoFiType1C::convertToType0: Fix crash in broken files
Bug #102724 | 0 | int FoFiType1C::getOp(int pos, GBool charstring, GBool *ok) {
static char nybChars[16] = "0123456789.ee -";
Type1COp op;
char buf[65];
int b0, b1, nyb0, nyb1, x, i;
b0 = getU8(pos++, ok);
op.isNum = gTrue;
op.isFP = gFalse;
if (b0 == 28) {
x = getU8(pos++, ok);
x = (x << 8) | getU8(pos++, ok);... | 269,051,169,461,771,560,000,000,000,000,000,000,000 | FoFiType1C.cc | 149,976,149,896,113,630,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-14976 | The FoFiType1C::convertToType0 function in FoFiType1C.cc in Poppler 0.59.0 has a heap-based buffer over-read vulnerability if an out-of-bounds font dictionary index is encountered, which allows an attacker to launch a denial of service attack. | https://nvd.nist.gov/vuln/detail/CVE-2017-14976 |
12,593 | poppler | da63c35549e8852a410946ab016a3f25ac701bdf | https://github.com/freedesktop/poppler | https://cgit.freedesktop.org/poppler/poppler/commit/?id=da63c35549e8852a410946ab016a3f25ac701bdf | FoFiType1C::convertToType0: Fix crash in broken files
Bug #102724 | 0 | char *FoFiType1C::getString(int sid, char *buf, GBool *ok) {
Type1CIndexVal val;
int n;
if (sid < 0) {
buf[0] = '\0';
} else if (sid < 391) {
strcpy(buf, fofiType1CStdStrings[sid]);
} else {
sid -= 391;
getIndexVal(&stringIdx, sid, &val, ok);
if (*ok) {
if ((n = val.len) > 255) {
n... | 328,912,220,860,697,800,000,000,000,000,000,000,000 | FoFiType1C.cc | 149,976,149,896,113,630,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-14976 | The FoFiType1C::convertToType0 function in FoFiType1C.cc in Poppler 0.59.0 has a heap-based buffer over-read vulnerability if an out-of-bounds font dictionary index is encountered, which allows an attacker to launch a denial of service attack. | https://nvd.nist.gov/vuln/detail/CVE-2017-14976 |
12,594 | poppler | da63c35549e8852a410946ab016a3f25ac701bdf | https://github.com/freedesktop/poppler | https://cgit.freedesktop.org/poppler/poppler/commit/?id=da63c35549e8852a410946ab016a3f25ac701bdf | FoFiType1C::convertToType0: Fix crash in broken files
Bug #102724 | 0 | FoFiType1C *FoFiType1C::load(char *fileName) {
FoFiType1C *ff;
char *fileA;
int lenA;
if (!(fileA = FoFiBase::readFile(fileName, &lenA))) {
return NULL;
}
ff = new FoFiType1C(fileA, lenA, gTrue);
if (!ff->parse()) {
delete ff;
return NULL;
}
return ff;
}
| 35,354,844,494,090,130,000,000,000,000,000,000,000 | FoFiType1C.cc | 149,976,149,896,113,630,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-14976 | The FoFiType1C::convertToType0 function in FoFiType1C.cc in Poppler 0.59.0 has a heap-based buffer over-read vulnerability if an out-of-bounds font dictionary index is encountered, which allows an attacker to launch a denial of service attack. | https://nvd.nist.gov/vuln/detail/CVE-2017-14976 |
12,595 | poppler | da63c35549e8852a410946ab016a3f25ac701bdf | https://github.com/freedesktop/poppler | https://cgit.freedesktop.org/poppler/poppler/commit/?id=da63c35549e8852a410946ab016a3f25ac701bdf | FoFiType1C::convertToType0: Fix crash in broken files
Bug #102724 | 0 | GBool FoFiType1C::parse() {
Type1CIndex fdIdx;
Type1CIndexVal val;
int i;
parsedOk = gTrue;
if (len > 0 && file[0] != '\x01') {
++file;
--len;
}
getIndex(getU8(2, &parsedOk), &nameIdx, &parsedOk);
getIndex(nameIdx.endPos, &topDictIdx, &parsedOk);
getIndex(topDictIdx.endPos, &stringIdx, &par... | 110,777,194,644,308,230,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2017-14976 | The FoFiType1C::convertToType0 function in FoFiType1C.cc in Poppler 0.59.0 has a heap-based buffer over-read vulnerability if an out-of-bounds font dictionary index is encountered, which allows an attacker to launch a denial of service attack. | https://nvd.nist.gov/vuln/detail/CVE-2017-14976 |
12,596 | poppler | da63c35549e8852a410946ab016a3f25ac701bdf | https://github.com/freedesktop/poppler | https://cgit.freedesktop.org/poppler/poppler/commit/?id=da63c35549e8852a410946ab016a3f25ac701bdf | FoFiType1C::convertToType0: Fix crash in broken files
Bug #102724 | 0 | GBool FoFiType1C::readCharset() {
int charsetFormat, c, pos;
int nLeft, i, j;
if (topDict.charsetOffset == 0) {
charset = fofiType1CISOAdobeCharset;
charsetLength = sizeof(fofiType1CISOAdobeCharset) / sizeof(Gushort);
} else if (topDict.charsetOffset == 1) {
charset = fofiType1CExpertCharset;
c... | 147,739,182,346,530,970,000,000,000,000,000,000,000 | FoFiType1C.cc | 149,976,149,896,113,630,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-14976 | The FoFiType1C::convertToType0 function in FoFiType1C.cc in Poppler 0.59.0 has a heap-based buffer over-read vulnerability if an out-of-bounds font dictionary index is encountered, which allows an attacker to launch a denial of service attack. | https://nvd.nist.gov/vuln/detail/CVE-2017-14976 |
12,597 | poppler | da63c35549e8852a410946ab016a3f25ac701bdf | https://github.com/freedesktop/poppler | https://cgit.freedesktop.org/poppler/poppler/commit/?id=da63c35549e8852a410946ab016a3f25ac701bdf | FoFiType1C::convertToType0: Fix crash in broken files
Bug #102724 | 0 | void FoFiType1C::readFD(int offset, int length, Type1CPrivateDict *pDict) {
int pos, pSize, pOffset;
double fontMatrix[6] = {0};
GBool hasFontMatrix;
hasFontMatrix = gFalse;
fontMatrix[0] = fontMatrix[1] = fontMatrix[2] = 0; // make gcc happy
fontMatrix[3] = fontMatrix[4] = fontMatrix[5] = 0;
pSize = pOf... | 195,538,857,858,037,130,000,000,000,000,000,000,000 | FoFiType1C.cc | 149,976,149,896,113,630,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-14976 | The FoFiType1C::convertToType0 function in FoFiType1C.cc in Poppler 0.59.0 has a heap-based buffer over-read vulnerability if an out-of-bounds font dictionary index is encountered, which allows an attacker to launch a denial of service attack. | https://nvd.nist.gov/vuln/detail/CVE-2017-14976 |
12,598 | poppler | da63c35549e8852a410946ab016a3f25ac701bdf | https://github.com/freedesktop/poppler | https://cgit.freedesktop.org/poppler/poppler/commit/?id=da63c35549e8852a410946ab016a3f25ac701bdf | FoFiType1C::convertToType0: Fix crash in broken files
Bug #102724 | 0 | void FoFiType1C::readFDSelect() {
int fdSelectFmt, pos, nRanges, gid0, gid1, fd, i, j;
fdSelect = (Guchar *)gmalloc(nGlyphs);
if (topDict.fdSelectOffset == 0) {
for (i = 0; i < nGlyphs; ++i) {
fdSelect[i] = 0;
}
} else {
pos = topDict.fdSelectOffset;
fdSelectFmt = getU8(pos++, &parsedOk);... | 290,535,625,021,605,000,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2017-14976 | The FoFiType1C::convertToType0 function in FoFiType1C.cc in Poppler 0.59.0 has a heap-based buffer over-read vulnerability if an out-of-bounds font dictionary index is encountered, which allows an attacker to launch a denial of service attack. | https://nvd.nist.gov/vuln/detail/CVE-2017-14976 |
12,599 | poppler | da63c35549e8852a410946ab016a3f25ac701bdf | https://github.com/freedesktop/poppler | https://cgit.freedesktop.org/poppler/poppler/commit/?id=da63c35549e8852a410946ab016a3f25ac701bdf | FoFiType1C::convertToType0: Fix crash in broken files
Bug #102724 | 0 | void FoFiType1C::readPrivateDict(int offset, int length,
Type1CPrivateDict *pDict) {
int pos;
pDict->hasFontMatrix = gFalse;
pDict->nBlueValues = 0;
pDict->nOtherBlues = 0;
pDict->nFamilyBlues = 0;
pDict->nFamilyOtherBlues = 0;
pDict->blueScale = 0.039625;
pDict->blueShift = 7;
pDict->blueFuzz =... | 261,810,179,316,234,660,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2017-14976 | The FoFiType1C::convertToType0 function in FoFiType1C.cc in Poppler 0.59.0 has a heap-based buffer over-read vulnerability if an out-of-bounds font dictionary index is encountered, which allows an attacker to launch a denial of service attack. | https://nvd.nist.gov/vuln/detail/CVE-2017-14976 |
12,600 | poppler | da63c35549e8852a410946ab016a3f25ac701bdf | https://github.com/freedesktop/poppler | https://cgit.freedesktop.org/poppler/poppler/commit/?id=da63c35549e8852a410946ab016a3f25ac701bdf | FoFiType1C::convertToType0: Fix crash in broken files
Bug #102724 | 0 | void FoFiType1C::readTopDict() {
Type1CIndexVal topDictPtr;
int pos;
topDict.firstOp = -1;
topDict.versionSID = 0;
topDict.noticeSID = 0;
topDict.copyrightSID = 0;
topDict.fullNameSID = 0;
topDict.familyNameSID = 0;
topDict.weightSID = 0;
topDict.isFixedPitch = 0;
topDict.italicAngle = 0;
topDi... | 140,465,452,717,788,500,000,000,000,000,000,000,000 | FoFiType1C.cc | 149,976,149,896,113,630,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-14976 | The FoFiType1C::convertToType0 function in FoFiType1C.cc in Poppler 0.59.0 has a heap-based buffer over-read vulnerability if an out-of-bounds font dictionary index is encountered, which allows an attacker to launch a denial of service attack. | https://nvd.nist.gov/vuln/detail/CVE-2017-14976 |
12,601 | poppler | da63c35549e8852a410946ab016a3f25ac701bdf | https://github.com/freedesktop/poppler | https://cgit.freedesktop.org/poppler/poppler/commit/?id=da63c35549e8852a410946ab016a3f25ac701bdf | FoFiType1C::convertToType0: Fix crash in broken files
Bug #102724 | 0 | void FoFiType1C::writePSString(char *s, FoFiOutputFunc outputFunc,
void *outputStream) {
char buf[80];
char *p;
int i, c;
i = 0;
buf[i++] = '(';
for (p = s; *p; ++p) {
c = *p & 0xff;
if (c == '(' || c == ')' || c == '\\') {
buf[i++] = '\\';
buf[i++] = c;
} else if (c < 0x2... | 274,333,630,754,969,200,000,000,000,000,000,000,000 | FoFiType1C.cc | 149,976,149,896,113,630,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-14976 | The FoFiType1C::convertToType0 function in FoFiType1C.cc in Poppler 0.59.0 has a heap-based buffer over-read vulnerability if an out-of-bounds font dictionary index is encountered, which allows an attacker to launch a denial of service attack. | https://nvd.nist.gov/vuln/detail/CVE-2017-14976 |
12,602 | poppler | da63c35549e8852a410946ab016a3f25ac701bdf | https://github.com/freedesktop/poppler | https://cgit.freedesktop.org/poppler/poppler/commit/?id=da63c35549e8852a410946ab016a3f25ac701bdf | FoFiType1C::convertToType0: Fix crash in broken files
Bug #102724 | 0 | FoFiType1C::~FoFiType1C() {
int i;
if (name) {
delete name;
}
if (encoding &&
encoding != fofiType1StandardEncoding &&
encoding != fofiType1ExpertEncoding) {
for (i = 0; i < 256; ++i) {
gfree(encoding[i]);
}
gfree(encoding);
}
if (privateDicts) {
gfree(privateDicts);
... | 79,914,171,410,358,600,000,000,000,000,000,000,000 | FoFiType1C.cc | 149,976,149,896,113,630,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-14976 | The FoFiType1C::convertToType0 function in FoFiType1C.cc in Poppler 0.59.0 has a heap-based buffer over-read vulnerability if an out-of-bounds font dictionary index is encountered, which allows an attacker to launch a denial of service attack. | https://nvd.nist.gov/vuln/detail/CVE-2017-14976 |
12,603 | mindrot | 1bf477d3cdf1a864646d59820878783d42357a1d | https://anongit.mindrot.org/openssh | https://anongit.mindrot.org/openssh.git/commit/?h=V_6_9&id=1bf477d3cdf1a864646d59820878783d42357a1d | None | 0 | channel_by_id(int id)
{
Channel *c;
if (id < 0 || (u_int)id >= channels_alloc) {
logit("channel_by_id: %d: bad id", id);
return NULL;
}
c = channels[id];
if (c == NULL) {
logit("channel_by_id: %d: bad id: channel free", id);
return NULL;
}
return c;
}
| 101,959,152,129,956,670,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2015-5352 | The x11_open_helper function in channels.c in ssh in OpenSSH before 6.9, when ForwardX11Trusted mode is not used, lacks a check of the refusal deadline for X connections, which makes it easier for remote attackers to bypass intended access restrictions via a connection outside of the permitted time window. | https://nvd.nist.gov/vuln/detail/CVE-2015-5352 |
12,604 | mindrot | 1bf477d3cdf1a864646d59820878783d42357a1d | https://anongit.mindrot.org/openssh | https://anongit.mindrot.org/openssh.git/commit/?h=V_6_9&id=1bf477d3cdf1a864646d59820878783d42357a1d | None | 0 | channel_cancel_cleanup(int id)
{
Channel *c = channel_by_id(id);
if (c == NULL) {
logit("channel_cancel_cleanup: %d: bad id", id);
return;
}
c->detach_user = NULL;
c->detach_close = 0;
}
| 226,143,744,237,702,870,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2015-5352 | The x11_open_helper function in channels.c in ssh in OpenSSH before 6.9, when ForwardX11Trusted mode is not used, lacks a check of the refusal deadline for X connections, which makes it easier for remote attackers to bypass intended access restrictions via a connection outside of the permitted time window. | https://nvd.nist.gov/vuln/detail/CVE-2015-5352 |
12,605 | mindrot | 1bf477d3cdf1a864646d59820878783d42357a1d | https://anongit.mindrot.org/openssh | https://anongit.mindrot.org/openssh.git/commit/?h=V_6_9&id=1bf477d3cdf1a864646d59820878783d42357a1d | None | 0 | channel_close_all(void)
{
u_int i;
for (i = 0; i < channels_alloc; i++)
if (channels[i] != NULL)
channel_close_fds(channels[i]);
}
| 330,619,020,875,761,900,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2015-5352 | The x11_open_helper function in channels.c in ssh in OpenSSH before 6.9, when ForwardX11Trusted mode is not used, lacks a check of the refusal deadline for X connections, which makes it easier for remote attackers to bypass intended access restrictions via a connection outside of the permitted time window. | https://nvd.nist.gov/vuln/detail/CVE-2015-5352 |
12,606 | mindrot | 1bf477d3cdf1a864646d59820878783d42357a1d | https://anongit.mindrot.org/openssh | https://anongit.mindrot.org/openssh.git/commit/?h=V_6_9&id=1bf477d3cdf1a864646d59820878783d42357a1d | None | 0 | channel_close_fd(int *fdp)
{
int ret = 0, fd = *fdp;
if (fd != -1) {
ret = close(fd);
*fdp = -1;
if (fd == channel_max_fd)
channel_max_fd = channel_find_maxfd();
}
return ret;
}
| 94,611,746,523,128,030,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2015-5352 | The x11_open_helper function in channels.c in ssh in OpenSSH before 6.9, when ForwardX11Trusted mode is not used, lacks a check of the refusal deadline for X connections, which makes it easier for remote attackers to bypass intended access restrictions via a connection outside of the permitted time window. | https://nvd.nist.gov/vuln/detail/CVE-2015-5352 |
12,607 | mindrot | 1bf477d3cdf1a864646d59820878783d42357a1d | https://anongit.mindrot.org/openssh | https://anongit.mindrot.org/openssh.git/commit/?h=V_6_9&id=1bf477d3cdf1a864646d59820878783d42357a1d | None | 0 | channel_close_fds(Channel *c)
{
channel_close_fd(&c->sock);
channel_close_fd(&c->rfd);
channel_close_fd(&c->wfd);
channel_close_fd(&c->efd);
}
| 162,503,335,223,069,330,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2015-5352 | The x11_open_helper function in channels.c in ssh in OpenSSH before 6.9, when ForwardX11Trusted mode is not used, lacks a check of the refusal deadline for X connections, which makes it easier for remote attackers to bypass intended access restrictions via a connection outside of the permitted time window. | https://nvd.nist.gov/vuln/detail/CVE-2015-5352 |
12,608 | mindrot | 1bf477d3cdf1a864646d59820878783d42357a1d | https://anongit.mindrot.org/openssh | https://anongit.mindrot.org/openssh.git/commit/?h=V_6_9&id=1bf477d3cdf1a864646d59820878783d42357a1d | None | 0 | channel_find_maxfd(void)
{
u_int i;
int max = 0;
Channel *c;
for (i = 0; i < channels_alloc; i++) {
c = channels[i];
if (c != NULL) {
max = MAX(max, c->rfd);
max = MAX(max, c->wfd);
max = MAX(max, c->efd);
}
}
return max;
}
| 279,004,556,027,265,640,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2015-5352 | The x11_open_helper function in channels.c in ssh in OpenSSH before 6.9, when ForwardX11Trusted mode is not used, lacks a check of the refusal deadline for X connections, which makes it easier for remote attackers to bypass intended access restrictions via a connection outside of the permitted time window. | https://nvd.nist.gov/vuln/detail/CVE-2015-5352 |
12,609 | mindrot | 1bf477d3cdf1a864646d59820878783d42357a1d | https://anongit.mindrot.org/openssh | https://anongit.mindrot.org/openssh.git/commit/?h=V_6_9&id=1bf477d3cdf1a864646d59820878783d42357a1d | None | 0 | channel_find_open(void)
{
u_int i;
Channel *c;
for (i = 0; i < channels_alloc; i++) {
c = channels[i];
if (c == NULL || c->remote_id < 0)
continue;
switch (c->type) {
case SSH_CHANNEL_CLOSED:
case SSH_CHANNEL_DYNAMIC:
case SSH_CHANNEL_X11_LISTENER:
case SSH_CHANNEL_PORT_LISTENER:
case SSH_CHANNEL... | 134,488,432,704,538,240,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2015-5352 | The x11_open_helper function in channels.c in ssh in OpenSSH before 6.9, when ForwardX11Trusted mode is not used, lacks a check of the refusal deadline for X connections, which makes it easier for remote attackers to bypass intended access restrictions via a connection outside of the permitted time window. | https://nvd.nist.gov/vuln/detail/CVE-2015-5352 |
12,610 | mindrot | 1bf477d3cdf1a864646d59820878783d42357a1d | https://anongit.mindrot.org/openssh | https://anongit.mindrot.org/openssh.git/commit/?h=V_6_9&id=1bf477d3cdf1a864646d59820878783d42357a1d | None | 0 | channel_free(Channel *c)
{
char *s;
u_int i, n;
struct channel_confirm *cc;
for (n = 0, i = 0; i < channels_alloc; i++)
if (channels[i])
n++;
debug("channel %d: free: %s, nchannels %u", c->self,
c->remote_name ? c->remote_name : "???", n);
s = channel_open_message();
debug3("channel %d: status: %s", ... | 296,605,497,581,080,480,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2015-5352 | The x11_open_helper function in channels.c in ssh in OpenSSH before 6.9, when ForwardX11Trusted mode is not used, lacks a check of the refusal deadline for X connections, which makes it easier for remote attackers to bypass intended access restrictions via a connection outside of the permitted time window. | https://nvd.nist.gov/vuln/detail/CVE-2015-5352 |
12,611 | mindrot | 1bf477d3cdf1a864646d59820878783d42357a1d | https://anongit.mindrot.org/openssh | https://anongit.mindrot.org/openssh.git/commit/?h=V_6_9&id=1bf477d3cdf1a864646d59820878783d42357a1d | None | 0 | channel_free_all(void)
{
u_int i;
for (i = 0; i < channels_alloc; i++)
if (channels[i] != NULL)
channel_free(channels[i]);
}
| 121,221,254,896,838,920,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2015-5352 | The x11_open_helper function in channels.c in ssh in OpenSSH before 6.9, when ForwardX11Trusted mode is not used, lacks a check of the refusal deadline for X connections, which makes it easier for remote attackers to bypass intended access restrictions via a connection outside of the permitted time window. | https://nvd.nist.gov/vuln/detail/CVE-2015-5352 |
12,612 | mindrot | 1bf477d3cdf1a864646d59820878783d42357a1d | https://anongit.mindrot.org/openssh | https://anongit.mindrot.org/openssh.git/commit/?h=V_6_9&id=1bf477d3cdf1a864646d59820878783d42357a1d | None | 0 | channel_lookup(int id)
{
Channel *c;
if ((c = channel_by_id(id)) == NULL)
return (NULL);
switch (c->type) {
case SSH_CHANNEL_X11_OPEN:
case SSH_CHANNEL_LARVAL:
case SSH_CHANNEL_CONNECTING:
case SSH_CHANNEL_DYNAMIC:
case SSH_CHANNEL_OPENING:
case SSH_CHANNEL_OPEN:
case SSH_CHANNEL_INPUT_DRAINING:
case SSH... | 28,479,340,263,004,214,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2015-5352 | The x11_open_helper function in channels.c in ssh in OpenSSH before 6.9, when ForwardX11Trusted mode is not used, lacks a check of the refusal deadline for X connections, which makes it easier for remote attackers to bypass intended access restrictions via a connection outside of the permitted time window. | https://nvd.nist.gov/vuln/detail/CVE-2015-5352 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.