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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
413,435 | git | 3c9d0414ed2db0167e6c828b547be8fc9f88fccc | https://github.com/git/git | http://git.kernel.org/?p=git/git.git;a=commitdiff;h=3c9d0414ed2db0167e6c828b547be8fc9f88fccc;hp=c173dad58787a7f11a526dbcdaa5a2fe9ff1c87f | Check size of path buffer before writing into it
This prevents a buffer overrun that could otherwise be triggered by
creating a file called '.git' with contents
gitdir: (something really long)
Signed-off-by: Greg Brockman <gdb@mit.edu>
Signed-off-by: Junio C Hamano <gitster@pobox.com> | 0 | static int is_git_directory(const char *suspect)
{
char path[PATH_MAX];
size_t len = strlen(suspect);
if (PATH_MAX <= len + strlen("/objects"))
die("Too long path: %.*s", 60, suspect);
strcpy(path, suspect);
if (getenv(DB_ENVIRONMENT)) {
if (access(getenv(DB_ENVIRONMENT), X_OK))
return 0;
}
else {
strc... | 162,957,199,263,871,540,000,000,000,000,000,000,000 | setup.c | 150,512,098,465,878,830,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2010-2542 | Stack-based buffer overflow in the is_git_directory function in setup.c in Git before 1.7.2.1 allows local users to gain privileges via a long gitdir: field in a .git file in a working copy. | https://nvd.nist.gov/vuln/detail/CVE-2010-2542 |
208,678 | connman | e4079a20f617a4b076af503f6e4e8b0304c9f2cb | https://git.kernel.org/pub/scm/network/connman/connman | https://git.kernel.org/pub/scm/network/connman/connman.git/commit/?id=e4079a20f617a4b076af503f6e4e8b0304c9f2cb | dnsproxy: Add length checks to prevent buffer overflow
Fixes: CVE-2021-26675 | 1 | static char *uncompress(int16_t field_count, char *start, char *end,
char *ptr, char *uncompressed, int uncomp_len,
char **uncompressed_ptr)
{
char *uptr = *uncompressed_ptr; /* position in result buffer */
debug("count %d ptr %p end %p uptr %p", field_count, ptr, end, uptr);
while (field_count-- > 0 && ptr ... | 185,213,935,440,958,530,000,000,000,000,000,000,000 | dnsproxy.c | 248,643,893,496,118,600,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-26675 | A stack-based buffer overflow in dnsproxy in ConnMan before 1.39 could be used by network adjacent attackers to execute code. | https://nvd.nist.gov/vuln/detail/CVE-2021-26675 |
413,516 | connman | e4079a20f617a4b076af503f6e4e8b0304c9f2cb | https://git.kernel.org/pub/scm/network/connman/connman | https://git.kernel.org/pub/scm/network/connman/connman.git/commit/?id=e4079a20f617a4b076af503f6e4e8b0304c9f2cb | dnsproxy: Add length checks to prevent buffer overflow
Fixes: CVE-2021-26675 | 0 | static char *uncompress(int16_t field_count, char *start, char *end,
char *ptr, char *uncompressed, int uncomp_len,
char **uncompressed_ptr)
{
char *uptr = *uncompressed_ptr; /* position in result buffer */
char * const uncomp_end = uncompressed + uncomp_len - 1;
debug("count %d ptr %p end %p uptr %p", field_... | 264,755,608,498,180,300,000,000,000,000,000,000,000 | dnsproxy.c | 283,960,017,603,808,050,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-26675 | A stack-based buffer overflow in dnsproxy in ConnMan before 1.39 could be used by network adjacent attackers to execute code. | https://nvd.nist.gov/vuln/detail/CVE-2021-26675 |
208,716 | jbig2dec | 0726320a4b55078e9d8deb590e477d598b3da66e | https://github.com/ArtifexSoftware/jbig2dec | https://github.com/ArtifexSoftware/jbig2dec/commit/0726320a4b55078e9d8deb590e477d598b3da66e | Fix OSS-Fuzz issue 20332: buffer overflow in jbig2_image_compose.
With extreme values of x/y/w/h we can get overflow. Test for this
and exit safely.
Thanks for OSS-Fuzz for reporting. | 1 | jbig2_image_compose(Jbig2Ctx *ctx, Jbig2Image *dst, Jbig2Image *src, int x, int y, Jbig2ComposeOp op)
{
uint32_t w, h;
uint32_t shift;
uint32_t leftbyte;
uint8_t *ss;
uint8_t *dd;
uint8_t leftmask, rightmask;
int early = x >= 0;
int late;
uint32_t bytewidth;
uint32_t syoffset = 0... | 321,902,796,246,136,250,000,000,000,000,000,000,000 | jbig2_image.c | 223,114,021,561,317,040,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2020-12268 | jbig2_image_compose in jbig2_image.c in Artifex jbig2dec before 0.18 has a heap-based buffer overflow. | https://nvd.nist.gov/vuln/detail/CVE-2020-12268 |
414,504 | jbig2dec | 0726320a4b55078e9d8deb590e477d598b3da66e | https://github.com/ArtifexSoftware/jbig2dec | https://github.com/ArtifexSoftware/jbig2dec/commit/0726320a4b55078e9d8deb590e477d598b3da66e | Fix OSS-Fuzz issue 20332: buffer overflow in jbig2_image_compose.
With extreme values of x/y/w/h we can get overflow. Test for this
and exit safely.
Thanks for OSS-Fuzz for reporting. | 0 | jbig2_image_compose(Jbig2Ctx *ctx, Jbig2Image *dst, Jbig2Image *src, int x, int y, Jbig2ComposeOp op)
{
uint32_t w, h;
uint32_t shift;
uint32_t leftbyte;
uint8_t *ss;
uint8_t *dd;
uint8_t leftmask, rightmask;
int early = x >= 0;
int late;
uint32_t bytewidth;
uint32_t syoffset = 0... | 317,683,035,226,769,900,000,000,000,000,000,000,000 | jbig2_image.c | 275,695,218,023,988,680,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2020-12268 | jbig2_image_compose in jbig2_image.c in Artifex jbig2dec before 0.18 has a heap-based buffer overflow. | https://nvd.nist.gov/vuln/detail/CVE-2020-12268 |
208,720 | evince | 350404c76dc8601e2cdd2636490e2afc83d3090e | https://github.com/GNOME/evince | https://git.gnome.org/browse/evince/commit/?id=350404c76dc8601e2cdd2636490e2afc83d3090e | dvi: Mitigate command injection attacks by quoting filename
With commit 1fcca0b8041de0d6074d7e17fba174da36c65f99 came a DVI backend.
It exports to PDF via the dvipdfm tool.
It calls that tool with the filename of the currently loaded document.
If that filename is cleverly crafted, it can escape the currently
used manu... | 1 | dvi_document_file_exporter_end (EvFileExporter *exporter)
{
gchar *command_line;
gint exit_stat;
GError *err = NULL;
gboolean success;
DviDocument *dvi_document = DVI_DOCUMENT(exporter);
command_line = g_strdup_printf ("dvipdfm %s -o %s \"%s\"", /* dvipdfm -s 1,2,.., -o exporter_filename dvi_filename */
... | 88,328,483,403,250,900,000,000,000,000,000,000,000 | dvi-document.c | 309,544,467,357,251,080,000,000,000,000,000,000,000 | [
"CWE-78"
] | CVE-2017-1000159 | Command injection in evince via filename when printing to PDF. This affects versions earlier than 3.25.91. | https://nvd.nist.gov/vuln/detail/CVE-2017-1000159 |
414,583 | evince | 350404c76dc8601e2cdd2636490e2afc83d3090e | https://github.com/GNOME/evince | https://git.gnome.org/browse/evince/commit/?id=350404c76dc8601e2cdd2636490e2afc83d3090e | dvi: Mitigate command injection attacks by quoting filename
With commit 1fcca0b8041de0d6074d7e17fba174da36c65f99 came a DVI backend.
It exports to PDF via the dvipdfm tool.
It calls that tool with the filename of the currently loaded document.
If that filename is cleverly crafted, it can escape the currently
used manu... | 0 | dvi_document_file_exporter_end (EvFileExporter *exporter)
{
gchar *command_line;
gint exit_stat;
GError *err = NULL;
gboolean success;
DviDocument *dvi_document = DVI_DOCUMENT(exporter);
gchar* quoted_filename = g_shell_quote (dvi_document->context->filename);
command_line = g_strdup_printf ("dvipdfm %s -o %... | 50,737,846,122,712,090,000,000,000,000,000,000,000 | dvi-document.c | 235,771,720,684,301,630,000,000,000,000,000,000,000 | [
"CWE-78"
] | CVE-2017-1000159 | Command injection in evince via filename when printing to PDF. This affects versions earlier than 3.25.91. | https://nvd.nist.gov/vuln/detail/CVE-2017-1000159 |
208,732 | vim | f50940531dd57135fe60aa393ac9d3281f352d88 | https://github.com/vim/vim | https://github.com/vim/vim/commit/f50940531dd57135fe60aa393ac9d3281f352d88 | patch 9.0.0105: illegal memory access when pattern starts with illegal byte
Problem: Illegal memory access when pattern starts with illegal byte.
Solution: Do not match a character with an illegal byte. | 1 | cstrchr(char_u *s, int c)
{
char_u *p;
int cc;
if (!rex.reg_ic || (!enc_utf8 && mb_char2len(c) > 1))
return vim_strchr(s, c);
// tolower() and toupper() can be slow, comparing twice should be a lot
// faster (esp. when using MS Visual C++!).
// For UTF-8 need to use folded case.
if (enc_... | 333,126,395,893,630,500,000,000,000,000,000,000,000 | regexp.c | 323,022,444,375,597,480,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2022-2581 | Out-of-bounds Read in GitHub repository vim/vim prior to 9.0.0104. | https://nvd.nist.gov/vuln/detail/CVE-2022-2581 |
414,831 | vim | f50940531dd57135fe60aa393ac9d3281f352d88 | https://github.com/vim/vim | https://github.com/vim/vim/commit/f50940531dd57135fe60aa393ac9d3281f352d88 | patch 9.0.0105: illegal memory access when pattern starts with illegal byte
Problem: Illegal memory access when pattern starts with illegal byte.
Solution: Do not match a character with an illegal byte. | 0 | cstrchr(char_u *s, int c)
{
char_u *p;
int cc;
if (!rex.reg_ic || (!enc_utf8 && mb_char2len(c) > 1))
return vim_strchr(s, c);
// tolower() and toupper() can be slow, comparing twice should be a lot
// faster (esp. when using MS Visual C++!).
// For UTF-8 need to use folded case.
if (enc_... | 232,159,544,625,016,480,000,000,000,000,000,000,000 | regexp.c | 137,917,551,285,872,000,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2022-2581 | Out-of-bounds Read in GitHub repository vim/vim prior to 9.0.0104. | https://nvd.nist.gov/vuln/detail/CVE-2022-2581 |
208,733 | linux | ecd1735f14d6ac868ae5d8b7a2bf193fa11f388b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ecd1735f14d6ac868ae5d8b7a2bf193fa11f388b | virt: acrn: fix a memory leak in acrn_dev_ioctl()
The vm_param and cpu_regs need to be freed via kfree()
before return -EINVAL error.
Fixes: 9c5137aedd11 ("virt: acrn: Introduce VM management interfaces")
Fixes: 2ad2aaee1bc9 ("virt: acrn: Introduce an ioctl to set vCPU registers state")
Signed-off-by: Xiaolong Huang ... | 1 | static long acrn_dev_ioctl(struct file *filp, unsigned int cmd,
unsigned long ioctl_param)
{
struct acrn_vm *vm = filp->private_data;
struct acrn_vm_creation *vm_param;
struct acrn_vcpu_regs *cpu_regs;
struct acrn_ioreq_notify notify;
struct acrn_ptdev_irq *irq_info;
struct acrn_ioeventfd ioeventfd;
struct... | 207,514,836,876,286,760,000,000,000,000,000,000,000 | hsm.c | 267,736,714,342,952,950,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2022-1651 | A memory leak flaw was found in the Linux kernel in acrn_dev_ioctl in the drivers/virt/acrn/hsm.c function in how the ACRN Device Model emulates virtual NICs in VM. This flaw allows a local privileged attacker to leak unauthorized kernel information, causing a denial of service. | https://nvd.nist.gov/vuln/detail/CVE-2022-1651 |
414,901 | linux | ecd1735f14d6ac868ae5d8b7a2bf193fa11f388b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ecd1735f14d6ac868ae5d8b7a2bf193fa11f388b | virt: acrn: fix a memory leak in acrn_dev_ioctl()
The vm_param and cpu_regs need to be freed via kfree()
before return -EINVAL error.
Fixes: 9c5137aedd11 ("virt: acrn: Introduce VM management interfaces")
Fixes: 2ad2aaee1bc9 ("virt: acrn: Introduce an ioctl to set vCPU registers state")
Signed-off-by: Xiaolong Huang ... | 0 | static long acrn_dev_ioctl(struct file *filp, unsigned int cmd,
unsigned long ioctl_param)
{
struct acrn_vm *vm = filp->private_data;
struct acrn_vm_creation *vm_param;
struct acrn_vcpu_regs *cpu_regs;
struct acrn_ioreq_notify notify;
struct acrn_ptdev_irq *irq_info;
struct acrn_ioeventfd ioeventfd;
struct... | 207,760,392,944,813,300,000,000,000,000,000,000,000 | hsm.c | 268,010,197,736,394,200,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2022-1651 | A memory leak flaw was found in the Linux kernel in acrn_dev_ioctl in the drivers/virt/acrn/hsm.c function in how the ACRN Device Model emulates virtual NICs in VM. This flaw allows a local privileged attacker to leak unauthorized kernel information, causing a denial of service. | https://nvd.nist.gov/vuln/detail/CVE-2022-1651 |
208,734 | samba | fab6b79b7724f0b636963be528483e3e946884aa | https://github.com/samba-team/samba | https://github.com/samba-team/samba/commit/fab6b79b7724f0b636963be528483e3e946884aa | CVE-2021-20277 ldb/attrib_handlers casefold: stay in bounds
For a string that had N spaces at the beginning, we would
try to move N bytes beyond the end of the string.
BUG: https://bugzilla.samba.org/show_bug.cgi?id=14655
Signed-off-by: Douglas Bagnall <douglas.bagnall@catalyst.net.nz>
Reviewed-by: Andrew Bartlett <... | 1 | int ldb_handler_fold(struct ldb_context *ldb, void *mem_ctx,
const struct ldb_val *in, struct ldb_val *out)
{
char *s, *t;
size_t l;
if (!in || !out || !(in->data)) {
return -1;
}
out->data = (uint8_t *)ldb_casefold(ldb, mem_ctx, (const char *)(in->data), in->length);
if (out->data == NULL) {
ldb_deb... | 52,987,283,014,228,250,000,000,000,000,000,000,000 | attrib_handlers.c | 20,945,031,300,116,022,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-20277 | A flaw was found in Samba's libldb. Multiple, consecutive leading spaces in an LDAP attribute can lead to an out-of-bounds memory write, leading to a crash of the LDAP server process handling the request. The highest threat from this vulnerability is to system availability. | https://nvd.nist.gov/vuln/detail/CVE-2021-20277 |
414,905 | samba | fab6b79b7724f0b636963be528483e3e946884aa | https://github.com/samba-team/samba | https://github.com/samba-team/samba/commit/fab6b79b7724f0b636963be528483e3e946884aa | CVE-2021-20277 ldb/attrib_handlers casefold: stay in bounds
For a string that had N spaces at the beginning, we would
try to move N bytes beyond the end of the string.
BUG: https://bugzilla.samba.org/show_bug.cgi?id=14655
Signed-off-by: Douglas Bagnall <douglas.bagnall@catalyst.net.nz>
Reviewed-by: Andrew Bartlett <... | 0 | int ldb_handler_fold(struct ldb_context *ldb, void *mem_ctx,
const struct ldb_val *in, struct ldb_val *out)
{
char *s, *t;
size_t l;
if (!in || !out || !(in->data)) {
return -1;
}
out->data = (uint8_t *)ldb_casefold(ldb, mem_ctx, (const char *)(in->data), in->length);
if (out->data == NULL) {
ldb_deb... | 138,276,973,143,951,900,000,000,000,000,000,000,000 | attrib_handlers.c | 315,633,263,718,350,400,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-20277 | A flaw was found in Samba's libldb. Multiple, consecutive leading spaces in an LDAP attribute can lead to an out-of-bounds memory write, leading to a crash of the LDAP server process handling the request. The highest threat from this vulnerability is to system availability. | https://nvd.nist.gov/vuln/detail/CVE-2021-20277 |
208,757 | ImageMagick | 7db3fa20893d557259da6e99e111954de83d2495 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/7db3fa20893d557259da6e99e111954de83d2495 | https://github.com/ImageMagick/ImageMagick/issues/1713 | 1 | static MagickBooleanType WriteHDRImage(const ImageInfo *image_info,Image *image,
ExceptionInfo *exception)
{
char
header[MagickPathExtent];
const char
*property;
MagickBooleanType
status;
register const Quantum
*p;
register ssize_t
i,
x;
size_t
length;
ssize_t
count... | 40,996,420,739,674,454,000,000,000,000,000,000,000 | hdr.c | 30,358,073,374,216,440,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2020-27762 | A flaw was found in ImageMagick in coders/hdr.c. An attacker who submits a crafted file that is processed by ImageMagick could trigger undefined behavior in the form of values outside the range of type `unsigned char`. This would most likely lead to an impact to application availability, but could potentially cause oth... | https://nvd.nist.gov/vuln/detail/CVE-2020-27762 |
415,160 | ImageMagick | 7db3fa20893d557259da6e99e111954de83d2495 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/7db3fa20893d557259da6e99e111954de83d2495 | https://github.com/ImageMagick/ImageMagick/issues/1713 | 0 | static MagickBooleanType WriteHDRImage(const ImageInfo *image_info,Image *image,
ExceptionInfo *exception)
{
char
header[MagickPathExtent];
const char
*property;
MagickBooleanType
status;
register const Quantum
*p;
register ssize_t
i,
x;
size_t
length;
ssize_t
count... | 298,946,769,867,154,980,000,000,000,000,000,000,000 | hdr.c | 116,084,284,343,404,930,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2020-27762 | A flaw was found in ImageMagick in coders/hdr.c. An attacker who submits a crafted file that is processed by ImageMagick could trigger undefined behavior in the form of values outside the range of type `unsigned char`. This would most likely lead to an impact to application availability, but could potentially cause oth... | https://nvd.nist.gov/vuln/detail/CVE-2020-27762 |
208,767 | curl | 75dc096e01ef1e21b6c57690d99371dedb2c0b80 | https://github.com/curl/curl | https://github.com/curl/curl/commit/75dc096e01ef1e21b6c57690d99371dedb2c0b80 | curl_multi_cleanup: clear connection pointer for easy handles
CVE-2016-5421
Bug: https://curl.haxx.se/docs/adv_20160803C.html
Reported-by: Marcelo Echeverria and Fernando Muñoz | 1 | static void close_all_connections(struct Curl_multi *multi)
{
struct connectdata *conn;
conn = Curl_conncache_find_first_connection(&multi->conn_cache);
while(conn) {
SIGPIPE_VARIABLE(pipe_st);
conn->data = multi->closure_handle;
sigpipe_ignore(conn->data, &pipe_st);
/* This will remove the conn... | 259,537,175,662,439,440,000,000,000,000,000,000,000 | multi.c | 2,935,492,645,489,206,400,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2016-5421 | Use-after-free vulnerability in libcurl before 7.50.1 allows attackers to control which connection is used or possibly have unspecified other impact via unknown vectors. | https://nvd.nist.gov/vuln/detail/CVE-2016-5421 |
415,282 | curl | 75dc096e01ef1e21b6c57690d99371dedb2c0b80 | https://github.com/curl/curl | https://github.com/curl/curl/commit/75dc096e01ef1e21b6c57690d99371dedb2c0b80 | curl_multi_cleanup: clear connection pointer for easy handles
CVE-2016-5421
Bug: https://curl.haxx.se/docs/adv_20160803C.html
Reported-by: Marcelo Echeverria and Fernando Muñoz | 0 | static void close_all_connections(struct Curl_multi *multi)
{
struct connectdata *conn;
conn = Curl_conncache_find_first_connection(&multi->conn_cache);
while(conn) {
SIGPIPE_VARIABLE(pipe_st);
conn->data = multi->closure_handle;
sigpipe_ignore(conn->data, &pipe_st);
conn->data->easy_conn = NULL... | 321,080,683,099,765,920,000,000,000,000,000,000,000 | multi.c | 247,601,779,947,554,570,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2016-5421 | Use-after-free vulnerability in libcurl before 7.50.1 allows attackers to control which connection is used or possibly have unspecified other impact via unknown vectors. | https://nvd.nist.gov/vuln/detail/CVE-2016-5421 |
208,804 | gdk-pixbuf | c2a40a92fe3df4111ed9da51fe3368c079b86926 | http://git.gnome.org/browse/gdk-pixbuf | https://git.gnome.org/browse/gdk-pixbuf/commit/gdk-pixbuf/io-jpeg.c?id=c2a40a92fe3df4111ed9da51fe3368c079b86926 | jpeg: Throw error when number of color components is unsupported
Explicitly check "3" or "4" output color components.
gdk-pixbuf assumed that the value of output_components to be either
3 or 4, but not an invalid value (9) or an unsupported value (1).
The way the buffer size was deduced was using a naive "== 4" chec... | 1 | gdk_pixbuf__jpeg_image_load_increment (gpointer data,
const guchar *buf, guint size,
GError **error)
{
JpegProgContext *context = (JpegProgContext *)data;
struct jpeg_decompress_struct *cinfo;
my_src_ptr src;
guint ... | 112,339,854,228,415,870,000,000,000,000,000,000,000 | io-jpeg.c | 36,431,351,539,375,805,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2017-2862 | An exploitable heap overflow vulnerability exists in the gdk_pixbuf__jpeg_image_load_increment functionality of Gdk-Pixbuf 2.36.6. A specially crafted jpeg file can cause a heap overflow resulting in remote code execution. An attacker can send a file or url to trigger this vulnerability. | https://nvd.nist.gov/vuln/detail/CVE-2017-2862 |
415,752 | gdk-pixbuf | c2a40a92fe3df4111ed9da51fe3368c079b86926 | http://git.gnome.org/browse/gdk-pixbuf | https://git.gnome.org/browse/gdk-pixbuf/commit/gdk-pixbuf/io-jpeg.c?id=c2a40a92fe3df4111ed9da51fe3368c079b86926 | jpeg: Throw error when number of color components is unsupported
Explicitly check "3" or "4" output color components.
gdk-pixbuf assumed that the value of output_components to be either
3 or 4, but not an invalid value (9) or an unsupported value (1).
The way the buffer size was deduced was using a naive "== 4" chec... | 0 | gdk_pixbuf__jpeg_image_load_increment (gpointer data,
const guchar *buf, guint size,
GError **error)
{
JpegProgContext *context = (JpegProgContext *)data;
struct jpeg_decompress_struct *cinfo;
my_src_ptr src;
guint ... | 190,270,801,747,076,470,000,000,000,000,000,000,000 | io-jpeg.c | 11,472,022,171,727,786,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2017-2862 | An exploitable heap overflow vulnerability exists in the gdk_pixbuf__jpeg_image_load_increment functionality of Gdk-Pixbuf 2.36.6. A specially crafted jpeg file can cause a heap overflow resulting in remote code execution. An attacker can send a file or url to trigger this vulnerability. | https://nvd.nist.gov/vuln/detail/CVE-2017-2862 |
208,805 | irssi | e32e9d63c67ab95ef0576154680a6c52334b97af | https://github.com/irssi/irssi | https://github.com/irssi/irssi/commit/e32e9d63c67ab95ef0576154680a6c52334b97af | Do not read beyond end of escaped string
Credit to OSS-Fuzz | 1 | static char *theme_format_expand_abstract(THEME_REC *theme, const char **formatp,
theme_rm_col *last_fg, theme_rm_col *last_bg, int flags,
GTree *block_list)
{
GString *str;
const char *p, *format;
char *abstract, *data, *ret;
theme... | 229,809,055,220,572,950,000,000,000,000,000,000,000 | themes.c | 226,229,851,090,433,180,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2018-7051 | An issue was discovered in Irssi before 1.0.7 and 1.1.x before 1.1.1. Certain nick names could result in out-of-bounds access when printing theme strings. | https://nvd.nist.gov/vuln/detail/CVE-2018-7051 |
415,757 | irssi | e32e9d63c67ab95ef0576154680a6c52334b97af | https://github.com/irssi/irssi | https://github.com/irssi/irssi/commit/e32e9d63c67ab95ef0576154680a6c52334b97af | Do not read beyond end of escaped string
Credit to OSS-Fuzz | 0 | static char *theme_format_expand_abstract(THEME_REC *theme, const char **formatp,
theme_rm_col *last_fg, theme_rm_col *last_bg, int flags,
GTree *block_list)
{
GString *str;
const char *p, *format;
char *abstract, *data, *ret;
theme... | 3,941,434,239,751,174,600,000,000,000,000,000,000 | themes.c | 29,214,600,380,873,606,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2018-7051 | An issue was discovered in Irssi before 1.0.7 and 1.1.x before 1.1.1. Certain nick names could result in out-of-bounds access when printing theme strings. | https://nvd.nist.gov/vuln/detail/CVE-2018-7051 |
208,847 | util-linux | cc8cc8f32c863f3ae6a8a88e97b47bcd6a21825f | https://github.com/karelzak/util-linux | http://git.kernel.org/?p=utils/util-linux/util-linux.git;a=commit;h=cc8cc8f32c863f3ae6a8a88e97b47bcd6a21825f | umount: sanitize paths from non-root users
Signed-off-by: Karel Zak <kzak@redhat.com> | 1 | int main(int argc, char **argv)
{
int c, rc = 0, all = 0, recursive = 0;
struct libmnt_context *cxt;
char *types = NULL;
enum {
UMOUNT_OPT_FAKE = CHAR_MAX + 1,
};
static const struct option longopts[] = {
{ "all", 0, 0, 'a' },
{ "detach-loop", 0, 0, 'd' },
{ "fake", 0, 0, UMOUNT_OPT_FAKE },
{ "force",... | 257,826,107,786,176,530,000,000,000,000,000,000,000 | umount.c | 70,533,690,310,287,740,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-0157 | (a) mount and (b) umount in util-linux 2.14.1, 2.17.2, and probably other versions allow local users to determine the existence of restricted directories by (1) using the --guess-fstype command-line option or (2) attempting to mount a non-existent device, which generates different error messages depending on whether th... | https://nvd.nist.gov/vuln/detail/CVE-2013-0157 |
416,275 | util-linux | cc8cc8f32c863f3ae6a8a88e97b47bcd6a21825f | https://github.com/karelzak/util-linux | http://git.kernel.org/?p=utils/util-linux/util-linux.git;a=commit;h=cc8cc8f32c863f3ae6a8a88e97b47bcd6a21825f | umount: sanitize paths from non-root users
Signed-off-by: Karel Zak <kzak@redhat.com> | 0 | int main(int argc, char **argv)
{
int c, rc = 0, all = 0, recursive = 0;
struct libmnt_context *cxt;
char *types = NULL;
enum {
UMOUNT_OPT_FAKE = CHAR_MAX + 1,
};
static const struct option longopts[] = {
{ "all", 0, 0, 'a' },
{ "detach-loop", 0, 0, 'd' },
{ "fake", 0, 0, UMOUNT_OPT_FAKE },
{ "force",... | 8,163,774,011,680,899,000,000,000,000,000,000,000 | umount.c | 107,862,004,988,991,350,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-0157 | (a) mount and (b) umount in util-linux 2.14.1, 2.17.2, and probably other versions allow local users to determine the existence of restricted directories by (1) using the --guess-fstype command-line option or (2) attempting to mount a non-existent device, which generates different error messages depending on whether th... | https://nvd.nist.gov/vuln/detail/CVE-2013-0157 |
208,918 | gst-plugins-base | 5d505d108800cef210f67dcfed2801ba36beac2a | https://github.com/GStreamer/gst-plugins-base | https://github.com/GStreamer/gst-plugins-base/commit/5d505d108800cef210f67dcfed2801ba36beac2a | riff-media: Don't divide block align by zero channels
https://bugzilla.gnome.org/show_bug.cgi?id=777525 | 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)
... | 310,510,510,447,105,350,000,000,000,000,000,000,000 | riff-media.c | 127,646,143,622,019,850,000,000,000,000,000,000,000 | [
"CWE-369"
] | CVE-2017-5844 | 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 ASF file. | https://nvd.nist.gov/vuln/detail/CVE-2017-5844 |
416,447 | gst-plugins-base | 5d505d108800cef210f67dcfed2801ba36beac2a | https://github.com/GStreamer/gst-plugins-base | https://github.com/GStreamer/gst-plugins-base/commit/5d505d108800cef210f67dcfed2801ba36beac2a | riff-media: Don't divide block align by zero channels
https://bugzilla.gnome.org/show_bug.cgi?id=777525 | 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)
... | 267,986,463,319,818,200,000,000,000,000,000,000,000 | riff-media.c | 230,035,508,028,196,200,000,000,000,000,000,000,000 | [
"CWE-369"
] | CVE-2017-5844 | 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 ASF file. | https://nvd.nist.gov/vuln/detail/CVE-2017-5844 |
208,919 | libvncserver | bef41f6ec4097a8ee094f90a1b34a708fbd757ec | https://github.com/LibVNC/libvncserver | https://github.com/LibVNC/libvncserver/commit/bef41f6ec4097a8ee094f90a1b34a708fbd757ec | libvncclient: free vncRec memory in rfbClientCleanup()
Otherwise we leak memory. Spotted by Ramin Farajpour Cami
<ramin.blackhat@gmail.com>, thanks! | 1 | void rfbClientCleanup(rfbClient* client) {
#ifdef LIBVNCSERVER_HAVE_LIBZ
int i;
for ( i = 0; i < 4; i++ ) {
if (client->zlibStreamActive[i] == TRUE ) {
if (inflateEnd (&client->zlibStream[i]) != Z_OK &&
client->zlibStream[i].msg != NULL)
rfbClientLog("inflateEnd: %s\n", client->zlibStream[i].msg);
... | 50,509,328,126,052,690,000,000,000,000,000,000,000 | None | null | [
"CWE-703"
] | CVE-2020-29260 | libvncclient v0.9.13 was discovered to contain a memory leak via the function rfbClientCleanup(). | https://nvd.nist.gov/vuln/detail/CVE-2020-29260 |
416,448 | libvncserver | bef41f6ec4097a8ee094f90a1b34a708fbd757ec | https://github.com/LibVNC/libvncserver | https://github.com/LibVNC/libvncserver/commit/bef41f6ec4097a8ee094f90a1b34a708fbd757ec | libvncclient: free vncRec memory in rfbClientCleanup()
Otherwise we leak memory. Spotted by Ramin Farajpour Cami
<ramin.blackhat@gmail.com>, thanks! | 0 | void rfbClientCleanup(rfbClient* client) {
#ifdef LIBVNCSERVER_HAVE_LIBZ
int i;
for ( i = 0; i < 4; i++ ) {
if (client->zlibStreamActive[i] == TRUE ) {
if (inflateEnd (&client->zlibStream[i]) != Z_OK &&
client->zlibStream[i].msg != NULL)
rfbClientLog("inflateEnd: %s\n", client->zlibStream[i].msg);
... | 168,950,825,518,541,240,000,000,000,000,000,000,000 | None | null | [
"CWE-703"
] | CVE-2020-29260 | libvncclient v0.9.13 was discovered to contain a memory leak via the function rfbClientCleanup(). | https://nvd.nist.gov/vuln/detail/CVE-2020-29260 |
208,920 | linux | 1d3ff0950e2b40dc861b1739029649d03f591820 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1d3ff0950e2b40dc861b1739029649d03f591820 | dccp: Fix memleak in __feat_register_sp
If dccp_feat_push_change fails, we forget free the mem
which is alloced by kmemdup in dccp_feat_clone_sp_val.
Reported-by: Hulk Robot <hulkci@huawei.com>
Fixes: e8ef967a54f4 ("dccp: Registration routines for changing feature values")
Reviewed-by: Mukesh Ojha <mojha@codeaurora.o... | 1 | static int __feat_register_sp(struct list_head *fn, u8 feat, u8 is_local,
u8 mandatory, u8 const *sp_val, u8 sp_len)
{
dccp_feat_val fval;
if (dccp_feat_type(feat) != FEAT_SP ||
!dccp_feat_sp_list_ok(feat, sp_val, sp_len))
return -EINVAL;
/* Avoid negotiating alien CCIDs by only advertising support... | 166,546,083,355,542,970,000,000,000,000,000,000,000 | feat.c | 10,439,163,242,856,101,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2019-20096 | In the Linux kernel before 5.1, there is a memory leak in __feat_register_sp() in net/dccp/feat.c, which may cause denial of service, aka CID-1d3ff0950e2b. | https://nvd.nist.gov/vuln/detail/CVE-2019-20096 |
416,495 | linux | 1d3ff0950e2b40dc861b1739029649d03f591820 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1d3ff0950e2b40dc861b1739029649d03f591820 | dccp: Fix memleak in __feat_register_sp
If dccp_feat_push_change fails, we forget free the mem
which is alloced by kmemdup in dccp_feat_clone_sp_val.
Reported-by: Hulk Robot <hulkci@huawei.com>
Fixes: e8ef967a54f4 ("dccp: Registration routines for changing feature values")
Reviewed-by: Mukesh Ojha <mojha@codeaurora.o... | 0 | static int __feat_register_sp(struct list_head *fn, u8 feat, u8 is_local,
u8 mandatory, u8 const *sp_val, u8 sp_len)
{
dccp_feat_val fval;
if (dccp_feat_type(feat) != FEAT_SP ||
!dccp_feat_sp_list_ok(feat, sp_val, sp_len))
return -EINVAL;
/* Avoid negotiating alien CCIDs by only advertising support... | 117,112,567,012,380,860,000,000,000,000,000,000,000 | feat.c | 130,731,748,402,017,170,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2019-20096 | In the Linux kernel before 5.1, there is a memory leak in __feat_register_sp() in net/dccp/feat.c, which may cause denial of service, aka CID-1d3ff0950e2b. | https://nvd.nist.gov/vuln/detail/CVE-2019-20096 |
208,921 | ImageMagick | 73fbc6a557b4f63af18b2debe83f817859ef7481 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/73fbc6a557b4f63af18b2debe83f817859ef7481 | https://github.com/ImageMagick/ImageMagick/issues/956 | 1 | static Image *ReadSUNImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
#define RMT_EQUAL_RGB 1
#define RMT_NONE 0
#define RMT_RAW 2
#define RT_STANDARD 1
#define RT_ENCODED 2
#define RT_FORMAT_RGB 3
typedef struct _SUNInfo
{
unsigned int
magic,
width,
height,
depth,
... | 155,972,564,503,698,450,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2018-11251 | In ImageMagick 7.0.7-23 Q16 x86_64 2018-01-24, there is a heap-based buffer over-read in ReadSUNImage in coders/sun.c, which allows attackers to cause a denial of service (application crash in SetGrayscaleImage in MagickCore/quantize.c) via a crafted SUN image file. | https://nvd.nist.gov/vuln/detail/CVE-2018-11251 |
416,506 | ImageMagick | 73fbc6a557b4f63af18b2debe83f817859ef7481 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/73fbc6a557b4f63af18b2debe83f817859ef7481 | https://github.com/ImageMagick/ImageMagick/issues/956 | 0 | static Image *ReadSUNImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
#define RMT_EQUAL_RGB 1
#define RMT_NONE 0
#define RMT_RAW 2
#define RT_STANDARD 1
#define RT_ENCODED 2
#define RT_FORMAT_RGB 3
typedef struct _SUNInfo
{
unsigned int
magic,
width,
height,
depth,
... | 125,905,524,653,750,070,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2018-11251 | In ImageMagick 7.0.7-23 Q16 x86_64 2018-01-24, there is a heap-based buffer over-read in ReadSUNImage in coders/sun.c, which allows attackers to cause a denial of service (application crash in SetGrayscaleImage in MagickCore/quantize.c) via a crafted SUN image file. | https://nvd.nist.gov/vuln/detail/CVE-2018-11251 |
208,922 | php-src | b061fa909de77085d3822a89ab901b934d0362c4 | https://github.com/php/php-src | https://github.com/php/php-src/commit/b061fa909de77085d3822a89ab901b934d0362c4 | Fix bug #73192 | 1 | PHPAPI php_url *php_url_parse_ex(char const *str, int 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) {
/* sch... | 98,702,414,901,692,920,000,000,000,000,000,000,000 | url.c | 18,566,943,646,987,276,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-10397 | In PHP before 5.6.28 and 7.x before 7.0.13, incorrect handling of various URI components in the URL parser could be used by attackers to bypass hostname-specific URL checks, as demonstrated by evil.example.com:80#@good.example.com/ and evil.example.com:80?@good.example.com/ inputs to the parse_url function (implemented... | https://nvd.nist.gov/vuln/detail/CVE-2016-10397 |
416,509 | php-src | b061fa909de77085d3822a89ab901b934d0362c4 | https://github.com/php/php-src | https://github.com/php/php-src/commit/b061fa909de77085d3822a89ab901b934d0362c4 | Fix bug #73192 | 0 | PHPAPI php_url *php_url_parse_ex(char const *str, int 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) {
/* sch... | 275,398,919,837,672,750,000,000,000,000,000,000,000 | url.c | 247,494,571,583,206,300,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-10397 | In PHP before 5.6.28 and 7.x before 7.0.13, incorrect handling of various URI components in the URL parser could be used by attackers to bypass hostname-specific URL checks, as demonstrated by evil.example.com:80#@good.example.com/ and evil.example.com:80?@good.example.com/ inputs to the parse_url function (implemented... | https://nvd.nist.gov/vuln/detail/CVE-2016-10397 |
208,934 | php-src | 1a4722a89ee85be74af5086a7027b3ad1e0a55e8 | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commitdiff;h=1a4722a89ee85be74af5086a7027b3ad1e0a55e8 | Fix #70064: imagescale(..., IMG_BICUBIC) leaks memory
A temporary image (tmp_im) is created with gdImageTrueColor() and freed with
gdFree() instead of gdImageDestroy(). Let's fix that. | 1 | gdImagePtr gdImageScaleTwoPass(const gdImagePtr src, const unsigned int src_width, const unsigned int src_height, const unsigned int new_width, const unsigned int new_height)
{
gdImagePtr tmp_im;
gdImagePtr dst;
/* Convert to truecolor if it isn't; this code requires it. */
if (!src->trueColor) {
gdImagePaletteT... | 166,412,437,609,933,620,000,000,000,000,000,000,000 | gd_interpolation.c | 239,764,360,549,637,640,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2015-8877 | The gdImageScaleTwoPass function in gd_interpolation.c in the GD Graphics Library (aka libgd) before 2.2.0, as used in PHP before 5.6.12, uses inconsistent allocate and free approaches, which allows remote attackers to cause a denial of service (memory consumption) via a crafted call, as demonstrated by a call to the P... | https://nvd.nist.gov/vuln/detail/CVE-2015-8877 |
416,695 | php-src | 1a4722a89ee85be74af5086a7027b3ad1e0a55e8 | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commitdiff;h=1a4722a89ee85be74af5086a7027b3ad1e0a55e8 | Fix #70064: imagescale(..., IMG_BICUBIC) leaks memory
A temporary image (tmp_im) is created with gdImageTrueColor() and freed with
gdFree() instead of gdImageDestroy(). Let's fix that. | 0 | gdImagePtr gdImageScaleTwoPass(const gdImagePtr src, const unsigned int src_width, const unsigned int src_height, const unsigned int new_width, const unsigned int new_height)
{
gdImagePtr tmp_im;
gdImagePtr dst;
/* Convert to truecolor if it isn't; this code requires it. */
if (!src->trueColor) {
gdImagePaletteT... | 98,191,283,610,433,800,000,000,000,000,000,000,000 | gd_interpolation.c | 56,199,321,201,124,190,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2015-8877 | The gdImageScaleTwoPass function in gd_interpolation.c in the GD Graphics Library (aka libgd) before 2.2.0, as used in PHP before 5.6.12, uses inconsistent allocate and free approaches, which allows remote attackers to cause a denial of service (memory consumption) via a crafted call, as demonstrated by a call to the P... | https://nvd.nist.gov/vuln/detail/CVE-2015-8877 |
208,953 | tor | 43414eb98821d3b5c6c65181d7545ce938f82c8e | https://github.com/torproject/tor | https://gitweb.torproject.org/tor.git/commitdiff/43414eb98821d3b5c6c65181d7545ce938f82c8e | Fix bounds-checking in policy_summarize
Found by piebeer. | 1 | policy_summarize(smartlist_t *policy)
{
smartlist_t *summary = policy_summary_create();
smartlist_t *accepts, *rejects;
int i, last, start_prt;
size_t accepts_len, rejects_len, shorter_len, final_size;
char *accepts_str = NULL, *rejects_str = NULL, *shorter_str, *result;
const char *prefix;
tor_assert(po... | 223,859,064,199,125,000,000,000,000,000,000,000,000 | policies.c | 81,269,338,163,373,590,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-1924 | Buffer overflow in the policy_summarize function in or/policies.c in Tor before 0.2.1.30 allows remote attackers to cause a denial of service (directory authority crash) via a crafted policy that triggers creation of a long port list. | https://nvd.nist.gov/vuln/detail/CVE-2011-1924 |
416,896 | tor | 43414eb98821d3b5c6c65181d7545ce938f82c8e | https://github.com/torproject/tor | https://gitweb.torproject.org/tor.git/commitdiff/43414eb98821d3b5c6c65181d7545ce938f82c8e | Fix bounds-checking in policy_summarize
Found by piebeer. | 0 | policy_summarize(smartlist_t *policy)
{
smartlist_t *summary = policy_summary_create();
smartlist_t *accepts, *rejects;
int i, last, start_prt;
size_t accepts_len, rejects_len, shorter_len, final_size;
char *accepts_str = NULL, *rejects_str = NULL, *shorter_str, *result;
const char *prefix;
tor_assert(po... | 198,342,825,034,703,900,000,000,000,000,000,000,000 | policies.c | 73,196,655,216,314,250,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-1924 | Buffer overflow in the policy_summarize function in or/policies.c in Tor before 0.2.1.30 allows remote attackers to cause a denial of service (directory authority crash) via a crafted policy that triggers creation of a long port list. | https://nvd.nist.gov/vuln/detail/CVE-2011-1924 |
208,979 | qemu | aab0e2a661b2b6bf7915c0aefe807fb60d6d9d13 | https://github.com/bonzini/qemu | https://git.qemu.org/?p=qemu.git;a=commit;h=aab0e2a661b2b6bf7915c0aefe807fb60d6d9d13 | ati: use vga_read_byte in ati_cursor_define
This makes sure reads are confined to vga video memory.
v3: use uint32_t, fix cut+paste bug.
v2: fix ati_cursor_draw_line too.
Reported-by: xu hang <flier_m@outlook.com>
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Reviewed-by: BALATON Zoltan <balaton@eik.bme.hu>
Revie... | 1 | static void ati_cursor_define(ATIVGAState *s)
{
uint8_t data[1024];
uint8_t *src;
int i, j, idx = 0;
if ((s->regs.cur_offset & BIT(31)) || s->cursor_guest_mode) {
return; /* Do not update cursor if locked or rendered by guest */
}
/* FIXME handle cur_hv_offs correctly */
src = s->vg... | 187,165,196,583,136,150,000,000,000,000,000,000,000 | ati.c | 239,537,731,829,298,450,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2019-20808 | In QEMU 4.1.0, an out-of-bounds read flaw was found in the ATI VGA implementation. It occurs in the ati_cursor_define() routine while handling MMIO write operations through the ati_mm_write() callback. A malicious guest could abuse this flaw to crash the QEMU process, resulting in a denial of service. | https://nvd.nist.gov/vuln/detail/CVE-2019-20808 |
416,997 | qemu | aab0e2a661b2b6bf7915c0aefe807fb60d6d9d13 | https://github.com/bonzini/qemu | https://git.qemu.org/?p=qemu.git;a=commit;h=aab0e2a661b2b6bf7915c0aefe807fb60d6d9d13 | ati: use vga_read_byte in ati_cursor_define
This makes sure reads are confined to vga video memory.
v3: use uint32_t, fix cut+paste bug.
v2: fix ati_cursor_draw_line too.
Reported-by: xu hang <flier_m@outlook.com>
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Reviewed-by: BALATON Zoltan <balaton@eik.bme.hu>
Revie... | 0 | static void ati_cursor_define(ATIVGAState *s)
{
uint8_t data[1024];
uint32_t srcoff;
int i, j, idx = 0;
if ((s->regs.cur_offset & BIT(31)) || s->cursor_guest_mode) {
return; /* Do not update cursor if locked or rendered by guest */
}
/* FIXME handle cur_hv_offs correctly */
srcoff =... | 150,231,946,557,871,890,000,000,000,000,000,000,000 | ati.c | 182,013,711,422,120,930,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2019-20808 | In QEMU 4.1.0, an out-of-bounds read flaw was found in the ATI VGA implementation. It occurs in the ati_cursor_define() routine while handling MMIO write operations through the ati_mm_write() callback. A malicious guest could abuse this flaw to crash the QEMU process, resulting in a denial of service. | https://nvd.nist.gov/vuln/detail/CVE-2019-20808 |
208,986 | linux | 6377f787aeb945cae7abbb6474798de129e1f3ac | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6377f787aeb945cae7abbb6474798de129e1f3ac | appletalk: Fix use-after-free in atalk_proc_exit
KASAN report this:
BUG: KASAN: use-after-free in pde_subdir_find+0x12d/0x150 fs/proc/generic.c:71
Read of size 8 at addr ffff8881f41fe5b0 by task syz-executor.0/2806
CPU: 0 PID: 2806 Comm: syz-executor.0 Not tainted 5.0.0-rc7+ #45
Hardware name: QEMU Standard PC (i440... | 1 | void __exit atalk_proc_exit(void)
{
remove_proc_subtree("atalk", init_net.proc_net);
} | 86,450,256,672,936,000,000,000,000,000,000,000,000 | atalk_proc.c | 239,586,294,381,000,150,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2019-15292 | An issue was discovered in the Linux kernel before 5.0.9. There is a use-after-free in atalk_proc_exit, related to net/appletalk/atalk_proc.c, net/appletalk/ddp.c, and net/appletalk/sysctl_net_atalk.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-15292 |
417,037 | linux | 6377f787aeb945cae7abbb6474798de129e1f3ac | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6377f787aeb945cae7abbb6474798de129e1f3ac | appletalk: Fix use-after-free in atalk_proc_exit
KASAN report this:
BUG: KASAN: use-after-free in pde_subdir_find+0x12d/0x150 fs/proc/generic.c:71
Read of size 8 at addr ffff8881f41fe5b0 by task syz-executor.0/2806
CPU: 0 PID: 2806 Comm: syz-executor.0 Not tainted 5.0.0-rc7+ #45
Hardware name: QEMU Standard PC (i440... | 0 | void atalk_proc_exit(void)
{
remove_proc_subtree("atalk", init_net.proc_net);
} | 311,578,655,433,473,980,000,000,000,000,000,000,000 | atalk_proc.c | 155,317,760,419,178,090,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2019-15292 | An issue was discovered in the Linux kernel before 5.0.9. There is a use-after-free in atalk_proc_exit, related to net/appletalk/atalk_proc.c, net/appletalk/ddp.c, and net/appletalk/sysctl_net_atalk.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-15292 |
208,988 | vim | ec66c41d84e574baf8009dbc0bd088d2bc5b2421 | https://github.com/vim/vim | https://github.com/vim/vim/commit/ec66c41d84e574baf8009dbc0bd088d2bc5b2421 | patch 8.1.2136: using freed memory with autocmd from fuzzer
Problem: using freed memory with autocmd from fuzzer. (Dhiraj Mishra,
Dominique Pelle)
Solution: Avoid using "wp" after autocommands. (closes #5041) | 1 | win_enter_ext(
win_T *wp,
int undo_sync,
int curwin_invalid,
int trigger_new_autocmds,
int trigger_enter_autocmds,
int trigger_leave_autocmds)
{
int other_buffer = FALSE;
if (wp == curwin && !curwin_invalid) /* nothing to do */
return;
#ifdef FEAT_JOB_CHANNEL
if (!curwin_inv... | 286,630,699,043,217,780,000,000,000,000,000,000,000 | window.c | 335,146,749,664,837,530,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2019-20079 | The autocmd feature in window.c in Vim before 8.1.2136 accesses freed memory. | https://nvd.nist.gov/vuln/detail/CVE-2019-20079 |
417,135 | vim | ec66c41d84e574baf8009dbc0bd088d2bc5b2421 | https://github.com/vim/vim | https://github.com/vim/vim/commit/ec66c41d84e574baf8009dbc0bd088d2bc5b2421 | patch 8.1.2136: using freed memory with autocmd from fuzzer
Problem: using freed memory with autocmd from fuzzer. (Dhiraj Mishra,
Dominique Pelle)
Solution: Avoid using "wp" after autocommands. (closes #5041) | 0 | win_enter_ext(
win_T *wp,
int undo_sync,
int curwin_invalid,
int trigger_new_autocmds,
int trigger_enter_autocmds,
int trigger_leave_autocmds)
{
int other_buffer = FALSE;
if (wp == curwin && !curwin_invalid) /* nothing to do */
return;
#ifdef FEAT_JOB_CHANNEL
if (!curwin_inv... | 273,457,862,967,840,630,000,000,000,000,000,000,000 | window.c | 160,003,465,030,923,530,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2019-20079 | The autocmd feature in window.c in Vim before 8.1.2136 accesses freed memory. | https://nvd.nist.gov/vuln/detail/CVE-2019-20079 |
209,001 | linux | 1995266727fa8143897e89b55f5d3c79aa828420 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1995266727fa8143897e89b55f5d3c79aa828420 | nfsd: auth: Fix gid sorting when rootsquash enabled
Commit bdcf0a423ea1 ("kernel: make groups_sort calling a responsibility
group_info allocators") appears to break nfsd rootsquash in a pretty
major way.
It adds a call to groups_sort() inside the loop that copies/squashes
gids, which means the valid gids are sorted a... | 1 | int nfsd_setuser(struct svc_rqst *rqstp, struct svc_export *exp)
{
struct group_info *rqgi;
struct group_info *gi;
struct cred *new;
int i;
int flags = nfsexp_flags(rqstp, exp);
validate_process_creds();
/* discard any old override before preparing the new set */
revert_creds(get_cred(current_real_cred()));
... | 43,833,698,754,086,860,000,000,000,000,000,000,000 | auth.c | 18,105,315,760,214,185,000,000,000,000,000,000,000 | [
"CWE-269"
] | CVE-2018-1000028 | Linux kernel version after commit bdcf0a423ea1 - 4.15-rc4+, 4.14.8+, 4.9.76+, 4.4.111+ contains a Incorrect Access Control vulnerability in NFS server (nfsd) that can result in remote users reading or writing files they should not be able to via NFS. This attack appear to be exploitable via NFS server must export a fil... | https://nvd.nist.gov/vuln/detail/CVE-2018-1000028 |
417,201 | linux | 1995266727fa8143897e89b55f5d3c79aa828420 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1995266727fa8143897e89b55f5d3c79aa828420 | nfsd: auth: Fix gid sorting when rootsquash enabled
Commit bdcf0a423ea1 ("kernel: make groups_sort calling a responsibility
group_info allocators") appears to break nfsd rootsquash in a pretty
major way.
It adds a call to groups_sort() inside the loop that copies/squashes
gids, which means the valid gids are sorted a... | 0 | int nfsd_setuser(struct svc_rqst *rqstp, struct svc_export *exp)
{
struct group_info *rqgi;
struct group_info *gi;
struct cred *new;
int i;
int flags = nfsexp_flags(rqstp, exp);
validate_process_creds();
/* discard any old override before preparing the new set */
revert_creds(get_cred(current_real_cred()));
... | 288,043,295,529,862,500,000,000,000,000,000,000,000 | auth.c | 286,732,712,378,841,100,000,000,000,000,000,000,000 | [
"CWE-269"
] | CVE-2018-1000028 | Linux kernel version after commit bdcf0a423ea1 - 4.15-rc4+, 4.14.8+, 4.9.76+, 4.4.111+ contains a Incorrect Access Control vulnerability in NFS server (nfsd) that can result in remote users reading or writing files they should not be able to via NFS. This attack appear to be exploitable via NFS server must export a fil... | https://nvd.nist.gov/vuln/detail/CVE-2018-1000028 |
209,002 | linux | f7a1337f0d29b98733c8824e165fca3371d7d4fd | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f7a1337f0d29b98733c8824e165fca3371d7d4fd | can: peak_usb: fix slab info leak
Fix a small slab info leak due to a failure to clear the command buffer
at allocation.
The first 16 bytes of the command buffer are always sent to the device
in pcan_usb_send_cmd() even though only the first two may have been
initialised in case no argument payload is provided (e.g. ... | 1 | static int peak_usb_create_dev(const struct peak_usb_adapter *peak_usb_adapter,
struct usb_interface *intf, int ctrl_idx)
{
struct usb_device *usb_dev = interface_to_usbdev(intf);
int sizeof_candev = peak_usb_adapter->sizeof_dev_private;
struct peak_usb_device *dev;
struct net_device *netdev;
int i, err;... | 261,949,449,194,331,020,000,000,000,000,000,000,000 | pcan_usb_core.c | 77,727,042,800,957,410,000,000,000,000,000,000,000 | [
"CWE-909"
] | CVE-2019-19534 | In the Linux kernel before 5.3.11, there is an info-leak bug that can be caused by a malicious USB device in the drivers/net/can/usb/peak_usb/pcan_usb_core.c driver, aka CID-f7a1337f0d29. | https://nvd.nist.gov/vuln/detail/CVE-2019-19534 |
417,204 | linux | f7a1337f0d29b98733c8824e165fca3371d7d4fd | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f7a1337f0d29b98733c8824e165fca3371d7d4fd | can: peak_usb: fix slab info leak
Fix a small slab info leak due to a failure to clear the command buffer
at allocation.
The first 16 bytes of the command buffer are always sent to the device
in pcan_usb_send_cmd() even though only the first two may have been
initialised in case no argument payload is provided (e.g. ... | 0 | static int peak_usb_create_dev(const struct peak_usb_adapter *peak_usb_adapter,
struct usb_interface *intf, int ctrl_idx)
{
struct usb_device *usb_dev = interface_to_usbdev(intf);
int sizeof_candev = peak_usb_adapter->sizeof_dev_private;
struct peak_usb_device *dev;
struct net_device *netdev;
int i, err;... | 115,836,313,028,330,770,000,000,000,000,000,000,000 | pcan_usb_core.c | 284,756,137,806,474,300,000,000,000,000,000,000,000 | [
"CWE-909"
] | CVE-2019-19534 | In the Linux kernel before 5.3.11, there is an info-leak bug that can be caused by a malicious USB device in the drivers/net/can/usb/peak_usb/pcan_usb_core.c driver, aka CID-f7a1337f0d29. | https://nvd.nist.gov/vuln/detail/CVE-2019-19534 |
209,005 | nbd | 4ed24fe0d64c7cc9963c57b52cad1555ad7c6b60 | https://github.com/yoe/nbd | https://github.com/yoe/nbd/commit/4ed24fe0d64c7cc9963c57b52cad1555ad7c6b60 | r134: CVE-2005-3534 | 1 | int mainloop(CLIENT *client) {
struct nbd_request request;
struct nbd_reply reply;
gboolean go_on=TRUE;
#ifdef DODBG
int i = 0;
#endif
negotiate(client);
DEBUG("Entering request loop!\n");
reply.magic = htonl(NBD_REPLY_MAGIC);
reply.error = 0;
while (go_on) {
char buf[BUFSIZE];
size_t len;
#ifdef DODBG
i... | 102,626,600,545,157,010,000,000,000,000,000,000,000 | nbd-server.c | 100,594,228,283,216,250,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-0530 | Buffer overflow in the mainloop function in nbd-server.c in the server in Network Block Device (nbd) before 2.9.20 might allow remote attackers to execute arbitrary code via a long request. NOTE: this issue exists because of a CVE-2005-3534 regression. | https://nvd.nist.gov/vuln/detail/CVE-2011-0530 |
417,260 | nbd | 4ed24fe0d64c7cc9963c57b52cad1555ad7c6b60 | https://github.com/yoe/nbd | https://github.com/yoe/nbd/commit/4ed24fe0d64c7cc9963c57b52cad1555ad7c6b60 | r134: CVE-2005-3534 | 0 | int mainloop(CLIENT *client) {
struct nbd_request request;
struct nbd_reply reply;
gboolean go_on=TRUE;
#ifdef DODBG
int i = 0;
#endif
negotiate(client);
DEBUG("Entering request loop!\n");
reply.magic = htonl(NBD_REPLY_MAGIC);
reply.error = 0;
while (go_on) {
char buf[BUFSIZE];
size_t len;
#ifdef DODBG
i... | 327,790,557,767,155,940,000,000,000,000,000,000,000 | nbd-server.c | 224,445,472,508,034,500,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-0530 | Buffer overflow in the mainloop function in nbd-server.c in the server in Network Block Device (nbd) before 2.9.20 might allow remote attackers to execute arbitrary code via a long request. NOTE: this issue exists because of a CVE-2005-3534 regression. | https://nvd.nist.gov/vuln/detail/CVE-2011-0530 |
209,011 | php-src | f3feddb5b45b5abd93abb1a95044b7e099d51c84 | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commit;h=f3feddb5b45b5abd93abb1a95044b7e099d51c84 | Partial fix for bug #72613 - do not treat negative returns from bz2 as size_t | 1 | static size_t php_bz2iop_read(php_stream *stream, char *buf, size_t count TSRMLS_DC)
{
struct php_bz2_stream_data_t *self = (struct php_bz2_stream_data_t *) stream->abstract;
size_t ret;
ret = BZ2_bzread(self->bz_file, buf, count);
if (ret == 0) {
stream->eof = 1;
}
return ret;
} | 251,183,821,630,888,830,000,000,000,000,000,000,000 | bz2.c | 184,323,623,567,454,800,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2016-5399 | The bzread function in ext/bz2/bz2.c in PHP before 5.5.38, 5.6.x before 5.6.24, and 7.x before 7.0.9 allows remote attackers to cause a denial of service (out-of-bounds write) or execute arbitrary code via a crafted bz2 archive. | https://nvd.nist.gov/vuln/detail/CVE-2016-5399 |
417,405 | php-src | f3feddb5b45b5abd93abb1a95044b7e099d51c84 | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commit;h=f3feddb5b45b5abd93abb1a95044b7e099d51c84 | Partial fix for bug #72613 - do not treat negative returns from bz2 as size_t | 0 | static size_t php_bz2iop_read(php_stream *stream, char *buf, size_t count TSRMLS_DC)
{
struct php_bz2_stream_data_t *self = (struct php_bz2_stream_data_t *) stream->abstract;
int bz2_ret;
bz2_ret = BZ2_bzread(self->bz_file, buf, count);
if (bz2_ret < 0) {
stream->eof = 1;
return -1;
}
if (bz2_ret == 0) {
... | 36,166,431,828,266,033,000,000,000,000,000,000,000 | bz2.c | 86,560,447,734,168,960,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2016-5399 | The bzread function in ext/bz2/bz2.c in PHP before 5.5.38, 5.6.x before 5.6.24, and 7.x before 7.0.9 allows remote attackers to cause a denial of service (out-of-bounds write) or execute arbitrary code via a crafted bz2 archive. | https://nvd.nist.gov/vuln/detail/CVE-2016-5399 |
209,029 | cifs-utils | 8acc963a2e7e9d63fe1f2e7f73f5a03f83d9c379 | https://github.com/piastry/cifs-utils | https://github.com/piastry/cifs-utils/commit/8acc963a2e7e9d63fe1f2e7f73f5a03f83d9c379 | mount.cifs: fix verbose messages on option parsing
When verbose logging is enabled, invalid credentials file lines may be
dumped to stderr. This may lead to information disclosure in particular
conditions when the credentials file given is sensitive and contains '='
signs.
Bug: https://bugzilla.samba.org/show_bug.cgi... | 1 | static int open_cred_file(char *file_name,
struct parsed_mount_info *parsed_info)
{
char *line_buf = NULL;
char *temp_val = NULL;
FILE *fs = NULL;
int i;
const int line_buf_size = 4096;
const int min_non_white = 10;
i = toggle_dac_capability(0, 1);
if (i)
goto return_i;
i = access(file_name, R_OK);
if ... | 61,641,370,677,193,840,000,000,000,000,000,000,000 | mount.cifs.c | 189,746,296,922,650,430,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2022-29869 | cifs-utils through 6.14, with verbose logging, can cause an information leak when a file contains = (equal sign) characters but is not a valid credentials file. | https://nvd.nist.gov/vuln/detail/CVE-2022-29869 |
417,495 | cifs-utils | 8acc963a2e7e9d63fe1f2e7f73f5a03f83d9c379 | https://github.com/piastry/cifs-utils | https://github.com/piastry/cifs-utils/commit/8acc963a2e7e9d63fe1f2e7f73f5a03f83d9c379 | mount.cifs: fix verbose messages on option parsing
When verbose logging is enabled, invalid credentials file lines may be
dumped to stderr. This may lead to information disclosure in particular
conditions when the credentials file given is sensitive and contains '='
signs.
Bug: https://bugzilla.samba.org/show_bug.cgi... | 0 | static int open_cred_file(char *file_name,
struct parsed_mount_info *parsed_info)
{
char *line_buf = NULL;
char *temp_val = NULL;
FILE *fs = NULL;
int i;
const int line_buf_size = 4096;
const int min_non_white = 10;
i = toggle_dac_capability(0, 1);
if (i)
goto return_i;
i = access(file_name, R_OK);
if ... | 227,523,526,943,730,600,000,000,000,000,000,000,000 | mount.cifs.c | 296,373,733,817,547,100,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2022-29869 | cifs-utils through 6.14, with verbose logging, can cause an information leak when a file contains = (equal sign) characters but is not a valid credentials file. | https://nvd.nist.gov/vuln/detail/CVE-2022-29869 |
209,046 | exiv2 | f6ee71526eef5649a529ac6da3f2843e3b63e227 | https://github.com/Exiv2/exiv2 | https://github.com/Exiv2/exiv2/commit/f6ee71526eef5649a529ac6da3f2843e3b63e227 | Add more bounds checks in Jp2Image::encodeJp2Header | 1 | void Jp2Image::encodeJp2Header(const DataBuf& boxBuf,DataBuf& outBuf)
{
DataBuf output(boxBuf.size_ + iccProfile_.size_ + 100); // allocate sufficient space
long outlen = sizeof(Jp2BoxHeader) ; // now many bytes have we written to output?
long inlen = sizeof(Jp2BoxHeader) ; // how ... | 103,579,399,336,757,700,000,000,000,000,000,000,000 | jp2image.cpp | 62,266,854,898,687,130,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2021-29470 | Exiv2 is a command-line utility and C++ library for reading, writing, deleting, and modifying the metadata of image files. An out-of-bounds read was found in Exiv2 versions v0.27.3 and earlier. The out-of-bounds read is triggered when Exiv2 is used to write metadata into a crafted image file. An attacker could potentia... | https://nvd.nist.gov/vuln/detail/CVE-2021-29470 |
417,952 | exiv2 | f6ee71526eef5649a529ac6da3f2843e3b63e227 | https://github.com/Exiv2/exiv2 | https://github.com/Exiv2/exiv2/commit/f6ee71526eef5649a529ac6da3f2843e3b63e227 | Add more bounds checks in Jp2Image::encodeJp2Header | 0 | void Jp2Image::encodeJp2Header(const DataBuf& boxBuf,DataBuf& outBuf)
{
DataBuf output(boxBuf.size_ + iccProfile_.size_ + 100); // allocate sufficient space
long outlen = sizeof(Jp2BoxHeader) ; // now many bytes have we written to output?
long inlen = sizeof(Jp2BoxHeader) ; // how ... | 104,478,261,149,791,850,000,000,000,000,000,000,000 | jp2image.cpp | 103,531,948,561,010,820,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2021-29470 | Exiv2 is a command-line utility and C++ library for reading, writing, deleting, and modifying the metadata of image files. An out-of-bounds read was found in Exiv2 versions v0.27.3 and earlier. The out-of-bounds read is triggered when Exiv2 is used to write metadata into a crafted image file. An attacker could potentia... | https://nvd.nist.gov/vuln/detail/CVE-2021-29470 |
209,056 | linux | 38ea1eac7d88072bbffb630e2b3db83ca649b826 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/38ea1eac7d88072bbffb630e2b3db83ca649b826 | usb: gadget: rndis: check size of RNDIS_MSG_SET command
Check the size of the RNDIS_MSG_SET command given to us before
attempting to respond to an invalid message size.
Reported-by: Szymon Heidrich <szymon.heidrich@gmail.com>
Cc: stable@kernel.org
Tested-by: Szymon Heidrich <szymon.heidrich@gmail.com>
Signed-off-by: ... | 1 | static int rndis_set_response(struct rndis_params *params,
rndis_set_msg_type *buf)
{
u32 BufLength, BufOffset;
rndis_set_cmplt_type *resp;
rndis_resp_t *r;
r = rndis_add_response(params, sizeof(rndis_set_cmplt_type));
if (!r)
return -ENOMEM;
resp = (rndis_set_cmplt_type *)r->buf;
BufLength = le32_t... | 234,426,455,993,270,700,000,000,000,000,000,000,000 | rndis.c | 84,424,031,421,829,370,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2022-25375 | An issue was discovered in drivers/usb/gadget/function/rndis.c in the Linux kernel before 5.16.10. The RNDIS USB gadget lacks validation of the size of the RNDIS_MSG_SET command. Attackers can obtain sensitive information from kernel memory. | https://nvd.nist.gov/vuln/detail/CVE-2022-25375 |
418,034 | linux | 38ea1eac7d88072bbffb630e2b3db83ca649b826 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/38ea1eac7d88072bbffb630e2b3db83ca649b826 | usb: gadget: rndis: check size of RNDIS_MSG_SET command
Check the size of the RNDIS_MSG_SET command given to us before
attempting to respond to an invalid message size.
Reported-by: Szymon Heidrich <szymon.heidrich@gmail.com>
Cc: stable@kernel.org
Tested-by: Szymon Heidrich <szymon.heidrich@gmail.com>
Signed-off-by: ... | 0 | static int rndis_set_response(struct rndis_params *params,
rndis_set_msg_type *buf)
{
u32 BufLength, BufOffset;
rndis_set_cmplt_type *resp;
rndis_resp_t *r;
BufLength = le32_to_cpu(buf->InformationBufferLength);
BufOffset = le32_to_cpu(buf->InformationBufferOffset);
if ((BufLength > RNDIS_MAX_TOTAL_SIZE... | 191,762,568,885,503,070,000,000,000,000,000,000,000 | rndis.c | 262,365,982,000,949,370,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2022-25375 | An issue was discovered in drivers/usb/gadget/function/rndis.c in the Linux kernel before 5.16.10. The RNDIS USB gadget lacks validation of the size of the RNDIS_MSG_SET command. Attackers can obtain sensitive information from kernel memory. | https://nvd.nist.gov/vuln/detail/CVE-2022-25375 |
209,057 | virglrenderer | 2abeb1802e3c005b17a7123e382171b3fb665971 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://gitlab.freedesktop.org/virgl/virglrenderer/commit/2abeb1802e3c005b17a7123e382171b3fb665971 | vrend: check that the transfer iov holds enough data for the data upload
Closes #140
Signed-off-by: Gert Wollny <gert.wollny@collabora.com>
Reviewed-by: Emil Velikov <emil.velikov@collabora.com> | 1 | static int vrend_renderer_transfer_write_iov(struct vrend_context *ctx,
struct vrend_resource *res,
struct iovec *iov, int num_iovs,
const struct vrend_transfer_info *info)
{
void *d... | 152,948,160,626,741,240,000,000,000,000,000,000,000 | vrend_renderer.c | 197,778,375,936,263,900,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-18391 | A heap-based buffer overflow in the vrend_renderer_transfer_write_iov function in vrend_renderer.c in virglrenderer through 0.8.0 allows guest OS users to cause a denial of service via VIRGL_CCMD_RESOURCE_INLINE_WRITE commands. | https://nvd.nist.gov/vuln/detail/CVE-2019-18391 |
418,048 | virglrenderer | 2abeb1802e3c005b17a7123e382171b3fb665971 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://gitlab.freedesktop.org/virgl/virglrenderer/commit/2abeb1802e3c005b17a7123e382171b3fb665971 | vrend: check that the transfer iov holds enough data for the data upload
Closes #140
Signed-off-by: Gert Wollny <gert.wollny@collabora.com>
Reviewed-by: Emil Velikov <emil.velikov@collabora.com> | 0 | static int vrend_renderer_transfer_write_iov(struct vrend_context *ctx,
struct vrend_resource *res,
struct iovec *iov, int num_iovs,
const struct vrend_transfer_info *info)
{
void *d... | 112,678,018,167,899,580,000,000,000,000,000,000,000 | vrend_renderer.c | 189,997,653,270,965,570,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-18391 | A heap-based buffer overflow in the vrend_renderer_transfer_write_iov function in vrend_renderer.c in virglrenderer through 0.8.0 allows guest OS users to cause a denial of service via VIRGL_CCMD_RESOURCE_INLINE_WRITE commands. | https://nvd.nist.gov/vuln/detail/CVE-2019-18391 |
209,067 | linux | 74b6b20df8cfe90ada777d621b54c32e69e27cd7 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=74b6b20df8cfe90ada777d621b54c32e69e27cd7 | staging: rtl8188eu: prevent ->ssid overflow in rtw_wx_set_scan()
This code has a check to prevent read overflow but it needs another
check to prevent writing beyond the end of the ->ssid[] array.
Fixes: a2c60d42d97c ("staging: r8188eu: Add files for new driver - part 16")
Signed-off-by: Dan Carpenter <dan.carpenter@o... | 1 | static int rtw_wx_set_scan(struct net_device *dev, struct iw_request_info *a,
union iwreq_data *wrqu, char *extra)
{
u8 _status = false;
int ret = 0;
struct adapter *padapter = rtw_netdev_priv(dev);
struct mlme_priv *pmlmepriv = &padapter->mlmepriv;
struct ndis_802_11_ssid ssid[RTW_SSID_SCAN_AMOUNT];
RT_TR... | 161,203,885,611,652,430,000,000,000,000,000,000,000 | ioctl_linux.c | 256,207,584,266,685,360,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-28660 | rtw_wx_set_scan in drivers/staging/rtl8188eu/os_dep/ioctl_linux.c in the Linux kernel through 5.11.6 allows writing beyond the end of the ->ssid[] array. NOTE: from the perspective of kernel.org releases, CVE IDs are not normally used for drivers/staging/* (unfinished work); however, system integrators may have situati... | https://nvd.nist.gov/vuln/detail/CVE-2021-28660 |
418,277 | linux | 74b6b20df8cfe90ada777d621b54c32e69e27cd7 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=74b6b20df8cfe90ada777d621b54c32e69e27cd7 | staging: rtl8188eu: prevent ->ssid overflow in rtw_wx_set_scan()
This code has a check to prevent read overflow but it needs another
check to prevent writing beyond the end of the ->ssid[] array.
Fixes: a2c60d42d97c ("staging: r8188eu: Add files for new driver - part 16")
Signed-off-by: Dan Carpenter <dan.carpenter@o... | 0 | static int rtw_wx_set_scan(struct net_device *dev, struct iw_request_info *a,
union iwreq_data *wrqu, char *extra)
{
u8 _status = false;
int ret = 0;
struct adapter *padapter = rtw_netdev_priv(dev);
struct mlme_priv *pmlmepriv = &padapter->mlmepriv;
struct ndis_802_11_ssid ssid[RTW_SSID_SCAN_AMOUNT];
RT_TR... | 10,876,643,125,206,687,000,000,000,000,000,000,000 | ioctl_linux.c | 69,061,706,621,327,810,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-28660 | rtw_wx_set_scan in drivers/staging/rtl8188eu/os_dep/ioctl_linux.c in the Linux kernel through 5.11.6 allows writing beyond the end of the ->ssid[] array. NOTE: from the perspective of kernel.org releases, CVE IDs are not normally used for drivers/staging/* (unfinished work); however, system integrators may have situati... | https://nvd.nist.gov/vuln/detail/CVE-2021-28660 |
209,073 | zziplib | feae4da1a5c92100c44ebfcbaaa895959cc0829b | https://github.com/gdraheim/zziplib | https://github.com/gdraheim/zziplib/commit/feae4da1a5c92100c44ebfcbaaa895959cc0829b | fix for zz_rootsize #41 | 1 | __zzip_parse_root_directory(int fd,
struct _disk_trailer *trailer,
struct zzip_dir_hdr **hdr_return,
zzip_plugin_io_t io)
{
auto struct zzip_disk_entry dirent;
struct zzip_dir_hdr *hdr;
struct zzip_dir_hdr *hdr0;
uint16_... | 182,580,721,112,496,400,000,000,000,000,000,000,000 | zip.c | 50,124,965,290,700,410,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2018-7726 | An issue was discovered in ZZIPlib 0.13.68. There is a bus error caused by the __zzip_parse_root_directory function of zip.c. Attackers could leverage this vulnerability to cause a denial of service via a crafted zip file. | https://nvd.nist.gov/vuln/detail/CVE-2018-7726 |
418,345 | zziplib | feae4da1a5c92100c44ebfcbaaa895959cc0829b | https://github.com/gdraheim/zziplib | https://github.com/gdraheim/zziplib/commit/feae4da1a5c92100c44ebfcbaaa895959cc0829b | fix for zz_rootsize #41 | 0 | __zzip_parse_root_directory(int fd,
struct _disk_trailer *trailer,
struct zzip_dir_hdr **hdr_return,
zzip_plugin_io_t io)
{
auto struct zzip_disk_entry dirent;
struct zzip_dir_hdr *hdr;
struct zzip_dir_hdr *hdr0;
uint16_... | 64,166,024,616,562,400,000,000,000,000,000,000,000 | zip.c | 159,541,872,777,670,890,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2018-7726 | An issue was discovered in ZZIPlib 0.13.68. There is a bus error caused by the __zzip_parse_root_directory function of zip.c. Attackers could leverage this vulnerability to cause a denial of service via a crafted zip file. | https://nvd.nist.gov/vuln/detail/CVE-2018-7726 |
209,078 | ImageMagick6 | db7a4be592328af06d776ce3bab24b8c6de5be20 | https://github.com/ImageMagick/ImageMagick6 | https://github.com/ImageMagick/ImageMagick6/commit/db7a4be592328af06d776ce3bab24b8c6de5be20 | https://github.com/ImageMagick/ImageMagick/issues/1221 | 1 | static Image *ReadMATImageV4(const ImageInfo *image_info,Image *image,
ExceptionInfo *exception)
{
typedef struct {
unsigned char Type[4];
unsigned int nRows;
unsigned int nCols;
unsigned int imagf;
unsigned int nameLen;
} MAT4_HDR;
long
ldblk;
EndianType
endian;
Image
*ro... | 26,469,455,516,059,184,000,000,000,000,000,000,000 | mat.c | 305,348,647,646,658,240,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2018-14551 | The ReadMATImageV4 function in coders/mat.c in ImageMagick 7.0.8-7 uses an uninitialized variable, leading to memory corruption. | https://nvd.nist.gov/vuln/detail/CVE-2018-14551 |
418,629 | ImageMagick6 | db7a4be592328af06d776ce3bab24b8c6de5be20 | https://github.com/ImageMagick/ImageMagick6 | https://github.com/ImageMagick/ImageMagick6/commit/db7a4be592328af06d776ce3bab24b8c6de5be20 | https://github.com/ImageMagick/ImageMagick/issues/1221 | 0 | static Image *ReadMATImageV4(const ImageInfo *image_info,Image *image,
ExceptionInfo *exception)
{
typedef struct {
unsigned char Type[4];
unsigned int nRows;
unsigned int nCols;
unsigned int imagf;
unsigned int nameLen;
} MAT4_HDR;
long
ldblk;
EndianType
endian;
Image
*ro... | 335,172,287,090,735,580,000,000,000,000,000,000,000 | mat.c | 196,259,138,446,610,300,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2018-14551 | The ReadMATImageV4 function in coders/mat.c in ImageMagick 7.0.8-7 uses an uninitialized variable, leading to memory corruption. | https://nvd.nist.gov/vuln/detail/CVE-2018-14551 |
209,082 | linux | 594cc251fdd0d231d342d88b2fdff4bc42fb0690 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=594cc251fdd0d231d342d88b2fdff4bc42fb0690 | make 'user_access_begin()' do 'access_ok()'
Originally, the rule used to be that you'd have to do access_ok()
separately, and then user_access_begin() before actually doing the
direct (optimized) user access.
But experience has shown that people then decide not to do access_ok()
at all, and instead rely on it being i... | 1 | i915_gem_execbuffer2_ioctl(struct drm_device *dev, void *data,
struct drm_file *file)
{
struct drm_i915_gem_execbuffer2 *args = data;
struct drm_i915_gem_exec_object2 *exec2_list;
struct drm_syncobj **fences = NULL;
const size_t count = args->buffer_count;
int err;
if (!check_buffer_count(count)) {
DRM_D... | 309,346,508,376,038,930,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2018-20669 | An issue where a provided address with access_ok() is not checked was discovered in i915_gem_execbuffer2_ioctl in drivers/gpu/drm/i915/i915_gem_execbuffer.c in the Linux kernel through 4.19.13. A local attacker can craft a malicious IOCTL function call to overwrite arbitrary kernel memory, resulting in a Denial of Serv... | https://nvd.nist.gov/vuln/detail/CVE-2018-20669 |
418,663 | linux | 594cc251fdd0d231d342d88b2fdff4bc42fb0690 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=594cc251fdd0d231d342d88b2fdff4bc42fb0690 | make 'user_access_begin()' do 'access_ok()'
Originally, the rule used to be that you'd have to do access_ok()
separately, and then user_access_begin() before actually doing the
direct (optimized) user access.
But experience has shown that people then decide not to do access_ok()
at all, and instead rely on it being i... | 0 | i915_gem_execbuffer2_ioctl(struct drm_device *dev, void *data,
struct drm_file *file)
{
struct drm_i915_gem_execbuffer2 *args = data;
struct drm_i915_gem_exec_object2 *exec2_list;
struct drm_syncobj **fences = NULL;
const size_t count = args->buffer_count;
int err;
if (!check_buffer_count(count)) {
DRM_D... | 53,610,882,686,569,340,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2018-20669 | An issue where a provided address with access_ok() is not checked was discovered in i915_gem_execbuffer2_ioctl in drivers/gpu/drm/i915/i915_gem_execbuffer.c in the Linux kernel through 4.19.13. A local attacker can craft a malicious IOCTL function call to overwrite arbitrary kernel memory, resulting in a Denial of Serv... | https://nvd.nist.gov/vuln/detail/CVE-2018-20669 |
209,105 | wireshark | d5f2657825e63e4126ebd7d13a59f3c6e8a9e4e1 | https://github.com/wireshark/wireshark | https://gitlab.com/wireshark/wireshark/-/commit/d5f2657825e63e4126ebd7d13a59f3c6e8a9e4e1 | epan: Limit our bits in decode_bits_in_field.
Limit the number of bits we process in decode_bits_in_field, otherwise
we'll overrun our buffer. Fixes #16958. | 1 | decode_bits_in_field(const guint bit_offset, const gint no_of_bits, const guint64 value)
{
guint64 mask = 0,tmp;
char *str;
int bit, str_p = 0;
int i;
mask = 1;
mask = mask << (no_of_bits-1);
/* Prepare the string, 256 pos for the bits and zero termination, + 64 for the spaces */
str=(char *)wmem_alloc0(wmem_... | 245,561,053,932,860,300,000,000,000,000,000,000,000 | to_str.c | 278,849,271,809,168,700,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2020-26421 | Crash in USB HID protocol dissector and possibly other dissectors in Wireshark 3.4.0 and 3.2.0 to 3.2.8 allows denial of service via packet injection or crafted capture file. | https://nvd.nist.gov/vuln/detail/CVE-2020-26421 |
418,967 | wireshark | d5f2657825e63e4126ebd7d13a59f3c6e8a9e4e1 | https://github.com/wireshark/wireshark | https://gitlab.com/wireshark/wireshark/-/commit/d5f2657825e63e4126ebd7d13a59f3c6e8a9e4e1 | epan: Limit our bits in decode_bits_in_field.
Limit the number of bits we process in decode_bits_in_field, otherwise
we'll overrun our buffer. Fixes #16958. | 0 | decode_bits_in_field(const guint bit_offset, const gint no_of_bits, const guint64 value)
{
guint64 mask;
char *str;
int bit, str_p = 0;
int i;
int max_bits = MIN(64, no_of_bits);
mask = G_GUINT64_CONSTANT(1) << (max_bits-1);
/* Prepare the string, 256 pos for the bits and zero termination, + 64 for the spaces ... | 95,786,002,323,150,460,000,000,000,000,000,000,000 | to_str.c | 121,518,338,197,249,020,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2020-26421 | Crash in USB HID protocol dissector and possibly other dissectors in Wireshark 3.4.0 and 3.2.0 to 3.2.8 allows denial of service via packet injection or crafted capture file. | https://nvd.nist.gov/vuln/detail/CVE-2020-26421 |
209,107 | libexif | 41bd04234b104312f54d25822f68738ba8d7133d | https://github.com/libexif/libexif | https://github.com/libexif/libexif/commit/41bd04234b104312f54d25822f68738ba8d7133d | fixes some (not all) buffer overreads during decoding pentax makernote entries.
This should fix:
https://sourceforge.net/p/libexif/bugs/125/ CVE-2016-6328 | 1 | mnote_pentax_entry_get_value (MnotePentaxEntry *entry,
char *val, unsigned int maxlen)
{
ExifLong vl;
ExifShort vs, vs2;
int i = 0, j = 0;
if (!entry) return (NULL);
memset (val, 0, maxlen);
maxlen--;
switch (entry->tag) {
case MNOTE_PENTAX_TAG_MODE:
case MNOTE_PENTAX_TAG_QUALITY:
case MNOTE... | 290,584,399,214,517,430,000,000,000,000,000,000,000 | mnote-pentax-entry.c | 187,105,534,432,722,000,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2016-6328 | A vulnerability was found in libexif. An integer overflow when parsing the MNOTE entry data of the input file. This can cause Denial-of-Service (DoS) and Information Disclosure (disclosing some critical heap chunk metadata, even other applications' private data). | https://nvd.nist.gov/vuln/detail/CVE-2016-6328 |
419,161 | libexif | 41bd04234b104312f54d25822f68738ba8d7133d | https://github.com/libexif/libexif | https://github.com/libexif/libexif/commit/41bd04234b104312f54d25822f68738ba8d7133d | fixes some (not all) buffer overreads during decoding pentax makernote entries.
This should fix:
https://sourceforge.net/p/libexif/bugs/125/ CVE-2016-6328 | 0 | mnote_pentax_entry_get_value (MnotePentaxEntry *entry,
char *val, unsigned int maxlen)
{
ExifLong vl;
ExifShort vs, vs2;
int i = 0, j = 0;
if (!entry) return (NULL);
memset (val, 0, maxlen);
maxlen--;
switch (entry->tag) {
case MNOTE_PENTAX_TAG_MODE:
case MNOTE_PENTAX_TAG_QUALITY:
case MNOTE... | 92,767,828,810,126,990,000,000,000,000,000,000,000 | mnote-pentax-entry.c | 278,952,903,220,615,550,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2016-6328 | A vulnerability was found in libexif. An integer overflow when parsing the MNOTE entry data of the input file. This can cause Denial-of-Service (DoS) and Information Disclosure (disclosing some critical heap chunk metadata, even other applications' private data). | https://nvd.nist.gov/vuln/detail/CVE-2016-6328 |
209,109 | linux | 2289adbfa559050d2a38bcd9caac1c18b800e928 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2289adbfa559050d2a38bcd9caac1c18b800e928 | media: usb: fix memory leak in af9005_identify_state
In af9005_identify_state when returning -EIO the allocated buffer should
be released. Replace the "return -EIO" with assignment into ret and move
deb_info() under a check.
Fixes: af4e067e1dcf ("V4L/DVB (5625): Add support for the AF9005 demodulator from Afatech")
S... | 1 | static int af9005_identify_state(struct usb_device *udev,
struct dvb_usb_device_properties *props,
struct dvb_usb_device_description **desc,
int *cold)
{
int ret;
u8 reply, *buf;
buf = kmalloc(FW_BULKOUT_SIZE + 2, GFP_KERNEL);
if (!buf)
return -ENOMEM;
ret = af9005_boot_packet(udev, FW_CONFIG, &... | 205,089,542,493,798,900,000,000,000,000,000,000,000 | af9005.c | 284,619,583,110,725,830,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2019-18809 | A memory leak in the af9005_identify_state() function in drivers/media/usb/dvb-usb/af9005.c in the Linux kernel through 5.3.9 allows attackers to cause a denial of service (memory consumption), aka CID-2289adbfa559. | https://nvd.nist.gov/vuln/detail/CVE-2019-18809 |
419,176 | linux | 2289adbfa559050d2a38bcd9caac1c18b800e928 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2289adbfa559050d2a38bcd9caac1c18b800e928 | media: usb: fix memory leak in af9005_identify_state
In af9005_identify_state when returning -EIO the allocated buffer should
be released. Replace the "return -EIO" with assignment into ret and move
deb_info() under a check.
Fixes: af4e067e1dcf ("V4L/DVB (5625): Add support for the AF9005 demodulator from Afatech")
S... | 0 | static int af9005_identify_state(struct usb_device *udev,
struct dvb_usb_device_properties *props,
struct dvb_usb_device_description **desc,
int *cold)
{
int ret;
u8 reply, *buf;
buf = kmalloc(FW_BULKOUT_SIZE + 2, GFP_KERNEL);
if (!buf)
return -ENOMEM;
ret = af9005_boot_packet(udev, FW_CONFIG, &... | 140,118,043,948,730,980,000,000,000,000,000,000,000 | af9005.c | 323,326,355,635,063,250,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2019-18809 | A memory leak in the af9005_identify_state() function in drivers/media/usb/dvb-usb/af9005.c in the Linux kernel through 5.3.9 allows attackers to cause a denial of service (memory consumption), aka CID-2289adbfa559. | https://nvd.nist.gov/vuln/detail/CVE-2019-18809 |
209,114 | bwa | 20d0a13092aa4cb73230492b05f9697d5ef0b88e | https://github.com/lh3/bwa | https://github.com/lh3/bwa/commit/20d0a13092aa4cb73230492b05f9697d5ef0b88e | r1198: exit if .alt is malformatted
Resolves #232 | 1 | bntseq_t *bns_restore(const char *prefix)
{
char ann_filename[1024], amb_filename[1024], pac_filename[1024], alt_filename[1024];
FILE *fp;
bntseq_t *bns;
strcat(strcpy(ann_filename, prefix), ".ann");
strcat(strcpy(amb_filename, prefix), ".amb");
strcat(strcpy(pac_filename, prefix), ".pac");
bns = bns_restore_c... | 148,051,323,671,477,580,000,000,000,000,000,000,000 | bntseq.c | 288,704,822,555,812,670,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-10269 | BWA (aka Burrow-Wheeler Aligner) before 2019-01-23 has a stack-based buffer overflow in the bns_restore function in bntseq.c via a long sequence name in a .alt file. | https://nvd.nist.gov/vuln/detail/CVE-2019-10269 |
419,228 | bwa | 20d0a13092aa4cb73230492b05f9697d5ef0b88e | https://github.com/lh3/bwa | https://github.com/lh3/bwa/commit/20d0a13092aa4cb73230492b05f9697d5ef0b88e | r1198: exit if .alt is malformatted
Resolves #232 | 0 | bntseq_t *bns_restore(const char *prefix)
{
char ann_filename[1024], amb_filename[1024], pac_filename[1024], alt_filename[1024];
FILE *fp;
bntseq_t *bns;
strcat(strcpy(ann_filename, prefix), ".ann");
strcat(strcpy(amb_filename, prefix), ".amb");
strcat(strcpy(pac_filename, prefix), ".pac");
bns = bns_restore_c... | 68,751,236,436,384,670,000,000,000,000,000,000,000 | bntseq.c | 52,323,830,341,887,980,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-10269 | BWA (aka Burrow-Wheeler Aligner) before 2019-01-23 has a stack-based buffer overflow in the bns_restore function in bntseq.c via a long sequence name in a .alt file. | https://nvd.nist.gov/vuln/detail/CVE-2019-10269 |
209,783 | gnutls | 8dc2822966f64dd9cf7dde9c7aacd80d49d3ffe5 | http://git.savannah.gnu.org/cgit/gnutls | https://gitorious.org/gnutls/gnutls/commit/8dc2822966f64dd9cf7dde9c7aacd80d49d3ffe5 | Fixes to avoid a timing attack in TLS CBC record parsing. | 1 | ciphertext_to_compressed (gnutls_session_t session,
gnutls_datum_t *ciphertext,
uint8_t * compress_data,
int compress_size,
uint8_t type, record_parameters_st * params,
uint64* sequence)
{... | 238,969,898,875,956,350,000,000,000,000,000,000,000 | gnutls_cipher.c | 69,907,825,033,302,790,000,000,000,000,000,000,000 | [
"CWE-310"
] | CVE-2013-0169 | The TLS protocol 1.1 and 1.2 and the DTLS protocol 1.0 and 1.2, as used in OpenSSL, OpenJDK, PolarSSL, and other products, do not properly consider timing side-channel attacks on a MAC check requirement during the processing of malformed CBC padding, which allows remote attackers to conduct distinguishing attacks and p... | https://nvd.nist.gov/vuln/detail/CVE-2013-0169 |
420,857 | gnutls | 8dc2822966f64dd9cf7dde9c7aacd80d49d3ffe5 | http://git.savannah.gnu.org/cgit/gnutls | https://gitorious.org/gnutls/gnutls/commit/8dc2822966f64dd9cf7dde9c7aacd80d49d3ffe5 | Fixes to avoid a timing attack in TLS CBC record parsing. | 0 | ciphertext_to_compressed (gnutls_session_t session,
gnutls_datum_t *ciphertext,
uint8_t * compress_data,
int compress_size,
uint8_t type, record_parameters_st * params,
uint64* sequence)
{... | 253,461,172,301,794,200,000,000,000,000,000,000,000 | gnutls_cipher.c | 142,113,439,814,033,700,000,000,000,000,000,000,000 | [
"CWE-310"
] | CVE-2013-0169 | The TLS protocol 1.1 and 1.2 and the DTLS protocol 1.0 and 1.2, as used in OpenSSL, OpenJDK, PolarSSL, and other products, do not properly consider timing side-channel attacks on a MAC check requirement during the processing of malformed CBC padding, which allows remote attackers to conduct distinguishing attacks and p... | https://nvd.nist.gov/vuln/detail/CVE-2013-0169 |
209,796 | shellinabox | 4f0ecc31ac6f985e0dd3f5a52cbfc0e9251f6361 | https://github.com/shellinabox/shellinabox | https://github.com/shellinabox/shellinabox/commit/4f0ecc31ac6f985e0dd3f5a52cbfc0e9251f6361 | Rolling code for version 2.21 | 1 | static void urlParsePostBody(struct URL *url,
const struct HttpConnection *http,
const char *buf, int len) {
struct HashMap contentType;
initHashMap(&contentType, urlDestroyHashMapEntry, NULL);
const char *ctHeader = getFromHashMap(&http->header, "cont... | 237,313,227,740,907,430,000,000,000,000,000,000,000 | url.c | 140,188,663,664,959,850,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2018-16789 | libhttp/url.c in shellinabox through 2.20 has an implementation flaw in the HTTP request parsing logic. By sending a crafted multipart/form-data HTTP request, an attacker could exploit this to force shellinaboxd into an infinite loop, exhausting available CPU resources and taking the service down. | https://nvd.nist.gov/vuln/detail/CVE-2018-16789 |
421,325 | shellinabox | 4f0ecc31ac6f985e0dd3f5a52cbfc0e9251f6361 | https://github.com/shellinabox/shellinabox | https://github.com/shellinabox/shellinabox/commit/4f0ecc31ac6f985e0dd3f5a52cbfc0e9251f6361 | Rolling code for version 2.21 | 0 | static void urlParsePostBody(struct URL *url,
const struct HttpConnection *http,
const char *buf, int len) {
struct HashMap contentType;
initHashMap(&contentType, urlDestroyHashMapEntry, NULL);
const char *ctHeader = getFromHashMap(&http->header, "cont... | 172,875,453,536,682,400,000,000,000,000,000,000,000 | url.c | 335,566,370,279,181,100,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2018-16789 | libhttp/url.c in shellinabox through 2.20 has an implementation flaw in the HTTP request parsing logic. By sending a crafted multipart/form-data HTTP request, an attacker could exploit this to force shellinaboxd into an infinite loop, exhausting available CPU resources and taking the service down. | https://nvd.nist.gov/vuln/detail/CVE-2018-16789 |
209,797 | libsass | b3374e3fd1a0c3658644d2bad24e4a0ff2e0dcea | https://github.com/sass/libsass | https://github.com/sass/libsass/commit/b3374e3fd1a0c3658644d2bad24e4a0ff2e0dcea | Fix handling of unclosed interpolant in url
Fixes #2661 | 1 | String_Obj Parser::parse_url_function_argument()
{
const char* p = position;
std::string uri("");
if (lex< real_uri_value >(false)) {
uri = lexed.to_string();
}
if (peek< exactly< hash_lbrace > >()) {
const char* pp = position;
// TODO: error checking for unclosed interpolant... | 315,117,395,642,322,300,000,000,000,000,000,000,000 | parser.cpp | 105,861,640,874,557,320,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2018-11693 | An issue was discovered in LibSass through 3.5.4. An out-of-bounds read of a memory region was found in the function Sass::Prelexer::skip_over_scopes which could be leveraged by an attacker to disclose information or manipulated to read from unmapped memory causing a denial of service. | https://nvd.nist.gov/vuln/detail/CVE-2018-11693 |
421,342 | libsass | b3374e3fd1a0c3658644d2bad24e4a0ff2e0dcea | https://github.com/sass/libsass | https://github.com/sass/libsass/commit/b3374e3fd1a0c3658644d2bad24e4a0ff2e0dcea | Fix handling of unclosed interpolant in url
Fixes #2661 | 0 | String_Obj Parser::parse_url_function_argument()
{
const char* p = position;
std::string uri("");
if (lex< real_uri_value >(false)) {
uri = lexed.to_string();
}
if (peek< exactly< hash_lbrace > >()) {
const char* pp = position;
// TODO: error checking for unclosed interpolant... | 304,360,674,160,713,800,000,000,000,000,000,000,000 | parser.cpp | 71,723,495,127,015,685,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2018-11693 | An issue was discovered in LibSass through 3.5.4. An out-of-bounds read of a memory region was found in the function Sass::Prelexer::skip_over_scopes which could be leveraged by an attacker to disclose information or manipulated to read from unmapped memory causing a denial of service. | https://nvd.nist.gov/vuln/detail/CVE-2018-11693 |
209,806 | vim | 60ae0e71490c97f2871a6344aca61cacf220f813 | https://github.com/vim/vim | https://github.com/vim/vim/commit/60ae0e71490c97f2871a6344aca61cacf220f813 | patch 8.2.4968: reading past end of the line when C-indenting
Problem: Reading past end of the line when C-indenting.
Solution: Check for NUL. | 1 | skip_string(char_u *p)
{
int i;
// We loop, because strings may be concatenated: "date""time".
for ( ; ; ++p)
{
if (p[0] == '\'') // 'c' or '\n' or '\000'
{
if (p[1] == NUL) // ' at end of line
break;
i = 2;
if (p[1] == '\\' && p[2] != NUL) // '\n' or '\000'
{
... | 116,999,295,327,318,900,000,000,000,000,000,000,000 | cindent.c | 220,702,061,262,218,500,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2022-1733 | Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.4968. | https://nvd.nist.gov/vuln/detail/CVE-2022-1733 |
421,488 | vim | 60ae0e71490c97f2871a6344aca61cacf220f813 | https://github.com/vim/vim | https://github.com/vim/vim/commit/60ae0e71490c97f2871a6344aca61cacf220f813 | patch 8.2.4968: reading past end of the line when C-indenting
Problem: Reading past end of the line when C-indenting.
Solution: Check for NUL. | 0 | skip_string(char_u *p)
{
int i;
// We loop, because strings may be concatenated: "date""time".
for ( ; ; ++p)
{
if (p[0] == '\'') // 'c' or '\n' or '\000'
{
if (p[1] == NUL) // ' at end of line
break;
i = 2;
if (p[1] == '\\' && p[2] != NUL) // '\n' or '\000'
{
... | 84,832,776,430,659,780,000,000,000,000,000,000,000 | cindent.c | 66,776,079,859,696,120,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2022-1733 | Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.4968. | https://nvd.nist.gov/vuln/detail/CVE-2022-1733 |
209,808 | linux | db8fd2cde93227e566a412cf53173ffa227998bc | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/db8fd2cde93227e566a412cf53173ffa227998bc | mwifiex: pcie: Fix memory leak in mwifiex_pcie_alloc_cmdrsp_buf
In mwifiex_pcie_alloc_cmdrsp_buf, a new skb is allocated which should be
released if mwifiex_map_pci_memory() fails. The release is added.
Fixes: fc3314609047 ("mwifiex: use pci_alloc/free_consistent APIs for PCIe")
Signed-off-by: Navid Emamdoost <navid.... | 1 | static int mwifiex_pcie_alloc_cmdrsp_buf(struct mwifiex_adapter *adapter)
{
struct pcie_service_card *card = adapter->card;
struct sk_buff *skb;
/* Allocate memory for receiving command response data */
skb = dev_alloc_skb(MWIFIEX_UPLD_SIZE);
if (!skb) {
mwifiex_dbg(adapter, ERROR,
"Unable to allocate sk... | 300,647,899,971,657,980,000,000,000,000,000,000,000 | None | null | [
"CWE-401"
] | CVE-2019-19056 | A memory leak in the mwifiex_pcie_alloc_cmdrsp_buf() function in drivers/net/wireless/marvell/mwifiex/pcie.c in the Linux kernel through 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering mwifiex_map_pci_memory() failures, aka CID-db8fd2cde932. | https://nvd.nist.gov/vuln/detail/CVE-2019-19056 |
421,632 | linux | db8fd2cde93227e566a412cf53173ffa227998bc | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/db8fd2cde93227e566a412cf53173ffa227998bc | mwifiex: pcie: Fix memory leak in mwifiex_pcie_alloc_cmdrsp_buf
In mwifiex_pcie_alloc_cmdrsp_buf, a new skb is allocated which should be
released if mwifiex_map_pci_memory() fails. The release is added.
Fixes: fc3314609047 ("mwifiex: use pci_alloc/free_consistent APIs for PCIe")
Signed-off-by: Navid Emamdoost <navid.... | 0 | static int mwifiex_pcie_alloc_cmdrsp_buf(struct mwifiex_adapter *adapter)
{
struct pcie_service_card *card = adapter->card;
struct sk_buff *skb;
/* Allocate memory for receiving command response data */
skb = dev_alloc_skb(MWIFIEX_UPLD_SIZE);
if (!skb) {
mwifiex_dbg(adapter, ERROR,
"Unable to allocate sk... | 14,277,820,730,969,820,000,000,000,000,000,000,000 | pcie.c | 151,248,231,780,596,260,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2019-19056 | A memory leak in the mwifiex_pcie_alloc_cmdrsp_buf() function in drivers/net/wireless/marvell/mwifiex/pcie.c in the Linux kernel through 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering mwifiex_map_pci_memory() failures, aka CID-db8fd2cde932. | https://nvd.nist.gov/vuln/detail/CVE-2019-19056 |
209,814 | gegl | c83b05d565a1e3392c9606a4ecaa560eb9a4ee29 | http://git.gnome.org/browse/gegl | https://git.gnome.org/browse/gegl/commit/?id=c83b05d565a1e3392c9606a4ecaa560eb9a4ee29 | ppm-load: limit max permitted buffer allocation to 2GB
Fixing bug #795248 | 1 | ppm_load_read_header(FILE *fp,
pnm_struct *img)
{
/* PPM Headers Variable Declaration */
gchar *ptr;
//gchar *retval;
gchar header[MAX_CHARS_IN_ROW];
gint maxval;
int channel_count;
/* Check the PPM file Type P3 or P6 */
if (fgets (header, MAX_CHARS_IN_R... | 20,259,545,839,696,437,000,000,000,000,000,000,000 | ppm-load.c | 90,182,842,211,605,510,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2018-10114 | An issue was discovered in GEGL through 0.3.32. The gegl_buffer_iterate_read_simple function in buffer/gegl-buffer-access.c allows remote attackers to cause a denial of service (write access violation) or possibly have unspecified other impact via a malformed PPM file, related to improper restrictions on memory allocat... | https://nvd.nist.gov/vuln/detail/CVE-2018-10114 |
421,835 | gegl | c83b05d565a1e3392c9606a4ecaa560eb9a4ee29 | http://git.gnome.org/browse/gegl | https://git.gnome.org/browse/gegl/commit/?id=c83b05d565a1e3392c9606a4ecaa560eb9a4ee29 | ppm-load: limit max permitted buffer allocation to 2GB
Fixing bug #795248 | 0 | ppm_load_read_header(FILE *fp,
pnm_struct *img)
{
/* PPM Headers Variable Declaration */
gchar *ptr;
//gchar *retval;
gchar header[MAX_CHARS_IN_ROW];
gint maxval;
int channel_count;
/* Check the PPM file Type P3 or P6 */
if (fgets (header, MAX_CHARS_IN_R... | 107,441,315,725,638,360,000,000,000,000,000,000,000 | ppm-load.c | 15,305,735,499,409,437,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2018-10114 | An issue was discovered in GEGL through 0.3.32. The gegl_buffer_iterate_read_simple function in buffer/gegl-buffer-access.c allows remote attackers to cause a denial of service (write access violation) or possibly have unspecified other impact via a malformed PPM file, related to improper restrictions on memory allocat... | https://nvd.nist.gov/vuln/detail/CVE-2018-10114 |
209,815 | ImageMagick | 406da3af9e09649cda152663c179902edf5ab3ac | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/406da3af9e09649cda152663c179902edf5ab3ac | https://github.com/ImageMagick/ImageMagick/issues/1732 | 1 | MagickExport MagickBooleanType InterpolatePixelChannels(
const Image *magick_restrict source,const CacheView_ *source_view,
const Image *magick_restrict destination,const PixelInterpolateMethod method,
const double x,const double y,Quantum *pixel,ExceptionInfo *exception)
{
MagickBooleanType
status;
doub... | 31,816,485,231,708,623,000,000,000,000,000,000,000 | pixel.c | 326,375,122,591,553,100,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2020-25676 | In CatromWeights(), MeshInterpolate(), InterpolatePixelChannel(), InterpolatePixelChannels(), and InterpolatePixelInfo(), which are all functions in /MagickCore/pixel.c, there were multiple unconstrained pixel offset calculations which were being used with the floor() function. These calculations produced undefined beh... | https://nvd.nist.gov/vuln/detail/CVE-2020-25676 |
421,858 | ImageMagick | 406da3af9e09649cda152663c179902edf5ab3ac | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/406da3af9e09649cda152663c179902edf5ab3ac | https://github.com/ImageMagick/ImageMagick/issues/1732 | 0 | MagickExport MagickBooleanType InterpolatePixelChannels(
const Image *magick_restrict source,const CacheView_ *source_view,
const Image *magick_restrict destination,const PixelInterpolateMethod method,
const double x,const double y,Quantum *pixel,ExceptionInfo *exception)
{
MagickBooleanType
status;
doub... | 285,508,097,729,357,500,000,000,000,000,000,000,000 | pixel.c | 203,831,495,068,906,250,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2020-25676 | In CatromWeights(), MeshInterpolate(), InterpolatePixelChannel(), InterpolatePixelChannels(), and InterpolatePixelInfo(), which are all functions in /MagickCore/pixel.c, there were multiple unconstrained pixel offset calculations which were being used with the floor() function. These calculations produced undefined beh... | https://nvd.nist.gov/vuln/detail/CVE-2020-25676 |
209,816 | ImageMagick | 406da3af9e09649cda152663c179902edf5ab3ac | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/406da3af9e09649cda152663c179902edf5ab3ac | https://github.com/ImageMagick/ImageMagick/issues/1732 | 1 | MagickExport MagickBooleanType InterpolatePixelInfo(const Image *image,
const CacheView_ *image_view,const PixelInterpolateMethod method,
const double x,const double y,PixelInfo *pixel,ExceptionInfo *exception)
{
MagickBooleanType
status;
double
alpha[16],
gamma;
PixelInfo
pixels[16];
reg... | 62,529,628,609,629,680,000,000,000,000,000,000,000 | pixel.c | 326,375,122,591,553,100,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2020-25676 | In CatromWeights(), MeshInterpolate(), InterpolatePixelChannel(), InterpolatePixelChannels(), and InterpolatePixelInfo(), which are all functions in /MagickCore/pixel.c, there were multiple unconstrained pixel offset calculations which were being used with the floor() function. These calculations produced undefined beh... | https://nvd.nist.gov/vuln/detail/CVE-2020-25676 |
421,875 | ImageMagick | 406da3af9e09649cda152663c179902edf5ab3ac | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/406da3af9e09649cda152663c179902edf5ab3ac | https://github.com/ImageMagick/ImageMagick/issues/1732 | 0 | MagickExport MagickBooleanType InterpolatePixelInfo(const Image *image,
const CacheView_ *image_view,const PixelInterpolateMethod method,
const double x,const double y,PixelInfo *pixel,ExceptionInfo *exception)
{
MagickBooleanType
status;
double
alpha[16],
gamma;
PixelInfo
pixels[16];
reg... | 98,442,728,406,374,490,000,000,000,000,000,000,000 | pixel.c | 203,831,495,068,906,250,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2020-25676 | In CatromWeights(), MeshInterpolate(), InterpolatePixelChannel(), InterpolatePixelChannels(), and InterpolatePixelInfo(), which are all functions in /MagickCore/pixel.c, there were multiple unconstrained pixel offset calculations which were being used with the floor() function. These calculations produced undefined beh... | https://nvd.nist.gov/vuln/detail/CVE-2020-25676 |
209,817 | ImageMagick | 406da3af9e09649cda152663c179902edf5ab3ac | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/406da3af9e09649cda152663c179902edf5ab3ac | https://github.com/ImageMagick/ImageMagick/issues/1732 | 1 | MagickExport MagickBooleanType InterpolatePixelChannel(
const Image *magick_restrict image,const CacheView_ *image_view,
const PixelChannel channel,const PixelInterpolateMethod method,
const double x,const double y,double *pixel,ExceptionInfo *exception)
{
double
alpha[16],
gamma,
pixels[16];
Mag... | 315,814,082,361,108,160,000,000,000,000,000,000,000 | pixel.c | 326,375,122,591,553,100,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2020-25676 | In CatromWeights(), MeshInterpolate(), InterpolatePixelChannel(), InterpolatePixelChannels(), and InterpolatePixelInfo(), which are all functions in /MagickCore/pixel.c, there were multiple unconstrained pixel offset calculations which were being used with the floor() function. These calculations produced undefined beh... | https://nvd.nist.gov/vuln/detail/CVE-2020-25676 |
421,855 | ImageMagick | 406da3af9e09649cda152663c179902edf5ab3ac | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/406da3af9e09649cda152663c179902edf5ab3ac | https://github.com/ImageMagick/ImageMagick/issues/1732 | 0 | MagickExport MagickBooleanType InterpolatePixelChannel(
const Image *magick_restrict image,const CacheView_ *image_view,
const PixelChannel channel,const PixelInterpolateMethod method,
const double x,const double y,double *pixel,ExceptionInfo *exception)
{
double
alpha[16],
gamma,
pixels[16];
Mag... | 283,382,698,789,705,800,000,000,000,000,000,000,000 | pixel.c | 203,831,495,068,906,250,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2020-25676 | In CatromWeights(), MeshInterpolate(), InterpolatePixelChannel(), InterpolatePixelChannels(), and InterpolatePixelInfo(), which are all functions in /MagickCore/pixel.c, there were multiple unconstrained pixel offset calculations which were being used with the floor() function. These calculations produced undefined beh... | https://nvd.nist.gov/vuln/detail/CVE-2020-25676 |
209,819 | linux | f65886606c2d3b562716de030706dfe1bea4ed5e | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f65886606c2d3b562716de030706dfe1bea4ed5e | KVM: fix memory leak in kvm_io_bus_unregister_dev()
when kmalloc() fails in kvm_io_bus_unregister_dev(), before removing
the bus, we should iterate over all other devices linked to it and call
kvm_iodevice_destructor() for them
Fixes: 90db10434b16 ("KVM: kvm_io_bus_unregister_dev() should never fail")
Cc: stable@vger... | 1 | void kvm_io_bus_unregister_dev(struct kvm *kvm, enum kvm_bus bus_idx,
struct kvm_io_device *dev)
{
int i;
struct kvm_io_bus *new_bus, *bus;
bus = kvm_get_bus(kvm, bus_idx);
if (!bus)
return;
for (i = 0; i < bus->dev_count; i++)
if (bus->range[i].dev == dev) {
break;
}
if (i == bus->dev_count... | 52,247,065,870,426,950,000,000,000,000,000,000,000 | kvm_main.c | 221,748,071,293,021,450,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2020-36312 | An issue was discovered in the Linux kernel before 5.8.10. virt/kvm/kvm_main.c has a kvm_io_bus_unregister_dev memory leak upon a kmalloc failure, aka CID-f65886606c2d. | https://nvd.nist.gov/vuln/detail/CVE-2020-36312 |
421,896 | linux | f65886606c2d3b562716de030706dfe1bea4ed5e | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f65886606c2d3b562716de030706dfe1bea4ed5e | KVM: fix memory leak in kvm_io_bus_unregister_dev()
when kmalloc() fails in kvm_io_bus_unregister_dev(), before removing
the bus, we should iterate over all other devices linked to it and call
kvm_iodevice_destructor() for them
Fixes: 90db10434b16 ("KVM: kvm_io_bus_unregister_dev() should never fail")
Cc: stable@vger... | 0 | void kvm_io_bus_unregister_dev(struct kvm *kvm, enum kvm_bus bus_idx,
struct kvm_io_device *dev)
{
int i, j;
struct kvm_io_bus *new_bus, *bus;
bus = kvm_get_bus(kvm, bus_idx);
if (!bus)
return;
for (i = 0; i < bus->dev_count; i++)
if (bus->range[i].dev == dev) {
break;
}
if (i == bus->dev_co... | 293,552,700,653,468,700,000,000,000,000,000,000,000 | kvm_main.c | 103,948,528,607,694,420,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2020-36312 | An issue was discovered in the Linux kernel before 5.8.10. virt/kvm/kvm_main.c has a kvm_io_bus_unregister_dev memory leak upon a kmalloc failure, aka CID-f65886606c2d. | https://nvd.nist.gov/vuln/detail/CVE-2020-36312 |
209,827 | qemu | 05a40b172e4d691371534828078be47e7fff524c | https://github.com/bonzini/qemu | https://gitlab.com/qemu-project/qemu/-/commit/05a40b172e4d691371534828078be47e7fff524c | usb: limit combined packets to 1 MiB (CVE-2021-3527)
usb-host and usb-redirect try to batch bulk transfers by combining many
small usb packets into a single, large transfer request, to reduce the
overhead and improve performance.
This patch adds a size limit of 1 MiB for those combined packets to
restrict the host re... | 1 | void usb_ep_combine_input_packets(USBEndpoint *ep)
{
USBPacket *p, *u, *next, *prev = NULL, *first = NULL;
USBPort *port = ep->dev->port;
int totalsize;
assert(ep->pipeline);
assert(ep->pid == USB_TOKEN_IN);
QTAILQ_FOREACH_SAFE(p, &ep->queue, queue, next) {
/* Empty the queue on a halt... | 305,778,976,348,475,800,000,000,000,000,000,000,000 | combined-packet.c | 4,571,623,146,106,899,500,000,000,000,000,000,000 | [
"CWE-770"
] | CVE-2021-3527 | A flaw was found in the USB redirector device (usb-redir) of QEMU. Small USB packets are combined into a single, large transfer request, to reduce the overhead and improve performance. The combined size of the bulk transfer is used to dynamically allocate a variable length array (VLA) on the stack without proper valida... | https://nvd.nist.gov/vuln/detail/CVE-2021-3527 |
421,932 | qemu | 05a40b172e4d691371534828078be47e7fff524c | https://github.com/bonzini/qemu | https://gitlab.com/qemu-project/qemu/-/commit/05a40b172e4d691371534828078be47e7fff524c | usb: limit combined packets to 1 MiB (CVE-2021-3527)
usb-host and usb-redirect try to batch bulk transfers by combining many
small usb packets into a single, large transfer request, to reduce the
overhead and improve performance.
This patch adds a size limit of 1 MiB for those combined packets to
restrict the host re... | 0 | void usb_ep_combine_input_packets(USBEndpoint *ep)
{
USBPacket *p, *u, *next, *prev = NULL, *first = NULL;
USBPort *port = ep->dev->port;
int totalsize;
assert(ep->pipeline);
assert(ep->pid == USB_TOKEN_IN);
QTAILQ_FOREACH_SAFE(p, &ep->queue, queue, next) {
/* Empty the queue on a halt... | 111,595,547,135,952,190,000,000,000,000,000,000,000 | combined-packet.c | 156,241,094,806,272,440,000,000,000,000,000,000,000 | [
"CWE-770"
] | CVE-2021-3527 | A flaw was found in the USB redirector device (usb-redir) of QEMU. Small USB packets are combined into a single, large transfer request, to reduce the overhead and improve performance. The combined size of the bulk transfer is used to dynamically allocate a variable length array (VLA) on the stack without proper valida... | https://nvd.nist.gov/vuln/detail/CVE-2021-3527 |
209,836 | mono | 2f00e4bbb2137130845afb1b2a1e678552fc8e5c | https://github.com/mono/mono | https://github.com/mono/mono/commit/2f00e4bbb2137130845afb1b2a1e678552fc8e5c | Disable some of the FastCopy fast paths since they are racy. | 1 | ves_icall_System_Array_FastCopy (MonoArray *source, int source_idx, MonoArray* dest, int dest_idx, int length)
{
int element_size;
void * dest_addr;
void * source_addr;
MonoClass *src_class;
MonoClass *dest_class;
int i;
MONO_ARCH_SAVE_REGS;
if (source->obj.vtable->klass->rank != dest->obj.vtable->klass->rank... | 336,656,143,262,860,640,000,000,000,000,000,000,000 | icall.c | 125,626,882,266,270,200,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-0989 | The RuntimeHelpers.InitializeArray method in metadata/icall.c in Mono, when Moonlight 2.x before 2.4.1 or 3.x before 3.99.3 is used, does not properly restrict data types, which allows remote attackers to modify internal read-only data structures, and cause a denial of service (plugin crash) or corrupt the internal sta... | https://nvd.nist.gov/vuln/detail/CVE-2011-0989 |
422,100 | mono | 2f00e4bbb2137130845afb1b2a1e678552fc8e5c | https://github.com/mono/mono | https://github.com/mono/mono/commit/2f00e4bbb2137130845afb1b2a1e678552fc8e5c | Disable some of the FastCopy fast paths since they are racy. | 0 | ves_icall_System_Array_FastCopy (MonoArray *source, int source_idx, MonoArray* dest, int dest_idx, int length)
{
int element_size;
void * dest_addr;
void * source_addr;
MonoClass *src_class;
MonoClass *dest_class;
MONO_ARCH_SAVE_REGS;
if (source->obj.vtable->klass->rank != dest->obj.vtable->klass->rank)
retu... | 245,172,186,216,914,400,000,000,000,000,000,000,000 | icall.c | 200,893,431,981,277,350,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-0989 | The RuntimeHelpers.InitializeArray method in metadata/icall.c in Mono, when Moonlight 2.x before 2.4.1 or 3.x before 3.99.3 is used, does not properly restrict data types, which allows remote attackers to modify internal read-only data structures, and cause a denial of service (plugin crash) or corrupt the internal sta... | https://nvd.nist.gov/vuln/detail/CVE-2011-0989 |
209,841 | php-src | 0e097f2c96ce31b16fa371981045f224e5a37160 | https://github.com/php/php-src | https://github.com/php/php-src/commit/0e097f2c96ce31b16fa371981045f224e5a37160 | Fixed bug #75535
The sizeof()s for Content-Length and Transfer-Encoding were missing
the trailing ":". Apart from being generally wrong, this no longer
verified that the header actually contains a colon, leading to the
null http_header_value being used.
Additionally, in the interest of being defensive, also make sure... | 1 | php_stream *php_stream_url_wrap_http_ex(php_stream_wrapper *wrapper,
const char *path, const char *mode, int options, zend_string **opened_path,
php_stream_context *context, int redirect_max, int flags STREAMS_DC) /* {{{ */
{
php_stream *stream = NULL;
php_url *resource = NULL;
int use_ssl;
int use_proxy = 0;
... | 296,928,152,559,755,300,000,000,000,000,000,000,000 | http_fopen_wrapper.c | 276,373,428,627,128,840,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2018-14884 | An issue was discovered in PHP 7.0.x before 7.0.27, 7.1.x before 7.1.13, and 7.2.x before 7.2.1. Inappropriately parsing an HTTP response leads to a segmentation fault because http_header_value in ext/standard/http_fopen_wrapper.c can be a NULL value that is mishandled in an atoi call. | https://nvd.nist.gov/vuln/detail/CVE-2018-14884 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.