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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
378,967 | ImageMagick | 43539e67a47d2f8de832d33a5b26dc2a7a12294f | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/43539e67a47d2f8de832d33a5b26dc2a7a12294f | https://github.com/ImageMagick/ImageMagick/issues/1718 | 0 | MagickPrivate ResizeFilter *AcquireResizeFilter(const Image *image,
const FilterType filter,const MagickBooleanType cylindrical,
ExceptionInfo *exception)
{
const char
*artifact;
FilterType
filter_type,
window_type;
double
B,
C,
value;
register ResizeFilter
*resize_filter;
... | 131,040,440,400,898,630,000,000,000,000,000,000,000 | resize.c | 173,804,738,798,834,020,000,000,000,000,000,000,000 | [
"CWE-369"
] | CVE-2020-27763 | A flaw was found in ImageMagick in MagickCore/resize.c. An attacker who submits a crafted file that is processed by ImageMagick could trigger undefined behavior in the form of math division by zero. This would most likely lead to an impact to application availability, but could potentially cause other problems related ... | https://nvd.nist.gov/vuln/detail/CVE-2020-27763 |
206,249 | qemu | 37cee01784ff0df13e5209517e1b3594a5e792d1 | https://github.com/bonzini/qemu | https://git.qemu.org/?p=qemu.git;a=commit;h=37cee01784ff0df13e5209517e1b3594a5e792d1 | lan9118: switch to use qemu_receive_packet() for loopback
This patch switches to use qemu_receive_packet() which can detect
reentrancy and return early.
This is intended to address CVE-2021-3416.
Cc: Prasad J Pandit <ppandit@redhat.com>
Cc: qemu-stable@nongnu.org
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.co... | 1 | static void do_tx_packet(lan9118_state *s)
{
int n;
uint32_t status;
/* FIXME: Honor TX disable, and allow queueing of packets. */
if (s->phy_control & 0x4000) {
/* This assumes the receive routine doesn't touch the VLANClient. */
lan9118_receive(qemu_get_queue(s->nic), s->txp->data,... | 17,501,104,160,228,506,000,000,000,000,000,000,000 | lan9118.c | 150,867,774,602,595,360,000,000,000,000,000,000,000 | [
"CWE-835"
] | CVE-2021-3416 | A potential stack overflow via infinite loop issue was found in various NIC emulators of QEMU in versions up to and including 5.2.0. The issue occurs in loopback mode of a NIC wherein reentrant DMA checks get bypassed. A guest user/process may use this flaw to consume CPU cycles or crash the QEMU process on the host re... | https://nvd.nist.gov/vuln/detail/CVE-2021-3416 |
379,013 | qemu | 37cee01784ff0df13e5209517e1b3594a5e792d1 | https://github.com/bonzini/qemu | https://git.qemu.org/?p=qemu.git;a=commit;h=37cee01784ff0df13e5209517e1b3594a5e792d1 | lan9118: switch to use qemu_receive_packet() for loopback
This patch switches to use qemu_receive_packet() which can detect
reentrancy and return early.
This is intended to address CVE-2021-3416.
Cc: Prasad J Pandit <ppandit@redhat.com>
Cc: qemu-stable@nongnu.org
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.co... | 0 | static void do_tx_packet(lan9118_state *s)
{
int n;
uint32_t status;
/* FIXME: Honor TX disable, and allow queueing of packets. */
if (s->phy_control & 0x4000) {
/* This assumes the receive routine doesn't touch the VLANClient. */
qemu_receive_packet(qemu_get_queue(s->nic), s->txp->d... | 112,098,064,747,593,550,000,000,000,000,000,000,000 | lan9118.c | 118,319,715,290,702,040,000,000,000,000,000,000,000 | [
"CWE-835"
] | CVE-2021-3416 | A potential stack overflow via infinite loop issue was found in various NIC emulators of QEMU in versions up to and including 5.2.0. The issue occurs in loopback mode of a NIC wherein reentrant DMA checks get bypassed. A guest user/process may use this flaw to consume CPU cycles or crash the QEMU process on the host re... | https://nvd.nist.gov/vuln/detail/CVE-2021-3416 |
206,252 | linux | 00b5f37189d24ac3ed46cb7f11742094778c46ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/00b5f37189d24ac3ed46cb7f11742094778c46ce | KVM: x86: Avoid theoretical NULL pointer dereference in kvm_irq_delivery_to_apic_fast()
When kvm_irq_delivery_to_apic_fast() is called with APIC_DEST_SELF
shorthand, 'src' must not be NULL. Crash the VM with KVM_BUG_ON()
instead of crashing the host.
Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Message-Id: <... | 1 | bool kvm_irq_delivery_to_apic_fast(struct kvm *kvm, struct kvm_lapic *src,
struct kvm_lapic_irq *irq, int *r, struct dest_map *dest_map)
{
struct kvm_apic_map *map;
unsigned long bitmap;
struct kvm_lapic **dst = NULL;
int i;
bool ret;
*r = -1;
if (irq->shorthand == APIC_DEST_SELF) {
*r = kvm_apic_set_irq(s... | 90,382,124,303,191,500,000,000,000,000,000,000,000 | lapic.c | 55,263,102,031,628,360,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2022-2153 | A flaw was found in the Linux kernel’s KVM when attempting to set a SynIC IRQ. This issue makes it possible for a misbehaving VMM to write to SYNIC/STIMER MSRs, causing a NULL pointer dereference. This flaw allows an unprivileged local attacker on the host to issue specific ioctl calls, causing a kernel oops condition ... | https://nvd.nist.gov/vuln/detail/CVE-2022-2153 |
379,038 | linux | 00b5f37189d24ac3ed46cb7f11742094778c46ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/00b5f37189d24ac3ed46cb7f11742094778c46ce | KVM: x86: Avoid theoretical NULL pointer dereference in kvm_irq_delivery_to_apic_fast()
When kvm_irq_delivery_to_apic_fast() is called with APIC_DEST_SELF
shorthand, 'src' must not be NULL. Crash the VM with KVM_BUG_ON()
instead of crashing the host.
Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Message-Id: <... | 0 | bool kvm_irq_delivery_to_apic_fast(struct kvm *kvm, struct kvm_lapic *src,
struct kvm_lapic_irq *irq, int *r, struct dest_map *dest_map)
{
struct kvm_apic_map *map;
unsigned long bitmap;
struct kvm_lapic **dst = NULL;
int i;
bool ret;
*r = -1;
if (irq->shorthand == APIC_DEST_SELF) {
if (KVM_BUG_ON(!src, kv... | 124,981,977,772,337,200,000,000,000,000,000,000,000 | lapic.c | 254,914,464,310,514,520,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2022-2153 | A flaw was found in the Linux kernel’s KVM when attempting to set a SynIC IRQ. This issue makes it possible for a misbehaving VMM to write to SYNIC/STIMER MSRs, causing a NULL pointer dereference. This flaw allows an unprivileged local attacker on the host to issue specific ioctl calls, causing a kernel oops condition ... | https://nvd.nist.gov/vuln/detail/CVE-2022-2153 |
206,253 | libarchive | cfaa28168a07ea4a53276b63068f94fce37d6aff | https://github.com/libarchive/libarchive | https://github.com/libarchive/libarchive/commit/cfaa28168a07ea4a53276b63068f94fce37d6aff | ZIP reader: fix possible out-of-bounds read in zipx_lzma_alone_init()
Fixes #1672 | 1 | zipx_lzma_alone_init(struct archive_read *a, struct zip *zip)
{
lzma_ret r;
const uint8_t* p;
#pragma pack(push)
#pragma pack(1)
struct _alone_header {
uint8_t bytes[5];
uint64_t uncompressed_size;
} alone_header;
#pragma pack(pop)
if(zip->zipx_lzma_valid) {
lzma_end(&zip->zipx_lzma_stream);
zip->z... | 103,327,392,550,364,350,000,000,000,000,000,000,000 | archive_read_support_format_zip.c | 251,241,689,421,631,700,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2022-26280 | Libarchive v3.6.0 was discovered to contain an out-of-bounds read via the component zipx_lzma_alone_init. | https://nvd.nist.gov/vuln/detail/CVE-2022-26280 |
379,176 | libarchive | cfaa28168a07ea4a53276b63068f94fce37d6aff | https://github.com/libarchive/libarchive | https://github.com/libarchive/libarchive/commit/cfaa28168a07ea4a53276b63068f94fce37d6aff | ZIP reader: fix possible out-of-bounds read in zipx_lzma_alone_init()
Fixes #1672 | 0 | zipx_lzma_alone_init(struct archive_read *a, struct zip *zip)
{
lzma_ret r;
const uint8_t* p;
#pragma pack(push)
#pragma pack(1)
struct _alone_header {
uint8_t bytes[5];
uint64_t uncompressed_size;
} alone_header;
#pragma pack(pop)
if(zip->zipx_lzma_valid) {
lzma_end(&zip->zipx_lzma_stream);
zip->z... | 9,842,444,750,631,591,000,000,000,000,000,000,000 | archive_read_support_format_zip.c | 127,674,003,736,596,800,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2022-26280 | Libarchive v3.6.0 was discovered to contain an out-of-bounds read via the component zipx_lzma_alone_init. | https://nvd.nist.gov/vuln/detail/CVE-2022-26280 |
206,255 | nginx | c1be55f97211d38b69ac0c2027e6812ab8b1b94e | https://github.com/nginx/nginx | https://github.com/nginx/nginx/commit/c1be55f97211d38b69ac0c2027e6812ab8b1b94e | Discard request body when redirecting to a URL via error_page.
Reported by Bert JW Regeer and Francisco Oca Gonzalez. | 1 | ngx_http_send_error_page(ngx_http_request_t *r, ngx_http_err_page_t *err_page)
{
ngx_int_t overwrite;
ngx_str_t uri, args;
ngx_table_elt_t *location;
ngx_http_core_loc_conf_t *clcf;
overwrite = err_page->overwrite;
if (overwrite && overwrite != NGX_... | 59,944,697,289,846,510,000,000,000,000,000,000,000 | ngx_http_special_response.c | 31,236,048,360,387,410,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-20372 | NGINX before 1.17.7, with certain error_page configurations, allows HTTP request smuggling, as demonstrated by the ability of an attacker to read unauthorized web pages in environments where NGINX is being fronted by a load balancer. | https://nvd.nist.gov/vuln/detail/CVE-2019-20372 |
379,254 | nginx | c1be55f97211d38b69ac0c2027e6812ab8b1b94e | https://github.com/nginx/nginx | https://github.com/nginx/nginx/commit/c1be55f97211d38b69ac0c2027e6812ab8b1b94e | Discard request body when redirecting to a URL via error_page.
Reported by Bert JW Regeer and Francisco Oca Gonzalez. | 0 | ngx_http_send_error_page(ngx_http_request_t *r, ngx_http_err_page_t *err_page)
{
ngx_int_t overwrite;
ngx_str_t uri, args;
ngx_table_elt_t *location;
ngx_http_core_loc_conf_t *clcf;
overwrite = err_page->overwrite;
if (overwrite && overwrite != NGX_... | 172,030,819,034,491,560,000,000,000,000,000,000,000 | ngx_http_special_response.c | 112,114,793,270,006,960,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-20372 | NGINX before 1.17.7, with certain error_page configurations, allows HTTP request smuggling, as demonstrated by the ability of an attacker to read unauthorized web pages in environments where NGINX is being fronted by a load balancer. | https://nvd.nist.gov/vuln/detail/CVE-2019-20372 |
206,261 | DBD-mysql | 793b72b1a0baa5070adacaac0e12fd995a6fbabe | https://github.com/perl5-dbi/DBD-mysql | https://github.com/perl5-dbi/DBD-mysql/commit/793b72b1a0baa5070adacaac0e12fd995a6fbabe | Added Pali's fix for CVE-2016-1249 | 1 | dbd_st_prepare(
SV *sth,
imp_sth_t *imp_sth,
char *statement,
SV *attribs)
{
int i;
SV **svp;
dTHX;
#if MYSQL_VERSION_ID >= SERVER_PREPARE_VERSION
#if MYSQL_VERSION_ID < CALL_PLACEHOLDER_VERSION
char *str_ptr, *str_last_ptr;
#if MYSQL_VERSION_ID < LIMIT_PLACEHOLDER_VERSION
int limit_flag=0;
#endif
#en... | 338,873,433,215,036,950,000,000,000,000,000,000,000 | dbdimp.c | 147,235,249,423,498,510,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2016-1249 | The DBD::mysql module before 4.039 for Perl, when using server-side prepared statement support, allows attackers to cause a denial of service (out-of-bounds read) via vectors involving an unaligned number of placeholders in WHERE condition and output fields in SELECT expression. | https://nvd.nist.gov/vuln/detail/CVE-2016-1249 |
379,312 | DBD-mysql | 793b72b1a0baa5070adacaac0e12fd995a6fbabe | https://github.com/perl5-dbi/DBD-mysql | https://github.com/perl5-dbi/DBD-mysql/commit/793b72b1a0baa5070adacaac0e12fd995a6fbabe | Added Pali's fix for CVE-2016-1249 | 0 | dbd_st_prepare(
SV *sth,
imp_sth_t *imp_sth,
char *statement,
SV *attribs)
{
int i;
SV **svp;
dTHX;
#if MYSQL_VERSION_ID >= SERVER_PREPARE_VERSION
#if MYSQL_VERSION_ID < CALL_PLACEHOLDER_VERSION
char *str_ptr, *str_last_ptr;
#if MYSQL_VERSION_ID < LIMIT_PLACEHOLDER_VERSION
int limit_flag=0;
#endif
#en... | 263,061,443,857,039,020,000,000,000,000,000,000,000 | dbdimp.c | 31,375,838,371,176,796,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2016-1249 | The DBD::mysql module before 4.039 for Perl, when using server-side prepared statement support, allows attackers to cause a denial of service (out-of-bounds read) via vectors involving an unaligned number of placeholders in WHERE condition and output fields in SELECT expression. | https://nvd.nist.gov/vuln/detail/CVE-2016-1249 |
206,274 | samba | d77a74237e660dd2ce9f1e14b02635f8a2569653 | https://github.com/samba-team/samba | http://git.samba.org/?p=samba.git;a=commitdiff;h=d77a74237e660dd2ce9f1e14b02635f8a2569653 | s3: nmbd: Fix bug 10633 - nmbd denial of service
The Linux kernel has a bug in that it can give spurious
wakeups on a non-blocking UDP socket for a non-deliverable packet.
When nmbd was changed to use non-blocking sockets it
became vulnerable to a spurious wakeup from poll/epoll.
Fix sys_recvfile() to return on EWOU... | 1 | ssize_t sys_recvfrom(int s, void *buf, size_t len, int flags, struct sockaddr *from, socklen_t *fromlen)
{
ssize_t ret;
do {
ret = recvfrom(s, buf, len, flags, from, fromlen);
#if defined(EWOULDBLOCK)
} while (ret == -1 && (errno == EINTR || errno == EAGAIN || errno == EWOULDBLOCK));
#else
} while (ret == -1 && ... | 325,836,439,391,496,000,000,000,000,000,000,000,000 | system.c | 314,976,457,975,713,330,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0244 | The sys_recvfrom function in nmbd in Samba 3.6.x before 3.6.24, 4.0.x before 4.0.19, and 4.1.x before 4.1.9 allows remote attackers to cause a denial of service (infinite loop and CPU consumption) via a malformed UDP packet. | https://nvd.nist.gov/vuln/detail/CVE-2014-0244 |
379,724 | samba | d77a74237e660dd2ce9f1e14b02635f8a2569653 | https://github.com/samba-team/samba | http://git.samba.org/?p=samba.git;a=commitdiff;h=d77a74237e660dd2ce9f1e14b02635f8a2569653 | s3: nmbd: Fix bug 10633 - nmbd denial of service
The Linux kernel has a bug in that it can give spurious
wakeups on a non-blocking UDP socket for a non-deliverable packet.
When nmbd was changed to use non-blocking sockets it
became vulnerable to a spurious wakeup from poll/epoll.
Fix sys_recvfile() to return on EWOU... | 0 | ssize_t sys_send(int s, const void *msg, size_t len, int flags)
{
ssize_t ret;
do {
ret = send(s, msg, len, flags);
#if defined(EWOULDBLOCK)
} while (ret == -1 && (errno == EINTR || errno == EAGAIN || errno == EWOULDBLOCK));
#else
} while (ret == -1 && (errno == EINTR || errno == EAGAIN)); | 175,832,006,711,017,050,000,000,000,000,000,000,000 | system.c | 121,610,426,184,569,950,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0244 | The sys_recvfrom function in nmbd in Samba 3.6.x before 3.6.24, 4.0.x before 4.0.19, and 4.1.x before 4.1.9 allows remote attackers to cause a denial of service (infinite loop and CPU consumption) via a malformed UDP packet. | https://nvd.nist.gov/vuln/detail/CVE-2014-0244 |
206,276 | gst-plugins-bad | 7b12593cceaa0726d7fc370a7556a8e773ccf318 | https://github.com/GStreamer/gst-plugins-bad | https://github.com/GStreamer/gst-plugins-bad/commit/7b12593cceaa0726d7fc370a7556a8e773ccf318 | mpegtssection: Fix PAT parsing
Use the estimated number of programs for parsing. Avoids over-reading.
https://bugzilla.gnome.org/show_bug.cgi?id=775120 | 1 | _parse_pat (GstMpegtsSection * section)
{
GPtrArray *pat;
guint16 i = 0, nb_programs;
GstMpegtsPatProgram *program;
guint8 *data, *end;
/* Skip already parsed data */
data = section->data + 8;
/* stop at the CRC */
end = section->data + section->section_length;
/* Initialize program list */
nb_pr... | 70,063,139,423,178,570,000,000,000,000,000,000,000 | gstmpegtssection.c | 98,984,072,635,951,500,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2016-9813 | The _parse_pat function in the mpegts parser in GStreamer before 1.10.2 allows remote attackers to cause a denial of service (NULL pointer dereference and crash) via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2016-9813 |
379,791 | gst-plugins-bad | 7b12593cceaa0726d7fc370a7556a8e773ccf318 | https://github.com/GStreamer/gst-plugins-bad | https://github.com/GStreamer/gst-plugins-bad/commit/7b12593cceaa0726d7fc370a7556a8e773ccf318 | mpegtssection: Fix PAT parsing
Use the estimated number of programs for parsing. Avoids over-reading.
https://bugzilla.gnome.org/show_bug.cgi?id=775120 | 0 | _parse_pat (GstMpegtsSection * section)
{
GPtrArray *pat;
guint16 i, nb_programs;
GstMpegtsPatProgram *program;
guint8 *data, *end;
/* Skip already parsed data */
data = section->data + 8;
/* stop at the CRC */
end = section->data + section->section_length;
/* Initialize program list */
nb_progra... | 133,892,808,355,732,030,000,000,000,000,000,000,000 | gstmpegtssection.c | 224,299,742,673,468,840,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2016-9813 | The _parse_pat function in the mpegts parser in GStreamer before 1.10.2 allows remote attackers to cause a denial of service (NULL pointer dereference and crash) via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2016-9813 |
206,329 | cracklib | 33d7fa4585247cd2247a1ffa032ad245836c6edb | https://github.com/cracklib/cracklib | https://github.com/cracklib/cracklib/commit/33d7fa4585247cd2247a1ffa032ad245836c6edb | Fix a buffer overflow processing long words
A buffer overflow processing long words has been discovered. This commit
applies the patch from
https://build.opensuse.org/package/view_file/Base:System/cracklib/0004-overflow-processing-long-words.patch
by Howard Guo.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=8... | 1 | Mangle(input, control) /* returns a pointer to a controlled Mangle */
char *input;
char *control;
{
int limit;
register char *ptr;
static char area[STRINGSIZE];
char area2[STRINGSIZE];
area[0] = '\0';
strcpy(area, input);
for (ptr = control; *ptr; ptr++)
{
switch (*ptr)
{
ca... | 101,827,419,295,944,440,000,000,000,000,000,000,000 | rules.c | 314,973,262,186,105,200,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2016-6318 | Stack-based buffer overflow in the FascistGecosUser function in lib/fascist.c in cracklib allows local users to cause a denial of service (application crash) or gain privileges via a long GECOS field, involving longbuffer. | https://nvd.nist.gov/vuln/detail/CVE-2016-6318 |
380,388 | cracklib | 33d7fa4585247cd2247a1ffa032ad245836c6edb | https://github.com/cracklib/cracklib | https://github.com/cracklib/cracklib/commit/33d7fa4585247cd2247a1ffa032ad245836c6edb | Fix a buffer overflow processing long words
A buffer overflow processing long words has been discovered. This commit
applies the patch from
https://build.opensuse.org/package/view_file/Base:System/cracklib/0004-overflow-processing-long-words.patch
by Howard Guo.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=8... | 0 | Mangle(input, control) /* returns a pointer to a controlled Mangle */
char *input;
char *control;
{
int limit;
register char *ptr;
static char area[STRINGSIZE * 2] = {0};
char area2[STRINGSIZE * 2] = {0};
strcpy(area, input);
for (ptr = control; *ptr; ptr++)
{
switch (*ptr)
{
ca... | 121,521,321,450,578,390,000,000,000,000,000,000,000 | rules.c | 176,744,192,097,838,260,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2016-6318 | Stack-based buffer overflow in the FascistGecosUser function in lib/fascist.c in cracklib allows local users to cause a denial of service (application crash) or gain privileges via a long GECOS field, involving longbuffer. | https://nvd.nist.gov/vuln/detail/CVE-2016-6318 |
206,330 | libheif | f7399b62d7fbc596f1b2871578c1d2053bedf1dd | https://github.com/strukturag/libheif | https://github.com/strukturag/libheif/commit/f7399b62d7fbc596f1b2871578c1d2053bedf1dd | Handle case where referenced "iref" box doesn't exist (fixes #138). | 1 | Error HeifContext::get_id_of_non_virtual_child_image(heif_item_id id, heif_item_id& out) const
{
std::string image_type = m_heif_file->get_item_type(id);
if (image_type=="grid" ||
image_type=="iden" ||
image_type=="iovl") {
auto iref_box = m_heif_file->get_iref_box();
std::vector<heif_item_id> i... | 249,280,123,119,720,300,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2020-19499 | An issue was discovered in heif::Box_iref::get_references in libheif 1.4.0, allows attackers to cause a Denial of Service or possibly other unspecified impact due to an invalid memory read. | https://nvd.nist.gov/vuln/detail/CVE-2020-19499 |
380,392 | libheif | f7399b62d7fbc596f1b2871578c1d2053bedf1dd | https://github.com/strukturag/libheif | https://github.com/strukturag/libheif/commit/f7399b62d7fbc596f1b2871578c1d2053bedf1dd | Handle case where referenced "iref" box doesn't exist (fixes #138). | 0 | Error HeifContext::get_id_of_non_virtual_child_image(heif_item_id id, heif_item_id& out) const
{
std::string image_type = m_heif_file->get_item_type(id);
if (image_type=="grid" ||
image_type=="iden" ||
image_type=="iovl") {
auto iref_box = m_heif_file->get_iref_box();
if (!iref_box) {
retu... | 80,978,364,071,265,350,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2020-19499 | An issue was discovered in heif::Box_iref::get_references in libheif 1.4.0, allows attackers to cause a Denial of Service or possibly other unspecified impact due to an invalid memory read. | https://nvd.nist.gov/vuln/detail/CVE-2020-19499 |
206,332 | linux | 8ce39eb5a67aee25d9f05b40b673c95b23502e3e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8ce39eb5a67aee25d9f05b40b673c95b23502e3e | nfp: flower: fix memory leak in nfp_flower_spawn_vnic_reprs
In nfp_flower_spawn_vnic_reprs in the loop if initialization or the
allocations fail memory is leaked. Appropriate releases are added.
Fixes: b94524529741 ("nfp: flower: add per repr private data for LAG offload")
Signed-off-by: Navid Emamdoost <navid.emamdo... | 1 | nfp_flower_spawn_vnic_reprs(struct nfp_app *app,
enum nfp_flower_cmsg_port_vnic_type vnic_type,
enum nfp_repr_type repr_type, unsigned int cnt)
{
u8 nfp_pcie = nfp_cppcore_pcie_unit(app->pf->cpp);
struct nfp_flower_priv *priv = app->priv;
atomic_t *replies = &priv->reify_replies;
struct nfp_flower_rep... | 162,859,459,100,153,320,000,000,000,000,000,000,000 | main.c | 83,701,049,146,303,390,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2019-19081 | A memory leak in the nfp_flower_spawn_vnic_reprs() function in drivers/net/ethernet/netronome/nfp/flower/main.c in the Linux kernel before 5.3.4 allows attackers to cause a denial of service (memory consumption), aka CID-8ce39eb5a67a. | https://nvd.nist.gov/vuln/detail/CVE-2019-19081 |
380,440 | linux | 8ce39eb5a67aee25d9f05b40b673c95b23502e3e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8ce39eb5a67aee25d9f05b40b673c95b23502e3e | nfp: flower: fix memory leak in nfp_flower_spawn_vnic_reprs
In nfp_flower_spawn_vnic_reprs in the loop if initialization or the
allocations fail memory is leaked. Appropriate releases are added.
Fixes: b94524529741 ("nfp: flower: add per repr private data for LAG offload")
Signed-off-by: Navid Emamdoost <navid.emamdo... | 0 | nfp_flower_spawn_vnic_reprs(struct nfp_app *app,
enum nfp_flower_cmsg_port_vnic_type vnic_type,
enum nfp_repr_type repr_type, unsigned int cnt)
{
u8 nfp_pcie = nfp_cppcore_pcie_unit(app->pf->cpp);
struct nfp_flower_priv *priv = app->priv;
atomic_t *replies = &priv->reify_replies;
struct nfp_flower_rep... | 199,676,585,464,684,780,000,000,000,000,000,000,000 | None | null | [
"CWE-401"
] | CVE-2019-19081 | A memory leak in the nfp_flower_spawn_vnic_reprs() function in drivers/net/ethernet/netronome/nfp/flower/main.c in the Linux kernel before 5.3.4 allows attackers to cause a denial of service (memory consumption), aka CID-8ce39eb5a67a. | https://nvd.nist.gov/vuln/detail/CVE-2019-19081 |
206,340 | openldap | 9badb73425a67768c09bcaed1a9c26c684af6c30 | https://github.com/openldap/openldap | https://git.openldap.org/openldap/openldap/-/commit/9badb73425a67768c09bcaed1a9c26c684af6c30 | ITS#9454 fix issuerAndThisUpdateCheck | 1 | issuerAndThisUpdateCheck(
struct berval *in,
struct berval *is,
struct berval *tu,
void *ctx )
{
int numdquotes = 0;
struct berval x = *in;
struct berval ni = BER_BVNULL;
/* Parse GSER format */
enum {
HAVE_NONE = 0x0,
HAVE_ISSUER = 0x1,
HAVE_THISUPDATE = 0x2,
HAVE_ALL = ( HAVE_ISSUER | HAVE_THISUPDAT... | 279,150,725,391,311,500,000,000,000,000,000,000,000 | schema_init.c | 178,853,289,235,310,460,000,000,000,000,000,000,000 | [
"CWE-617"
] | CVE-2021-27212 | In OpenLDAP through 2.4.57 and 2.5.x through 2.5.1alpha, an assertion failure in slapd can occur in the issuerAndThisUpdateCheck function via a crafted packet, resulting in a denial of service (daemon exit) via a short timestamp. This is related to schema_init.c and checkTime. | https://nvd.nist.gov/vuln/detail/CVE-2021-27212 |
380,554 | openldap | 9badb73425a67768c09bcaed1a9c26c684af6c30 | https://github.com/openldap/openldap | https://git.openldap.org/openldap/openldap/-/commit/9badb73425a67768c09bcaed1a9c26c684af6c30 | ITS#9454 fix issuerAndThisUpdateCheck | 0 | issuerAndThisUpdateCheck(
struct berval *in,
struct berval *is,
struct berval *tu,
void *ctx )
{
int numdquotes = 0;
struct berval x = *in;
struct berval ni = BER_BVNULL;
/* Parse GSER format */
enum {
HAVE_NONE = 0x0,
HAVE_ISSUER = 0x1,
HAVE_THISUPDATE = 0x2,
HAVE_ALL = ( HAVE_ISSUER | HAVE_THISUPDAT... | 305,929,737,244,353,230,000,000,000,000,000,000,000 | schema_init.c | 50,725,013,164,397,910,000,000,000,000,000,000,000 | [
"CWE-617"
] | CVE-2021-27212 | In OpenLDAP through 2.4.57 and 2.5.x through 2.5.1alpha, an assertion failure in slapd can occur in the issuerAndThisUpdateCheck function via a crafted packet, resulting in a denial of service (daemon exit) via a short timestamp. This is related to schema_init.c and checkTime. | https://nvd.nist.gov/vuln/detail/CVE-2021-27212 |
206,341 | redis | 24cc0b984d4ed5045c6ff125b0e619b6ce5ea9c6 | https://github.com/antirez/redis | https://github.com/redis/redis/commit/24cc0b984d4ed5045c6ff125b0e619b6ce5ea9c6 | Fix integer overflow in _sdsMakeRoomFor (CVE-2021-41099) (#9558)
The existing overflow checks handled the greedy growing, but didn't handle
a case where the addition of the header size is what causes the overflow. | 1 | sds _sdsMakeRoomFor(sds s, size_t addlen, int greedy) {
void *sh, *newsh;
size_t avail = sdsavail(s);
size_t len, newlen;
char type, oldtype = s[-1] & SDS_TYPE_MASK;
int hdrlen;
size_t usable;
/* Return ASAP if there is enough space left. */
if (avail >= addlen) return s;
len = sds... | 317,499,763,028,066,930,000,000,000,000,000,000,000 | sds.c | 289,803,793,292,851,070,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2021-41099 | Redis is an open source, in-memory database that persists on disk. An integer overflow bug in the underlying string library can be used to corrupt the heap and potentially result with denial of service or remote code execution. The vulnerability involves changing the default proto-max-bulk-len configuration parameter t... | https://nvd.nist.gov/vuln/detail/CVE-2021-41099 |
380,565 | redis | 24cc0b984d4ed5045c6ff125b0e619b6ce5ea9c6 | https://github.com/antirez/redis | https://github.com/redis/redis/commit/24cc0b984d4ed5045c6ff125b0e619b6ce5ea9c6 | Fix integer overflow in _sdsMakeRoomFor (CVE-2021-41099) (#9558)
The existing overflow checks handled the greedy growing, but didn't handle
a case where the addition of the header size is what causes the overflow. | 0 | sds _sdsMakeRoomFor(sds s, size_t addlen, int greedy) {
void *sh, *newsh;
size_t avail = sdsavail(s);
size_t len, newlen, reqlen;
char type, oldtype = s[-1] & SDS_TYPE_MASK;
int hdrlen;
size_t usable;
/* Return ASAP if there is enough space left. */
if (avail >= addlen) return s;
l... | 275,854,825,923,622,650,000,000,000,000,000,000,000 | sds.c | 230,866,917,799,331,630,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2021-41099 | Redis is an open source, in-memory database that persists on disk. An integer overflow bug in the underlying string library can be used to corrupt the heap and potentially result with denial of service or remote code execution. The vulnerability involves changing the default proto-max-bulk-len configuration parameter t... | https://nvd.nist.gov/vuln/detail/CVE-2021-41099 |
206,359 | opencv | 5691d998ead1d9b0542bcfced36c2dceb3a59023 | https://github.com/opencv/opencv | https://github.com/opencv/opencv/commit/5691d998ead1d9b0542bcfced36c2dceb3a59023 | core(persistence): added null ptr checks | 1 | bool parse( char* ptr )
{
ptr = skipSpaces( ptr );
if ( !ptr || !*ptr )
return false;
FileNode root_collection(fs->getFS(), 0, 0);
if( *ptr == '{' )
{
FileNode root_node = fs->addNode(root_collection, std::string(), FileNode::MAP);
pa... | 86,322,245,994,193,500,000,000,000,000,000,000,000 | persistence_json.cpp | 222,141,642,948,304,400,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2019-14493 | An issue was discovered in OpenCV before 4.1.1. There is a NULL pointer dereference in the function cv::XMLParser::parse at modules/core/src/persistence.cpp. | https://nvd.nist.gov/vuln/detail/CVE-2019-14493 |
380,690 | opencv | 5691d998ead1d9b0542bcfced36c2dceb3a59023 | https://github.com/opencv/opencv | https://github.com/opencv/opencv/commit/5691d998ead1d9b0542bcfced36c2dceb3a59023 | core(persistence): added null ptr checks | 0 | bool parse( char* ptr )
{
if (!ptr)
CV_PARSE_ERROR_CPP("Invalid input");
ptr = skipSpaces( ptr );
if ( !ptr || !*ptr )
return false;
FileNode root_collection(fs->getFS(), 0, 0);
if( *ptr == '{' )
{
FileNode root_node = fs->ad... | 271,201,592,010,666,080,000,000,000,000,000,000,000 | persistence_json.cpp | 27,022,348,444,150,360,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2019-14493 | An issue was discovered in OpenCV before 4.1.1. There is a NULL pointer dereference in the function cv::XMLParser::parse at modules/core/src/persistence.cpp. | https://nvd.nist.gov/vuln/detail/CVE-2019-14493 |
206,362 | opencv | 5691d998ead1d9b0542bcfced36c2dceb3a59023 | https://github.com/opencv/opencv | https://github.com/opencv/opencv/commit/5691d998ead1d9b0542bcfced36c2dceb3a59023 | core(persistence): added null ptr checks | 1 | bool parse(char* ptr)
{
CV_Assert( fs != 0 );
std::string key, key2, type_name;
int tag_type = 0;
bool ok = false;
// CV_XML_INSIDE_TAG is used to prohibit leading comments
ptr = skipSpaces( ptr, CV_XML_INSIDE_TAG );
if( memcmp( ptr, "<?xml", 5 ) != 0 )... | 165,598,434,521,015,180,000,000,000,000,000,000,000 | persistence_xml.cpp | 103,749,191,393,054,180,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2019-14493 | An issue was discovered in OpenCV before 4.1.1. There is a NULL pointer dereference in the function cv::XMLParser::parse at modules/core/src/persistence.cpp. | https://nvd.nist.gov/vuln/detail/CVE-2019-14493 |
380,700 | opencv | 5691d998ead1d9b0542bcfced36c2dceb3a59023 | https://github.com/opencv/opencv | https://github.com/opencv/opencv/commit/5691d998ead1d9b0542bcfced36c2dceb3a59023 | core(persistence): added null ptr checks | 0 | bool parse(char* ptr)
{
CV_Assert( fs != 0 );
std::string key, key2, type_name;
int tag_type = 0;
bool ok = false;
// CV_XML_INSIDE_TAG is used to prohibit leading comments
ptr = skipSpaces( ptr, CV_XML_INSIDE_TAG );
if (!ptr)
CV_PARSE_ERROR_... | 303,945,420,125,129,000,000,000,000,000,000,000,000 | persistence_xml.cpp | 79,223,977,649,292,110,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2019-14493 | An issue was discovered in OpenCV before 4.1.1. There is a NULL pointer dereference in the function cv::XMLParser::parse at modules/core/src/persistence.cpp. | https://nvd.nist.gov/vuln/detail/CVE-2019-14493 |
206,364 | opencv | 5691d998ead1d9b0542bcfced36c2dceb3a59023 | https://github.com/opencv/opencv | https://github.com/opencv/opencv/commit/5691d998ead1d9b0542bcfced36c2dceb3a59023 | core(persistence): added null ptr checks | 1 | bool parse( char* ptr )
{
bool first = true;
bool ok = true;
FileNode root_collection(fs->getFS(), 0, 0);
for(;;)
{
// 0. skip leading comments and directives and ...
// 1. reach the first item
for(;;)
{
pt... | 155,421,972,265,754,690,000,000,000,000,000,000,000 | persistence_yml.cpp | 78,365,908,269,031,730,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2019-14493 | An issue was discovered in OpenCV before 4.1.1. There is a NULL pointer dereference in the function cv::XMLParser::parse at modules/core/src/persistence.cpp. | https://nvd.nist.gov/vuln/detail/CVE-2019-14493 |
380,711 | opencv | 5691d998ead1d9b0542bcfced36c2dceb3a59023 | https://github.com/opencv/opencv | https://github.com/opencv/opencv/commit/5691d998ead1d9b0542bcfced36c2dceb3a59023 | core(persistence): added null ptr checks | 0 | bool parse( char* ptr )
{
if (!ptr)
CV_PARSE_ERROR_CPP("Invalid input");
bool first = true;
bool ok = true;
FileNode root_collection(fs->getFS(), 0, 0);
for(;;)
{
// 0. skip leading comments and directives and ...
// 1. reach... | 283,250,287,675,925,930,000,000,000,000,000,000,000 | persistence_yml.cpp | 114,263,838,743,274,910,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2019-14493 | An issue was discovered in OpenCV before 4.1.1. There is a NULL pointer dereference in the function cv::XMLParser::parse at modules/core/src/persistence.cpp. | https://nvd.nist.gov/vuln/detail/CVE-2019-14493 |
206,366 | haproxy | bfb15ab34ead85f64cd6da0e9fb418c9cd14cee8 | https://github.com/haproxy/haproxy | https://github.com/haproxy/haproxy/commit/bfb15ab34ead85f64cd6da0e9fb418c9cd14cee8 | BUG/MAJOR: http/htx: prevent unbounded loop in http_manage_server_side_cookies
Ensure calls to http_find_header() terminate. If a "Set-Cookie2"
header is found then the while(1) loop in
http_manage_server_side_cookies() will never terminate, resulting in
the watchdog firing and the process terminating via SIGABRT.
Th... | 1 | static void http_manage_server_side_cookies(struct stream *s, struct channel *res)
{
struct session *sess = s->sess;
struct http_txn *txn = s->txn;
struct htx *htx;
struct http_hdr_ctx ctx;
struct server *srv;
char *hdr_beg, *hdr_end;
char *prev, *att_beg, *att_end, *equal, *val_beg, *val_end, *next;
int is_coo... | 256,419,690,196,809,900,000,000,000,000,000,000,000 | http_ana.c | 318,145,318,038,281,470,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2022-0711 | A flaw was found in the way HAProxy processed HTTP responses containing the "Set-Cookie2" header. This flaw could allow an attacker to send crafted HTTP response packets which lead to an infinite loop, eventually resulting in a denial of service condition. The highest threat from this vulnerability is availability. | https://nvd.nist.gov/vuln/detail/CVE-2022-0711 |
380,743 | haproxy | bfb15ab34ead85f64cd6da0e9fb418c9cd14cee8 | https://github.com/haproxy/haproxy | https://github.com/haproxy/haproxy/commit/bfb15ab34ead85f64cd6da0e9fb418c9cd14cee8 | BUG/MAJOR: http/htx: prevent unbounded loop in http_manage_server_side_cookies
Ensure calls to http_find_header() terminate. If a "Set-Cookie2"
header is found then the while(1) loop in
http_manage_server_side_cookies() will never terminate, resulting in
the watchdog firing and the process terminating via SIGABRT.
Th... | 0 | static void http_manage_server_side_cookies(struct stream *s, struct channel *res)
{
struct session *sess = s->sess;
struct http_txn *txn = s->txn;
struct htx *htx;
struct http_hdr_ctx ctx;
struct server *srv;
char *hdr_beg, *hdr_end;
char *prev, *att_beg, *att_end, *equal, *val_beg, *val_end, *next;
int is_coo... | 17,090,041,627,448,226,000,000,000,000,000,000,000 | http_ana.c | 28,381,506,185,217,635,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2022-0711 | A flaw was found in the way HAProxy processed HTTP responses containing the "Set-Cookie2" header. This flaw could allow an attacker to send crafted HTTP response packets which lead to an infinite loop, eventually resulting in a denial of service condition. The highest threat from this vulnerability is availability. | https://nvd.nist.gov/vuln/detail/CVE-2022-0711 |
206,414 | linux | 819b23f1c501b17b9694325471789e6b5cc2d0d2 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=819b23f1c501b17b9694325471789e6b5cc2d0d2 | ext4: always check block group bounds in ext4_init_block_bitmap()
Regardless of whether the flex_bg feature is set, we should always
check to make sure the bits we are setting in the block bitmap are
within the block group bounds.
https://bugzilla.kernel.org/show_bug.cgi?id=199865
Signed-off-by: Theodore Ts'o <tytso... | 1 | static int ext4_init_block_bitmap(struct super_block *sb,
struct buffer_head *bh,
ext4_group_t block_group,
struct ext4_group_desc *gdp)
{
unsigned int bit, bit_max;
struct ext4_sb_info *sbi = EXT4_SB(sb);
ext4_fsblk_t start, tmp;
int flex_bg = 0;
J_ASSERT_BH(bh, buffer_locked(bh));
/* If c... | 117,903,950,515,274,600,000,000,000,000,000,000,000 | balloc.c | 48,749,550,431,085,350,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2018-10878 | A flaw was found in the Linux kernel's ext4 filesystem. A local user can cause an out-of-bounds write and a denial of service or unspecified other impact is possible by mounting and operating a crafted ext4 filesystem image. | https://nvd.nist.gov/vuln/detail/CVE-2018-10878 |
380,932 | linux | 819b23f1c501b17b9694325471789e6b5cc2d0d2 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=819b23f1c501b17b9694325471789e6b5cc2d0d2 | ext4: always check block group bounds in ext4_init_block_bitmap()
Regardless of whether the flex_bg feature is set, we should always
check to make sure the bits we are setting in the block bitmap are
within the block group bounds.
https://bugzilla.kernel.org/show_bug.cgi?id=199865
Signed-off-by: Theodore Ts'o <tytso... | 0 | static int ext4_init_block_bitmap(struct super_block *sb,
struct buffer_head *bh,
ext4_group_t block_group,
struct ext4_group_desc *gdp)
{
unsigned int bit, bit_max;
struct ext4_sb_info *sbi = EXT4_SB(sb);
ext4_fsblk_t start, tmp;
J_ASSERT_BH(bh, buffer_locked(bh));
/* If checksum is bad mar... | 178,679,703,954,277,880,000,000,000,000,000,000,000 | balloc.c | 203,187,898,457,897,200,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2018-10878 | A flaw was found in the Linux kernel's ext4 filesystem. A local user can cause an out-of-bounds write and a denial of service or unspecified other impact is possible by mounting and operating a crafted ext4 filesystem image. | https://nvd.nist.gov/vuln/detail/CVE-2018-10878 |
206,415 | php-src | 2d3d72412a6734e19a38ed10f385227a6238e4a6 | https://github.com/php/php-src | https://github.com/php/php-src/commit/2d3d72412a6734e19a38ed10f385227a6238e4a6 | Fix #77423: parse_url() will deliver a wrong host to user
To avoid that `parse_url()` returns an erroneous host, which would be
valid for `FILTER_VALIDATE_URL`, we make sure that only userinfo which
is valid according to RFC 3986 is treated as such.
For consistency with the existing url parsing code, we use ctype
fun... | 1 | PHPAPI php_url *php_url_parse_ex(char const *str, size_t length)
{
char port_buf[6];
php_url *ret = ecalloc(1, sizeof(php_url));
char const *s, *e, *p, *pp, *ue;
s = str;
ue = s + length;
/* parse scheme */
if ((e = memchr(s, ':', length)) && e != s) {
/* validate scheme */
p = s;
while (p < e) {
/* s... | 13,877,044,810,541,438,000,000,000,000,000,000,000 | url.c | 83,745,363,475,758,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2020-7071 | In PHP versions 7.3.x below 7.3.26, 7.4.x below 7.4.14 and 8.0.0, when validating URL with functions like filter_var($url, FILTER_VALIDATE_URL), PHP will accept an URL with invalid password as valid URL. This may lead to functions that rely on URL being valid to mis-parse the URL and produce wrong data as components of... | https://nvd.nist.gov/vuln/detail/CVE-2020-7071 |
380,938 | php-src | 2d3d72412a6734e19a38ed10f385227a6238e4a6 | https://github.com/php/php-src | https://github.com/php/php-src/commit/2d3d72412a6734e19a38ed10f385227a6238e4a6 | Fix #77423: parse_url() will deliver a wrong host to user
To avoid that `parse_url()` returns an erroneous host, which would be
valid for `FILTER_VALIDATE_URL`, we make sure that only userinfo which
is valid according to RFC 3986 is treated as such.
For consistency with the existing url parsing code, we use ctype
fun... | 0 | PHPAPI php_url *php_url_parse_ex(char const *str, size_t length)
{
char port_buf[6];
php_url *ret = ecalloc(1, sizeof(php_url));
char const *s, *e, *p, *pp, *ue;
s = str;
ue = s + length;
/* parse scheme */
if ((e = memchr(s, ':', length)) && e != s) {
/* validate scheme */
p = s;
while (p < e) {
/* s... | 144,884,197,857,150,260,000,000,000,000,000,000,000 | url.c | 196,687,129,291,332,700,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2020-7071 | In PHP versions 7.3.x below 7.3.26, 7.4.x below 7.4.14 and 8.0.0, when validating URL with functions like filter_var($url, FILTER_VALIDATE_URL), PHP will accept an URL with invalid password as valid URL. This may lead to functions that rely on URL being valid to mis-parse the URL and produce wrong data as components of... | https://nvd.nist.gov/vuln/detail/CVE-2020-7071 |
206,458 | taglib | dcdf4fd954e3213c355746fa15b7480461972308 | https://github.com/taglib/taglib | https://github.com/taglib/taglib/commit/dcdf4fd954e3213c355746fa15b7480461972308 | Avoid uint overflow in case the length + index is over UINT_MAX | 1 | ByteVector ByteVector::mid(uint index, uint length) const
{
ByteVector v;
if(index > size())
return v;
ConstIterator endIt;
if(length < 0xffffffff && length + index < size())
endIt = d->data.begin() + index + length;
else
endIt = d->data.end();
v.d->data.insert(v.d->data.begin(), ConstIterat... | 55,829,333,746,245,790,000,000,000,000,000,000,000 | tbytevector.cpp | 187,179,701,026,000,600,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2012-1584 | Integer overflow in the mid function in toolkit/tbytevector.cpp in TagLib 1.7 and earlier allows context-dependent attackers to cause a denial of service (application crash) via a crafted file header field in a media file, which triggers a large memory allocation. | https://nvd.nist.gov/vuln/detail/CVE-2012-1584 |
381,298 | taglib | dcdf4fd954e3213c355746fa15b7480461972308 | https://github.com/taglib/taglib | https://github.com/taglib/taglib/commit/dcdf4fd954e3213c355746fa15b7480461972308 | Avoid uint overflow in case the length + index is over UINT_MAX | 0 | ByteVector ByteVector::mid(uint index, uint length) const
{
ByteVector v;
if(index > size())
return v;
ConstIterator endIt;
if(length < size() - index)
endIt = d->data.begin() + index + length;
else
endIt = d->data.end();
v.d->data.insert(v.d->data.begin(), ConstIterator(d->data.begin() + in... | 291,892,524,292,591,300,000,000,000,000,000,000,000 | tbytevector.cpp | 10,845,877,402,355,880,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2012-1584 | Integer overflow in the mid function in toolkit/tbytevector.cpp in TagLib 1.7 and earlier allows context-dependent attackers to cause a denial of service (application crash) via a crafted file header field in a media file, which triggers a large memory allocation. | https://nvd.nist.gov/vuln/detail/CVE-2012-1584 |
206,491 | qemu | cffb446e8fd19a14e1634c7a3a8b07be3f01d5c9 | https://github.com/bonzini/qemu | https://git.qemu.org/?p=qemu.git;a=commit;h=cffb446e8fd19a14e1634c7a3a8b07be3f01d5c9 | hw/sd: sdhci: Reset the data pointer of s->fifo_buffer[] when a different block size is programmed
If the block size is programmed to a different value from the
previous one, reset the data pointer of s->fifo_buffer[] so that
s->fifo_buffer[] can be filled in using the new block size in
the next transfer.
With this f... | 1 | sdhci_write(void *opaque, hwaddr offset, uint64_t val, unsigned size)
{
SDHCIState *s = (SDHCIState *)opaque;
unsigned shift = 8 * (offset & 0x3);
uint32_t mask = ~(((1ULL << (size * 8)) - 1) << shift);
uint32_t value = val;
value <<= shift;
if (timer_pending(s->transfer_timer)) {
sdhc... | 284,196,491,939,309,240,000,000,000,000,000,000,000 | sdhci.c | 196,004,443,585,549,200,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2021-3409 | The patch for CVE-2020-17380/CVE-2020-25085 was found to be ineffective, thus making QEMU vulnerable to the out-of-bounds read/write access issues previously found in the SDHCI controller emulation code. This flaw allows a malicious privileged guest to crash the QEMU process on the host, resulting in a denial of servic... | https://nvd.nist.gov/vuln/detail/CVE-2021-3409 |
381,720 | qemu | cffb446e8fd19a14e1634c7a3a8b07be3f01d5c9 | https://github.com/bonzini/qemu | https://git.qemu.org/?p=qemu.git;a=commit;h=cffb446e8fd19a14e1634c7a3a8b07be3f01d5c9 | hw/sd: sdhci: Reset the data pointer of s->fifo_buffer[] when a different block size is programmed
If the block size is programmed to a different value from the
previous one, reset the data pointer of s->fifo_buffer[] so that
s->fifo_buffer[] can be filled in using the new block size in
the next transfer.
With this f... | 0 | sdhci_write(void *opaque, hwaddr offset, uint64_t val, unsigned size)
{
SDHCIState *s = (SDHCIState *)opaque;
unsigned shift = 8 * (offset & 0x3);
uint32_t mask = ~(((1ULL << (size * 8)) - 1) << shift);
uint32_t value = val;
value <<= shift;
if (timer_pending(s->transfer_timer)) {
sdhc... | 107,162,306,664,992,040,000,000,000,000,000,000,000 | sdhci.c | 249,341,765,627,820,170,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2021-3409 | The patch for CVE-2020-17380/CVE-2020-25085 was found to be ineffective, thus making QEMU vulnerable to the out-of-bounds read/write access issues previously found in the SDHCI controller emulation code. This flaw allows a malicious privileged guest to crash the QEMU process on the host, resulting in a denial of servic... | https://nvd.nist.gov/vuln/detail/CVE-2021-3409 |
206,493 | gst-plugins-base | 81d3ba3fa212bb25fe2ac661993887c4b69af6f1 | https://github.com/GStreamer/gst-plugins-base | https://github.com/GStreamer/gst-plugins-base/commit/81d3ba3fa212bb25fe2ac661993887c4b69af6f1 | riff-media: Check for valid channels/rate before using the values
Otherwise we might divide by zero or otherwise create invalid caps.
https://bugzilla.gnome.org/show_bug.cgi?id=777262 | 1 | gst_riff_create_audio_caps (guint16 codec_id,
gst_riff_strh * strh, gst_riff_strf_auds * strf,
GstBuffer * strf_data, GstBuffer * strd_data, char **codec_name,
gint channel_reorder_map[18])
{
gboolean block_align = FALSE, rate_chan = TRUE;
GstCaps *caps = NULL;
gint i;
if (channel_reorder_map)
... | 114,510,539,903,322,000,000,000,000,000,000,000,000 | None | null | [
"CWE-369"
] | CVE-2017-5837 | The gst_riff_create_audio_caps function in gst-libs/gst/riff/riff-media.c in gst-plugins-base in GStreamer before 1.10.3 allows remote attackers to cause a denial of service (floating point exception and crash) via a crafted video file. | https://nvd.nist.gov/vuln/detail/CVE-2017-5837 |
381,733 | gst-plugins-base | 81d3ba3fa212bb25fe2ac661993887c4b69af6f1 | https://github.com/GStreamer/gst-plugins-base | https://github.com/GStreamer/gst-plugins-base/commit/81d3ba3fa212bb25fe2ac661993887c4b69af6f1 | riff-media: Check for valid channels/rate before using the values
Otherwise we might divide by zero or otherwise create invalid caps.
https://bugzilla.gnome.org/show_bug.cgi?id=777262 | 0 | gst_riff_create_audio_caps (guint16 codec_id,
gst_riff_strh * strh, gst_riff_strf_auds * strf,
GstBuffer * strf_data, GstBuffer * strd_data, char **codec_name,
gint channel_reorder_map[18])
{
gboolean block_align = FALSE, rate_chan = TRUE;
GstCaps *caps = NULL;
gint i;
if (channel_reorder_map)
... | 199,407,471,864,953,550,000,000,000,000,000,000,000 | None | null | [
"CWE-369"
] | CVE-2017-5837 | The gst_riff_create_audio_caps function in gst-libs/gst/riff/riff-media.c in gst-plugins-base in GStreamer before 1.10.3 allows remote attackers to cause a denial of service (floating point exception and crash) via a crafted video file. | https://nvd.nist.gov/vuln/detail/CVE-2017-5837 |
206,495 | gimp | a9671395f6573e90316a9d748588c5435216f6ce | https://github.com/GNOME/gimp | http://git.gnome.org/browse/gimp/commit/?id=a9671395f6573e90316a9d748588c5435216f6ce | PCX: Avoid allocation overflows.
Multiplying gint values may overflow unless cast into a larger type. | 1 | load_image (const gchar *filename,
GError **error)
{
FILE *fd;
GimpDrawable *drawable;
GimpPixelRgn pixel_rgn;
guint16 offset_x, offset_y, bytesperline;
gint32 width, height;
gint32 image, layer;
guchar *dest, cmap[768];
guint8 header_buf[128];... | 174,461,229,176,372,030,000,000,000,000,000,000,000 | file-pcx.c | 156,623,078,661,560,030,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2011-1178 | Multiple integer overflows in the load_image function in file-pcx.c in the Personal Computer Exchange (PCX) plugin in GIMP 2.6.x and earlier allow remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted PCX image that triggers a heap-based buffer overflow. | https://nvd.nist.gov/vuln/detail/CVE-2011-1178 |
381,746 | gimp | a9671395f6573e90316a9d748588c5435216f6ce | https://github.com/GNOME/gimp | http://git.gnome.org/browse/gimp/commit/?id=a9671395f6573e90316a9d748588c5435216f6ce | PCX: Avoid allocation overflows.
Multiplying gint values may overflow unless cast into a larger type. | 0 | load_image (const gchar *filename,
GError **error)
{
FILE *fd;
GimpDrawable *drawable;
GimpPixelRgn pixel_rgn;
guint16 offset_x, offset_y, bytesperline;
gint32 width, height;
gint32 image, layer;
guchar *dest, cmap[768];
guint8 header_buf[128];... | 58,094,975,385,294,890,000,000,000,000,000,000,000 | file-pcx.c | 275,028,944,563,909,830,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2011-1178 | Multiple integer overflows in the load_image function in file-pcx.c in the Personal Computer Exchange (PCX) plugin in GIMP 2.6.x and earlier allow remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted PCX image that triggers a heap-based buffer overflow. | https://nvd.nist.gov/vuln/detail/CVE-2011-1178 |
206,519 | ImageMagick | a47e7a994766b92b10d4a87df8c1c890c8b170f3 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/a47e7a994766b92b10d4a87df8c1c890c8b170f3 | https://github.com/ImageMagick/ImageMagick/issues/1724 | 1 | MagickExport MagickBooleanType SetImageAlphaChannel(Image *image,
const AlphaChannelOption alpha_type,ExceptionInfo *exception)
{
CacheView
*image_view;
MagickBooleanType
status;
ssize_t
y;
assert(image != (Image *) NULL);
if (image->debug != MagickFalse)
(void) LogMagickEvent(TraceEvent,... | 314,125,977,496,999,000,000,000,000,000,000,000,000 | channel.c | 151,069,586,909,253,210,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2020-25663 | A call to ConformPixelInfo() in the SetImageAlphaChannel() routine of /MagickCore/channel.c caused a subsequent heap-use-after-free or heap-buffer-overflow READ when GetPixelRed() or GetPixelBlue() was called. This could occur if an attacker is able to submit a malicious image file to be processed by ImageMagick and co... | https://nvd.nist.gov/vuln/detail/CVE-2020-25663 |
382,126 | ImageMagick | a47e7a994766b92b10d4a87df8c1c890c8b170f3 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/a47e7a994766b92b10d4a87df8c1c890c8b170f3 | https://github.com/ImageMagick/ImageMagick/issues/1724 | 0 | MagickExport MagickBooleanType SetImageAlphaChannel(Image *image,
const AlphaChannelOption alpha_type,ExceptionInfo *exception)
{
CacheView
*image_view;
MagickBooleanType
status;
ssize_t
y;
assert(image != (Image *) NULL);
if (image->debug != MagickFalse)
(void) LogMagickEvent(TraceEvent,... | 293,984,533,938,619,830,000,000,000,000,000,000,000 | channel.c | 38,021,156,089,399,940,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2020-25663 | A call to ConformPixelInfo() in the SetImageAlphaChannel() routine of /MagickCore/channel.c caused a subsequent heap-use-after-free or heap-buffer-overflow READ when GetPixelRed() or GetPixelBlue() was called. This could occur if an attacker is able to submit a malicious image file to be processed by ImageMagick and co... | https://nvd.nist.gov/vuln/detail/CVE-2020-25663 |
206,523 | poppler | 30c731b487190c02afff3f036736a392eb60cd9a | https://github.com/freedesktop/poppler | https://gitlab.freedesktop.org/poppler/poppler/-/commit/30c731b487190c02afff3f036736a392eb60cd9a | Properly initialize HtmlOutputDev::page to avoid SIGSEGV upon error exit.
Closes #742 | 1 | HtmlOutputDev::HtmlOutputDev(Catalog *catalogA, const char *fileName, const char *title,
const char *author, const char *keywords, const char *subject, const char *date,
bool rawOrder, int firstPage, bool outline)
{
catalog = catalogA;
fContentsFrame = nullptr;
docTitle = new GooString(title);
pages = nullpt... | 189,259,989,103,865,920,000,000,000,000,000,000,000 | HtmlOutputDev.cc | 172,867,718,193,740,050,000,000,000,000,000,000,000 | [
"CWE-824"
] | CVE-2020-27778 | A flaw was found in Poppler in the way certain PDF files were converted into HTML. A remote attacker could exploit this flaw by providing a malicious PDF file that, when processed by the 'pdftohtml' program, would crash the application causing a denial of service. | https://nvd.nist.gov/vuln/detail/CVE-2020-27778 |
382,188 | poppler | 30c731b487190c02afff3f036736a392eb60cd9a | https://github.com/freedesktop/poppler | https://gitlab.freedesktop.org/poppler/poppler/-/commit/30c731b487190c02afff3f036736a392eb60cd9a | Properly initialize HtmlOutputDev::page to avoid SIGSEGV upon error exit.
Closes #742 | 0 | HtmlOutputDev::HtmlOutputDev(Catalog *catalogA, const char *fileName, const char *title,
const char *author, const char *keywords, const char *subject, const char *date,
bool rawOrder, int firstPage, bool outline)
{
catalog = catalogA;
fContentsFrame = nullptr;
page = nullptr;
docTitle = new GooString(title)... | 221,407,663,964,117,900,000,000,000,000,000,000,000 | HtmlOutputDev.cc | 174,002,491,608,462,570,000,000,000,000,000,000,000 | [
"CWE-824"
] | CVE-2020-27778 | A flaw was found in Poppler in the way certain PDF files were converted into HTML. A remote attacker could exploit this flaw by providing a malicious PDF file that, when processed by the 'pdftohtml' program, would crash the application causing a denial of service. | https://nvd.nist.gov/vuln/detail/CVE-2020-27778 |
206,527 | bro | c2b18849f8bb833253538f5dfedb4ed1dc176a30 | https://github.com/bro/bro | https://github.com/bro/bro/commit/c2b18849f8bb833253538f5dfedb4ed1dc176a30 | Fix IRC names command parsing | 1 | void IRC_Analyzer::DeliverStream(int length, const u_char* line, bool orig)
{
tcp::TCP_ApplicationAnalyzer::DeliverStream(length, line, orig);
if ( starttls )
{
ForwardStream(length, line, orig);
return;
}
// check line size
if ( length > 512 )
{
Weird("irc_line_size_exceeded");
return;
}
strin... | 104,908,764,181,850,850,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2018-17019 | In Bro through 2.5.5, there is a DoS in IRC protocol names command parsing in analyzer/protocol/irc/IRC.cc. | https://nvd.nist.gov/vuln/detail/CVE-2018-17019 |
382,251 | bro | c2b18849f8bb833253538f5dfedb4ed1dc176a30 | https://github.com/bro/bro | https://github.com/bro/bro/commit/c2b18849f8bb833253538f5dfedb4ed1dc176a30 | Fix IRC names command parsing | 0 | void IRC_Analyzer::DeliverStream(int length, const u_char* line, bool orig)
{
tcp::TCP_ApplicationAnalyzer::DeliverStream(length, line, orig);
if ( starttls )
{
ForwardStream(length, line, orig);
return;
}
// check line size
if ( length > 512 )
{
Weird("irc_line_size_exceeded");
return;
}
strin... | 196,203,411,310,230,640,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2018-17019 | In Bro through 2.5.5, there is a DoS in IRC protocol names command parsing in analyzer/protocol/irc/IRC.cc. | https://nvd.nist.gov/vuln/detail/CVE-2018-17019 |
206,528 | linux | c7ed6d0183d5ea9bc31bcaeeba4070bd62546471 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c7ed6d0183d5ea9bc31bcaeeba4070bd62546471 | net/mlx5: fix memory leak in mlx5_fw_fatal_reporter_dump
In mlx5_fw_fatal_reporter_dump if mlx5_crdump_collect fails the
allocated memory for cr_data must be released otherwise there will be
memory leak. To fix this, this commit changes the return instruction
into goto error handling.
Fixes: 9b1f29823605 ("net/mlx5: ... | 1 | mlx5_fw_fatal_reporter_dump(struct devlink_health_reporter *reporter,
struct devlink_fmsg *fmsg, void *priv_ctx)
{
struct mlx5_core_dev *dev = devlink_health_reporter_priv(reporter);
u32 crdump_size = dev->priv.health.crdump_size;
u32 *cr_data;
u32 data_size;
u32 offset;
int err;
if (!mlx5_core_is_pf(dev... | 155,578,812,356,632,900,000,000,000,000,000,000,000 | health.c | 119,736,003,087,835,670,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2019-19047 | A memory leak in the mlx5_fw_fatal_reporter_dump() function in drivers/net/ethernet/mellanox/mlx5/core/health.c in the Linux kernel before 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering mlx5_crdump_collect() failures, aka CID-c7ed6d0183d5. | https://nvd.nist.gov/vuln/detail/CVE-2019-19047 |
382,259 | linux | c7ed6d0183d5ea9bc31bcaeeba4070bd62546471 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c7ed6d0183d5ea9bc31bcaeeba4070bd62546471 | net/mlx5: fix memory leak in mlx5_fw_fatal_reporter_dump
In mlx5_fw_fatal_reporter_dump if mlx5_crdump_collect fails the
allocated memory for cr_data must be released otherwise there will be
memory leak. To fix this, this commit changes the return instruction
into goto error handling.
Fixes: 9b1f29823605 ("net/mlx5: ... | 0 | mlx5_fw_fatal_reporter_dump(struct devlink_health_reporter *reporter,
struct devlink_fmsg *fmsg, void *priv_ctx)
{
struct mlx5_core_dev *dev = devlink_health_reporter_priv(reporter);
u32 crdump_size = dev->priv.health.crdump_size;
u32 *cr_data;
u32 data_size;
u32 offset;
int err;
if (!mlx5_core_is_pf(dev... | 247,500,739,340,662,870,000,000,000,000,000,000,000 | health.c | 132,196,212,618,225,490,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2019-19047 | A memory leak in the mlx5_fw_fatal_reporter_dump() function in drivers/net/ethernet/mellanox/mlx5/core/health.c in the Linux kernel before 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering mlx5_crdump_collect() failures, aka CID-c7ed6d0183d5. | https://nvd.nist.gov/vuln/detail/CVE-2019-19047 |
206,552 | wireshark | a9fc769d7bb4b491efb61c699d57c9f35269d871 | https://github.com/wireshark/wireshark | https://gitlab.com/wireshark/wireshark/-/commit/a9fc769d7bb4b491efb61c699d57c9f35269d871 | epan: Fix a memory leak.
Make sure _proto_tree_add_bits_ret_val allocates a bits array using the
packet scope, otherwise we leak memory. Fixes #17032. | 1 | _proto_tree_add_bits_ret_val(proto_tree *tree, const int hfindex, tvbuff_t *tvb,
const guint bit_offset, const gint no_of_bits,
guint64 *return_value, const guint encoding)
{
gint offset;
guint length;
guint8 tot_no_bits;
char *bf_str;
char lbl_str[ITEM_LABEL_LENGTH];
guint64 value ... | 81,551,864,866,540,370,000,000,000,000,000,000,000 | None | null | [
"CWE-401"
] | CVE-2020-26419 | Memory leak in the dissection engine in Wireshark 3.4.0 allows denial of service via packet injection or crafted capture file. | https://nvd.nist.gov/vuln/detail/CVE-2020-26419 |
382,442 | wireshark | a9fc769d7bb4b491efb61c699d57c9f35269d871 | https://github.com/wireshark/wireshark | https://gitlab.com/wireshark/wireshark/-/commit/a9fc769d7bb4b491efb61c699d57c9f35269d871 | epan: Fix a memory leak.
Make sure _proto_tree_add_bits_ret_val allocates a bits array using the
packet scope, otherwise we leak memory. Fixes #17032. | 0 | _proto_tree_add_bits_ret_val(proto_tree *tree, const int hfindex, tvbuff_t *tvb,
const guint bit_offset, const gint no_of_bits,
guint64 *return_value, const guint encoding)
{
gint offset;
guint length;
guint8 tot_no_bits;
char *bf_str;
char lbl_str[ITEM_LABEL_LENGTH];
guint64 value ... | 196,425,867,915,168,100,000,000,000,000,000,000,000 | None | null | [
"CWE-401"
] | CVE-2020-26419 | Memory leak in the dissection engine in Wireshark 3.4.0 allows denial of service via packet injection or crafted capture file. | https://nvd.nist.gov/vuln/detail/CVE-2020-26419 |
206,556 | radare2 | e710401ebb4a892a87b0c709d709af8b5dcbbb01 | https://github.com/radare/radare2 | https://github.com/radare/radare2/commit/e710401ebb4a892a87b0c709d709af8b5dcbbb01 | patch #14211 heap buffer overflow in large ragg2
inputs. this should be refactored to use an RBuffer to enable dynamic
resizing, but for now just patching it to bail out if we are about to
overwrite the allocated statically sized buffer | 1 | R_API int r_egg_compile(REgg *egg) {
r_buf_seek (egg->src, 0, R_BUF_SET);
char b;
int r = r_buf_read (egg->src, (ut8 *)&b, sizeof (b));
if (r != sizeof (b) || !egg->remit) {
return true;
}
// only emit begin if code is found
r_egg_lang_init (egg);
for (; b; ) {
r_egg_lang_parsechar (egg, b);
int r = r_buf... | 151,226,584,601,483,490,000,000,000,000,000,000,000 | egg.c | 309,520,097,877,931,960,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2019-12790 | In radare2 through 3.5.1, there is a heap-based buffer over-read in the r_egg_lang_parsechar function of egg_lang.c. This allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact because of missing length validation in libr/egg/egg.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-12790 |
382,824 | radare2 | e710401ebb4a892a87b0c709d709af8b5dcbbb01 | https://github.com/radare/radare2 | https://github.com/radare/radare2/commit/e710401ebb4a892a87b0c709d709af8b5dcbbb01 | patch #14211 heap buffer overflow in large ragg2
inputs. this should be refactored to use an RBuffer to enable dynamic
resizing, but for now just patching it to bail out if we are about to
overwrite the allocated statically sized buffer | 0 | R_API int r_egg_compile(REgg *egg) {
r_buf_seek (egg->src, 0, R_BUF_SET);
char b;
int r = r_buf_read (egg->src, (ut8 *)&b, sizeof (b));
if (r != sizeof (b) || !egg->remit) {
return true;
}
// only emit begin if code is found
r_egg_lang_init (egg);
for (; b; ) {
r_egg_lang_parsechar (egg, b);
if (egg->lang... | 67,683,338,985,325,100,000,000,000,000,000,000,000 | egg.c | 9,348,765,551,945,885,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2019-12790 | In radare2 through 3.5.1, there is a heap-based buffer over-read in the r_egg_lang_parsechar function of egg_lang.c. This allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact because of missing length validation in libr/egg/egg.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-12790 |
206,557 | libjpeg-turbo | 82923eb93a2eacf4a593e00e3e672bbb86a8a3a0 | https://github.com/libjpeg-turbo/libjpeg-turbo | https://github.com/libjpeg-turbo/libjpeg-turbo/commit/82923eb93a2eacf4a593e00e3e672bbb86a8a3a0 | Check image size when reading targa file
Throw an error when image width or height is 0.
Fixes mozilla/mozjpeg#140, closes #7. | 1 | start_input_tga (j_compress_ptr cinfo, cjpeg_source_ptr sinfo)
{
tga_source_ptr source = (tga_source_ptr) sinfo;
U_CHAR targaheader[18];
int idlen, cmaptype, subtype, flags, interlace_type, components;
unsigned int width, height, maplen;
boolean is_bottom_up;
#define GET_2B(offset) ((unsigned int) UCH(targa... | 5,505,616,681,141,710,000,000,000,000,000,000,000 | rdtarga.c | 94,870,048,215,203,630,000,000,000,000,000,000,000 | [
"CWE-369"
] | CVE-2018-11212 | An issue was discovered in libjpeg 9a and 9d. The alloc_sarray function in jmemmgr.c allows remote attackers to cause a denial of service (divide-by-zero error) via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2018-11212 |
382,846 | libjpeg-turbo | 82923eb93a2eacf4a593e00e3e672bbb86a8a3a0 | https://github.com/libjpeg-turbo/libjpeg-turbo | https://github.com/libjpeg-turbo/libjpeg-turbo/commit/82923eb93a2eacf4a593e00e3e672bbb86a8a3a0 | Check image size when reading targa file
Throw an error when image width or height is 0.
Fixes mozilla/mozjpeg#140, closes #7. | 0 | start_input_tga (j_compress_ptr cinfo, cjpeg_source_ptr sinfo)
{
tga_source_ptr source = (tga_source_ptr) sinfo;
U_CHAR targaheader[18];
int idlen, cmaptype, subtype, flags, interlace_type, components;
unsigned int width, height, maplen;
boolean is_bottom_up;
#define GET_2B(offset) ((unsigned int) UCH(targa... | 103,837,218,571,856,340,000,000,000,000,000,000,000 | rdtarga.c | 108,411,749,245,089,720,000,000,000,000,000,000,000 | [
"CWE-369"
] | CVE-2018-11212 | An issue was discovered in libjpeg 9a and 9d. The alloc_sarray function in jmemmgr.c allows remote attackers to cause a denial of service (divide-by-zero error) via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2018-11212 |
206,558 | pure-ftpd | aea56f4bcb9948d456f3fae4d044fd3fa2e19706 | https://github.com/jedisct1/pure-ftpd | https://github.com/jedisct1/pure-ftpd/commit/aea56f4bcb9948d456f3fae4d044fd3fa2e19706 | listdir(): reuse a single buffer to store every file name to display
Allocating a new buffer for each entry is useless.
And as these buffers are allocated on the stack, on systems with a
small stack size, with many entries, the limit can easily be reached,
causing a stack exhaustion and aborting the user session.
Re... | 1 | static void listdir(unsigned int depth, int f, void * const tls_fd,
const char *name)
{
PureFileInfo *dir;
char *names;
PureFileInfo *s;
PureFileInfo *r;
int d;
if (depth >= max_ls_depth || matches >= max_ls_files) {
return;
}
if ((dir = sreaddir(&names)) == ... | 92,532,116,885,527,750,000,000,000,000,000,000,000 | ls.c | 83,153,656,877,070,570,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2019-20176 | In Pure-FTPd 1.0.49, a stack exhaustion issue was discovered in the listdir function in ls.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-20176 |
382,862 | pure-ftpd | aea56f4bcb9948d456f3fae4d044fd3fa2e19706 | https://github.com/jedisct1/pure-ftpd | https://github.com/jedisct1/pure-ftpd/commit/aea56f4bcb9948d456f3fae4d044fd3fa2e19706 | listdir(): reuse a single buffer to store every file name to display
Allocating a new buffer for each entry is useless.
And as these buffers are allocated on the stack, on systems with a
small stack size, with many entries, the limit can easily be reached,
causing a stack exhaustion and aborting the user session.
Re... | 0 | static void listdir(unsigned int depth, int f, void * const tls_fd,
const char *name)
{
PureFileInfo *dir;
char *names;
PureFileInfo *s;
PureFileInfo *r;
char *alloca_subdir;
size_t sizeof_subdir;
int d;
if (depth >= max_ls_depth || matches >= max_ls_files) {
... | 228,013,459,123,011,560,000,000,000,000,000,000,000 | ls.c | 244,530,149,602,828,200,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2019-20176 | In Pure-FTPd 1.0.49, a stack exhaustion issue was discovered in the listdir function in ls.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-20176 |
206,566 | sound | 19bce474c45be69a284ecee660aa12d8f1e88f18 | https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound | https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=19bce474c45be69a284ecee660aa12d8f1e88f18 | ALSA: usb-audio: Fix a stack buffer overflow bug in check_input_term
`check_input_term` recursively calls itself with input from
device side (e.g., uac_input_terminal_descriptor.bCSourceID)
as argument (id). In `check_input_term`, if `check_input_term`
is called with the same `id` argument as the caller, it triggers
e... | 1 | static int check_input_term(struct mixer_build *state, int id,
struct usb_audio_term *term)
{
int protocol = state->mixer->protocol;
int err;
void *p1;
memset(term, 0, sizeof(*term));
while ((p1 = find_audio_control_unit(state, id)) != NULL) {
unsigned char *hdr = p1;
term->id = id;
if (protocol == ... | 281,000,276,977,992,660,000,000,000,000,000,000,000 | mixer.c | 217,929,766,023,230,020,000,000,000,000,000,000,000 | [
"CWE-674"
] | CVE-2019-15118 | check_input_term in sound/usb/mixer.c in the Linux kernel through 5.2.9 mishandles recursion, leading to kernel stack exhaustion. | https://nvd.nist.gov/vuln/detail/CVE-2019-15118 |
382,939 | sound | 19bce474c45be69a284ecee660aa12d8f1e88f18 | https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound | https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=19bce474c45be69a284ecee660aa12d8f1e88f18 | ALSA: usb-audio: Fix a stack buffer overflow bug in check_input_term
`check_input_term` recursively calls itself with input from
device side (e.g., uac_input_terminal_descriptor.bCSourceID)
as argument (id). In `check_input_term`, if `check_input_term`
is called with the same `id` argument as the caller, it triggers
e... | 0 | static int __check_input_term(struct mixer_build *state, int id,
struct usb_audio_term *term)
{
int protocol = state->mixer->protocol;
int err;
void *p1;
unsigned char *hdr;
memset(term, 0, sizeof(*term));
for (;;) {
/* a loop in the terminal chain? */
if (test_and_set_bit(id, state->termbitmap))
r... | 123,189,914,483,497,370,000,000,000,000,000,000,000 | None | null | [
"CWE-674"
] | CVE-2019-15118 | check_input_term in sound/usb/mixer.c in the Linux kernel through 5.2.9 mishandles recursion, leading to kernel stack exhaustion. | https://nvd.nist.gov/vuln/detail/CVE-2019-15118 |
206,567 | linux | 3f93616951138a598d930dcaec40f2bfd9ce43bb | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/3f93616951138a598d930dcaec40f2bfd9ce43bb | rtlwifi: prevent memory leak in rtl_usb_probe
In rtl_usb_probe if allocation for usb_data fails the allocated hw
should be released. In addition the allocated rtlpriv->usb_data should
be released on error handling path.
Signed-off-by: Navid Emamdoost <navid.emamdoost@gmail.com>
Signed-off-by: Kalle Valo <kvalo@codeau... | 1 | int rtl_usb_probe(struct usb_interface *intf,
const struct usb_device_id *id,
struct rtl_hal_cfg *rtl_hal_cfg)
{
int err;
struct ieee80211_hw *hw = NULL;
struct rtl_priv *rtlpriv = NULL;
struct usb_device *udev;
struct rtl_usb_priv *usb_priv;
hw = ieee80211_alloc_hw(sizeof(struct rtl_priv) +
sizeof(s... | 226,899,180,908,335,970,000,000,000,000,000,000,000 | usb.c | 243,186,790,375,221,370,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2019-19063 | Two memory leaks in the rtl_usb_probe() function in drivers/net/wireless/realtek/rtlwifi/usb.c in the Linux kernel through 5.3.11 allow attackers to cause a denial of service (memory consumption), aka CID-3f9361695113. | https://nvd.nist.gov/vuln/detail/CVE-2019-19063 |
382,957 | linux | 3f93616951138a598d930dcaec40f2bfd9ce43bb | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/3f93616951138a598d930dcaec40f2bfd9ce43bb | rtlwifi: prevent memory leak in rtl_usb_probe
In rtl_usb_probe if allocation for usb_data fails the allocated hw
should be released. In addition the allocated rtlpriv->usb_data should
be released on error handling path.
Signed-off-by: Navid Emamdoost <navid.emamdoost@gmail.com>
Signed-off-by: Kalle Valo <kvalo@codeau... | 0 | int rtl_usb_probe(struct usb_interface *intf,
const struct usb_device_id *id,
struct rtl_hal_cfg *rtl_hal_cfg)
{
int err;
struct ieee80211_hw *hw = NULL;
struct rtl_priv *rtlpriv = NULL;
struct usb_device *udev;
struct rtl_usb_priv *usb_priv;
hw = ieee80211_alloc_hw(sizeof(struct rtl_priv) +
sizeof(s... | 268,536,646,211,216,200,000,000,000,000,000,000,000 | usb.c | 252,174,132,686,657,500,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2019-19063 | Two memory leaks in the rtl_usb_probe() function in drivers/net/wireless/realtek/rtlwifi/usb.c in the Linux kernel through 5.3.11 allow attackers to cause a denial of service (memory consumption), aka CID-3f9361695113. | https://nvd.nist.gov/vuln/detail/CVE-2019-19063 |
206,583 | systemd | 9d880b70ba5c6ca83c82952f4c90e86e56c7b70c | https://github.com/systemd/systemd | https://github.com/systemd/systemd/commit/9d880b70ba5c6ca83c82952f4c90e86e56c7b70c | analyze: check for RestrictSUIDSGID= in "systemd-analyze security"
And let's give it a heigh weight, since it pretty much can be used for
bad things only. | 1 | static int acquire_security_info(sd_bus *bus, const char *name, struct security_info *info, AnalyzeSecurityFlags flags) {
static const struct bus_properties_map security_map[] = {
{ "AmbientCapabilities", "t", NULL, offsetof(struct security_info, amb... | 53,879,801,098,288,180,000,000,000,000,000,000,000 | analyze-security.c | 142,410,186,367,812,810,000,000,000,000,000,000,000 | [
"CWE-269"
] | CVE-2019-3843 | It was discovered that a systemd service that uses DynamicUser property can create a SUID/SGID binary that would be allowed to run as the transient service UID/GID even after the service is terminated. A local attacker may use this flaw to access resources that will be owned by a potentially different service in the fu... | https://nvd.nist.gov/vuln/detail/CVE-2019-3843 |
383,158 | systemd | 9d880b70ba5c6ca83c82952f4c90e86e56c7b70c | https://github.com/systemd/systemd | https://github.com/systemd/systemd/commit/9d880b70ba5c6ca83c82952f4c90e86e56c7b70c | analyze: check for RestrictSUIDSGID= in "systemd-analyze security"
And let's give it a heigh weight, since it pretty much can be used for
bad things only. | 0 | static int acquire_security_info(sd_bus *bus, const char *name, struct security_info *info, AnalyzeSecurityFlags flags) {
static const struct bus_properties_map security_map[] = {
{ "AmbientCapabilities", "t", NULL, offsetof(struct security_info, amb... | 175,895,982,156,614,660,000,000,000,000,000,000,000 | analyze-security.c | 91,314,318,658,062,120,000,000,000,000,000,000,000 | [
"CWE-269"
] | CVE-2019-3843 | It was discovered that a systemd service that uses DynamicUser property can create a SUID/SGID binary that would be allowed to run as the transient service UID/GID even after the service is terminated. A local attacker may use this flaw to access resources that will be owned by a potentially different service in the fu... | https://nvd.nist.gov/vuln/detail/CVE-2019-3843 |
206,586 | linux | 5146f95df782b0ac61abde36567e718692725c89 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5146f95df782b0ac61abde36567e718692725c89 | USB: hso: Fix OOB memory access in hso_probe/hso_get_config_data
The function hso_probe reads if_num from the USB device (as an u8) and uses
it without a length check to index an array, resulting in an OOB memory read
in hso_probe or hso_get_config_data.
Add a length check for both locations and updated hso_probe to ... | 1 | static int hso_get_config_data(struct usb_interface *interface)
{
struct usb_device *usbdev = interface_to_usbdev(interface);
u8 *config_data = kmalloc(17, GFP_KERNEL);
u32 if_num = interface->cur_altsetting->desc.bInterfaceNumber;
s32 result;
if (!config_data)
return -ENOMEM;
if (usb_control_msg(usbdev, usb_r... | 323,749,645,329,160,840,000,000,000,000,000,000,000 | hso.c | 203,081,192,216,308,100,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2018-19985 | The function hso_get_config_data in drivers/net/usb/hso.c in the Linux kernel through 4.19.8 reads if_num from the USB device (as a u8) and uses it to index a small array, resulting in an object out-of-bounds (OOB) read that potentially allows arbitrary read in the kernel address space. | https://nvd.nist.gov/vuln/detail/CVE-2018-19985 |
383,208 | linux | 5146f95df782b0ac61abde36567e718692725c89 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5146f95df782b0ac61abde36567e718692725c89 | USB: hso: Fix OOB memory access in hso_probe/hso_get_config_data
The function hso_probe reads if_num from the USB device (as an u8) and uses
it without a length check to index an array, resulting in an OOB memory read
in hso_probe or hso_get_config_data.
Add a length check for both locations and updated hso_probe to ... | 0 | static int hso_get_config_data(struct usb_interface *interface)
{
struct usb_device *usbdev = interface_to_usbdev(interface);
u8 *config_data = kmalloc(17, GFP_KERNEL);
u32 if_num = interface->cur_altsetting->desc.bInterfaceNumber;
s32 result;
if (!config_data)
return -ENOMEM;
if (usb_control_msg(usbdev, usb_r... | 95,768,811,931,099,800,000,000,000,000,000,000,000 | hso.c | 151,700,781,826,718,970,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2018-19985 | The function hso_get_config_data in drivers/net/usb/hso.c in the Linux kernel through 4.19.8 reads if_num from the USB device (as a u8) and uses it to index a small array, resulting in an object out-of-bounds (OOB) read that potentially allows arbitrary read in the kernel address space. | https://nvd.nist.gov/vuln/detail/CVE-2018-19985 |
206,593 | poppler | f162ecdea0dda5dbbdb45503c1d55d9afaa41d44 | https://github.com/freedesktop/poppler | https://github.com/freedesktop/poppler/commit/f162ecdea0dda5dbbdb45503c1d55d9afaa41d44 | Fix crash on missing embedded file
Check whether an embedded file is actually present in the PDF
and show warning in that case.
https://bugs.freedesktop.org/show_bug.cgi?id=106137
https://gitlab.freedesktop.org/poppler/poppler/issues/236 | 1 | _poppler_attachment_new (FileSpec *emb_file)
{
PopplerAttachment *attachment;
PopplerAttachmentPrivate *priv;
EmbFile *embFile;
g_assert (emb_file != nullptr);
attachment = (PopplerAttachment *) g_object_new (POPPLER_TYPE_ATTACHMENT, nullptr);
priv = POPPLER_ATTACHMENT_GET_PRIVATE (attachment);
if (emb... | 129,599,571,337,960,760,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2018-19149 | Poppler before 0.70.0 has a NULL pointer dereference in _poppler_attachment_new when called from poppler_annot_file_attachment_get_attachment. | https://nvd.nist.gov/vuln/detail/CVE-2018-19149 |
383,566 | poppler | f162ecdea0dda5dbbdb45503c1d55d9afaa41d44 | https://github.com/freedesktop/poppler | https://github.com/freedesktop/poppler/commit/f162ecdea0dda5dbbdb45503c1d55d9afaa41d44 | Fix crash on missing embedded file
Check whether an embedded file is actually present in the PDF
and show warning in that case.
https://bugs.freedesktop.org/show_bug.cgi?id=106137
https://gitlab.freedesktop.org/poppler/poppler/issues/236 | 0 | _poppler_attachment_new (FileSpec *emb_file)
{
PopplerAttachment *attachment;
PopplerAttachmentPrivate *priv;
EmbFile *embFile;
g_assert (emb_file != nullptr);
attachment = (PopplerAttachment *) g_object_new (POPPLER_TYPE_ATTACHMENT, nullptr);
priv = POPPLER_ATTACHMENT_GET_PRIVATE (attachment);
if (emb... | 45,107,408,965,391,330,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2018-19149 | Poppler before 0.70.0 has a NULL pointer dereference in _poppler_attachment_new when called from poppler_annot_file_attachment_get_attachment. | https://nvd.nist.gov/vuln/detail/CVE-2018-19149 |
206,603 | clamav-devel | fc3794a54d2affe5770c1f876484a871c783e91e | https://github.com/vrtadmin/clamav-devel | https://github.com/vrtadmin/clamav-devel/commit/fc3794a54d2affe5770c1f876484a871c783e91e | Merge fix from security/bb11155 branch | 1 |
int cli_scanpe(cli_ctx *ctx)
{
uint16_t e_magic; /* DOS signature ("MZ") */
uint16_t nsections;
uint32_t e_lfanew; /* address of new exe header */
uint32_t ep, vep; /* entry point (raw, virtual) */
uint8_t polipos = 0;
time_t timestamp;
struct pe_image_file_hdr file_hdr;
union {
struct pe_image_optional_h... | 33,206,013,378,027,820,000,000,000,000,000,000,000 | pe.c | 83,104,154,431,770,090,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2014-9050 | Heap-based buffer overflow in the cli_scanpe function in libclamav/pe.c in ClamAV before 0.98.5 allows remote attackers to cause a denial of service (crash) via a crafted y0da Crypter PE file. | https://nvd.nist.gov/vuln/detail/CVE-2014-9050 |
383,762 | clamav-devel | fc3794a54d2affe5770c1f876484a871c783e91e | https://github.com/vrtadmin/clamav-devel | https://github.com/vrtadmin/clamav-devel/commit/fc3794a54d2affe5770c1f876484a871c783e91e | Merge fix from security/bb11155 branch | 0 |
int cli_scanpe(cli_ctx *ctx)
{
uint16_t e_magic; /* DOS signature ("MZ") */
uint16_t nsections;
uint32_t e_lfanew; /* address of new exe header */
uint32_t ep, vep; /* entry point (raw, virtual) */
uint8_t polipos = 0;
time_t timestamp;
struct pe_image_file_hdr file_hdr;
union {
struct pe_image_optional_h... | 263,500,159,853,671,800,000,000,000,000,000,000,000 | pe.c | 256,489,500,243,273,900,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2014-9050 | Heap-based buffer overflow in the cli_scanpe function in libclamav/pe.c in ClamAV before 0.98.5 allows remote attackers to cause a denial of service (crash) via a crafted y0da Crypter PE file. | https://nvd.nist.gov/vuln/detail/CVE-2014-9050 |
206,604 | systemd | 6d586a13717ae057aa1b4127400c3de61cd5b9e7 | https://github.com/systemd/systemd | https://github.com/systemd/systemd/commit/6d586a13717ae057aa1b4127400c3de61cd5b9e7 | sd-bus: if we receive an invalid dbus message, ignore and proceeed
dbus-daemon might have a slightly different idea of what a valid msg is
than us (for example regarding valid msg and field sizes). Let's hence
try to proceed if we can and thus drop messages rather than fail the
connection if we fail to validate a mess... | 1 | static int bus_socket_make_message(sd_bus *bus, size_t size) {
sd_bus_message *t;
void *b;
int r;
assert(bus);
assert(bus->rbuffer_size >= size);
assert(IN_SET(bus->state, BUS_RUNNING, BUS_HELLO));
r = bus_rqueue_make_room(bus);
if (r < 0)
... | 240,780,417,026,379,030,000,000,000,000,000,000,000 | bus-socket.c | 7,377,282,213,668,138,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-6454 | An issue was discovered in sd-bus in systemd 239. bus_process_object() in libsystemd/sd-bus/bus-objects.c allocates a variable-length stack buffer for temporarily storing the object path of incoming D-Bus messages. An unprivileged local user can exploit this by sending a specially crafted message to PID1, causing the s... | https://nvd.nist.gov/vuln/detail/CVE-2019-6454 |
383,771 | systemd | 6d586a13717ae057aa1b4127400c3de61cd5b9e7 | https://github.com/systemd/systemd | https://github.com/systemd/systemd/commit/6d586a13717ae057aa1b4127400c3de61cd5b9e7 | sd-bus: if we receive an invalid dbus message, ignore and proceeed
dbus-daemon might have a slightly different idea of what a valid msg is
than us (for example regarding valid msg and field sizes). Let's hence
try to proceed if we can and thus drop messages rather than fail the
connection if we fail to validate a mess... | 0 | static int bus_socket_make_message(sd_bus *bus, size_t size) {
sd_bus_message *t = NULL;
void *b;
int r;
assert(bus);
assert(bus->rbuffer_size >= size);
assert(IN_SET(bus->state, BUS_RUNNING, BUS_HELLO));
r = bus_rqueue_make_room(bus);
if (r < 0)
... | 212,531,360,120,118,670,000,000,000,000,000,000,000 | bus-socket.c | 3,316,351,671,383,243,300,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-6454 | An issue was discovered in sd-bus in systemd 239. bus_process_object() in libsystemd/sd-bus/bus-objects.c allocates a variable-length stack buffer for temporarily storing the object path of incoming D-Bus messages. An unprivileged local user can exploit this by sending a specially crafted message to PID1, causing the s... | https://nvd.nist.gov/vuln/detail/CVE-2019-6454 |
206,607 | libxslt | 6ce8de69330783977dd14f6569419489875fb71b | http://git.gnome.org/browse/libxslt | https://gitlab.gnome.org/GNOME/libxslt/commit/6ce8de69330783977dd14f6569419489875fb71b | Fix uninitialized read with UTF-8 grouping chars
The character type in xsltFormatNumberConversion was too narrow and
an invalid character/length combination could be passed to
xsltNumberFormatDecimal, resulting in an uninitialized read.
Found by OSS-Fuzz. | 1 | xsltFormatNumberConversion(xsltDecimalFormatPtr self,
xmlChar *format,
double number,
xmlChar **result)
{
xmlXPathError status = XPATH_EXPRESSION_OK;
xmlBufferPtr buffer;
xmlChar *the_format, *prefix = NULL, *suffix = NULL;
xmlChar *nprefix, *nsuffix = NULL;
xmlChar pchar;
int ... | 92,315,311,840,756,490,000,000,000,000,000,000,000 | numbers.c | 62,458,620,971,211,260,000,000,000,000,000,000,000 | [
"CWE-843"
] | CVE-2019-13118 | In numbers.c in libxslt 1.1.33, a type holding grouping characters of an xsl:number instruction was too narrow and an invalid character/length combination could be passed to xsltNumberFormatDecimal, leading to a read of uninitialized stack data. | https://nvd.nist.gov/vuln/detail/CVE-2019-13118 |
383,796 | libxslt | 6ce8de69330783977dd14f6569419489875fb71b | http://git.gnome.org/browse/libxslt | https://gitlab.gnome.org/GNOME/libxslt/commit/6ce8de69330783977dd14f6569419489875fb71b | Fix uninitialized read with UTF-8 grouping chars
The character type in xsltFormatNumberConversion was too narrow and
an invalid character/length combination could be passed to
xsltNumberFormatDecimal, resulting in an uninitialized read.
Found by OSS-Fuzz. | 0 | xsltFormatNumberConversion(xsltDecimalFormatPtr self,
xmlChar *format,
double number,
xmlChar **result)
{
xmlXPathError status = XPATH_EXPRESSION_OK;
xmlBufferPtr buffer;
xmlChar *the_format, *prefix = NULL, *suffix = NULL;
xmlChar *nprefix, *nsuffix = NULL;
xmlChar pchar;
int ... | 118,485,032,459,403,150,000,000,000,000,000,000,000 | numbers.c | 117,256,670,444,019,240,000,000,000,000,000,000,000 | [
"CWE-843"
] | CVE-2019-13118 | In numbers.c in libxslt 1.1.33, a type holding grouping characters of an xsl:number instruction was too narrow and an invalid character/length combination could be passed to xsltNumberFormatDecimal, leading to a read of uninitialized stack data. | https://nvd.nist.gov/vuln/detail/CVE-2019-13118 |
206,608 | curl | 13c9a9ded3ae744a1e11cbc14e9146d9fa427040 | https://github.com/curl/curl | https://github.com/curl/curl/commit/13c9a9ded3ae744a1e11cbc14e9146d9fa427040 | imap: if a FETCH response has no size, don't call write callback
CVE-2017-1000257
Reported-by: Brian Carpenter and 0xd34db347
Also detected by OSS-Fuzz: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3586 | 1 | static CURLcode imap_state_fetch_resp(struct connectdata *conn, int imapcode,
imapstate instate)
{
CURLcode result = CURLE_OK;
struct Curl_easy *data = conn->data;
struct imap_conn *imapc = &conn->proto.imapc;
struct pingpong *pp = &imapc->pp;
const char *ptr = data->stat... | 265,726,410,517,277,500,000,000,000,000,000,000,000 | imap.c | 57,586,852,248,387,495,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-1000257 | An IMAP FETCH response line indicates the size of the returned data, in number of bytes. When that response says the data is zero bytes, libcurl would pass on that (non-existing) data with a pointer and the size (zero) to the deliver-data function. libcurl's deliver-data function treats zero as a magic number and invok... | https://nvd.nist.gov/vuln/detail/CVE-2017-1000257 |
383,819 | curl | 13c9a9ded3ae744a1e11cbc14e9146d9fa427040 | https://github.com/curl/curl | https://github.com/curl/curl/commit/13c9a9ded3ae744a1e11cbc14e9146d9fa427040 | imap: if a FETCH response has no size, don't call write callback
CVE-2017-1000257
Reported-by: Brian Carpenter and 0xd34db347
Also detected by OSS-Fuzz: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3586 | 0 | static CURLcode imap_state_fetch_resp(struct connectdata *conn, int imapcode,
imapstate instate)
{
CURLcode result = CURLE_OK;
struct Curl_easy *data = conn->data;
struct imap_conn *imapc = &conn->proto.imapc;
struct pingpong *pp = &imapc->pp;
const char *ptr = data->stat... | 273,698,853,697,869,040,000,000,000,000,000,000,000 | imap.c | 336,598,134,456,019,300,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-1000257 | An IMAP FETCH response line indicates the size of the returned data, in number of bytes. When that response says the data is zero bytes, libcurl would pass on that (non-existing) data with a pointer and the size (zero) to the deliver-data function. libcurl's deliver-data function treats zero as a magic number and invok... | https://nvd.nist.gov/vuln/detail/CVE-2017-1000257 |
206,617 | ImageMagick | 94691f00839dbdf43edb1508af945ab19b388573 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/94691f00839dbdf43edb1508af945ab19b388573 | https://github.com/ImageMagick/ImageMagick/issues/1750 | 1 | static int HistogramCompare(const void *x,const void *y)
{
const PixelInfo
*color_1,
*color_2;
color_1=(const PixelInfo *) x;
color_2=(const PixelInfo *) y;
if (color_2->red != color_1->red)
return((int) color_1->red-(int) color_2->red);
if (color_2->green != color_1->green)
return((int) colo... | 217,370,642,174,871,800,000,000,000,000,000,000,000 | histogram.c | 10,076,331,252,478,390,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2020-25666 | There are 4 places in HistogramCompare() in MagickCore/histogram.c where an integer overflow is possible during simple math calculations. This occurs in the rgb values and `count` value for a color. The patch uses casts to `ssize_t` type for these calculations, instead of `int`. This flaw could impact application relia... | https://nvd.nist.gov/vuln/detail/CVE-2020-25666 |
383,931 | ImageMagick | 94691f00839dbdf43edb1508af945ab19b388573 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/94691f00839dbdf43edb1508af945ab19b388573 | https://github.com/ImageMagick/ImageMagick/issues/1750 | 0 | static int HistogramCompare(const void *x,const void *y)
{
const PixelInfo
*color_1,
*color_2;
color_1=(const PixelInfo *) x;
color_2=(const PixelInfo *) y;
if (color_2->red != color_1->red)
return((int) ((ssize_t) color_1->red-(ssize_t) color_2->red));
if (color_2->green != color_1->green)
r... | 59,330,297,650,861,990,000,000,000,000,000,000,000 | histogram.c | 50,850,599,537,012,570,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2020-25666 | There are 4 places in HistogramCompare() in MagickCore/histogram.c where an integer overflow is possible during simple math calculations. This occurs in the rgb values and `count` value for a color. The patch uses casts to `ssize_t` type for these calculations, instead of `int`. This flaw could impact application relia... | https://nvd.nist.gov/vuln/detail/CVE-2020-25666 |
206,626 | e2fsprogs | 49d0fe2a14f2a23da2fe299643379b8c1d37df73 | http://git.kernel.org/cgit/fs/ext2/e2fsprogs | https://git.kernel.org/cgit/fs/ext2/e2fsprogs.git/commit/?id=49d0fe2a14f2a23da2fe299643379b8c1d37df73 | libext2fs: fix potential buffer overflow in closefs()
The bug fix in f66e6ce4446: "libext2fs: avoid buffer overflow if
s_first_meta_bg is too big" had a typo in the fix for
ext2fs_closefs(). In practice most of the security exposure was from
the openfs path, since this meant if there was a carefully crafted
file syst... | 1 | errcode_t ext2fs_flush2(ext2_filsys fs, int flags)
{
dgrp_t i;
errcode_t retval;
unsigned long fs_state;
__u32 feature_incompat;
struct ext2_super_block *super_shadow = 0;
struct ext2_group_desc *group_shadow = 0;
#ifdef WORDS_BIGENDIAN
struct ext2_group_desc *gdp;
dgrp_t j;
#endif
char *group_ptr;
int old... | 317,399,360,686,681,700,000,000,000,000,000,000,000 | closefs.c | 257,467,040,288,118,450,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-1572 | Heap-based buffer overflow in closefs.c in the libext2fs library in e2fsprogs before 1.42.12 allows local users to execute arbitrary code by causing a crafted block group descriptor to be marked as dirty. NOTE: this vulnerability exists because of an incomplete fix for CVE-2015-0247. | https://nvd.nist.gov/vuln/detail/CVE-2015-1572 |
384,133 | e2fsprogs | 49d0fe2a14f2a23da2fe299643379b8c1d37df73 | http://git.kernel.org/cgit/fs/ext2/e2fsprogs | https://git.kernel.org/cgit/fs/ext2/e2fsprogs.git/commit/?id=49d0fe2a14f2a23da2fe299643379b8c1d37df73 | libext2fs: fix potential buffer overflow in closefs()
The bug fix in f66e6ce4446: "libext2fs: avoid buffer overflow if
s_first_meta_bg is too big" had a typo in the fix for
ext2fs_closefs(). In practice most of the security exposure was from
the openfs path, since this meant if there was a carefully crafted
file syst... | 0 | errcode_t ext2fs_flush2(ext2_filsys fs, int flags)
{
dgrp_t i;
errcode_t retval;
unsigned long fs_state;
__u32 feature_incompat;
struct ext2_super_block *super_shadow = 0;
struct ext2_group_desc *group_shadow = 0;
#ifdef WORDS_BIGENDIAN
struct ext2_group_desc *gdp;
dgrp_t j;
#endif
char *group_ptr;
blk64_t... | 141,575,417,313,702,420,000,000,000,000,000,000,000 | closefs.c | 317,035,968,897,966,430,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-1572 | Heap-based buffer overflow in closefs.c in the libext2fs library in e2fsprogs before 1.42.12 allows local users to execute arbitrary code by causing a crafted block group descriptor to be marked as dirty. NOTE: this vulnerability exists because of an incomplete fix for CVE-2015-0247. | https://nvd.nist.gov/vuln/detail/CVE-2015-1572 |
206,629 | pykerberos | 02d13860b25fab58e739f0e000bed0067b7c6f9c | https://github.com/02strich/pykerberos | https://github.com/02strich/pykerberos/commit/02d13860b25fab58e739f0e000bed0067b7c6f9c | adding KDC verification support (enabled by default) | 1 | static PyObject *checkPassword(PyObject *self, PyObject *args)
{
const char *user = NULL;
const char *pswd = NULL;
const char *service = NULL;
const char *default_realm = NULL;
int result = 0;
if (!PyArg_ParseTuple(args, "ssss", &user, &pswd, &service, &default_realm))
return NULL;
... | 129,530,747,519,882,240,000,000,000,000,000,000,000 | None | null | [
"CWE-287"
] | CVE-2015-3206 | The checkPassword function in python-kerberos does not authenticate the KDC it attempts to communicate with, which allows remote attackers to cause a denial of service (bad response), or have other unspecified impact by performing a man-in-the-middle attack. | https://nvd.nist.gov/vuln/detail/CVE-2015-3206 |
384,134 | pykerberos | 02d13860b25fab58e739f0e000bed0067b7c6f9c | https://github.com/02strich/pykerberos | https://github.com/02strich/pykerberos/commit/02d13860b25fab58e739f0e000bed0067b7c6f9c | adding KDC verification support (enabled by default) | 0 | static PyObject *checkPassword(PyObject *self, PyObject *args)
{
const char *user = NULL;
const char *pswd = NULL;
const char *service = NULL;
const char *default_realm = NULL;
const int verify = 1;
int result = 0;
if (!PyArg_ParseTuple(args, "ssssb", &user, &pswd, &service, &default_realm,... | 202,226,275,590,517,600,000,000,000,000,000,000,000 | None | null | [
"CWE-287"
] | CVE-2015-3206 | The checkPassword function in python-kerberos does not authenticate the KDC it attempts to communicate with, which allows remote attackers to cause a denial of service (bad response), or have other unspecified impact by performing a man-in-the-middle attack. | https://nvd.nist.gov/vuln/detail/CVE-2015-3206 |
206,631 | avahi | 3093047f1aa36bed8a37fa79004bf0ee287929f4 | http://git.0pointer.de/?p=avahi | http://git.0pointer.de/?p=avahi.git;a=commitdiff;h=3093047f1aa36bed8a37fa79004bf0ee287929f4 | Don't get confused by UDP packets with a source port that is zero
This is a fix for rhbz 475394.
Problem identified by Hugo Dias. | 1 | static void dispatch_packet(AvahiServer *s, AvahiDnsPacket *p, const AvahiAddress *src_address, uint16_t port, const AvahiAddress *dst_address, AvahiIfIndex iface, int ttl) {
AvahiInterface *i;
int from_local_iface = 0;
assert(s);
assert(p);
assert(src_address);
assert(dst_address);
assert(... | 3,118,443,621,759,505,000,000,000,000,000,000,000 | server.c | 72,800,776,031,626,470,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2008-5081 | The originates_from_local_legacy_unicast_socket function (avahi-core/server.c) in avahi-daemon in Avahi before 0.6.24 allows remote attackers to cause a denial of service (crash) via a crafted mDNS packet with a source port of 0, which triggers an assertion failure. | https://nvd.nist.gov/vuln/detail/CVE-2008-5081 |
384,154 | avahi | 3093047f1aa36bed8a37fa79004bf0ee287929f4 | http://git.0pointer.de/?p=avahi | http://git.0pointer.de/?p=avahi.git;a=commitdiff;h=3093047f1aa36bed8a37fa79004bf0ee287929f4 | Don't get confused by UDP packets with a source port that is zero
This is a fix for rhbz 475394.
Problem identified by Hugo Dias. | 0 | static void dispatch_packet(AvahiServer *s, AvahiDnsPacket *p, const AvahiAddress *src_address, uint16_t port, const AvahiAddress *dst_address, AvahiIfIndex iface, int ttl) {
AvahiInterface *i;
int from_local_iface = 0;
assert(s);
assert(p);
assert(src_address);
assert(dst_address);
assert(... | 119,789,684,495,358,820,000,000,000,000,000,000,000 | server.c | 296,206,066,282,861,840,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2008-5081 | The originates_from_local_legacy_unicast_socket function (avahi-core/server.c) in avahi-daemon in Avahi before 0.6.24 allows remote attackers to cause a denial of service (crash) via a crafted mDNS packet with a source port of 0, which triggers an assertion failure. | https://nvd.nist.gov/vuln/detail/CVE-2008-5081 |
206,634 | libtasn1 | 53958290ab731c8486531a3bdef54a933533579d | http://git.savannah.gnu.org/cgit/libtasn1 | http://git.savannah.gnu.org/cgit/libtasn1.git/commit/lib/element.c?id=53958290ab731c8486531a3bdef54a933533579d | Allow a NULL value in asn1_read_value() for all types. | 1 | asn1_read_value_type (asn1_node root, const char *name, void *ivalue,
int *len, unsigned int *etype)
{
asn1_node node, p, p2;
int len2, len3, result;
int value_size = *len;
unsigned char *value = ivalue;
unsigned type;
node = asn1_find_node (root, name);
if (node == NULL)
return ASN1_ELEMENT_... | 122,128,328,092,969,900,000,000,000,000,000,000,000 | element.c | 335,938,869,824,155,600,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2014-3469 | The (1) asn1_read_value_type and (2) asn1_read_value functions in GNU Libtasn1 before 3.6 allows context-dependent attackers to cause a denial of service (NULL pointer dereference and crash) via a NULL value in an ivalue argument. | https://nvd.nist.gov/vuln/detail/CVE-2014-3469 |
384,179 | libtasn1 | 53958290ab731c8486531a3bdef54a933533579d | http://git.savannah.gnu.org/cgit/libtasn1 | http://git.savannah.gnu.org/cgit/libtasn1.git/commit/lib/element.c?id=53958290ab731c8486531a3bdef54a933533579d | Allow a NULL value in asn1_read_value() for all types. | 0 | asn1_read_value_type (asn1_node root, const char *name, void *ivalue,
int *len, unsigned int *etype)
{
asn1_node node, p, p2;
int len2, len3, result;
int value_size = *len;
unsigned char *value = ivalue;
unsigned type;
node = asn1_find_node (root, name);
if (node == NULL)
return ASN1_ELEMENT_... | 172,385,465,457,207,570,000,000,000,000,000,000,000 | element.c | 329,511,346,067,806,320,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2014-3469 | The (1) asn1_read_value_type and (2) asn1_read_value functions in GNU Libtasn1 before 3.6 allows context-dependent attackers to cause a denial of service (NULL pointer dereference and crash) via a NULL value in an ivalue argument. | https://nvd.nist.gov/vuln/detail/CVE-2014-3469 |
206,640 | gnutls | 34d87a7c3f12794a3ec2305cd2fdbae152bf2a76 | http://git.savannah.gnu.org/cgit/gnutls | http://git.savannah.gnu.org/cgit/gnutls.git/commit/?id=34d87a7c3f12794a3ec2305cd2fdbae152bf2a76 | (_gnutls_x509_oid2mac_algorithm): Don't crash trying to strcmp the
NULL OID value in the hash_algorithms array, which happens when the
input OID doesn't match our OIDs for SHA1, MD5, MD2 or RIPEMD160.
Reported by satyakumar <satyam_kkd@hyd.hellosoft.com>. | 1 | _gnutls_x509_oid2mac_algorithm (const char *oid)
{
gnutls_mac_algorithm_t ret = 0;
GNUTLS_HASH_LOOP (if (strcmp (oid, p->oid) == 0)
{
ret = p->id; break;}
);
if (ret == 0)
return GNUTLS_MAC_UNKNOWN;
return ret;
} | 6,157,203,445,617,455,000,000,000,000,000,000,000 | None | null | [
"CWE-310"
] | CVE-2006-7239 | The _gnutls_x509_oid2mac_algorithm function in lib/gnutls_algorithms.c in GnuTLS before 1.4.2 allows remote attackers to cause a denial of service (crash) via a crafted X.509 certificate that uses a hash algorithm that is not supported by GnuTLS, which triggers a NULL pointer dereference. | https://nvd.nist.gov/vuln/detail/CVE-2006-7239 |
384,267 | gnutls | 34d87a7c3f12794a3ec2305cd2fdbae152bf2a76 | http://git.savannah.gnu.org/cgit/gnutls | http://git.savannah.gnu.org/cgit/gnutls.git/commit/?id=34d87a7c3f12794a3ec2305cd2fdbae152bf2a76 | (_gnutls_x509_oid2mac_algorithm): Don't crash trying to strcmp the
NULL OID value in the hash_algorithms array, which happens when the
input OID doesn't match our OIDs for SHA1, MD5, MD2 or RIPEMD160.
Reported by satyakumar <satyam_kkd@hyd.hellosoft.com>. | 0 | _gnutls_x509_oid2mac_algorithm (const char *oid)
{
gnutls_mac_algorithm_t ret = 0;
GNUTLS_HASH_LOOP (if (p->oid && strcmp (oid, p->oid) == 0)
{
ret = p->id; break;}
);
if (ret == 0)
return GNUTLS_MAC_UNKNOWN;
return ret;
} | 134,585,458,830,945,930,000,000,000,000,000,000,000 | None | null | [
"CWE-310"
] | CVE-2006-7239 | The _gnutls_x509_oid2mac_algorithm function in lib/gnutls_algorithms.c in GnuTLS before 1.4.2 allows remote attackers to cause a denial of service (crash) via a crafted X.509 certificate that uses a hash algorithm that is not supported by GnuTLS, which triggers a NULL pointer dereference. | https://nvd.nist.gov/vuln/detail/CVE-2006-7239 |
206,642 | samba | a065c177dfc8f968775593ba00dffafeebb2e054 | https://github.com/samba-team/samba | http://git.samba.org/?p=samba.git;a=commit;h=a065c177dfc8f968775593ba00dffafeebb2e054 | mount.cifs: check for invalid characters in device name and mountpoint
It's apparently possible to corrupt the mtab if you pass embedded
newlines to addmntent. Apparently tabs are also a problem with certain
earlier glibc versions. Backslashes are also a minor issue apparently,
but we can't reasonably filter those.
M... | 1 | int main(int argc, char ** argv)
{
int c;
unsigned long flags = MS_MANDLOCK;
char * orgoptions = NULL;
char * share_name = NULL;
const char * ipaddr = NULL;
char * uuid = NULL;
char * mountpoint = NULL;
char * options = NULL;
char * optionstail;
char * resolved_path = NULL;
char * temp;
char * dev_name;
in... | 207,894,986,714,128,400,000,000,000,000,000,000,000 | mount.cifs.c | 110,388,567,230,996,620,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2010-0788 | ncpfs 2.2.6 allows local users to cause a denial of service, obtain sensitive information, or possibly gain privileges via symlink attacks involving the (1) ncpmount and (2) ncpumount programs. | https://nvd.nist.gov/vuln/detail/CVE-2010-0788 |
384,307 | samba | a065c177dfc8f968775593ba00dffafeebb2e054 | https://github.com/samba-team/samba | http://git.samba.org/?p=samba.git;a=commit;h=a065c177dfc8f968775593ba00dffafeebb2e054 | mount.cifs: check for invalid characters in device name and mountpoint
It's apparently possible to corrupt the mtab if you pass embedded
newlines to addmntent. Apparently tabs are also a problem with certain
earlier glibc versions. Backslashes are also a minor issue apparently,
but we can't reasonably filter those.
M... | 0 | int main(int argc, char ** argv)
{
int c;
unsigned long flags = MS_MANDLOCK;
char * orgoptions = NULL;
char * share_name = NULL;
const char * ipaddr = NULL;
char * uuid = NULL;
char * mountpoint = NULL;
char * options = NULL;
char * optionstail;
char * resolved_path = NULL;
char * temp;
char * dev_name;
in... | 239,573,362,229,496,100,000,000,000,000,000,000,000 | mount.cifs.c | 125,945,006,076,597,920,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2010-0788 | ncpfs 2.2.6 allows local users to cause a denial of service, obtain sensitive information, or possibly gain privileges via symlink attacks involving the (1) ncpmount and (2) ncpumount programs. | https://nvd.nist.gov/vuln/detail/CVE-2010-0788 |
206,644 | linux | edc4746f253d907d048de680a621e121517f484b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=edc4746f253d907d048de680a621e121517f484b | USB: iowarrior: fix use-after-free on disconnect
A recent fix addressing a deadlock on disconnect introduced a new bug
by moving the present flag out of the critical section protected by the
driver-data mutex. This could lead to a racing release() freeing the
driver data before disconnect() is done with it.
Due to in... | 1 | static void iowarrior_disconnect(struct usb_interface *interface)
{
struct iowarrior *dev;
int minor;
dev = usb_get_intfdata(interface);
mutex_lock(&iowarrior_open_disc_lock);
usb_set_intfdata(interface, NULL);
/* prevent device read, write and ioctl */
dev->present = 0;
minor = dev->minor;
mutex_unlock(&iow... | 233,393,805,857,565,980,000,000,000,000,000,000,000 | iowarrior.c | 291,866,677,504,276,220,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2019-19528 | In the Linux kernel before 5.3.7, there is a use-after-free bug that can be caused by a malicious USB device in the drivers/usb/misc/iowarrior.c driver, aka CID-edc4746f253d. | https://nvd.nist.gov/vuln/detail/CVE-2019-19528 |
384,336 | linux | edc4746f253d907d048de680a621e121517f484b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=edc4746f253d907d048de680a621e121517f484b | USB: iowarrior: fix use-after-free on disconnect
A recent fix addressing a deadlock on disconnect introduced a new bug
by moving the present flag out of the critical section protected by the
driver-data mutex. This could lead to a racing release() freeing the
driver data before disconnect() is done with it.
Due to in... | 0 | static void iowarrior_disconnect(struct usb_interface *interface)
{
struct iowarrior *dev;
int minor;
dev = usb_get_intfdata(interface);
mutex_lock(&iowarrior_open_disc_lock);
usb_set_intfdata(interface, NULL);
minor = dev->minor;
mutex_unlock(&iowarrior_open_disc_lock);
/* give back our minor - this will cal... | 143,978,675,382,746,430,000,000,000,000,000,000,000 | iowarrior.c | 45,613,723,983,582,010,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2019-19528 | In the Linux kernel before 5.3.7, there is a use-after-free bug that can be caused by a malicious USB device in the drivers/usb/misc/iowarrior.c driver, aka CID-edc4746f253d. | https://nvd.nist.gov/vuln/detail/CVE-2019-19528 |
206,647 | haproxy | 5dfc5d5cd0d2128d77253ead3acf03a421ab5b88 | https://github.com/haproxy/haproxy | https://git.haproxy.org/?p=haproxy.git;a=commit;h=5dfc5d5cd0d2128d77253ead3acf03a421ab5b88 | BUG/CRITICAL: hpack: never index a header into the headroom after wrapping
The HPACK header table is implemented as a wrapping list inside a contigous
area. Headers names and values are stored from right to left while indexes
are stored from left to right. When there's no more room to store a new one,
we wrap to the r... | 1 | int hpack_dht_insert(struct hpack_dht *dht, struct ist name, struct ist value)
{
unsigned int used;
unsigned int head;
unsigned int prev;
unsigned int wrap;
unsigned int tail;
uint32_t headroom, tailroom;
if (!hpack_dht_make_room(dht, name.len + value.len))
return 0;
/* Now there is enough room in the table... | 28,066,708,458,580,588,000,000,000,000,000,000,000 | hpack-tbl.c | 286,642,837,562,412,900,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2020-11100 | In hpack_dht_insert in hpack-tbl.c in the HPACK decoder in HAProxy 1.8 through 2.x before 2.1.4, a remote attacker can write arbitrary bytes around a certain location on the heap via a crafted HTTP/2 request, possibly causing remote code execution. | https://nvd.nist.gov/vuln/detail/CVE-2020-11100 |
384,379 | haproxy | 5dfc5d5cd0d2128d77253ead3acf03a421ab5b88 | https://github.com/haproxy/haproxy | https://git.haproxy.org/?p=haproxy.git;a=commit;h=5dfc5d5cd0d2128d77253ead3acf03a421ab5b88 | BUG/CRITICAL: hpack: never index a header into the headroom after wrapping
The HPACK header table is implemented as a wrapping list inside a contigous
area. Headers names and values are stored from right to left while indexes
are stored from left to right. When there's no more room to store a new one,
we wrap to the r... | 0 | int hpack_dht_insert(struct hpack_dht *dht, struct ist name, struct ist value)
{
unsigned int used;
unsigned int head;
unsigned int prev;
unsigned int wrap;
unsigned int tail;
uint32_t headroom, tailroom;
if (!hpack_dht_make_room(dht, name.len + value.len))
return 0;
/* Now there is enough room in the table... | 108,830,341,792,104,600,000,000,000,000,000,000,000 | hpack-tbl.c | 306,994,177,552,948,900,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2020-11100 | In hpack_dht_insert in hpack-tbl.c in the HPACK decoder in HAProxy 1.8 through 2.x before 2.1.4, a remote attacker can write arbitrary bytes around a certain location on the heap via a crafted HTTP/2 request, possibly causing remote code execution. | https://nvd.nist.gov/vuln/detail/CVE-2020-11100 |
206,654 | jansson | 42016a35c8907e477be73b0b5d06cc09af231ee4 | https://github.com/akheron/jansson | https://github.com/akheron/jansson/commit/42016a35c8907e477be73b0b5d06cc09af231ee4 | Oops, ATOMIC_ACQ_REL is not a correct memmodel for __atomic_store_n | 1 | void json_object_seed(size_t seed) {
uint32_t new_seed = (uint32_t)seed;
if (hashtable_seed == 0) {
if (__atomic_test_and_set(&seed_initialized, __ATOMIC_RELAXED) == 0) {
/* Do the seeding ourselves */
if (new_seed == 0)
new_seed = generate_seed();
_... | 195,891,029,301,175,230,000,000,000,000,000,000,000 | hashtable_seed.c | 232,429,098,651,356,150,000,000,000,000,000,000,000 | [
"CWE-310"
] | CVE-2013-6401 | Jansson, possibly 2.4 and earlier, does not restrict the ability to trigger hash collisions predictably, which allows context-dependent attackers to cause a denial of service (CPU consumption) via a crafted JSON document. | https://nvd.nist.gov/vuln/detail/CVE-2013-6401 |
384,393 | jansson | 42016a35c8907e477be73b0b5d06cc09af231ee4 | https://github.com/akheron/jansson | https://github.com/akheron/jansson/commit/42016a35c8907e477be73b0b5d06cc09af231ee4 | Oops, ATOMIC_ACQ_REL is not a correct memmodel for __atomic_store_n | 0 | void json_object_seed(size_t seed) {
uint32_t new_seed = (uint32_t)seed;
if (hashtable_seed == 0) {
if (__atomic_test_and_set(&seed_initialized, __ATOMIC_RELAXED) == 0) {
/* Do the seeding ourselves */
if (new_seed == 0)
new_seed = generate_seed();
_... | 249,554,445,288,554,800,000,000,000,000,000,000,000 | hashtable_seed.c | 209,029,082,066,148,470,000,000,000,000,000,000,000 | [
"CWE-310"
] | CVE-2013-6401 | Jansson, possibly 2.4 and earlier, does not restrict the ability to trigger hash collisions predictably, which allows context-dependent attackers to cause a denial of service (CPU consumption) via a crafted JSON document. | https://nvd.nist.gov/vuln/detail/CVE-2013-6401 |
206,655 | libxml2 | e2a9122b8dde53d320750451e9907a7dcb2ca8bb | https://github.com/GNOME/libxml2 | https://git.gnome.org/browse/libxml2/commit/?id=e2a9122b8dde53d320750451e9907a7dcb2ca8bb | Set memory limit for LZMA decompression
Otherwise malicious LZMA compressed files could consume large amounts
of memory when decompressed.
According to the xz man page, files compressed with `xz -9` currently
require 65 MB to decompress, so set the limit to 100 MB.
Should fix bug 786696. | 1 | xz_head(xz_statep state)
{
lzma_stream *strm = &(state->strm);
lzma_stream init = LZMA_STREAM_INIT;
int flags;
unsigned len;
/* allocate read buffers and inflate memory */
if (state->size == 0) {
/* allocate buffers */
state->in = xmlMalloc(state->want);
state->out = xml... | 31,244,923,179,373,630,000,000,000,000,000,000,000 | xzlib.c | 214,417,675,830,901,240,000,000,000,000,000,000,000 | [
"CWE-770"
] | CVE-2017-18258 | The xz_head function in xzlib.c in libxml2 before 2.9.6 allows remote attackers to cause a denial of service (memory consumption) via a crafted LZMA file, because the decoder functionality does not restrict memory usage to what is required for a legitimate file. | https://nvd.nist.gov/vuln/detail/CVE-2017-18258 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.