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,391 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | SPICE_GNUC_VISIBLE void spice_server_set_name(SpiceServer *s, const char *name)
{
free(spice_name);
spice_name = spice_strdup(name);
}
| 206,031,007,371,551,740,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,392 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | SPICE_GNUC_VISIBLE int spice_server_set_noauth(SpiceServer *s)
{
spice_assert(reds == s);
memset(taTicket.password, 0, sizeof(taTicket.password));
ticketing_enabled = 0;
return 0;
}
| 102,331,403,260,721,270,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,393 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | SPICE_GNUC_VISIBLE int spice_server_set_playback_compression(SpiceServer *s, int enable)
{
spice_assert(reds == s);
snd_set_playback_compression(enable);
return 0;
}
| 200,615,964,159,715,360,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,394 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | SPICE_GNUC_VISIBLE int spice_server_set_port(SpiceServer *s, int port)
{
spice_assert(reds == s);
if (port < 0 || port > 0xffff) {
return -1;
}
spice_port = port;
return 0;
}
| 182,951,123,139,633,900,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,395 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | SPICE_GNUC_VISIBLE int spice_server_set_sasl(SpiceServer *s, int enabled)
{
spice_assert(reds == s);
#if HAVE_SASL
sasl_enabled = enabled;
return 0;
#else
return -1;
#endif
}
| 258,713,538,713,094,370,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,396 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | SPICE_GNUC_VISIBLE int spice_server_set_sasl_appname(SpiceServer *s, const char *appname)
{
spice_assert(reds == s);
#if HAVE_SASL
free(sasl_appname);
sasl_appname = spice_strdup(appname);
return 0;
#else
return -1;
#endif
}
| 332,087,916,377,494,000,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,397 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | SPICE_GNUC_VISIBLE void spice_server_set_seamless_migration(SpiceServer *s, int enable)
{
spice_assert(s == reds);
/* seamless migration is not supported with multiple clients */
reds->seamless_migration_enabled = enable && !reds->allow_multiple_clients;
spice_debug("seamless migration enabled=%d", enab... | 10,571,528,736,434,147,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,398 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | SPICE_GNUC_VISIBLE int spice_server_set_streaming_video(SpiceServer *s, int value)
{
spice_assert(reds == s);
if (value != SPICE_STREAM_VIDEO_OFF &&
value != SPICE_STREAM_VIDEO_ALL &&
value != SPICE_STREAM_VIDEO_FILTER)
return -1;
streaming_video = value;
red_dispatcher_on_sv_cha... | 83,849,097,836,437,640,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,399 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | SPICE_GNUC_VISIBLE int spice_server_set_ticket(SpiceServer *s,
const char *passwd, int lifetime,
int fail_if_connected,
int disconnect_if_connected)
{
spice_assert(reds == s);... | 91,509,267,939,669,900,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,400 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | SPICE_GNUC_VISIBLE int spice_server_set_tls(SpiceServer *s, int port,
const char *ca_cert_file, const char *certs_file,
const char *private_key_file, const char *key_passwd,
const char *dh... | 152,983,711,243,881,610,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,401 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | SPICE_GNUC_VISIBLE void spice_server_set_uuid(SpiceServer *s, const uint8_t uuid[16])
{
memcpy(spice_uuid, uuid, sizeof(spice_uuid));
spice_uuid_is_set = TRUE;
}
| 235,026,872,069,199,030,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,402 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | SPICE_GNUC_VISIBLE int spice_server_set_zlib_glz_compression(SpiceServer *s, spice_wan_compression_t comp)
{
spice_assert(reds == s);
if (comp == SPICE_WAN_COMPRESSION_INVALID) {
spice_error("invalid zlib_glz state");
return -1;
}
zlib_glz_state = comp;
return 0;
}
| 299,659,171,049,327,000,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,403 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | SPICE_GNUC_VISIBLE void spice_server_vm_start(SpiceServer *s)
{
RingItem *item;
spice_assert(s == reds);
reds->vm_running = TRUE;
RING_FOREACH(item, &reds->char_devs_states) {
SpiceCharDeviceStateItem *st_item;
st_item = SPICE_CONTAINEROF(item, SpiceCharDeviceStateItem, link);
... | 297,133,376,616,898,800,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,404 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | SPICE_GNUC_VISIBLE void spice_server_vm_stop(SpiceServer *s)
{
RingItem *item;
spice_assert(s == reds);
reds->vm_running = FALSE;
RING_FOREACH(item, &reds->char_devs_states) {
SpiceCharDeviceStateItem *st_item;
st_item = SPICE_CONTAINEROF(item, SpiceCharDeviceStateItem, link);
... | 303,333,808,868,231,160,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,405 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | static int ssl_password_cb(char *buf, int size, int flags, void *userdata)
{
char *pass = ssl_parameters.keyfile_password;
if (size < strlen(pass) + 1) {
return (0);
}
strcpy(buf, pass);
return (strlen(pass));
}
| 92,840,310,276,165,800,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,406 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | uint64_t *stat_add_counter(StatNodeRef parent, const char *name, int visible)
{
StatNodeRef ref = stat_add_node(parent, name, visible);
SpiceStatNode *node;
if (ref == INVALID_STAT_REF) {
return NULL;
}
node = &reds->stat->nodes[ref];
node->flags |= SPICE_STAT_NODE_FLAG_VALUE;
retur... | 134,538,988,624,076,860,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,407 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | StatNodeRef stat_add_node(StatNodeRef parent, const char *name, int visible)
{
StatNodeRef ref;
SpiceStatNode *node;
spice_assert(name && strlen(name) > 0);
if (strlen(name) >= sizeof(node->name)) {
return INVALID_STAT_REF;
}
pthread_mutex_lock(&reds->stat_lock);
ref = (parent == IN... | 85,022,882,264,857,105,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,408 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | static void stat_remove(SpiceStatNode *node)
{
pthread_mutex_lock(&reds->stat_lock);
node->flags &= ~SPICE_STAT_NODE_FLAG_ENABLED;
reds->stat->generation++;
reds->stat->num_of_nodes--;
pthread_mutex_unlock(&reds->stat_lock);
}
| 339,867,217,351,725,140,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,409 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | void stat_remove_counter(uint64_t *counter)
{
stat_remove((SpiceStatNode *)(counter - offsetof(SpiceStatNode, value)));
}
| 30,262,875,840,956,936,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,410 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | void stat_remove_node(StatNodeRef ref)
{
stat_remove(&reds->stat->nodes[ref]);
}
| 261,157,780,722,794,460,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,411 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | static ssize_t stream_read_cb(RedsStream *s, void *buf, size_t size)
{
return read(s->socket, buf, size);
}
| 246,249,156,466,847,780,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,412 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | static ssize_t stream_ssl_write_cb(RedsStream *s, const void *buf, size_t size)
{
int return_code;
SPICE_GNUC_UNUSED int ssl_error;
return_code = SSL_write(s->ssl, buf, size);
if (return_code < 0) {
ssl_error = SSL_get_error(s->ssl, return_code);
}
return return_code;
}
| 202,640,255,323,305,360,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,413 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | static ssize_t stream_write_cb(RedsStream *s, const void *buf, size_t size)
{
return write(s->socket, buf, size);
}
| 119,060,635,093,383,880,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,414 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | static ssize_t stream_writev_cb(RedsStream *s, const struct iovec *iov, int iovcnt)
{
ssize_t ret = 0;
do {
int tosend;
ssize_t n, expected = 0;
int i;
#ifdef IOV_MAX
tosend = MIN(iovcnt, IOV_MAX);
#else
tosend = iovcnt;
#endif
for (i = 0; i < tosend; i++) {
... | 218,923,867,132,840,400,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,415 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | static int sync_write(RedsStream *stream, const void *in_buf, size_t n)
{
const uint8_t *buf = (uint8_t *)in_buf;
while (n) {
int now = reds_stream_write(stream, buf, n);
if (now <= 0) {
if (now == -1 && (errno == EINTR || errno == EAGAIN)) {
continue;
}
... | 268,217,355,482,582,740,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,416 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | static void vdi_port_on_free_self_token(void *opaque)
{
if (inputs_inited() && reds->pending_mouse_event) {
spice_debug("pending mouse event");
reds_handle_agent_mouse_event(inputs_get_mouse_state());
}
}
| 264,524,266,415,630,170,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,417 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | static VDIReadBuf *vdi_port_read_buf_get(void)
{
VDIPortState *state = &reds->agent_state;
RingItem *item;
VDIReadBuf *buf;
if (!(item = ring_get_head(&state->read_bufs))) {
return NULL;
}
ring_remove(item);
buf = SPICE_CONTAINEROF(item, VDIReadBuf, link);
buf->refs = 1;
r... | 264,460,280,148,292,200,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,418 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | static int vdi_port_read_buf_process(int port, VDIReadBuf *buf)
{
VDIPortState *state = &reds->agent_state;
int res;
switch (port) {
case VDP_CLIENT_PORT: {
res = agent_msg_filter_process_data(&state->read_filter,
buf->data, buf->len);
switch ... | 42,867,169,587,943,980,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,419 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | static VDIReadBuf* vdi_port_read_buf_ref(VDIReadBuf *buf)
{
buf->refs++;
return buf;
}
| 121,925,892,393,105,140,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,420 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | static void vdi_port_read_buf_release(uint8_t *data, void *opaque)
{
VDIReadBuf *buf = (VDIReadBuf *)opaque;
vdi_port_read_buf_unref(buf);
}
| 335,000,902,358,556,200,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,421 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | static void vdi_port_read_buf_unref(VDIReadBuf *buf)
{
if (!--buf->refs) {
ring_add(&reds->agent_state.read_bufs, &buf->link);
/* read_one_msg_from_vdi_port may have never completed because the read_bufs
ring was empty. So we call it again so it can complete its work if
necessary. N... | 293,181,148,917,323,670,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,422 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | static SpiceCharDeviceMsgToClient *vdi_port_read_one_msg_from_device(SpiceCharDeviceInstance *sin,
void *opaque)
{
VDIPortState *state = &reds->agent_state;
SpiceCharDeviceInterface *sif;
VDIReadBuf *dispatch_buf;
int n;
if (!vdag... | 187,912,399,007,493,030,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,423 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | static void vdi_port_send_msg_to_client(SpiceCharDeviceMsgToClient *msg,
RedClient *client,
void *opaque)
{
VDIReadBuf *agent_data_buf = msg;
main_channel_client_push_agent_data(red_client_get_main(client),
... | 335,575,536,623,258,600,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,424 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | static void vdi_port_send_tokens_to_client(RedClient *client, uint32_t tokens, void *opaque)
{
main_channel_client_push_agent_tokens(red_client_get_main(client),
tokens);
}
| 129,235,570,760,915,540,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,425 | spice | 8af619009660b24e0b41ad26b30289eea288fcc2 | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/spice/commit/?id=8af619009660b24e0b41ad26b30289eea288fcc2 | Fix buffer overflow when decrypting client SPICE ticket
reds_handle_ticket uses a fixed size 'password' buffer for the decrypted
password whose size is SPICE_MAX_PASSWORD_LENGTH. However,
RSA_private_decrypt which we call for the decryption expects the
destination buffer to be at least RSA_size(link->tiTicketing.rsa)
... | 0 | static void vdi_port_unref_msg_to_client(SpiceCharDeviceMsgToClient *msg,
void *opaque)
{
vdi_port_read_buf_unref(msg);
}
| 336,825,986,774,491,840,000,000,000,000,000,000,000 | reds.c | 253,596,976,331,707,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4282 | Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. | https://nvd.nist.gov/vuln/detail/CVE-2013-4282 |
12,448 | 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 add_capability(uint32_t **caps, int *num_caps, uint32_t cap)
{
int nbefore, n;
nbefore = *num_caps;
n = cap / 32;
*num_caps = MAX(*num_caps, n + 1);
*caps = spice_renew(uint32_t, *caps, *num_caps);
memset(*caps + nbefore, 0, (*num_caps - nbefore) * sizeof(uint32_t));
(*caps)[n] ... | 188,450,141,247,495,530,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,449 | 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 do_nothing_handle_message(RedChannelClient *rcc,
uint16_t type,
uint32_t size,
uint8_t *msg)
{
return TRUE;
}
| 272,126,603,578,031,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,450 | 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 dummy_watch_remove(SpiceWatch *watch)
{
}
| 109,796,567,907,449,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,451 | 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 dummy_watch_update_mask(SpiceWatch *watch, int event_mask)
{
}
| 83,255,161,336,949,150,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,452 | 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 uint32_t full_header_get_msg_size(SpiceDataHeaderOpaque *header)
{
return ((SpiceDataHeader *)header->data)->size;
}
| 10,883,435,013,701,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,453 | 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 uint16_t full_header_get_msg_type(SpiceDataHeaderOpaque *header)
{
return ((SpiceDataHeader *)header->data)->type;
}
| 181,645,502,115,536,370,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,454 | 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 full_header_set_msg_serial(SpiceDataHeaderOpaque *header, uint64_t serial)
{
((SpiceDataHeader *)header->data)->serial = serial;
}
| 1,460,836,590,764,322,700,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,455 | 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 full_header_set_msg_size(SpiceDataHeaderOpaque *header, uint32_t size)
{
((SpiceDataHeader *)header->data)->size = size;
}
| 321,349,219,133,263,360,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,456 | 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 full_header_set_msg_sub_list(SpiceDataHeaderOpaque *header, uint32_t sub_list)
{
((SpiceDataHeader *)header->data)->sub_list = sub_list;
}
| 46,972,540,008,577,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,457 | 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 full_header_set_msg_type(SpiceDataHeaderOpaque *header, uint16_t type)
{
((SpiceDataHeader *)header->data)->type = type;
}
| 289,764,831,795,732,380,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,458 | 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 uint32_t mini_header_get_msg_size(SpiceDataHeaderOpaque *header)
{
return ((SpiceMiniDataHeader *)header->data)->size;
}
| 3,426,597,417,843,624,500,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,459 | 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 uint16_t mini_header_get_msg_type(SpiceDataHeaderOpaque *header)
{
return ((SpiceMiniDataHeader *)header->data)->type;
}
| 121,203,179,760,172,940,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,460 | 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 mini_header_set_msg_serial(SpiceDataHeaderOpaque *header, uint64_t serial)
{
spice_error("attempt to set header serial on mini header");
}
| 178,402,698,122,359,000,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,461 | 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 mini_header_set_msg_size(SpiceDataHeaderOpaque *header, uint32_t size)
{
((SpiceMiniDataHeader *)header->data)->size = size;
}
| 160,202,804,003,749,040,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,462 | 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 mini_header_set_msg_sub_list(SpiceDataHeaderOpaque *header, uint32_t sub_list)
{
spice_error("attempt to set header sub list on mini header");
}
| 70,137,446,854,928,260,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,463 | 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 mini_header_set_msg_type(SpiceDataHeaderOpaque *header, uint16_t type)
{
((SpiceMiniDataHeader *)header->data)->type = type;
}
| 116,647,429,650,721,010,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,464 | 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_add_client(RedChannel *channel, RedChannelClient *rcc)
{
spice_assert(rcc);
ring_add(&channel->clients, &rcc->channel_link);
channel->clients_num++;
}
| 131,179,978,566,830,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,465 | 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_all_blocked(RedChannel *channel)
{
RingItem *link;
RedChannelClient *rcc;
if (!channel || channel->clients_num == 0) {
return FALSE;
}
RING_FOREACH(link, &channel->clients) {
rcc = SPICE_CONTAINEROF(link, RedChannelClient, channel_link);
if (!rcc->send_data.b... | 66,987,801,933,018,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,466 | 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_any_blocked(RedChannel *channel)
{
RingItem *link;
RedChannelClient *rcc;
RING_FOREACH(link, &channel->clients) {
rcc = SPICE_CONTAINEROF(link, RedChannelClient, channel_link);
if (rcc->send_data.blocked) {
return TRUE;
}
}
return FALSE;
}
| 257,058,743,439,637,620,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,467 | 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_apply_clients(RedChannel *channel, channel_client_callback cb)
{
RingItem *link;
RingItem *next;
RedChannelClient *rcc;
RING_FOREACH_SAFE(link, next, &channel->clients) {
rcc = SPICE_CONTAINEROF(link, RedChannelClient, channel_link);
cb(rcc);
}
}
| 203,732,446,881,483,570,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,468 | 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_apply_clients_data(RedChannel *channel, channel_client_callback_data cb, void *data)
{
RingItem *link;
RingItem *next;
RedChannelClient *rcc;
RING_FOREACH_SAFE(link, next, &channel->clients) {
rcc = SPICE_CONTAINEROF(link, RedChannelClient, channel_link);
cb(rcc, data);... | 316,377,279,344,791,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,469 | 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_ack_set_client_window(RedChannelClient *rcc, int client_window)
{
rcc->ack_data.client_window = client_window;
}
| 339,714,342,989,070,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,470 | 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_ack_zero_messages_window(RedChannelClient *rcc)
{
rcc->ack_data.messages_window = 0;
}
| 316,207,662,613,070,560,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,471 | 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_blocked(RedChannelClient *rcc)
{
return rcc && rcc->send_data.blocked;
}
| 43,034,628,098,284,320,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,472 | 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_cancel_ping_timer(RedChannelClient *rcc)
{
if (!rcc->latency_monitor.timer) {
return;
}
if (rcc->latency_monitor.state != PING_STATE_TIMER) {
return;
}
rcc->channel->core->timer_cancel(rcc->latency_monitor.timer);
rcc->latency_monitor.state = PING_... | 133,211,873,505,958,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,473 | 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_clear_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;
}
rcc->send_data.blocked = FALSE;
rcc->send_data.size = 0;
}
| 250,256,684,305,394,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,474 | 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 | RedChannelClient *red_channel_client_create(int size, RedChannel *channel, RedClient *client,
RedsStream *stream,
int monitor_latency,
int num_common_caps, uint32_t *common_caps,
... | 39,047,634,947,405,305,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,475 | 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 | RedChannelClient *red_channel_client_create_dummy(int size,
RedChannel *channel,
RedClient *client,
int num_common_caps, uint32_t *common_caps,
... | 181,971,299,844,687,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,476 | 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_default_connect(RedChannel *channel, RedClient *client,
RedsStream *stream,
int migration,
int num_common_caps, uint32_t *common_caps,
... | 293,505,153,964,649,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,477 | 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_default_disconnect(RedChannelClient *base)
{
red_channel_client_disconnect(base);
}
| 240,444,655,632,595,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,478 | 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_default_migrate(RedChannelClient *rcc)
{
if (rcc->latency_monitor.timer) {
red_channel_client_cancel_ping_timer(rcc);
rcc->channel->core->timer_remove(rcc->latency_monitor.timer);
rcc->latency_monitor.timer = NULL;
}
red_channel_client_pipe_add_type(rcc, PIPE_... | 212,447,954,332,594,980,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,479 | 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_default_peer_on_error(RedChannelClient *rcc)
{
red_channel_client_disconnect(rcc);
}
| 308,422,912,931,546,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,480 | 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_destroy(RedChannelClient *rcc)
{
rcc->destroying = 1;
red_channel_client_disconnect(rcc);
red_client_remove_channel(rcc);
red_channel_client_unref(rcc);
}
| 310,195,645,556,634,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,481 | 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_destroy_remote_caps(RedChannelClient* rcc)
{
rcc->remote_caps.num_common_caps = 0;
free(rcc->remote_caps.common_caps);
rcc->remote_caps.num_caps = 0;
free(rcc->remote_caps.caps);
}
| 118,182,134,192,609,880,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,482 | 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_disconnect(RedChannelClient *rcc)
{
spice_printerr("%p (channel %p type %d id %d)", rcc, rcc->channel,
rcc->channel->type, rcc->channel->id);
if (rcc->dummy) {
red_channel_client_disconnect_dummy(rcc);
return;
}
if (... | 167,241,092,735,823,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,483 | 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_disconnect_dummy(RedChannelClient *rcc)
{
spice_assert(rcc->dummy);
if (ring_item_is_linked(&rcc->channel_link)) {
red_channel_remove_client(rcc);
}
rcc->dummy_connected = FALSE;
}
| 29,098,143,870,400,200,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,484 | 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_event(int fd, int event, void *data)
{
RedChannelClient *rcc = (RedChannelClient *)data;
red_channel_client_ref(rcc);
if (event & SPICE_WATCH_EVENT_READ) {
red_channel_client_receive(rcc);
}
if (event & SPICE_WATCH_EVENT_WRITE) {
red_channel_client_pus... | 250,787,660,995,906,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,485 | 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 | SpiceMarshaller *red_channel_client_get_marshaller(RedChannelClient *rcc)
{
return rcc->send_data.marshaller;
}
| 41,532,832,280,989,110,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,486 | 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 | uint64_t red_channel_client_get_message_serial(RedChannelClient *rcc)
{
return rcc->send_data.serial;
}
| 188,359,580,687,565,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,487 | 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_get_roundtrip_ms(RedChannelClient *rcc)
{
if (rcc->latency_monitor.roundtrip < 0) {
return rcc->latency_monitor.roundtrip;
}
return rcc->latency_monitor.roundtrip / 1000 / 1000;
}
| 206,634,879,446,086,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,488 | 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 | RedsStream *red_channel_client_get_stream(RedChannelClient *rcc)
{
return rcc->stream;
}
| 283,985,334,689,275,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,489 | 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_handle_message(RedChannelClient *rcc, uint32_t size,
uint16_t type, void *message)
{
switch (type) {
case SPICE_MSGC_ACK_SYNC:
if (size != sizeof(uint32_t)) {
spice_printerr("bad message size");
return FALSE;
}
... | 174,899,731,145,326,660,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,490 | 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_handle_pong(RedChannelClient *rcc, SpiceMsgPing *ping)
{
uint64_t now;
struct timespec ts;
/* ignoring unexpected pongs, or post-migration pongs for pings that
* started just before migration */
if (ping->id != rcc->latency_monitor.id) {
spice_warning("ping-i... | 106,405,339,623,301,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,491 | 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_init_outgoing_messages_window(RedChannelClient *rcc)
{
rcc->ack_data.messages_window = 0;
red_channel_client_push(rcc);
}
| 141,849,208,860,382,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,492 | 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_init_send_data(RedChannelClient *rcc, uint16_t msg_type, PipeItem *item)
{
spice_assert(red_channel_client_no_item_being_sent(rcc));
spice_assert(msg_type != 0);
rcc->send_data.header.set_msg_type(&rcc->send_data.header, msg_type);
rcc->send_data.item = item;
if (item) {
... | 176,356,560,730,542,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,493 | 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_is_connected(RedChannelClient *rcc)
{
if (!rcc->dummy) {
return rcc->stream != NULL;
} else {
return rcc->dummy_connected;
}
}
| 151,123,396,248,137,320,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,494 | 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_no_item_being_sent(RedChannelClient *rcc)
{
return !rcc || (rcc->send_data.size == 0);
}
| 306,036,121,509,525,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,495 | 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_on_output(void *opaque, int n)
{
RedChannelClient *rcc = opaque;
stat_inc_counter(rcc->channel->out_bytes_counter, n);
}
| 308,689,499,149,610,040,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,496 | 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_channel_client_peer_get_out_msg_size(void *opaque)
{
RedChannelClient *rcc = (RedChannelClient *)opaque;
return rcc->send_data.size;
}
| 39,724,929,485,629,617,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,497 | 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_peer_on_out_block(void *opaque)
{
RedChannelClient *rcc = (RedChannelClient *)opaque;
rcc->send_data.blocked = TRUE;
rcc->channel->core->watch_update_mask(rcc->stream->watch,
SPICE_WATCH_EVENT_READ |
SP... | 117,023,710,693,509,220,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,498 | 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_peer_prepare_out_msg(
void *opaque, struct iovec *vec, int *vec_size, int pos)
{
RedChannelClient *rcc = (RedChannelClient *)opaque;
*vec_size = spice_marshaller_fill_iovec(rcc->send_data.marshaller,
vec, IOV_MAX, pos);
}
| 205,411,247,670,967,200,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,499 | 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_ping_timer(void *opaque)
{
int so_unsent_size = 0;
RedChannelClient *rcc = opaque;
spice_assert(rcc->latency_monitor.state == PING_STATE_TIMER);
red_channel_client_cancel_ping_timer(rcc);
/* retrieving the occupied size of the socket's tcp snd buffer (unacked + unsent... | 207,642,064,251,902,430,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,500 | 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_pipe_add(RedChannelClient *rcc, PipeItem *item)
{
spice_assert(rcc && item);
rcc->pipe_size++;
ring_add(&rcc->pipe, &item->link);
}
| 48,026,597,918,808,010,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,501 | 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_pipe_add_after(RedChannelClient *rcc,
PipeItem *item, PipeItem *pos)
{
spice_assert(rcc);
spice_assert(pos);
spice_assert(item);
rcc->pipe_size++;
ring_add_after(&item->link, &pos->link);
}
| 31,159,402,757,396,885,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,502 | 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_pipe_add_empty_msg(RedChannelClient *rcc, int msg_type)
{
EmptyMsgPipeItem *item = spice_new(EmptyMsgPipeItem, 1);
red_channel_pipe_item_init(rcc->channel, &item->base, PIPE_ITEM_TYPE_EMPTY_MSG);
item->msg = msg_type;
red_channel_client_pipe_add(rcc, &item->base);
red_channe... | 279,999,390,076,152,000,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,503 | 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_pipe_add_push(RedChannelClient *rcc, PipeItem *item)
{
red_channel_client_pipe_add(rcc, item);
red_channel_client_push(rcc);
}
| 265,541,559,332,215,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,504 | 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_pipe_add_tail(RedChannelClient *rcc, PipeItem *item)
{
spice_assert(rcc);
rcc->pipe_size++;
ring_add_before(&item->link, &rcc->pipe);
red_channel_client_push(rcc);
}
| 95,848,967,741,031,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,505 | 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_pipe_add_tail_no_push(RedChannelClient *rcc,
PipeItem *item)
{
spice_assert(rcc);
rcc->pipe_size++;
ring_add_before(&item->link, &rcc->pipe);
}
| 292,727,043,192,440,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,506 | 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_pipe_add_type(RedChannelClient *rcc, int pipe_item_type)
{
PipeItem *item = spice_new(PipeItem, 1);
red_channel_pipe_item_init(rcc->channel, item, pipe_item_type);
red_channel_client_pipe_add(rcc, item);
red_channel_client_push(rcc);
}
| 115,300,301,467,680,200,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,507 | 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_pipe_clear(RedChannelClient *rcc)
{
PipeItem *item;
if (rcc) {
red_channel_client_clear_sent_item(rcc);
}
while ((item = (PipeItem *)ring_get_head(&rcc->pipe))) {
ring_remove(&item->link);
red_channel_client_release_item(rcc, item, FALSE);
}
rcc->... | 64,785,119,222,890,210,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,508 | 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 PipeItem *red_channel_client_pipe_item_get(RedChannelClient *rcc)
{
PipeItem *item;
if (!rcc || rcc->send_data.blocked
|| red_channel_client_waiting_for_ack(rcc)
|| !(item = (PipeItem *)ring_get_tail(&rcc->pipe))) {
return NULL;
}
red_channel_client_pipe_... | 101,279,353,215,700,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,509 | 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_pipe_item_is_linked(RedChannelClient *rcc,
PipeItem *item)
{
return ring_item_is_linked(&item->link);
}
| 243,125,896,199,849,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,510 | 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_pipe_remove(RedChannelClient *rcc, PipeItem *item)
{
rcc->pipe_size--;
ring_remove(&item->link);
}
| 66,305,986,108,527,240,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,511 | 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_pipe_remove_and_release(RedChannelClient *rcc,
PipeItem *item)
{
red_channel_client_pipe_remove(rcc, item);
red_channel_client_release_item(rcc, item, FALSE);
}
| 200,382,958,197,519,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,512 | 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_channel_client_pre_create_validate(RedChannel *channel, RedClient *client)
{
if (red_client_get_channel(client, channel->type, channel->id)) {
spice_printerr("Error client %p: duplicate channel type %d id %d",
client, channel->type, channel->id);
return FALSE;
... | 78,162,787,864,863,260,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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.