instance_id string | description string | exploit(poc)_url string | patch_url string | weakness_enumeration string | github_repo string | base_commit string | developers_patch string | bug_report string | sanitizer_report string | sanitizer string | github_issue string | nvd_url string |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
imagemagick.cve-2017-14400 | In ImageMagick 7.0.7-1 Q16, the PersistPixelCache function in magick/cache.c mishandles the pixel cache nexus, which allows remote attackers to cause a denial of service (NULL pointer dereference in the function GetVirtualPixels in MagickCore/cache.c) via a crafted file. | https://github.com/ImageMagick/ImageMagick/issues/746 | https://github.com/ImageMagick/ImageMagick/commit/2c2206bcd4ff98dd097dd0acb5e92dd464465231, https://github.com/ImageMagick/ImageMagick/commit/76f94fa2d9ae5d96e15929b6b6ce0c866fc44c69 | CWE-476 | ImageMagick/ImageMagick | 2c2206bcd4ff98dd097dd0acb5e92dd464465231~1 | diff --git a/MagickCore/cache.c b/MagickCore/cache.c
index 8b5a91fb4c8..bf60ae8cdb1 100644
--- a/MagickCore/cache.c
+++ b/MagickCore/cache.c
@@ -3852,8 +3852,6 @@ MagickExport MagickBooleanType PersistPixelCache(Image *image,
MagickPathExtent);
cache_info->type=DiskCache;
cache_info->offset=(*off... | https://github.com/ImageMagick/ImageMagick/issues/746 | ASAN:SIGSEGV
=================================================================
==49786==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x7f9150edb72b bp 0x7ffd830679e0 sp 0x7ffd83067980 T0)
#0 0x7f9150edb72a in GetVirtualPixels MagickCore/cache.c:3185
#1 0x7f9151203e88 in WriteAAIImage code... | null | === https://github.com/ImageMagick/ImageMagick/issues/746 ===
Title: Null Pointer Dereference in GetVirtualPixels MagickCore/cache.c:3185
---
Body:
poc1
version:
ImageMagick 7.0.7-1 Q16 x86_64
gcc 7.1
crash link :
https://raw.githubusercontent.com/jerryl3e/poc/master/im_poc_1505120100
trigger command :
... | https://nvd.nist.gov/vuln/detail/CVE-2017-14400 |
imagemagick.cve-2022-1115 | A heap-buffer-overflow flaw was found in ImageMagick’s PushShortPixel() function of quantum-private.h file. This vulnerability is triggered when an attacker passes a specially crafted TIFF image file to ImageMagick for conversion, potentially leading to a denial of service. | https://github.com/ImageMagick/ImageMagick/issues/4974 | https://github.com/ImageMagick/ImageMagick/commit/c8718305f120293d8bf13724f12eed885d830b09, https://github.com/ImageMagick/ImageMagick6/commit/1f860f52bd8d58737ad883072203391096b30b51 | CWE-119, CWE-787 | ImageMagick/ImageMagick | c8718305f120293d8bf13724f12eed885d830b09~1 | diff --git a/coders/tiff.c b/coders/tiff.c
index 31839f67e29..32ae00ab812 100644
--- a/coders/tiff.c
+++ b/coders/tiff.c
@@ -1987,7 +1987,7 @@ static Image *ReadTIFFImage(const ImageInfo *image_info,
number_pixels=(MagickSizeType) columns*rows;
if (HeapOverflowSanityCheck(rows,sizeof(*tile_pixels)) !=... | https://access.redhat.com/security/cve/CVE-2022-1115, https://bugzilla.redhat.com/show_bug.cgi?id=2067022, https://github.com/ImageMagick/ImageMagick/issues/4974 | ==1195823==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x61900000181c at pc 0x000000cd5328 bp 0x7ffdacd61fa0 sp 0x7ffdacd61f98
READ of size 1 at 0x61900000181c thread T0
#0 0xcd5327 in PushShortPixel /root/fuzz/target/image_magick/ImageMagick/./MagickCore/quantum-private.h
#1 0xcd5327 in ImportRGBA... | ASan (inferred) | === https://github.com/ImageMagick/ImageMagick/issues/4974 ===
Title: heap-buffer-overflow in magick at quantum-private.h PushShortPixel
---
Body:
### ImageMagick version
7.1.0-28
### Operating system
Linux
### Operating system, version and so on
OS: Ubuntu 20.04.3 LTS
Version: ImageMagick 7.1.0-28 Q... | https://nvd.nist.gov/vuln/detail/CVE-2022-1115 |
exiv2.cve-2020-18899 | An uncontrolled memory allocation in DataBufdata(subBox.length-sizeof(box)) function of Exiv2 0.27 allows attackers to cause a denial of service (DOS) via a crafted input. | https://github.com/Exiv2/exiv2/issues/742 | https://github.com/Exiv2/exiv2/commit/051b5d9df1f4669117937b7a40104404cc252993 | CWE-770 | Exiv2/exiv2 | fd0f29bd1e91bd05c855b88794209179a9e27761 | diff --git a/src/jp2image.cpp b/src/jp2image.cpp
index 39a6f5814d..a4b2d901f8 100644
--- a/src/jp2image.cpp
+++ b/src/jp2image.cpp
@@ -501,8 +501,8 @@ namespace Exiv2
subBox.length = getLong((byte*)&subBox.length, bigEndian);
subBox.type = getLong((byte*)&subB... | https://github.com/Exiv2/exiv2/issues/742 | ==9819==WARNING: AddressSanitizer failed to allocate 0xffffffffffffffff bytes
=================================================================
==9819==ERROR: AddressSanitizer: unknown-crash on address 0xffffffffffffffff at pc 0x0000004a9325 bp 0x7fffe470cec0 sp 0x7fffe470c670
WRITE of size 18446744073709551615 at 0xff... | null | === https://github.com/Exiv2/exiv2/issues/742 ===
Title: [bug report] Program crash due to uncontrolled memory allocation on function DataBuf data(subBox.length-sizeof(box))
---
Body:
Hi there,
An issue was discovered in DataBuf data(subBox.length-sizeof(box)) function in image.cpp, as distributed in master and ve... | https://nvd.nist.gov/vuln/detail/CVE-2020-18899 |
njs.cve-2022-29780 | Nginx NJS v0.7.2 was discovered to contain a segmentation violation in the function njs_array_prototype_sort at src/njs_array.c. | https://github.com/nginx/njs/issues/486 | https://github.com/nginx/njs/commit/8b39afdad9a0761e0a5d4af1a762bd9a6daef572 | null | nginx/njs | 8b39afdad9a0761e0a5d4af1a762bd9a6daef572~1 | diff --git a/src/njs_array.c b/src/njs_array.c
index 81a7c1555..0b8c7b919 100644
--- a/src/njs_array.c
+++ b/src/njs_array.c
@@ -2696,7 +2696,7 @@ njs_array_prototype_sort(njs_vm_t *vm, njs_value_t *args, njs_uint_t nargs,
goto exception;
}
- if (njs_fast_path(fast_path)) {
+ if (njs_fast_path(fas... | https://github.com/nginx/njs/issues/486 | AddressSanitizer:DEADLYSIGNAL
=================================================================
==610159==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x7ffff6f91b13 bp 0x7fffffffb3d0 sp 0x7fffffffab48 T0)
==610159==The signal is caused by a WRITE memory access.
==610159==Hint: address points to ... | null | === https://github.com/nginx/njs/issues/486 ===
Title: SEGV in njs_array_prototype_sort
---
Body:
# Environment
OS : Linux leanderwang-LC2 5.13.0-30-generic https://github.com/nginx/njs/issues/33 SMP Mon Feb 7 14:25:10 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Commit : https://github.com/nginx/njs/commit/f65981b0b... | https://nvd.nist.gov/vuln/detail/CVE-2022-29780 |
libredwg.cve-2020-21814 | A heap based buffer overflow issue exists in GNU LibreDWG 0.10.2641 via htmlwescape ../../programs/escape.c:97. | https://github.com/LibreDWG/libredwg/issues/182#issuecomment-572891083 | https://github.com/LibreDWG/libredwg/commit/e8c3edb987ce5602c2daca8e1593d7d1c95befdb | CWE-787 | LibreDWG/libredwg | 7b9cb829f93d1c1f67584345ed65ea830de8bdda | diff --git a/programs/escape.c b/programs/escape.c
index 4d409ea43f..0bf9656c16 100644
--- a/programs/escape.c
+++ b/programs/escape.c
@@ -113,9 +113,9 @@ htmlwescape (BITCODE_TU wstr)
while ((c = *tmp++))
len++;
len += 16;
- d = dest = malloc (len);
+ d = dest = calloc (len, 1);
- while (*wstr++)
+ wh... | https://github.com/LibreDWG/libredwg/issues/182#issuecomment-572891083 | null | null | === https://github.com/LibreDWG/libredwg/issues/182#issuecomment-572891083 ===
Title: Several bugs found by fuzzing
---
Body:
Hi,
After fuzzing libredwg, I found the following bugs on the latest commit on master.
Command: ./dwg2SVG $PoC
**1.NULL pointer dereference in htmlescape ../../programs/escape.c:29**
POC: ... | https://nvd.nist.gov/vuln/detail/CVE-2020-21814 |
imagemagick.cve-2019-13295 | ImageMagick 7.0.8-50 Q16 has a heap-based buffer over-read at MagickCore/threshold.c in AdaptiveThresholdImage because a width of zero is mishandled. | https://github.com/ImageMagick/ImageMagick/issues/1608 | https://github.com/ImageMagick/ImageMagick/commit/a7759f410b773a1dd57b0e1fb28112e1cd8b97bc, https://github.com/ImageMagick/ImageMagick/issues/1608, https://github.com/ImageMagick/ImageMagick6/commit/55e6dc49f1a381d9d511ee2f888fdc3e3c3e3953 | CWE-125 | ImageMagick/ImageMagick | a7759f410b773a1dd57b0e1fb28112e1cd8b97bc~1 | diff --git a/MagickCore/threshold.c b/MagickCore/threshold.c
index a3bb96a2147..f9412bb52e5 100644
--- a/MagickCore/threshold.c
+++ b/MagickCore/threshold.c
@@ -212,6 +212,8 @@ MagickExport Image *AdaptiveThresholdImage(const Image *image,
threshold_image=CloneImage(image,0,0,MagickTrue,exception);
if (threshold_... | https://github.com/ImageMagick/ImageMagick/issues/1608 | ==10393==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x7f8ba61737f0 at pc 0x7f8bb5c0f9fa bp 0x7ffc04d5fad0 sp 0x7ffc04d5fac8
READ of size 4 at 0x7f8ba61737f0 thread T0
#0 0x7f8bb5c0f9f9 in AdaptiveThresholdImage MagickCore/threshold.c:323:33
#1 0x7f8bb51c1cb6 in CLISimpleOperatorImage MagickWand/op... | null | === https://github.com/ImageMagick/ImageMagick/issues/1608 ===
Title: heap-buffer-overflow at MagickCore/threshold.c:323:33 in AdaptiveThresholdImage
---
Body:
### Prerequisites
- [x] I have written a descriptive issue title
- [x] I have verified that I am using the latest version of ImageMagick
- [x] I have sea... | https://nvd.nist.gov/vuln/detail/CVE-2019-13295 |
exiv2.cve-2017-14859 | An Invalid memory address dereference was discovered in Exiv2::StringValueBase::read in value.cpp in Exiv2 0.26. The vulnerability causes a segmentation fault and application crash, which leads to denial of service. | https://bugzilla.redhat.com/show_bug.cgi?id=1494780 | https://github.com/Exiv2/exiv2/commit/8a586c74bbe3fbca64e86e42a42282c73f427607, https://github.com/Exiv2/exiv2/commit/c686843e205e06abb9f30ccb15a191749e2ec01f, https://github.com/Exiv2/exiv2/commit/75940da0a61a8821a0d42a2c0358b9036b6c1a45 | CWE-119 | Exiv2/exiv2 | 8a586c74bbe3fbca64e86e42a42282c73f427607~1 | diff --git a/src/tiffvisitor.cpp b/src/tiffvisitor.cpp
index 4ab733d475..ef13542e7c 100644
--- a/src/tiffvisitor.cpp
+++ b/src/tiffvisitor.cpp
@@ -47,6 +47,7 @@ EXIV2_RCSID("@(#) $Id$")
#include <iostream>
#include <iomanip>
#include <cassert>
+#include <limits>
// ************************************************... | https://bugzilla.redhat.com/show_bug.cgi?id=1494780 | null | null | null | https://nvd.nist.gov/vuln/detail/CVE-2017-14859 |
jq.cve-2023-50246 | jq is a command-line JSON processor. Version 1.7 is vulnerable to heap-based buffer overflow. Version 1.7.1 contains a patch for this issue. | https://github.com/jqlang/jq/security/advisories/GHSA-686w-5m7m-54vc | http://www.openwall.com/lists/oss-security/2023/12/15/10, https://github.com/jqlang/jq/commit/71c2ab509a8628dbbad4bc7b3f98a64aa90d3297 | CWE-120, CWE-122, CWE-787 | jqlang/jq | 71c2ab509a8628dbbad4bc7b3f98a64aa90d3297~1 | diff --git a/NEWS.md b/NEWS.md
index 913be89879..14a594ba70 100644
--- a/NEWS.md
+++ b/NEWS.md
@@ -2,7 +2,7 @@
## Security
-- CVE-2023-50246: ....
+- CVE-2023-50246: Fix heap buffer overflow in jvp\_literal\_number\_literal
- CVE-2023-50268: fix stack-buffer-overflow if comparing nan with payload
## CLI change... | https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=64574 | null | null | null | https://nvd.nist.gov/vuln/detail/CVE-2023-50246 |
njs.cve-2020-24348 | njs through 0.4.3, used in NGINX, has an out-of-bounds read in njs_json_stringify_iterator in njs_json.c. | https://github.com/nginx/njs/issues/322 | https://github.com/nginx/njs/commit/63aa001ebd7a386939851cf8b2c0332d718f5c23 | CWE-125 | nginx/njs | 63aa001ebd7a386939851cf8b2c0332d718f5c23~1 | diff --git a/src/njs_json.c b/src/njs_json.c
index 6bbf13b1f..2a2e4dd87 100644
--- a/src/njs_json.c
+++ b/src/njs_json.c
@@ -1296,7 +1296,18 @@ njs_json_stringify_iterator(njs_vm_t *vm, njs_json_stringify_t *stringify,
njs_json_stringify_indent(stringify, &chain, 0);
}
- strin... | https://github.com/nginx/njs/issues/322 | AddressSanitizer:DEADLYSIGNAL
=================================================================
==181398==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000040 (pc 0x7f2cbf620477 bp 0x7fff1a082ad0 sp 0x7fff1a082288 T0)
==181398==The signal is caused by a READ memory access.
==181398==Hint: address points to t... | ASan (inferred) | === https://github.com/nginx/njs/issues/322 ===
Title: Segfault in njs_json_stringify_iterator
---
Body:
Version:`0.4.2`, git commit `32a70c899c1f136fbc3f97fcc050d59e0bd8c6a5`
POC:
```javascript
var array = [];
var funky;
funky = {
get value() { array[10000000] = 12; }
};
for (var i = 0; i < 10; i++)
... | https://nvd.nist.gov/vuln/detail/CVE-2020-24348 |
libdwarf.cve-2022-34299 | There is a heap-based buffer over-read in libdwarf 0.4.0. This issue is related to dwarf_global_formref_b. | https://github.com/davea42/libdwarf-code/issues/119 | https://github.com/davea42/libdwarf-code/commit/7ef09e1fc9ba07653dd078edb2408631c7969162 | CWE-125 | davea42/libdwarf-code | 7ef09e1fc9ba07653dd078edb2408631c7969162~1 | diff --git a/src/lib/libdwarf/dwarf_form.c b/src/lib/libdwarf/dwarf_form.c
index 8e8e23090..fe4b013ef 100644
--- a/src/lib/libdwarf/dwarf_form.c
+++ b/src/lib/libdwarf/dwarf_form.c
@@ -605,7 +605,6 @@ find_sig8_target_as_global_offset(Dwarf_Attribute attr,
Dwarf_Bool targ_is_info = 0;
Dwarf_Off localoff = 0;... | https://github.com/davea42/libdwarf-code/issues/119 | =================================================================
==3946410==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x61b000000697 at pc 0x0000005d9f2d bp 0x7fffffff94f0 sp 0x7fffffff94e8
READ of size 8 at 0x61b000000697 thread T0
#0 0x5d9f2c in dwarf_global_formref_b /libdwarf/SRC/src/lib/libdwar... | null | === https://github.com/davea42/libdwarf-code/issues/119 ===
Title: heap overflow in dwarf_global_formref_b
---
Body:
asan output:
```
=================================================================
==3946410==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x61b000000697 at pc 0x0000005d9f2d bp 0x7fff... | https://nvd.nist.gov/vuln/detail/CVE-2022-34299 |
gpac.cve-2023-46927 | GPAC 2.3-DEV-rev605-gfc9e29089-master contains a heap-buffer-overflow in gf_isom_use_compact_size gpac/src/isomedia/isom_write.c:3403:3 in gpac/MP4Box. | null | https://github.com/gpac/gpac/commit/a7b467b151d9b54badbc4dd71e7a366b7c391817 | CWE-787 | gpac/gpac | a7b467b151d9b54badbc4dd71e7a366b7c391817~1 | diff --git a/src/isomedia/isom_write.c b/src/isomedia/isom_write.c
index 11e3f1c37d..8ed3043a9b 100644
--- a/src/isomedia/isom_write.c
+++ b/src/isomedia/isom_write.c
@@ -359,7 +359,7 @@ static GF_Err gf_isom_set_root_iod(GF_ISOFile *movie)
GF_IsomInitialObjectDescriptor *iod;
GF_IsomObjectDescriptor *od;
GF_Err ... | https://github.com/gpac/gpac/issues/2657 | =================================================================
==3459603==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x602000006b71 at pc 0x0000004a2c4f bp 0x7ffffffec1a0 sp 0x7ffffffeb968
WRITE of size 4 at 0x602000006b71 thread T0
#0 0x4a2c4e in __asan_memset (/afltest/gpac/bin/gcc/MP4Box+0x4a2c4... | ASan (inferred) | === https://github.com/gpac/gpac/issues/2657 ===
Title: heap-buffer-overflow in gf_isom_use_compact_size gpac/src/isomedia/isom_write.c:3403:3 in gpac/gpac
---
Body:
# heap-buffer-overflow in gf_isom_use_compact_size gpac/src/isomedia/isom_write.c:3403:3 in gpac/gpac
### Description
Heap-buffer-overflow in MP4B... | https://nvd.nist.gov/vuln/detail/CVE-2023-46927 |
php.cve-2017-12933 | The finish_nested_data function in ext/standard/var_unserializer.re in PHP before 5.6.31, 7.0.x before 7.0.21, and 7.1.x before 7.1.7 is prone to a buffer over-read while unserializing untrusted data. Exploitation of this issue can have an unspecified impact on the integrity of PHP. | null | null | CWE-125 | null | fb59213fc461f079bc218abf44cb5e2b4db2182c | null | https://bugs.php.net/bug.php?id=74111 | null | null | null | https://nvd.nist.gov/vuln/detail/CVE-2017-12933 |
exiv2.cve-2017-18005 | Exiv2 0.26 has a Null Pointer Dereference in the Exiv2::DataValue::toLong function in value.cpp, related to crafted metadata in a TIFF file. | https://github.com/Exiv2/exiv2/issues/168 | https://github.com/Exiv2/exiv2/commit/1c76ecbd66263b2ed14c82e41917ab3d7e8b0ef9 | CWE-476 | Exiv2/exiv2, a17r/exiv2 | a9f7e7c9b47ba59bca88be0d91ac0a7b1c03d89c~1 | diff --git a/src/actions.cpp b/src/actions.cpp
index 0ebe850..12f2c4a 100644
--- a/src/actions.cpp
+++ b/src/actions.cpp
@@ -702,8 +702,9 @@ namespace Action {
<< std::setfill(' ') << std::right
<< md.size();
}
- if (Params::instance().printItems_ & Params::... | https://github.com/Exiv2/exiv2/issues/168 | ==4728==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x557dc0c47468 bp 0x7fff7558bbb0 sp 0x7fff7558bbb0 T0)
==4728==The signal is caused by a READ memory access.
==4728==Hint: address points to the zero page.
#0 0x557dc0c47467 in Exiv2::DataValue::toLong(long) const /home/ksg/exiv2/src/value.... | null | === https://github.com/Exiv2/exiv2/issues/168 ===
Title: CVE-2017-18005: NULL Pointer Dereference while extracting metadata of a malformed tiff
---
Body:
There's a NULL Pointer Dereference occurring during the metadata extraction from a malformed tiff file.
This can be triggered by running `./exiv2 -v pr -P EIXxgkln... | https://nvd.nist.gov/vuln/detail/CVE-2017-18005 |
matio.cve-2019-9037 | An issue was discovered in libmatio.a in matio (aka MAT File I/O Library) 1.5.13. There is a buffer over-read in the function Mat_VarPrint() in mat.c. | https://github.com/TeamSeri0us/pocs/tree/master/matio | https://github.com/tbeu/matio/commit/2c20d2178017b3eb13ab160cef239648f9915bdb | CWE-125 | tbeu/matio | a0539135c9b1ab7613aa7953279da9224da88775~1 | diff --git a/src/mat.c b/src/mat.c
index a0bc257..6380504 100644
--- a/src/mat.c
+++ b/src/mat.c
@@ -873,7 +873,7 @@ Mat_VarCreate(const char *name,enum matio_classes class_type,
while ( fields[nfields] != NULL )
nfields++;
if ( nmemb )
- nfields... | https://github.com/tbeu/matio/issues/103 | $ tools/matdump ~/pocs/matio/ReadNextFunctionHandle@mat5.c_1837-26___heap-buffer-overflow
=================================================================
==29570==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60200000efd0 at pc 0x7f5b9c14f9fe bp... | null | === https://github.com/tbeu/matio/issues/103 ===
Title: some memory corruption problems when the library parse the mat file
---
Body:
I found several memory corruption problem in the library.
More details can be found at [here](https://github.com/TeamSeri0us/pocs/tree/master/matio).
---
Comment #1 by PhilipMorris... | https://nvd.nist.gov/vuln/detail/CVE-2019-9037 |
imagemagick.cve-2019-13310 | ImageMagick 7.0.8-50 Q16 has memory leaks at AcquireMagickMemory because of an error in MagickWand/mogrify.c. | https://github.com/ImageMagick/ImageMagick/issues/1616 | https://github.com/ImageMagick/ImageMagick/commit/5f21230b657ccd65452dd3d94c5b5401ba691a2d, https://github.com/ImageMagick/ImageMagick/issues/1616, https://github.com/ImageMagick/ImageMagick6/commit/5982632109cad48bc6dab867298fdea4dea57c51 | CWE-401 | ImageMagick/ImageMagick | 5f21230b657ccd65452dd3d94c5b5401ba691a2d~1 | diff --git a/MagickWand/mogrify.c b/MagickWand/mogrify.c
index 82b3c0c1c4a..150b6792304 100644
--- a/MagickWand/mogrify.c
+++ b/MagickWand/mogrify.c
@@ -7908,6 +7908,8 @@ WandExport MagickBooleanType MogrifyImageList(ImageInfo *image_info,
&distortion,exception);
if (difference_image == (Ima... | https://github.com/ImageMagick/ImageMagick/issues/1616 | null | null | === https://github.com/ImageMagick/ImageMagick/issues/1616 ===
Title: memory leaks is detected at AcquireMagickMemory
---
Body:
### Prerequisites
- [x] I have written a descriptive issue title
- [x] I have verified that I am using the latest version of ImageMagick
- [x] I have searched [open](https://github.com/... | https://nvd.nist.gov/vuln/detail/CVE-2019-13310 |
qpdf.cve-2021-36978 | QPDF 9.x through 9.1.1 and 10.x through 10.0.4 has a heap-based buffer overflow in Pl_ASCII85Decoder::write (called from Pl_AES_PDF::flush and Pl_AES_PDF::finish) when a certain downstream write fails. | null | https://github.com/qpdf/qpdf/commit/dc92574c10f3e2516ec6445b88c5d584f40df4e5 | CWE-787 | qpdf/qpdf | dc92574c10f3e2516ec6445b88c5d584f40df4e5~1 | diff --git a/ChangeLog b/ChangeLog
index 2db53cb8..1e31efb4 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2021-01-04 Jay Berkenbilt <ejb@ql.org>
+
+ * Move getNext()->write() calls in some pipelines to ensure that
+ state gates properly reset even if the next pipeline's write
+ throws an exception (fuzz iss... | https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28262, https://github.com/qpdf/qpdf/issues/492 | ==28751==ERROR: AddressSanitizer: heap-use-after-free on address 0x6070000076c5 at pc 0x0000008799bc bp 0x7fffffff6a30 sp 0x7fffffff6a28
WRITE of size 1 at 0x6070000076c5 thread T0
#0 0x8799bb in Pl_ASCII85Decoder::write(unsigned char*, unsigned long) /src/qpdf/libqpdf/Pl_ASCII85Decoder.cc:85:32
#1 0x877725 in ... | null | === https://github.com/qpdf/qpdf/issues/492 ===
Title: Heap-use-after-free in `Pl_ASCII85Decoder::write`
---
Body:
- version: 10.0.4
- commit: 78b9d6bfd4cbd3e947b1c5ffe73eb97b040e312a
- How to reproduce: qpdf_afl_fuzzer ./poc
The log from ASAN:
```
==28751==ERROR: AddressSanitizer: heap-use-after-free on addre... | https://nvd.nist.gov/vuln/detail/CVE-2021-36978 |
imagemagick.cve-2019-13296 | ImageMagick 7.0.8-50 Q16 has direct memory leaks in AcquireMagickMemory because of an error in CLIListOperatorImages in MagickWand/operation.c for a NULL value. | https://github.com/ImageMagick/ImageMagick/issues/1604 | https://github.com/ImageMagick/ImageMagick/commit/ce08a3691a8ac29125e29fc41967b3737fa3f425, https://github.com/ImageMagick/ImageMagick/issues/1604 | CWE-401 | ImageMagick/ImageMagick | ce08a3691a8ac29125e29fc41967b3737fa3f425~1 | diff --git a/MagickWand/operation.c b/MagickWand/operation.c
index f53cf6dca7c..2edf8d4b873 100644
--- a/MagickWand/operation.c
+++ b/MagickWand/operation.c
@@ -3868,7 +3868,10 @@ WandPrivate MagickBooleanType CLIListOperatorImages(MagickCLI *cli_wand,
reconstruct_image=RemoveFirstImageFromList(&_images);
... | https://github.com/ImageMagick/ImageMagick/issues/1604 | ==5674==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 13504 byte(s) in 1 object(s) allocated from:
#0 0x4e5397 in __interceptor_malloc (install/bin/magick+0x4e5397)
#1 0x7fdfed7f4146 in AcquireMagickMemory MagickCore/memory.c:478:10
#2 0x7fdfed7a1154 in AcquireCriticalMemory ./MagickCore/memor... | null | === https://github.com/ImageMagick/ImageMagick/issues/1604 ===
Title: Direct memory leaks in AcquireMagickMemory and indirect memory leaks
---
Body:
### Prerequisites
- [x] I have written a descriptive issue title
- [x] I have verified that I am using the latest version of ImageMagick
- [x] I have searched [ope... | https://nvd.nist.gov/vuln/detail/CVE-2019-13296 |
readstat.cve-2018-5698 | libreadstat.a in WizardMac ReadStat 0.1.1 has a heap-based buffer over-read via an unterminated string. | https://github.com/WizardMac/ReadStat/issues/108 | https://github.com/WizardMac/ReadStat/commit/79793dba3b665ff037ca60140441a6679a8971cf | CWE-125 | WizardMac/ReadStat | 79793dba3b665ff037ca60140441a6679a8971cf~1 | diff --git a/src/bin/readstat.c b/src/bin/readstat.c
index 032dce5e..4c088f92 100644
--- a/src/bin/readstat.c
+++ b/src/bin/readstat.c
@@ -85,7 +85,7 @@ int can_write(rs_module_t *modules, long modules_count, char *filename) {
}
static void handle_error(const char *msg, void *ctx) {
- fprintf(stderr, "%s", msg);... | https://github.com/WizardMac/ReadStat/issues/108 | =================================================================
==19976==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x6030000000b2 at pc 0x000000448071 bp 0x7fff0960c110 sp 0x7fff0960b8c0
READ of size 19 at 0x6030000000b2 thread T0
#0 0x448070 (/home/test/libfuzz/new/ReadStat/build/bin/readstat+0x4... | null | === https://github.com/WizardMac/ReadStat/issues/108 ===
Title: Heap overflow in ReadStat
---
Body:
ReadStat version 1.0-prerelease
Ubuntu 16.04 x86_64
git log
```
commit 2330b36f536705a23a50e9cbd9f0f72b38b0be98
Author: Evan Miller <emmiller@gmail.com>
Date: Wed Jan 10 20:26:31 2018 -0500
SAS7BDAT: F... | https://nvd.nist.gov/vuln/detail/CVE-2018-5698 |
njs.cve-2022-43284 | Nginx NJS v0.7.2 to v0.7.4 was discovered to contain a segmentation violation via njs_scope_valid_value at njs_scope.h. NOTE: the vendor disputes the significance of this report because NJS does not operate on untrusted input. | https://github.com/nginx/njs/issues/470, https://github.com/nginx/njs/issues/529 | https://github.com/nginx/njs/commit/04f59f9defeeb618260e620bb11466741c0e41e5 | null | nginx/njs | 04f59f9defeeb618260e620bb11466741c0e41e5~1 | diff --git a/src/njs_vmcode.c b/src/njs_vmcode.c
index ae1d1bb4f..9833ada03 100644
--- a/src/njs_vmcode.c
+++ b/src/njs_vmcode.c
@@ -1259,9 +1259,9 @@ njs_vmcode_function_copy(njs_vm_t *vm, njs_value_t *value, njs_index_t retidx)
njs_value_t *retval;
njs_function_t *function;
- retval = njs_scope_va... | https://github.com/nginx/njs/issues/470, https://github.com/nginx/njs/issues/529 | AddressSanitizer:DEADLYSIGNAL
=================================================================
==2064564==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x0000004e36b5 bp 0x7ffd26e5c130 sp 0x7ffd26e5b920 T0)
==2064564==The signal is caused by a READ memory access.
==2064564==Hint: address points t... | null | === https://github.com/nginx/njs/issues/470 ===
Title: SEGV njs_scope.h:85:10 in njs_scope_valid_value
---
Body:
### Environment
```
OS : Linux ubuntu 5.13.0-27-generic #29~20.04.1-Ubuntu SMP Fri Jan 14 00:32:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Commit : 7bd570b39297d3d91902c93a624c89b08be7a6fe
Vers... | https://nvd.nist.gov/vuln/detail/CVE-2022-43284 |
imagemagick.cve-2019-17541 | ImageMagick before 7.0.8-55 has a use-after-free in DestroyStringInfo in MagickCore/string.c because the error manager is mishandled in coders/jpeg.c. | https://github.com/ImageMagick/ImageMagick/issues/1641 | https://github.com/ImageMagick/ImageMagick/commit/39f226a9c137f547e12afde972eeba7551124493, https://github.com/ImageMagick/ImageMagick/compare/7.0.8-54...7.0.8-55, https://github.com/ImageMagick/ImageMagick/issues/1641 | CWE-416 | ImageMagick/ImageMagick | 39f226a9c137f547e12afde972eeba7551124493~1 | diff --git a/ChangeLog b/ChangeLog
index cba66b8b7fe..52dcc9bc8ab 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,16 +1,23 @@
+2019-07-18 7.0.8-55 Cristy <quetzlzacatenango@image...>
+ * Release ImageMagick version 7.0.8-55, GIT revision 15...
+
+2019-07-18 7.0.8-55 Cristy <quetzlzacatenango@image...>
+ * Heap-buffe... | https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15827, https://github.com/ImageMagick/ImageMagick/issues/1641 | ==29840==ERROR: AddressSanitizer: heap-use-after-free on address 0x60400000af68 at pc 0x7f9e79581fab bp 0x7fff303409f0 sp 0x7fff303409e0
READ of size 8 at 0x60400000af68 thread T0
#0 0x7f9e79581faa in DestroyStringInfo MagickCore/string.c:853
#1 0x7f9e7985ebaf in ReadJPEGImage coders/jpeg.c:1198
#2 0x7f9e79... | ASan (inferred) | === https://github.com/ImageMagick/ImageMagick/issues/1641 ===
Title: heap-buffer-overflow at MagickCore/string.c:853 in DestroyStringInfo
---
Body:
### Prerequisites
- [x] I have written a descriptive issue title
- [x] I have verified that I am using the latest version of ImageMagick
- [x] I have searched [open... | https://nvd.nist.gov/vuln/detail/CVE-2019-17541 |
openjpeg.cve-2016-10507 | Integer overflow vulnerability in the bmp24toimage function in convertbmp.c in OpenJPEG before 2.2.0 allows remote attackers to cause a denial of service (heap-based buffer over-read and application crash) via a crafted bmp file. | null | https://github.com/uclouvain/openjpeg/commit/da940424816e11d624362ce080bc026adffa26e8, https://github.com/uclouvain/openjpeg/issues/833 | CWE-190 | uclouvain/openjpeg | da940424816e11d624362ce080bc026adffa26e8~1 | diff --git a/src/bin/jp2/convertbmp.c b/src/bin/jp2/convertbmp.c
index d264823f0..ae83077ca 100644
--- a/src/bin/jp2/convertbmp.c
+++ b/src/bin/jp2/convertbmp.c
@@ -675,10 +675,28 @@ opj_image_t* bmptoimage(const char *filename, opj_cparameters_t *parameters)
}
}
+ if (Info_h.biWidth == 0 || Info_h.biHeight == ... | https://github.com/uclouvain/openjpeg/commit/da940424816e11d624362ce080bc026adffa26e8, https://github.com/uclouvain/openjpeg/issues/833 | ==3498==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60200000eff5
at pc 0x00000041ced5 bp 0x7ffddcd299b0 sp 0x7ffddcd299a0
READ of size 1 at 0x60200000eff5 thread T0
#0 0x41ced4 in bmp24toimage openjpeg/src/bin/jp2/convertbmp.c:150
#1 0x42273c in bmptoimage openjpeg/src/bin/jp2/convertbmp.c:747
... | null | === https://github.com/uclouvain/openjpeg/issues/833 ===
Title: [CVE-2016-10507] Out-of-Bounds Read in function bmp24toimage of convertbmp.c
---
Body:
# DESCRIPTION
An Out-of-Bounds Read issue was found in function bmp24toimage of convertbmp.c. The root cause of this issue was an Integer Overflow issue. The opj_comp... | https://nvd.nist.gov/vuln/detail/CVE-2016-10507 |
openjpeg.cve-2021-3575 | A heap-based buffer overflow was found in openjpeg in color.c:379:42 in sycc420_to_rgb when decompressing a crafted .j2k file. An attacker could use this to execute arbitrary code with the permissions of the application compiled against openjpeg. | https://github.com/uclouvain/openjpeg/issues/1347 | https://github.com/uclouvain/openjpeg/commit/89bf51c782639d5799d1378d28470d8bef312eca | CWE-787 | uclouvain/openjpeg | 89bf51c782639d5799d1378d28470d8bef312eca~1 | diff --git a/src/bin/common/color.c b/src/bin/common/color.c
index 27f15f137..ae5d648da 100644
--- a/src/bin/common/color.c
+++ b/src/bin/common/color.c
@@ -358,7 +358,15 @@ static void sycc420_to_rgb(opj_image_t *img)
if (i < loopmaxh) {
size_t j;
- for (j = 0U; j < (maxw & ~(size_t)1U); j += 2U... | https://bugzilla.redhat.com/show_bug.cgi?id=1957616, https://github.com/uclouvain/openjpeg/issues/1347 | =================================================================
==2371124==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x612000000760 at pc 0x0000004f278c bp 0x7ffd11a3eca0 sp 0x7ffd11a3ec98
READ of size 4 at 0x612000000760 thread T0
#0 0x4f278b in sycc420_to_rgb /home/yuawn/fuzz-targets/openjpeg/rep... | null | === https://github.com/uclouvain/openjpeg/issues/1347 ===
Title: Heap-buffer-overflow in color.c:379:42 in sycc420_to_rgb
---
Body:
Hi,
I found a vulnerability in current master [0bda718](https://github.com/uclouvain/openjpeg/commit/0bda7188b7b545232a341f1d978b1e4feda46fc2), and I also reproduced it on latest releas... | https://nvd.nist.gov/vuln/detail/CVE-2021-3575 |
exiv2.cve-2017-14864 | An Invalid memory address dereference was discovered in Exiv2::getULong in types.cpp in Exiv2 0.26. The vulnerability causes a segmentation fault and application crash, which leads to denial of service. | https://bugzilla.redhat.com/show_bug.cgi?id=1494467 | https://github.com/Exiv2/exiv2/commit/8a586c74bbe3fbca64e86e42a42282c73f427607 | CWE-119 | Exiv2/exiv2 | 8a586c74bbe3fbca64e86e42a42282c73f427607~1 | diff --git a/src/tiffvisitor.cpp b/src/tiffvisitor.cpp
index 4ab733d475..ef13542e7c 100644
--- a/src/tiffvisitor.cpp
+++ b/src/tiffvisitor.cpp
@@ -47,6 +47,7 @@ EXIV2_RCSID("@(#) $Id$")
#include <iostream>
#include <iomanip>
#include <cassert>
+#include <limits>
// ************************************************... | https://bugzilla.redhat.com/show_bug.cgi?id=1494467 | null | null | null | https://nvd.nist.gov/vuln/detail/CVE-2017-14864 |
openjpeg.cve-2017-14041 | A stack-based buffer overflow was discovered in the pgxtoimage function in bin/jp2/convert.c in OpenJPEG 2.2.0. The vulnerability causes an out-of-bounds write, which may lead to remote denial of service or possibly remote code execution. | null | https://blogs.gentoo.org/ago/2017/08/28/openjpeg-stack-based-buffer-overflow-write-in-pgxtoimage-convert-c/, https://github.com/uclouvain/openjpeg/commit/e5285319229a5d77bf316bb0d3a6cbd3cb8666d9, https://github.com/uclouvain/openjpeg/issues/997 | CWE-787 | uclouvain/openjpeg | e5285319229a5d77bf316bb0d3a6cbd3cb8666d9~1 | diff --git a/src/bin/jp2/convert.c b/src/bin/jp2/convert.c
index 5459f7d44..e606c9be7 100644
--- a/src/bin/jp2/convert.c
+++ b/src/bin/jp2/convert.c
@@ -1185,7 +1185,7 @@ opj_image_t* pgxtoimage(const char *filename, opj_cparameters_t *parameters)
}
fseek(f, 0, SEEK_SET);
- if (fscanf(f, "PG%[ \t]%c%c%[ ... | https://github.com/uclouvain/openjpeg/commit/e5285319229a5d77bf316bb0d3a6cbd3cb8666d9, https://github.com/uclouvain/openjpeg/issues/997 | ==159529==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7fde59900160 at pc 0x000000450bef bp 0x7ffe7641f3c0 sp 0x7ffe7641eb70
WRITE of size 36 at 0x7fde59900160 thread T0
#0 0x450bee in scanf_common /var/tmp/portage/sys-libs/compiler-rt-sanitizers-4.0.1/work/compiler-rt-4.0.1.src/lib/asan/../sanitizer... | ASan (inferred) | === https://github.com/uclouvain/openjpeg/issues/997 ===
Title: stack-based buffer overflow write in pgxtoimage (/convert.c)
---
Body:
On master, I didn't try on 2.2.0:
```
# opj_compress -n 1 -i $FILE -o null.j2k
==159529==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7fde59900160 at pc 0x00000045... | https://nvd.nist.gov/vuln/detail/CVE-2017-14041 |
upx.cve-2023-23457 | A Segmentation fault was found in UPX in PackLinuxElf64::invert_pt_dynamic() in p_lx_elf.cpp. An attacker with a crafted input file allows invalid memory address access that could lead to a denial of service. | https://github.com/upx/upx/issues/631 | https://bugzilla.redhat.com/show_bug.cgi?id=2160382, https://github.com/upx/upx/commit/779b648c5f6aa9b33f4728f79dd4d0efec0bf860, https://github.com/upx/upx/issues/631 | CWE-119 | upx/upx | 779b648c5f6aa9b33f4728f79dd4d0efec0bf860~1 | diff --git a/src/p_lx_elf.cpp b/src/p_lx_elf.cpp
index fa55470f75..b698ee0a2c 100644
--- a/src/p_lx_elf.cpp
+++ b/src/p_lx_elf.cpp
@@ -256,7 +256,8 @@ PackLinuxElf32::PackLinuxElf32help1(InputFile *f)
e_phnum = get_te16(&ehdri.e_phnum);
e_shnum = get_te16(&ehdri.e_shnum);
unsigned const e_phentsize = get... | https://bugzilla.redhat.com/show_bug.cgi?id=2160382, https://github.com/upx/upx/issues/631 | Ultimate Packer for eXecutables
Copyright (C) 1996 - 2022
UPX git-fdec47+ Markus Oberhumer, Laszlo Molnar & John Reiser Nov 16th 2022
File size Ratio Format Name
-------------------- ------ ----------- -----------
ASAN:SIGSEGV
=============================... | null | === https://github.com/upx/upx/issues/631 ===
Title: SEGV on PackLinuxElf64::invert_pt_dynamic
---
Body:
This issue tracker is **ONLY** used for reporting bugs.
Please use [stackoverflow](https://stackoverflow.com) for supporting issues.
<!---
IF YOU REMOVE THIS TEMPLATE WE WILL CLOSE YOUR ISSUE WITHOUT RESPON... | https://nvd.nist.gov/vuln/detail/CVE-2023-23457 |
imagemagick.cve-2017-11540 | When ImageMagick 7.0.6-1 processes a crafted file in convert, it can lead to a heap-based buffer over-read in the GetPixelIndex() function, called from the WritePICONImage function in coders/xpm.c. | https://github.com/ImageMagick/ImageMagick/issues/581 | https://github.com/ImageMagick/ImageMagick/commit/20635b9b859fc649f7682ab08a4c58c644a94bf5 | CWE-125 | ImageMagick/ImageMagick | 20635b9b859fc649f7682ab08a4c58c644a94bf5~1 | diff --git a/coders/xpm.c b/coders/xpm.c
index 1469fe445dd..26c71be1a74 100644
--- a/coders/xpm.c
+++ b/coders/xpm.c
@@ -826,7 +826,7 @@ static MagickBooleanType WritePICONImage(const ImageInfo *image_info,
symbol[j]='\0';
(void) CopyMagickString(buffer,symbol,MagickPathExtent);
(void) WriteBlobStr... | https://github.com/ImageMagick/ImageMagick/issues/581 | =================================================================
==43957==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x61d000017a88 at pc 0x7f298fbefc28 bp 0x7fff46d63780 sp 0x7fff46d63770
READ of size 4 at 0x61d000017a88 thread T0
#0 0x7f298fbefc27 in GetPixelIndex MagickCore/pixel-accessor.h:191
... | null | === https://github.com/ImageMagick/ImageMagick/issues/581 ===
Title: Heap-Overflow in GetPixelIndex() MagickCore/pixel-accessor.h
---
Body:
Crash Link : https://raw.githubusercontent.com/lcatro/My_PoC/master/ImageMagick/heap-overflow_output_picon_READ_GetPixelIndex
Trigger Command : ./magick convert heap-overflo... | https://nvd.nist.gov/vuln/detail/CVE-2017-11540 |
libjpeg-turbo.cve-2020-13790 | libjpeg-turbo 2.0.4, and mozjpeg 4.0.0, has a heap-based buffer over-read in get_rgb_row() in rdppm.c via a malformed PPM input file. | https://github.com/libjpeg-turbo/libjpeg-turbo/issues/433 | https://github.com/libjpeg-turbo/libjpeg-turbo/commit/3de15e0c344d11d4b90f4a47136467053eb2d09a | CWE-125 | libjpeg-turbo/libjpeg-turbo | 3de15e0c344d11d4b90f4a47136467053eb2d09a~1 | diff --git a/ChangeLog.md b/ChangeLog.md
index d63ad90f6..ab58b9bd0 100644
--- a/ChangeLog.md
+++ b/ChangeLog.md
@@ -13,6 +13,12 @@ TurboJPEG Java API that caused an error ("java.lang.IllegalStateException: No
source image is associated with this instance") when attempting to use that
method to compress a YUV image.
... | https://github.com/libjpeg-turbo/libjpeg-turbo/issues/433 | ==2127==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x62900000417f at pc 0x55f48a780991 bp 0x7ffccfe84010 sp 0x7ffccfe84000
READ of size 1 at 0x62900000417f thread T0
#0 0x55f48a780990 in get_rgb_row libjpeg-turbo/rdppm.c:434
#1 0x55f48a77cadd in main libjpeg-turbo/cjpeg.c:664
#2 0x7f9476b50b96... | null | === https://github.com/libjpeg-turbo/libjpeg-turbo/issues/433 ===
Title: Heap-based buffer over-read in get_rgb_row() in rdppm.c
---
Body:
**Have you searched the existing issues (both open and closed) in the libjpeg-turbo issue tracker to ensure that this bug report is not a duplicate?**
Yes
**Does this bug repo... | https://nvd.nist.gov/vuln/detail/CVE-2020-13790 |
imagemagick.cve-2018-5246 | In ImageMagick 7.0.7-17 Q16, there are memory leaks in ReadPATTERNImage in coders/pattern.c. | https://github.com/ImageMagick/ImageMagick/issues/929 | https://github.com/ImageMagick/ImageMagick/commit/1c3dd700bbb17837ee6f540aff3eafc76262accf | CWE-772 | ImageMagick/ImageMagick | 1c3dd700bbb17837ee6f540aff3eafc76262accf~1 | diff --git a/coders/pattern.c b/coders/pattern.c
index bb22c1604f7..a5893c70e76 100644
--- a/coders/pattern.c
+++ b/coders/pattern.c
@@ -977,7 +977,10 @@ static Image *ReadPATTERNImage(const ImageInfo *image_info,
break;
}
if (blob == (const void *) NULL)
- ThrowReaderException(OptionError,"Unreco... | https://github.com/ImageMagick/ImageMagick/issues/929 | ==108470==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 13024 byte(s) in 1 object(s) allocated from:
#0 0x4b9ad3 in malloc (/usr/local/bin/magick+0x4b9ad3)
#1 0x7f1281f6b7dd in AcquireCriticalMemory /home/ubuntu/ImageMagick/./MagickCore/memory-private.h:57:10
#2 0x7f1281f74d29 in AcquireImageI... | null | === https://github.com/ImageMagick/ImageMagick/issues/929 ===
Title: memory leaks
---
Body:
ubuntu@ubuntu:~/fuzz_py$ magick -version
Version: ImageMagick 7.0.7-17 Q16 x86_64 2017-12-26 http://www.imagemagick.org
Copyright: © 1999-2018 ImageMagick Studio LLC
License: http://www.imagemagick.org/script/license.php
F... | https://nvd.nist.gov/vuln/detail/CVE-2018-5246 |
mruby.cve-2022-1212 | Use-After-Free in str_escape in mruby/mruby in GitHub repository mruby/mruby prior to 3.2. Possible arbitrary code execution if being exploited. | https://huntr.dev/bounties/9fcc06d0-08e4-49c8-afda-2cae40946abe | https://github.com/mruby/mruby/commit/3cf291f72224715942beaf8553e42ba8891ab3c6, https://huntr.dev/bounties/9fcc06d0-08e4-49c8-afda-2cae40946abe | CWE-416 | mruby/mruby | 3cf291f72224715942beaf8553e42ba8891ab3c6~1 | diff --git a/src/vm.c b/src/vm.c
index 3796f41738..6d61386b31 100644
--- a/src/vm.c
+++ b/src/vm.c
@@ -2268,9 +2268,9 @@ mrb_vm_exec(mrb_state *mrb, const struct RProc *proc, const mrb_code *pc)
}
if (ci->cci > CINFO_NONE) {
ci = cipop(mrb);
+ mrb->exc = (struct RObject*)br... | https://huntr.dev/bounties/9fcc06d0-08e4-49c8-afda-2cae40946abe | null | ASan (inferred) | null | https://nvd.nist.gov/vuln/detail/CVE-2022-1212 |
upx.cve-2020-27787 | A Segmentaation fault was found in UPX in invert_pt_dynamic() function in p_lx_elf.cpp. An attacker with a crafted input file allows invalid memory address access that could lead to a denial of service. | https://github.com/upx/upx/issues/333 | https://github.com/upx/upx/commit/e2f60adc95334f47e286838dac33160819c5d74d, https://github.com/upx/upx/issues/333 | CWE-119 | upx/upx | e2f60adc95334f47e286838dac33160819c5d74d~1 | diff --git a/src/p_lx_elf.cpp b/src/p_lx_elf.cpp
index 96f5838d6f..7034948702 100644
--- a/src/p_lx_elf.cpp
+++ b/src/p_lx_elf.cpp
@@ -1639,8 +1639,8 @@ PackLinuxElf32::invert_pt_dynamic(Elf32_Dyn const *dynp)
unsigned const *const buckets = &hashtab[2];
unsigned const *const chains = &buckets[nbucket... | https://github.com/upx/upx/issues/333 | ==11637==ERROR: AddressSanitizer: SEGV on unknown address 0x632000014810 (pc 0x00000087d00d bp 0x7ffedceeaf20 sp 0x7ffedceeaef0 T0)
#0 0x87d00c in acc_ua_get_le64(void const*) /home/upx_tc/upx_debug_2/src/miniacc.h:6208
#1 0x45eace in get_le64(void const*) /home/upx_tc/upx_debug_2/src/bele.h:184
#2 0x883e8f... | null | === https://github.com/upx/upx/issues/333 ===
Title: Segmentation fault in PackLinuxElf64::invert_pt_dynamic at p_lx_elf.cpp:5173
---
Body:
## Environment
A crafted input will lead to crash in p_lx_elf.cpp at UPX 3.96(latest version,git clone from branch devel)
upx 3.96-git-1bb93d4fce9f+
UCL data compression lib... | https://nvd.nist.gov/vuln/detail/CVE-2020-27787 |
gpac.cve-2024-50664 | gpac 2.4 contains a heap-buffer-overflow at isomedia/sample_descs.c:1799 in gf_isom_new_mpha_description in gpac/MP4Box. | https://github.com/gpac/gpac/issues/2988 | https://github.com/Mu-L/gpac/commit/56ce0b952a0a3cbd39ec1b41237df062f9648cb9 | CWE-120, CWE-787 | Mu-L/gpac | 56ce0b952a0a3cbd39ec1b41237df062f9648cb9~1 | diff --git a/src/isomedia/sample_descs.c b/src/isomedia/sample_descs.c
index cc130141a3..b900e3b56f 100644
--- a/src/isomedia/sample_descs.c
+++ b/src/isomedia/sample_descs.c
@@ -1157,7 +1157,7 @@ GF_Err gf_isom_xml_subtitle_get_description(GF_ISOFile *the_file, u32 trackNumbe
entry = (GF_MetaDataSampleEntryBox *)g... | https://github.com/gpac/gpac/issues/2988 | =================================================================
==3389396==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x602000003751 at pc 0x7f740dee42c3 bp 0x7ffc60ecac00 sp 0x7ffc60eca3a8
WRITE of size 14 at 0x602000003751 thread T0
#0 0x7f740dee42c2 in __interceptor_memcpy ../../../../src/libsani... | ASan (inferred) | === https://github.com/gpac/gpac/issues/2988 ===
Title: heap-buffer-overflow at isomedia/sample_descs.c:1799 in gf_isom_new_mpha_description in gpac/MP4Box
---
Body:
### Description
Dear developers,
We found the following heap buffer overflow bug on gpac(version 2.4), please confirm.
The latest master branc... | https://nvd.nist.gov/vuln/detail/CVE-2024-50664 |
libredwg.cve-2020-6612 | GNU LibreDWG 0.9.3.2564 has a heap-based buffer over-read in copy_compressed_bytes in decode_r2007.c. | https://github.com/LibreDWG/libredwg/issues/179#issuecomment-570447169 | null | CWE-125 | LibreDWG/libredwg | null | null | https://github.com/LibreDWG/libredwg/issues/179#issuecomment-570447169 | null | null | === https://github.com/LibreDWG/libredwg/issues/179#issuecomment-570447169 ===
Title: Several bugs found by fuzzing
---
Body:
Hi,
After fuzzing libredwg, I found the following bugs on the latest commit on master.
Command: ./dwg2svg2 $PoC
**1.heap-buffer-overflow in read_pages_map ../../src/decode_r2007.c:1007**
P... | https://nvd.nist.gov/vuln/detail/CVE-2020-6612 |
libmodbus.cve-2022-0367 | A heap-based buffer overflow flaw was found in libmodbus in function modbus_reply() in src/modbus.c. | https://github.com/stephane/libmodbus/issues/614 | https://github.com/stephane/libmodbus/commit/b4ef4c17d618eba0adccc4c7d9e9a1ef809fc9b6, https://github.com/stephane/libmodbus/issues/614 | CWE-119, CWE-787 | stephane/libmodbus | b4ef4c17d618eba0adccc4c7d9e9a1ef809fc9b6~1 | diff --git a/src/modbus.c b/src/modbus.c
index 99f333b85..e13bd0df7 100644
--- a/src/modbus.c
+++ b/src/modbus.c
@@ -961,7 +961,7 @@ int modbus_reply(modbus_t *ctx, const uint8_t *req,
nb_write, nb, MODBUS_MAX_WR_WRITE_REGISTERS, MODBUS_MAX_WR_READ_REGISTERS);
} else if (mapping_address < 0 ||... | https://bugzilla.redhat.com/show_bug.cgi?id=2045571, https://github.com/stephane/libmodbus/issues/614 | AddressSanitizer:DEADLYSIGNAL
=================================================================
==174549==ERROR: AddressSanitizer: SEGV on unknown address 0x605ffffffec8 (pc 0x7fd8514abc62 bp 0x7ffebf02e730 sp 0x7ffebf02dcc0 T0)
==174549==The signal is caused by a WRITE memory access.
#0 0x7fd8514abc62 in modbus_re... | null | === https://github.com/stephane/libmodbus/issues/614 ===
Title: Heap-based Buffer Overflow in modbus_reply
---
Body:
## libmodbus version
ebc4f4788678eda8d99e23be87c61a662a9d26b7
## OS and/or distribution
Ubuntu 20.04 focal
## Environment
,AMD EPYC 7742 64-Core @ 16x 2.25GHz
## Description
Heap-b... | https://nvd.nist.gov/vuln/detail/CVE-2022-0367 |
faad2.cve-2021-32278 | An issue was discovered in faad2 through 2.10.0. A heap-buffer-overflow exists in the function lt_prediction located in lt_predict.c. It allows an attacker to cause code Execution. | https://github.com/knik0/faad2/issues/62 | https://github.com/awesie/faad2/commit/e19a5e491354e0e4664d02b796dacee28fb2521e | CWE-787 | awesie/faad2 | e19a5e491354e0e4664d02b796dacee28fb2521e~1 | diff --git a/libfaad/syntax.c b/libfaad/syntax.c
index 5df254ff..c71c67a2 100644
--- a/libfaad/syntax.c
+++ b/libfaad/syntax.c
@@ -884,7 +884,10 @@ static uint8_t ics_info(NeAACDecStruct *hDecoder, ic_stream *ics, bitfile *ld,
if ((ics->ltp.data_present = faad_get1bit(ld
DE... | https://github.com/knik0/faad2/issues/62 | =================================================================
==13979==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x620000003006 at pc 0x0000005e1605 bp 0x7ffc00e45c30 sp 0x7ffc00e45c28
READ of size 2 at 0x620000003006 thread T0
#0 0x5e1604 in lt_prediction /home/seviezhou/faad2/libfaad/lt_predict... | ASan (inferred) | === https://github.com/knik0/faad2/issues/62 ===
Title: A heap-buffer-overflow in lt_predict.c:108:36
---
Body:
## System info
Ubuntu x86_64, clang 6.0, faad (latest master [f71b5e](https://github.com/knik0/faad2/commit/f71b5e81f563d94fa284977a326520d269d8353e))
## Configure
CFLAGS="-g -fsanitize=address" LD... | https://nvd.nist.gov/vuln/detail/CVE-2021-32278 |
matio.cve-2020-19497 | Integer overflow vulnerability in Mat_VarReadNextInfo5 in mat5.c in tbeu matio (aka MAT File I/O Library) 1.5.17, allows attackers to cause a Denial of Service or possibly other unspecified impacts. | https://github.com/tbeu/matio/issues/121 | https://github.com/tbeu/matio/commit/5fa49ef9fc4368fe3d19b5fdaa36d8fa5e7f4606, https://github.com/tbeu/matio/issues/121 | CWE-190 | tbeu/matio | 5fa49ef9fc4368fe3d19b5fdaa36d8fa5e7f4606~1 | diff --git a/src/mat5.c b/src/mat5.c
index abdb351e..78e2f4fe 100644
--- a/src/mat5.c
+++ b/src/mat5.c
@@ -1009,9 +1009,16 @@ ReadNextCell( mat_t *mat, matvar_t *matvar )
if ( uncomp_buf[0] == MAT_T_INT8 ) { /* Name not in tag */
mat_uint32_t len = uncomp_buf[1];
- ... | https://github.com/tbeu/matio/issues/121 | ==17186==ERROR: AddressSanitizer: SEGV on unknown address 0x60210000efcf (pc 0x7ff5bd4a42ce bp 0x7ffd873b9460 sp 0x7ffd873b9230 T0)
#0 0x7ff5bd4a42cd in Mat_VarReadNextInfo5 ../../src/mat5.c:4983
#1 0x7ff5bd4b8c57 in Mat_VarReadNextInfo ../../src/mat.c:2311
#2 0x408122 in main ../../tools/matdump.c:942
... | null | === https://github.com/tbeu/matio/issues/121 ===
Title: SEGV in mat5.c:4983
---
Body:
Hi,
I found a crash in mat5.c:4983 (the latest commit `bcf0447` on master).
PoC: https://github.com/strongcourage/PoCs/blob/master/matio_bcf0447/PoC_segv_Mat_VarReadNextInfo5
Command: matdump $PoC
ASAN says:
~~~
==17186==ERROR... | https://nvd.nist.gov/vuln/detail/CVE-2020-19497 |
njs.cve-2023-27730 | Nginx NJS v0.7.10 was discovered to contain a segmentation violation via the function njs_lvlhsh_find at src/njs_lvlhsh.c. | https://github.com/nginx/njs/issues/615 | https://github.com/nginx/njs/commit/9cec874582b925e373adb0896b85a112702f6664 | CWE-125 | nginx/njs | 9cec874582b925e373adb0896b85a112702f6664~1 | diff --git a/src/njs_array.c b/src/njs_array.c
index ec21e60c9..0eb3276f8 100644
--- a/src/njs_array.c
+++ b/src/njs_array.c
@@ -1404,10 +1404,11 @@ njs_array_prototype_to_string(njs_vm_t *vm, njs_value_t *args, njs_uint_t nargs,
static const njs_value_t join_string = njs_string("join");
- if (njs_is_objec... | https://github.com/nginx/njs/issues/615 | ==21471==ERROR: AddressSanitizer: SEGV on unknown address 0x00000000726f (pc 0x0000004cde74 bp 0x7ffcd78018d0 sp 0x7ffcd78018d0 T0)
==21471==The signal is caused by a READ memory access.
#0 0x4cde74 in njs_lvlhsh_find /root/njs/src/njs_lvlhsh.c:176:16
#1 0x51efff in njs_object_property /root/njs/src/njs_object_... | null | === https://github.com/nginx/njs/issues/615 ===
Title: SEGV src/njs_lvlhsh.c:176:16 in njs_lvlhsh_find
---
Body:
Environment
```
commit: 4c1e23326e1c30e4e051bf588bfc1aaa63954976
version: 0.7.10
Build :
./configure --cc=clang --address-sanitizer=YES
make
```
Poc
```js
const v1 = URIError();... | https://nvd.nist.gov/vuln/detail/CVE-2023-27730 |
imagemagick.cve-2019-13302 | ImageMagick 7.0.8-50 Q16 has a heap-based buffer over-read in MagickCore/fourier.c in ComplexImages. | https://github.com/ImageMagick/ImageMagick/issues/1597 | https://github.com/ImageMagick/ImageMagick/commit/d5089971bd792311aaab5cb73460326d7ef7f32d, https://github.com/ImageMagick/ImageMagick/issues/1597 | CWE-125 | ImageMagick/ImageMagick | d5089971bd792311aaab5cb73460326d7ef7f32d~1 | diff --git a/MagickCore/fourier.c b/MagickCore/fourier.c
index 24b3824201f..47c3ccd2eaa 100644
--- a/MagickCore/fourier.c
+++ b/MagickCore/fourier.c
@@ -164,6 +164,9 @@ MagickExport Image *ComplexImages(const Image *images,const ComplexOperator op,
MagickOffsetType
progress;
+ size_t
+ number_channels;
+
... | https://github.com/ImageMagick/ImageMagick/issues/1597 | ==16842==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x61e000000a80 at pc 0x7fea5bb0c52f bp 0x7fff5c11c590 sp 0x7fff5c11c588
READ of size 4 at 0x61e000000a80 thread T0
#0 0x7fea5bb0c52e in ComplexImages MagickCore/fourier.c:305:45
#1 0x7fea5b3328c1 in CLIListOperatorImages MagickWand/operation.c:38... | null | === https://github.com/ImageMagick/ImageMagick/issues/1597 ===
Title: heap-buffer-overflow in MagickCore/fourier.c:305:45 in ComplexImages
---
Body:
### Prerequisites
- [x] I have written a descriptive issue title
- [x] I have verified that I am using the latest version of ImageMagick
- [x] I have searched [open... | https://nvd.nist.gov/vuln/detail/CVE-2019-13302 |
mruby.cve-2018-12249 | An issue was discovered in mruby 1.4.1. There is a NULL pointer dereference in mrb_class_real because "class BasicObject" is not properly supported in class.c. | https://github.com/mruby/mruby/issues/4037 | https://github.com/mruby/mruby/commit/faa4eaf6803bd11669bc324b4c34e7162286bfa3 | CWE-476 | mruby/mruby | faa4eaf6803bd11669bc324b4c34e7162286bfa3~1 | diff --git a/src/class.c b/src/class.c
index c761f46af1..a9439d7d7d 100644
--- a/src/class.c
+++ b/src/class.c
@@ -1763,10 +1763,10 @@ mrb_class_path(mrb_state *mrb, struct RClass *c)
MRB_API struct RClass*
mrb_class_real(struct RClass* cl)
{
- if (cl == 0)
- return NULL;
+ if (cl == 0) return NULL;
while ((... | https://github.com/mruby/mruby/issues/4037 | ASAN:DEADLYSIGNAL
=================================================================
==26786==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x00010d1fdfbe bp 0x7ffee2a2e4f0 sp 0x7ffee2a2e4b0 T0)
==26786==The signal is caused by a READ memory access.
==26786==Hint: address points to the zero page.
... | null | === https://github.com/mruby/mruby/issues/4037 ===
Title: Null pointer dereference in mrb_class_real
---
Body:
The following input demonstrates a crash:
```ruby
BasicObject.prepend Enumerable
class BasicObject < Class
end
```
ASAN report:
```
ASAN:DEADLYSIGNAL
==============================================... | https://nvd.nist.gov/vuln/detail/CVE-2018-12249 |
md4c.cve-2020-26148 | md_push_block_bytes in md4c.c in md4c 0.4.5 allows attackers to trigger use of uninitialized memory, and cause a denial of service (e.g., assertion failure) via a malformed Markdown document. | https://github.com/mity/md4c/issues/130 | https://github.com/mity/md4c/commit/22ca89a3008966c4316d6b0a158b1a49f9038df0 | CWE-908 | mity/md4c | db7d1c92ec34cae9624be373726e36f22a7d7019 | diff --git a/CHANGELOG.md b/CHANGELOG.md
index 5176d975..d7967d27 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -2,6 +2,16 @@
# MD4C Change Log
+## Next Version (Work in Progress)
+
+Fixes:
+
+* [#130](https://github.com/mity/md4c/issues/130):
+ Fix `ISANYOF` macro, which could provide unexpected results when e... | https://github.com/mity/md4c/issues/130 | ==257142==WARNING: MemorySanitizer: use-of-uninitialized-value
#0 0x7f6d02f3e5ed in md_push_block_bytes /home/fcambus/md4c-release-0.4.5/src/md4c.c:4848:12
#1 0x7f6d02f3e5ed in md_start_new_block /home/fcambus/md4c-release-0.4.5/src/md4c.c:4868:25
#2 0x7f6d02f3e5ed in md_process_line /home/fcambus/md4c-rele... | null | === https://github.com/mity/md4c/issues/130 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/mity/md4c/issues/130] | https://nvd.nist.gov/vuln/detail/CVE-2020-26148 |
matio.cve-2019-20018 | A stack-based buffer over-read was discovered in ReadNextCell in mat5.c in matio 1.5.17. | https://github.com/tbeu/matio/issues/129 | https://github.com/tbeu/matio/commit/65831b7ec829b0ae0ac9d691a2f8fbc2b26af677 | CWE-125 | tbeu/matio | 65831b7ec829b0ae0ac9d691a2f8fbc2b26af677~1 | diff --git a/src/mat5.c b/src/mat5.c
index b76a3316..5e3464e5 100644
--- a/src/mat5.c
+++ b/src/mat5.c
@@ -989,10 +989,26 @@ ReadNextCell( mat_t *mat, matvar_t *matvar )
/* Rank and Dimension */
if ( uncomp_buf[0] == MAT_T_INT32 ) {
int j;
+ size... | https://github.com/tbeu/matio/issues/129 | ./matdump 003-stackoverflow-ReadNextCell-mat51001
InflateRankDims: inflate returned data error
=================================================================
==41935==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7ffdd5e70bb0 at pc 0x7f134197a587 bp 0x7ffdd5e70a20 sp 0x7ffdd5e70a10
READ of size 4 at 0... | null | === https://github.com/tbeu/matio/issues/129 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/tbeu/matio/issues/129] | https://nvd.nist.gov/vuln/detail/CVE-2019-20018 |
njs.cve-2019-13617 | njs through 0.3.3, used in NGINX, has a heap-based buffer over-read in nxt_vsprintf in nxt/nxt_sprintf.c during error handling, as demonstrated by an njs_regexp_literal call that leads to an njs_parser_lexer_error call and then an njs_parser_scope_error call. | https://github.com/nginx/njs/issues/174 | https://github.com/nginx/njs/commit/ee400ea880dc46bb02c4be2564b183c114d4cd42 | CWE-125 | nginx/njs | ee400ea880dc46bb02c4be2564b183c114d4cd42~1 | diff --git a/src/njs_regexp.c b/src/njs_regexp.c
index c488ce09f..038cbfef5 100644
--- a/src/njs_regexp.c
+++ b/src/njs_regexp.c
@@ -333,14 +333,22 @@ njs_regexp_literal(njs_vm_t *vm, njs_parser_t *parser, njs_value_t *value)
goto failed;
case '[':
- while (++p < lexer->end && *p != '... | https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15093, https://github.com/nginx/njs/issues/174 | ==16711==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x61100000039b at pc 0x0000004dc4e2 bp 0x7ffc117a8770 sp 0x7ffc117a7f20
READ of size 217 at 0x61100000039b thread T0
#0 0x4dc4e1 in __asan_memcpy (/home/fuzz/Desktop/fuzzproject/njs/build/njs+0x4dc4e1)
#1 0x521ce2 in nxt_vsprintf /home/fuzz/Deskt... | null | === https://github.com/nginx/njs/issues/174 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/nginx/njs/issues/174] | https://nvd.nist.gov/vuln/detail/CVE-2019-13617 |
njs.cve-2022-27007 | nginx njs 0.7.2 is affected suffers from Use-after-free in njs_function_frame_alloc() when it try to invoke from a restored frame saved with njs_function_frame_save(). | https://github.com/nginx/njs/issues/469 | https://github.com/nginx/njs/commit/ad48705bf1f04b4221a5f5b07715ac48b3160d53, https://github.com/nginx/njs/issues/469 | CWE-416 | nginx/njs | ad48705bf1f04b4221a5f5b07715ac48b3160d53~1 | diff --git a/src/njs_function.c b/src/njs_function.c
index c9d4d9732..78857e01e 100644
--- a/src/njs_function.c
+++ b/src/njs_function.c
@@ -811,9 +811,13 @@ njs_function_frame_save(njs_vm_t *vm, njs_frame_t *frame, u_char *pc)
njs_native_frame_t *active, *native;
*frame = *vm->active_frame;
+
frame->... | https://github.com/nginx/njs/issues/469 | null | ASan (inferred) | === https://github.com/nginx/njs/issues/469 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/nginx/njs/issues/469] | https://nvd.nist.gov/vuln/detail/CVE-2022-27007 |
gpac.cve-2023-4754 | Out-of-bounds Write in GitHub repository gpac/gpac prior to 2.3-DEV. | https://huntr.dev/bounties/b7ed24ad-7d0b-40b7-8f4d-3c18a906620c | https://github.com/gpac/gpac/commit/7e2e92feb1b30fac1d659f6620d743b5a188ffe0, https://huntr.dev/bounties/b7ed24ad-7d0b-40b7-8f4d-3c18a906620c | CWE-787 | gpac/gpac | 7e2e92feb1b30fac1d659f6620d743b5a188ffe0~1 | diff --git a/src/scene_manager/swf_parse.c b/src/scene_manager/swf_parse.c
index f4b974aab5..2afa80c3e8 100644
--- a/src/scene_manager/swf_parse.c
+++ b/src/scene_manager/swf_parse.c
@@ -1426,7 +1426,7 @@ static GF_Err swf_def_font(SWFReader *read, u32 revision)
count = swf_get_16(read);
ft->nbGlyphs = count / 2;... | https://huntr.dev/bounties/b7ed24ad-7d0b-40b7-8f4d-3c18a906620c | null | ASan (inferred) | null | https://nvd.nist.gov/vuln/detail/CVE-2023-4754 |
gpac.cve-2021-32437 | The gf_hinter_finalize function in GPAC 1.0.1 allows attackers to cause a denial of service (NULL pointer dereference) via a crafted file in the MP4Box command. | https://github.com/gpac/gpac/issues/1770 | https://github.com/gpac/gpac/commit/1653f31cf874eb6df964bea88d58d8e9b98b485e | CWE-476 | gpac/gpac | 1653f31cf874eb6df964bea88d58d8e9b98b485e~1 | diff --git a/src/media_tools/isom_hinter.c b/src/media_tools/isom_hinter.c
index c05d38ccca..9bff67767a 100644
--- a/src/media_tools/isom_hinter.c
+++ b/src/media_tools/isom_hinter.c
@@ -1233,7 +1233,7 @@ GF_Err gf_hinter_finalize(GF_ISOFile *file, GF_SDP_IODProfile IOD_Profile, u32 b
esd = gf_isom_get_esd(file, sce... | https://github.com/gpac/gpac/issues/1770 | AddressSanitizer:DEADLYSIGNAL
=================================================================
==1042==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x7fc3d4e76d0b bp 0x7ffd390b09a0 sp 0x7ffd390ae160 T0)
==1042==The signal is caused by a READ memory access.
==1042==Hint: address points to the zer... | null | === https://github.com/gpac/gpac/issues/1770 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/gpac/gpac/issues/1770] | https://nvd.nist.gov/vuln/detail/CVE-2021-32437 |
gpac.cve-2023-4755 | Use After Free in GitHub repository gpac/gpac prior to 2.3-DEV. | https://huntr.dev/bounties/463474b7-a4e8-42b6-8b30-e648a77ee6b3 | https://github.com/gpac/gpac/commit/895ac12da168435eb8db3f96978ffa4c69d66c3a, https://huntr.dev/bounties/463474b7-a4e8-42b6-8b30-e648a77ee6b3 | CWE-416 | gpac/gpac | 895ac12da168435eb8db3f96978ffa4c69d66c3a~1 | diff --git a/src/filters/mux_isom.c b/src/filters/mux_isom.c
index 4044ef11fc..e9bc42231f 100644
--- a/src/filters/mux_isom.c
+++ b/src/filters/mux_isom.c
@@ -3991,6 +3991,7 @@ static GF_Err mp4_mux_configure_pid(GF_Filter *filter, GF_FilterPid *pid, Bool i
TrackWriter *tkw = gf_filter_pid_get_udta(pid);
if (tkw)... | https://huntr.dev/bounties/463474b7-a4e8-42b6-8b30-e648a77ee6b3 | null | null | null | https://nvd.nist.gov/vuln/detail/CVE-2023-4755 |
gpac.cve-2021-32440 | The Media_RewriteODFrame function in GPAC 1.0.1 allows attackers to cause a denial of service (NULL pointer dereference) via a crafted file in the MP4Box command. | https://github.com/gpac/gpac/issues/1772 | https://github.com/gpac/gpac/commit/f0ba83717b6e4d7a15a1676d1fe06152e199b011 | CWE-476 | gpac/gpac | f0ba83717b6e4d7a15a1676d1fe06152e199b011~1 | diff --git a/src/isomedia/media_odf.c b/src/isomedia/media_odf.c
index 33c41a36f1..76ecf9d135 100644
--- a/src/isomedia/media_odf.c
+++ b/src/isomedia/media_odf.c
@@ -131,8 +131,9 @@ GF_Err Media_RewriteODFrame(GF_MediaBox *mdia, GF_ISOSample *sample)
//then rewrite the ESDesc
j=0;
while ((ref = (GF_ES_I... | https://github.com/gpac/gpac/issues/1772 | AddressSanitizer:DEADLYSIGNAL
=================================================================
==29303==ERROR: AddressSanitizer: SEGV on unknown address 0x602000021b70 (pc 0x7fc90a84caa9 bp 0x7ffee2653e40 sp 0x7ffee2653da0 T0)
==29303==The signal is caused by a READ memory access.
#0 0x7fc90a84caa8 in Media_Rewrit... | null | === https://github.com/gpac/gpac/issues/1772 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/gpac/gpac/issues/1772] | https://nvd.nist.gov/vuln/detail/CVE-2021-32440 |
gpac.cve-2023-42298 | An issue in GPAC GPAC v.2.2.1 and before allows a local attacker to cause a denial of service via the Q_DecCoordOnUnitSphere function of file src/bifs/unquantize.c. | null | https://github.com/gpac/gpac/pull/2568/changes/16c4fafc2881112eba7051cac48f922eb2b94e06 | CWE-190 | gpac/gpac | 941a0891b989f5ad86b739cfb12c84b7e62e8ee4 | diff --git a/src/bifs/unquantize.c b/src/bifs/unquantize.c
index 008a830982..f0a124cb55 100644
--- a/src/bifs/unquantize.c
+++ b/src/bifs/unquantize.c
@@ -284,7 +284,7 @@ GF_Err Q_DecCoordOnUnitSphere(GF_BifsDecoder *codec, GF_BitStream *bs, u32 NbBit
s32 value;
Fixed tang[4], delta;
s32 dir;
- if (NbBits>32) ret... | https://github.com/gpac/gpac/issues/2567 | bifs/unquantize.c:298:43: runtime error: shift exponent 4294967295 is too large for 32-bit type 'int'
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior bifs/unquantize.c:298:43 in | null | === https://github.com/gpac/gpac/issues/2567 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/gpac/gpac/issues/2567] | https://nvd.nist.gov/vuln/detail/CVE-2023-42298 |
libredwg.cve-2020-21817 | A null pointer dereference issue exists in GNU LibreDWG 0.10.2641 via htmlescape ../../programs/escape.c:29. which causes a denial of service (application crash). | https://github.com/LibreDWG/libredwg/issues/182#issue-547887727 | https://github.com/LibreDWG/libredwg/issues/182#issue-547887727 | CWE-476 | LibreDWG/libredwg | null | null | https://github.com/LibreDWG/libredwg/issues/182#issue-547887727 | null | null | === https://github.com/LibreDWG/libredwg/issues/182#issue-547887727 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/LibreDWG/libredwg/issues/182] | https://nvd.nist.gov/vuln/detail/CVE-2020-21817 |
gpac.cve-2023-41000 | GPAC through 2.2.1 has a use-after-free vulnerability in the function gf_bifs_flush_command_list in bifs/memory_decoder.c. | https://github.com/gpac/gpac/issues/2550 | https://github.com/gpac/gpac/commit/0018b5e4e07a1465287e7dff69b387929f5a75fa | CWE-416 | gpac/gpac | 0018b5e4e07a1465287e7dff69b387929f5a75fa~1 | diff --git a/src/bifs/memory_decoder.c b/src/bifs/memory_decoder.c
index faf35c16d9..eed7e3fd12 100644
--- a/src/bifs/memory_decoder.c
+++ b/src/bifs/memory_decoder.c
@@ -902,6 +902,8 @@ GF_Err BM_ParseCommand(GF_BifsDecoder *codec, GF_BitStream *bs, GF_List *com_lis
GF_SceneGraph *cur_graph = codec->current_graph;
... | https://github.com/gpac/gpac/issues/2550 | AddressSanitizer:DEADLYSIGNAL
=================================================================
==841115==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x7fae75bd843e bp 0x7ffc7386e7a0 sp 0x7ffc7386e770 T0)
==841115==The signal is caused by a READ memory access.
==841115==Hint: address points to t... | ASan (inferred) | === https://github.com/gpac/gpac/issues/2550 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/gpac/gpac/issues/2550] | https://nvd.nist.gov/vuln/detail/CVE-2023-41000 |
php.cve-2018-12882 | exif_read_from_impl in ext/exif/exif.c in PHP 7.2.x through 7.2.7 allows attackers to trigger a use-after-free (in exif_read_from_file) because it closes a stream that it is not responsible for closing. The vulnerable code is reachable through the PHP exif_read_data function. | null | https://bugs.php.net/bug.php?id=76409 | CWE-416 | null | null | null | https://bugs.php.net/bug.php?id=76409 | null | ASan (inferred) | null | https://nvd.nist.gov/vuln/detail/CVE-2018-12882 |
exiv2.cve-2018-17229 | Exiv2::d2Data in types.cpp in Exiv2 v0.26 allows remote attackers to cause a denial of service (heap-based buffer overflow) via a crafted image file. | https://github.com/Exiv2/exiv2/issues/453 | https://github.com/Exiv2/exiv2/commit/afb98cbc6e288dc8ea75f3394a347fb9b37abc55 | CWE-787 | Exiv2/exiv2 | afb98cbc6e288dc8ea75f3394a347fb9b37abc55~1 | diff --git a/src/tiffimage.cpp b/src/tiffimage.cpp
index 8731449cd3..a69c7afd5b 100644
--- a/src/tiffimage.cpp
+++ b/src/tiffimage.cpp
@@ -191,7 +191,7 @@ namespace Exiv2 {
Exiv2::ExifKey key("Exif.Image.InterColorProfile");
Exiv2::ExifData::iterator pos = exifData_.findKey(key);
... | https://github.com/Exiv2/exiv2/issues/453 | ==29719==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60200000edda at pc 0x7f380fbee411 bp 0x7ffe90b43600 sp 0x7ffe90b435f0
WRITE of size 1 at 0x60200000edda thread T0
#0 0x7f380fbee410 in Exiv2::d2Data(unsigned char*, double, Exiv2::ByteOrder) /home/marsman/Desktop/crashana/exiv2/exiv2-b6a8d39613a286... | null | === https://github.com/Exiv2/exiv2/issues/453 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/Exiv2/exiv2/issues/453] | https://nvd.nist.gov/vuln/detail/CVE-2018-17229 |
libredwg.cve-2021-42585 | A heap buffer overflow was discovered in copy_compressed_bytes in decode_r2007.c in dwgread before 0.12.4 via a crafted dwg file. | https://github.com/LibreDWG/libredwg/issues/351 | https://github.com/LibreDWG/libredwg/commit/ecf5183d8b3b286afe2a30021353b7116e0208dd | CWE-787 | LibreDWG/libredwg | ecf5183d8b3b286afe2a30021353b7116e0208dd~1 | diff --git a/src/decode_r2007.c b/src/decode_r2007.c
index 3b5af4c4b2..c1e270fc4b 100644
--- a/src/decode_r2007.c
+++ b/src/decode_r2007.c
@@ -923,7 +923,8 @@ read_sections_map (Bit_Chain *dat, int64_t size_comp, int64_t size_uncomp,
#if 1
/* compressed */
if (section->data_size > 10 * dat->size
- ... | https://github.com/LibreDWG/libredwg/issues/351 | =================================================================
==9485==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x6020000002e3 at pc 0x000000ca5f2b bp 0x7ffdbc6926d0 sp 0x7ffdbc6926c8
WRITE of size 8 at 0x6020000002e3 thread T0
#0 0xca5f2a in memcpy /usr/include/x86_64-linux-gnu/bits/string3.h:53... | null | === https://github.com/LibreDWG/libredwg/issues/351 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/LibreDWG/libredwg/issues/351] | https://nvd.nist.gov/vuln/detail/CVE-2021-42585 |
gpac.cve-2023-4681 | NULL Pointer Dereference in GitHub repository gpac/gpac prior to 2.3-DEV. | https://huntr.dev/bounties/d67c5619-ab36-41cc-93b7-04828e25f60e | https://github.com/gpac/gpac/commit/4bac19ad854159b21ba70d8ab7c4e1cd1db8ea1c, https://huntr.dev/bounties/d67c5619-ab36-41cc-93b7-04828e25f60e | CWE-476 | gpac/gpac | 4bac19ad854159b21ba70d8ab7c4e1cd1db8ea1c~1 | diff --git a/src/filters/dasher.c b/src/filters/dasher.c
index 2619d2291c..bc768804fd 100644
--- a/src/filters/dasher.c
+++ b/src/filters/dasher.c
@@ -8387,6 +8387,9 @@ static GF_Err dasher_process(GF_Filter *filter)
u32 num_ready=0, num_blocked=0;
for (i=0; i<count; i++) {
GF_DashStream *ds = gf_list_get(ctx... | null | null | null | null | https://nvd.nist.gov/vuln/detail/CVE-2023-4681 |
exiv2.cve-2018-17230 | Exiv2::ul2Data in types.cpp in Exiv2 v0.26 allows remote attackers to cause a denial of service (heap-based buffer overflow) via a crafted image file. | https://github.com/Exiv2/exiv2/issues/455 | https://github.com/Exiv2/exiv2/commit/afb98cbc6e288dc8ea75f3394a347fb9b37abc55 | CWE-787 | Exiv2/exiv2 | afb98cbc6e288dc8ea75f3394a347fb9b37abc55~1 | diff --git a/src/tiffimage.cpp b/src/tiffimage.cpp
index 8731449cd3..a69c7afd5b 100644
--- a/src/tiffimage.cpp
+++ b/src/tiffimage.cpp
@@ -191,7 +191,7 @@ namespace Exiv2 {
Exiv2::ExifKey key("Exif.Image.InterColorProfile");
Exiv2::ExifData::iterator pos = exifData_.findKey(key);
... | https://github.com/Exiv2/exiv2/issues/455 | ==29742==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60300000cf59 at pc 0x7f79f092888f bp 0x7ffe74e0c920 sp 0x7ffe74e0c910
WRITE of size 1 at 0x60300000cf59 thread T0
#0 0x7f79f092888e in Exiv2::ul2Data(unsigned char*, unsigned int, Exiv2::ByteOrder) /home/marsman/Desktop/crashana/exiv2/exiv2-b6a8d39... | null | === https://github.com/Exiv2/exiv2/issues/455 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/Exiv2/exiv2/issues/455] | https://nvd.nist.gov/vuln/detail/CVE-2018-17230 |
libredwg.cve-2023-36273 | LibreDWG v0.12.5 was discovered to contain a heap buffer overflow via the function bit_calc_CRC at bits.c. | https://github.com/LibreDWG/libredwg/issues/677#BUG1 | null | CWE-787 | LibreDWG/libredwg | null | null | https://github.com/LibreDWG/libredwg/issues/677#BUG1 | AddressSanitizer:DEADLYSIGNAL
=================================================================
==78==ERROR: AddressSanitizer: SEGV on unknown address 0x62100a3d71b3 (pc 0x563f38494cff bp 0x7ffd51ea1fa8 sp 0x7ffd51ea09e0 T0)
==78==The signal is caused by a READ memory access.
#0 0x563f38494cfe in bit_calc_CRC /libr... | null | === https://github.com/LibreDWG/libredwg/issues/677#BUG1 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/LibreDWG/libredwg/issues/677] | https://nvd.nist.gov/vuln/detail/CVE-2023-36273 |
gpac.cve-2024-50665 | gpac 2.4 contains a SEGV at src/isomedia/drm_sample.c:1562:96 in isom_cenc_get_sai_by_saiz_saio in MP4Box. | https://github.com/gpac/gpac/issues/2987 | https://github.com/Mu-L/gpac/commit/ba8778cec7bdf5dbb722b4f0fec68e00b796d68e | CWE-476 | Mu-L/gpac | ba8778cec7bdf5dbb722b4f0fec68e00b796d68e~1 | diff --git a/src/isomedia/drm_sample.c b/src/isomedia/drm_sample.c
index a2f69d7627..d9580d3094 100644
--- a/src/isomedia/drm_sample.c
+++ b/src/isomedia/drm_sample.c
@@ -1559,7 +1559,7 @@ static GF_Err isom_cenc_get_sai_by_saiz_saio(GF_MediaBox *mdia, u32 sampleNumber
}
if ((nb_saio==1) && !saio_cenc->total_size... | https://github.com/gpac/gpac/issues/2987 | AddressSanitizer:DEADLYSIGNAL
=================================================================
==1963314==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x7f4f7ad3f484 bp 0x7ffd649eed20 sp 0x7ffd649eebc0 T0)
==1963314==The signal is caused by a READ memory access.
==1963314==Hint: address points t... | null | === https://github.com/gpac/gpac/issues/2987 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/gpac/gpac/issues/2987] | https://nvd.nist.gov/vuln/detail/CVE-2024-50665 |
gpac.cve-2023-46001 | Buffer Overflow vulnerability in gpac MP4Box v.2.3-DEV-rev573-g201320819-master allows a local attacker to cause a denial of service via the gpac/src/isomedia/isom_read.c:2807:51 function in gf_isom_get_user_data. | https://github.com/gpac/gpac/issues/2629 | https://github.com/gpac/gpac/commit/e79b0cf7e72404750630bc01340e999f3940dbc4, https://github.com/gpac/gpac/issues/2629 | CWE-120 | gpac/gpac | e79b0cf7e72404750630bc01340e999f3940dbc4~1 | diff --git a/src/isomedia/isom_read.c b/src/isomedia/isom_read.c
index 5a8109e2de..60bded7e77 100644
--- a/src/isomedia/isom_read.c
+++ b/src/isomedia/isom_read.c
@@ -2804,7 +2804,7 @@ GF_Err gf_isom_get_user_data(GF_ISOFile *movie, u32 trackNumber, u32 UserDataTyp
i=0;
while ((map = (GF_UserDataMap*)gf_list_enum... | https://github.com/gpac/gpac/issues/2629 | AddressSanitizer:DEADLYSIGNAL
=================================================================
==4066570==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x7ffff5cc2ed0 bp 0x7ffffffeaf40 sp 0x7ffffffea6d8 T0)
==4066570==The signal is caused by a READ memory access.
==4066570==Hint: address points t... | null | === https://github.com/gpac/gpac/issues/2629 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/gpac/gpac/issues/2629] | https://nvd.nist.gov/vuln/detail/CVE-2023-46001 |
upx.cve-2017-15056 | p_lx_elf.cpp in UPX 3.94 mishandles ELF headers, which allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a crafted binary file, as demonstrated by an Invalid Pointer Read in PackLinuxElf64::unpack(). | null | https://github.com/upx/upx/commit/ef336dbcc6dc8344482f8cf6c909ae96c3286317 | CWE-476 | upx/upx | ef336dbcc6dc8344482f8cf6c909ae96c3286317~1 | diff --git a/src/p_lx_elf.cpp b/src/p_lx_elf.cpp
index e6336425c4..9272cf9bac 100644
--- a/src/p_lx_elf.cpp
+++ b/src/p_lx_elf.cpp
@@ -245,8 +245,15 @@ PackLinuxElf32::PackLinuxElf32help1(InputFile *f)
sz_phdrs = 0;
return;
}
+ if (0==e_phnum) throwCantUnpack("0==e_phnum");
e_phoff = get_... | https://github.com/upx/upx/issues/128 | ==18371==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x61a00000bf10 at pc 0x00000068ab40 bp 0x7ffcdf76a020 sp 0x7ffcdf76a018
READ of size 4 at 0x61a00000bf10 thread T0
#0 0x68ab3f in get_le32(void const*) /home/bm/Desktop/Origin/upx/src/./bele.h:164:12
#1 0x68ab3f in N_BELE_RTP::LEPolicy::get32(voi... | null | === https://github.com/upx/upx/issues/128 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/upx/upx/issues/128] | https://nvd.nist.gov/vuln/detail/CVE-2017-15056 |
imagemagick.cve-2019-13311 | ImageMagick 7.0.8-50 Q16 has memory leaks at AcquireMagickMemory because of a wand/mogrify.c error. | https://github.com/ImageMagick/ImageMagick/issues/1623 | https://github.com/ImageMagick/ImageMagick/commit/4a334bbf5584de37c6f5a47c380a531c8c4b140a, https://github.com/ImageMagick/ImageMagick/issues/1623, https://github.com/ImageMagick/ImageMagick6/commit/bb812022d0bc12107db215c981cab0b1ccd73d91 | CWE-401 | ImageMagick/ImageMagick | 4a334bbf5584de37c6f5a47c380a531c8c4b140a~1 | diff --git a/MagickWand/mogrify.c b/MagickWand/mogrify.c
index 150b6792304..9f7eb6b551d 100644
--- a/MagickWand/mogrify.c
+++ b/MagickWand/mogrify.c
@@ -7824,6 +7824,9 @@ WandExport MagickBooleanType MogrifyImageList(ImageInfo *image_info,
clut_image=RemoveFirstImageFromList(images);
if (clut_... | https://github.com/ImageMagick/ImageMagick/issues/1623 | ==26664==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 13504 byte(s) in 1 object(s) allocated from:
#0 0x4e5397 in malloc (install/bin/magick+0x4e5397)
#1 0x7f121156ec16 in AcquireMagickMemory MagickCore/memory.c:478:10
#2 0x7f121151bb54 in AcquireCriticalMemory ./MagickCore/memory-private.h:6... | null | === https://github.com/ImageMagick/ImageMagick/issues/1623 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/ImageMagick/ImageMagick/issues/1623] | https://nvd.nist.gov/vuln/detail/CVE-2019-13311 |
md4c.cve-2018-11545 | md4c 0.2.5 has a heap-based buffer overflow in md_merge_lines because md_is_link_label mishandles the case of a link label composed solely of backslash escapes. | null | null | CWE-787 | mity/md4c | null | null | https://github.com/mity/md4c/issues/39 | =================================================================
==21464==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x6040000000b1 at pc 0x00000054ff84 bp 0x7fff500be8d0 sp 0x7fff500be8c8
WRITE of size 1 at 0x6040000000b1 thread T0
#0 0x54ff83 in md_merge_lines /home/ubuntu/fuzz/test/md4... | null | === https://github.com/mity/md4c/issues/39 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/mity/md4c/issues/39] | https://nvd.nist.gov/vuln/detail/CVE-2018-11545 |
imagemagick.cve-2019-13297 | ImageMagick 7.0.8-50 Q16 has a heap-based buffer over-read at MagickCore/threshold.c in AdaptiveThresholdImage because a height of zero is mishandled. | https://github.com/ImageMagick/ImageMagick/issues/1609 | https://github.com/ImageMagick/ImageMagick/commit/604588fc35c7585abb7a9e71f69bb82e4389fefc, https://github.com/ImageMagick/ImageMagick/issues/1609, https://github.com/ImageMagick/ImageMagick6/commit/35c7032723d85eee7318ff6c82f031fa2666b773 | CWE-125 | ImageMagick/ImageMagick | 604588fc35c7585abb7a9e71f69bb82e4389fefc~1 | diff --git a/MagickCore/threshold.c b/MagickCore/threshold.c
index f9412bb52e5..0c3a488d7e3 100644
--- a/MagickCore/threshold.c
+++ b/MagickCore/threshold.c
@@ -212,7 +212,7 @@ MagickExport Image *AdaptiveThresholdImage(const Image *image,
threshold_image=CloneImage(image,0,0,MagickTrue,exception);
if (threshold_... | https://github.com/ImageMagick/ImageMagick/issues/1609 | ==22189==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x620000001090 at pc 0x7fd7e5dd4be2 bp 0x7ffd816c3a30 sp 0x7ffd816c3a28
READ of size 4 at 0x620000001090 thread T0
#0 0x7fd7e5dd4be1 in AdaptiveThresholdImage MagickCore/threshold.c:328:11
#1 0x7fd7e5386cb6 in CLISimpleOperatorImage MagickWand/op... | null | === https://github.com/ImageMagick/ImageMagick/issues/1609 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/ImageMagick/ImageMagick/issues/1609] | https://nvd.nist.gov/vuln/detail/CVE-2019-13297 |
md4c.cve-2021-30027 | md_analyze_line in md4c.c in md4c 0.4.7 allows attackers to trigger use of uninitialized memory, and cause a denial of service via a malformed Markdown document. | https://github.com/mity/md4c/issues/155 | https://github.com/mity/md4c/commit/4fc808d8fe8d8904f8525bb4231d854f45e23a19 | CWE-908 | mity/md4c | 4fc808d8fe8d8904f8525bb4231d854f45e23a19~1 | diff --git a/CHANGELOG.md b/CHANGELOG.md
index 649cf1b1..1067a675 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -21,6 +21,9 @@ Fixes:
correctly, even when the blocks are nested at the same line in a complicated
ways.
+ * [#155](https://github.com/mity/md4c/issues/155):
+ Avoid reading 1 character beyond t... | https://github.com/mity/md4c/issues/155 | ==2793660==WARNING: MemorySanitizer: use-of-uninitialized-value
#0 0x7f021124c622 in md_analyze_line /home/bsdboy/md/md4c-release-0.4.7/src/md4c.c:5985:12
#1 0x7f021122ee27 in md_process_doc /home/bsdboy/md/md4c-release-0.4.7/src/md4c.c:6254:9
#2 0x7f021122dca5 in md_parse /home/bsdboy/md/md4c-release-0.4.7... | null | === https://github.com/mity/md4c/issues/155 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/mity/md4c/issues/155] | https://nvd.nist.gov/vuln/detail/CVE-2021-30027 |
libredwg.cve-2020-23861 | A heap-based buffer overflow vulnerability exists in LibreDWG 0.10.1 via the read_system_page function at libredwg-0.10.1/src/decode_r2007.c:666:5, which causes a denial of service by submitting a dwg file. | https://github.com/LibreDWG/libredwg/issues/248 | https://github.com/LibreDWG/libredwg/issues/248 | CWE-787 | LibreDWG/libredwg | null | null | https://github.com/LibreDWG/libredwg/issues/248 | ==2593==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x602000000031 at pc 0x0000004e7e12 bp 0x7ffd91a390c0 sp 0x7ffd91a38870
READ of size 96 at 0x602000000031 thread T0
#0 0x4e7e11 in __asan_memcpy /root/Download/llvm-8.0.0.src/projects/compiler-rt-8.0.0.src/lib/asan/asan_interceptors_memintrinsics.cc:2... | null | === https://github.com/LibreDWG/libredwg/issues/248 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/LibreDWG/libredwg/issues/248] | https://nvd.nist.gov/vuln/detail/CVE-2020-23861 |
imagemagick.cve-2022-0284 | A heap-based-buffer-over-read flaw was found in ImageMagick's GetPixelAlpha() function of 'pixel-accessor.h'. This vulnerability is triggered when an attacker passes a specially crafted Tagged Image File Format (TIFF) image to convert it into a PICON file format. This issue can potentially lead to a denial of service a... | https://github.com/ImageMagick/ImageMagick/issues/4729 | https://bugzilla.redhat.com/show_bug.cgi?id=2045943, https://github.com/ImageMagick/ImageMagick/commit/e50f19fd73c792ebe912df8ab83aa51a243a3da7 | CWE-125 | ImageMagick/ImageMagick | e50f19fd73c792ebe912df8ab83aa51a243a3da7~1 | diff --git a/coders/xpm.c b/coders/xpm.c
index 782ed732544..5f73df8bca4 100644
--- a/coders/xpm.c
+++ b/coders/xpm.c
@@ -773,7 +773,7 @@ static MagickBooleanType WritePICONImage(const ImageInfo *image_info,
break;
for (x=0; x < (ssize_t) picon->columns; x++)
{
- if ... | https://access.redhat.com/security/cve/CVE-2022-0284, https://bugzilla.redhat.com/show_bug.cgi?id=2045943, https://github.com/ImageMagick/ImageMagick/issues/4729 | ==46632==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x62a00000b540 at pc 0x7f7e88ca3257 bp 0x7fffdb9f7370 sp 0x7fffdb9f7360
READ of size 4 at 0x62a00000b540 thread T0
#0 0x7f7e88ca3256 in GetPixelAlpha MagickCore/pixel-accessor.h:59
#1 0x7f7e88ca763e in WritePICONImage coders/xpm.c:807
#2 0x7f... | null | === https://github.com/ImageMagick/ImageMagick/issues/4729 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/ImageMagick/ImageMagick/issues/4729] | https://nvd.nist.gov/vuln/detail/CVE-2022-0284 |
gpac.cve-2023-4758 | Buffer Over-read in GitHub repository gpac/gpac prior to 2.3-DEV. | https://huntr.dev/bounties/2f496261-1090-45ac-bc89-cc93c82090d6 | https://github.com/gpac/gpac/commit/193633b1648582444fc99776cd741d7ba0125e86, https://github.com/gpac/gpac/commit/3eeaead5369c167c6de9952396ffc398ba659b45 | CWE-125, CWE-126 | gpac/gpac | cc95b16 | diff --git a/src/media_tools/avilib.c b/src/media_tools/avilib.c
index 7cdca7d..66e9d0c 100644
--- a/src/media_tools/avilib.c
+++ b/src/media_tools/avilib.c
@@ -1804,6 +1804,7 @@ int AVI_close(avi_t *AVI)
#define ERR_EXIT(x) \
{ \
+ if (hdrl_data) { gf_free(hdrl_data); hdrl_data=NULL; }\
AVI_close(AVI); \
... | https://huntr.dev/bounties/2f496261-1090-45ac-bc89-cc93c82090d6 | null | null | null | https://nvd.nist.gov/vuln/detail/CVE-2023-4758 |
libplist.cve-2017-5545 | The main function in plistutil.c in libimobiledevice libplist through 1.12 allows attackers to obtain sensitive information from process memory or cause a denial of service (buffer over-read) via Apple Property List data that is too short. | null | https://github.com/libimobiledevice/libplist/commit/eb929319388cb7f48141b3fde062a8392fe4c00d | CWE-125 | libimobiledevice/libplist | 7a28a14 | printf("ERROR: Input file is too small to contain valid plist data.\n");
diff --git a/tools/plistutil.c b/tools/plistutil.c
index 6451604..49d05aa 100644
--- a/tools/plistutil.c
+++ b/tools/plistutil.c
@@ -129,6 +129,12 @@ int main(int argc, char *argv[])
}
stat(options->in_file, &filestats);
+ i... | https://github.com/libimobiledevice/libplist/commit/7391a506352c009fe044dead7baad9e22dd279ee, https://github.com/libimobiledevice/libplist/issues/87 | ==21852== ERROR: AddressSanitizer: heap-buffer-overflow on address 0xb5e007d7 at pc 0x804a78c bp 0xbf815888 sp 0xbf81587c
READ of size 1 at 0xb5e007d7 thread T0
#0 0x804a78b in main /home/b/asan/libplist/tools/plistutil.c:137
#1 0xb5f7fa82 (/lib/i386-linux-gnu/libc.so.6+0x19a82)
#2 0x804ad45 in _start (/hom... | null | === https://github.com/libimobiledevice/libplist/issues/87 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/libimobiledevice/libplist/issues/87] | https://nvd.nist.gov/vuln/detail/CVE-2017-5545 |
libredwg.cve-2020-21818 | A heap based buffer overflow vulnerability exists in GNU LibreDWG 0.10.2641 via htmlescape ../../programs/escape.c:48. | https://github.com/LibreDWG/libredwg/issues/182#issuecomment-572891053 | null | CWE-787 | LibreDWG/libredwg | null | null | https://github.com/LibreDWG/libredwg/issues/182#issuecomment-572891053 | null | null | === https://github.com/LibreDWG/libredwg/issues/182#issuecomment-572891053 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/LibreDWG/libredwg/issues/182] | https://nvd.nist.gov/vuln/detail/CVE-2020-21818 |
libredwg.cve-2022-33034 | LibreDWG v0.12.4.4608 was discovered to contain a stack overflow via the function copy_bytes at decode_r2007.c. | https://github.com/LibreDWG/libredwg/issues/494 | null | CWE-787 | LibreDWG/libredwg | null | null | https://github.com/LibreDWG/libredwg/issues/494 | ==9543==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7fffffffc8f0 at pc 0x0000007257bb bp 0x7fffffffbc90 sp 0x7fffffffbc88
WRITE of size 1 at 0x7fffffffc8f0 thread T0
#0 0x7257ba in copy_bytes /testcase/libredwg/src/decode_r2007.c:228:12
#1 0x7257ba in decompress_r2007 /testcase/libredwg/src/deco... | null | === https://github.com/LibreDWG/libredwg/issues/494 ===
Title: stack-buffer-overflow exists in the function copy_bytes in decode_r2007.c
---
Body:
### system info
Ubuntu x86_64, clang 6.0, dwg2dxf([0.12.4.4608](https://github.com/LibreDWG/libredwg/releases/tag/0.12.4.4608))
### Command line
./programs/dwg2dxf -b... | https://nvd.nist.gov/vuln/detail/CVE-2022-33034 |
imagemagick.cve-2019-13298 | ImageMagick 7.0.8-50 Q16 has a heap-based buffer overflow at MagickCore/pixel-accessor.h in SetPixelViaPixelInfo because of a MagickCore/enhance.c error. | https://github.com/ImageMagick/ImageMagick/issues/1611 | https://github.com/ImageMagick/ImageMagick/commit/d4fc44b58a14f76b1ac997517d742ee12c9dc5d3, https://github.com/ImageMagick/ImageMagick/issues/1611 | CWE-787 | ImageMagick/ImageMagick | d4fc44b58a14f76b1ac997517d742ee12c9dc5d3~1 | diff --git a/MagickCore/enhance.c b/MagickCore/enhance.c
index ed3202757e2..35346890a40 100644
--- a/MagickCore/enhance.c
+++ b/MagickCore/enhance.c
@@ -1973,7 +1973,7 @@ MagickExport Image *EnhanceImage(const Image *image,ExceptionInfo *exception)
pixel.black=((aggregate.black+total_weight/2.0)/total_weight... | https://github.com/ImageMagick/ImageMagick/issues/1611 | =================================================================
==6928==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x7faaff40fa80 at pc 0x7fab0dddcb45 bp 0x7fff3e3ee2b0 sp 0x7fff3e3ee2a8
WRITE of size 4 at 0x7faaff40fa80 thread T0
#0 0x7fab0dddcb44 in SetPixelViaPixelInfo ./MagickCore/pixel-accessor... | null | === https://github.com/ImageMagick/ImageMagick/issues/1611 ===
Title: heap-buffer-overflow at MagickCore/pixel-accessor.h:804:56 in SetPixelViaPixelInfo
---
Body:
### Prerequisites
- [x] I have written a descriptive issue title
- [x] I have verified that I am using the latest version of ImageMagick
- [x] I have ... | https://nvd.nist.gov/vuln/detail/CVE-2019-13298 |
imagemagick.cve-2017-18022 | In ImageMagick 7.0.7-12 Q16, there are memory leaks in MontageImageCommand in MagickWand/montage.c. | https://github.com/ImageMagick/ImageMagick/issues/904 | null | CWE-772 | ImageMagick/ImageMagick | null | null | https://github.com/ImageMagick/ImageMagick/issues/904 | ==116829==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 4712 byte(s) in 1 object(s) allocated from:
#0 0x4b9ad3 in malloc (/usr/local/bin/magick+0x4b9ad3)
#1 0x7ff9bd11fb76 in AcquireCriticalMemory /home/ubuntu/ImageMagick/./MagickCore/memory-private.h:57:10
#2 0x7ff9bd11fb76 in CloneMontageIn... | null | === https://github.com/ImageMagick/ImageMagick/issues/904 ===
Title: memory leaks
---
Body:
system：ubuntu 14.04 64
ubuntu@ubuntu:~/fuzz_py$ magick -version
Version: ImageMagick 7.0.7-12 Q16 x86_64 2017-12-19 http://www.imagemagick.org
Copyright: © 1999-2017 ImageMagick Studio LLC
License: http://www.imagemagick... | https://nvd.nist.gov/vuln/detail/CVE-2017-18022 |
yara.cve-2016-10211 | libyara/grammar.y in YARA 3.5.0 allows remote attackers to cause a denial of service (use-after-free and application crash) via a crafted rule that is mishandled in the yr_parser_lookup_loop_variable function. | https://github.com/VirusTotal/yara/issues/575 | https://github.com/VirusTotal/yara/commit/890c3f850293176c0e996a602ffa88b315f4e98f, https://github.com/VirusTotal/yara/issues/575 | CWE-416 | VirusTotal/yara | 890c3f850293176c0e996a602ffa88b315f4e98f~1 | diff --git a/libyara/grammar.c b/libyara/grammar.c
index 9ab6dfe78e..6e5c46e5e1 100644
--- a/libyara/grammar.c
+++ b/libyara/grammar.c
@@ -546,16 +546,16 @@ union yyalloc
/* YYFINAL -- State number of the termination state. */
#define YYFINAL 2
/* YYLAST -- Last index in YYTABLE. */
-#define YYLAST 408
+#define... | https://github.com/VirusTotal/yara/issues/575 | ==17551==ERROR: AddressSanitizer: heap-use-after-free on address 0x60200000ed50 at pc 0x000000425ff6 bp 0x7fff57ebe190 sp 0x7fff57ebd920
READ of size 1 at 0x60200000ed50 thread T0
#0 0x425ff5 in __interceptor_strcmp /home/development/llvm/3.9.0/final/llvm.src/projects/compiler-rt/lib/asan/../sanitizer_common/saniti... | ASan (inferred) | === https://github.com/VirusTotal/yara/issues/575 ===
Title: Use After Free in yr_parser_lookup_loop_variable()
---
Body:
**Use After Free in yr_parser_lookup_loop_variable()**
Tested on latest Git HEAD: 779b9a77aa4377152a5cba031255029afb0c19a5
[Payload](https://github.com/VirusTotal/yara/files/633374/yara_uaf.... | https://nvd.nist.gov/vuln/detail/CVE-2016-10211 |
mruby.cve-2022-0570 | Heap-based Buffer Overflow in Homebrew mruby prior to 3.2. | https://huntr.dev/bounties/65a7632e-f95b-4836-b1a7-9cb95e5124f1 | https://github.com/mruby/mruby/commit/47068ae07a5fa3aa9a1879cdfe98a9ce0f339299 | CWE-122 | mruby/mruby | 0ed3fcf | diff --git a/src/vm.c b/src/vm.c
index 9cb50847f2..aa5569503e 100644
--- a/src/vm.c
+++ b/src/vm.c
@@ -689,9 +689,11 @@ mrb_f_send(mrb_state *mrb, mrb_value self)
regs = mrb->c->ci->stack+1;
if (n == 0) {
+ argnum_error:
mrb_argnum_error(mrb, 0, 1, -1);
}
else if (n == 15) {
+ if (RARRAY_LEN(regs... | null | null | null | null | https://nvd.nist.gov/vuln/detail/CVE-2022-0570 |
matio.cve-2019-20017 | A stack-based buffer over-read was discovered in Mat_VarReadNextInfo5 in mat5.c in matio 1.5.17. | https://github.com/tbeu/matio/issues/127 | null | CWE-125 | tbeu/matio | null | null | https://github.com/tbeu/matio/issues/127 | ./matdump 001-stackover-Mat_VarReadNextInfo5_mat54915
InflateRankDims: inflate returned data error
=================================================================
==31427==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7ffcc32c92d0 at pc 0x7fcd463809a6 bp 0x7ffcc32c90c0 sp 0x7ffcc32c90b0
READ of size 4 ... | null | === https://github.com/tbeu/matio/issues/127 ===
Title: There is a stack-based buffer overflow in the Mat_VarReadNextInfo5 function of mat5.c(at 4915)
---
Body:
A crafted input will lead to crash in mat5.c at matio 1.5.17.
Triggered by
./matdump POC
Poc
[001-stackover-Mat_VarReadNextInfo5_mat54915](https://gith... | https://nvd.nist.gov/vuln/detail/CVE-2019-20017 |
matio.cve-2019-9035 | An issue was discovered in libmatio.a in matio (aka MAT File I/O Library) 1.5.13. There is a stack-based buffer over-read in the function ReadNextStructField() in mat5.c. | https://github.com/TeamSeri0us/pocs/tree/master/matio | null | CWE-125 | TeamSeri0us/pocs | null | null | https://github.com/tbeu/matio/issues/103 | $ tools/matdump ~/pocs/matio/ReadNextFunctionHandle@mat5.c_1837-26___heap-buffer-overflow
=================================================================
==29570==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60200000efd0 at pc 0x7f5b9c14f9fe bp... | null | === https://github.com/tbeu/matio/issues/103 ===
Title: some memory corruption problems when the library parse the mat file
---
Body:
I found several memory corruption problem in the library.
More details can be found at [here](https://github.com/TeamSeri0us/pocs/tree/master/matio).
---
Comment #1 by PhilipMorris... | https://nvd.nist.gov/vuln/detail/CVE-2019-9035 |
libxls.cve-2023-38855 | Buffer Overflow vulnerability in libxlsv.1.6.2 allows a remote attacker to execute arbitrary code and cause a denial of service via a crafted XLS file to the get_string function in xlstool.c:395. | https://github.com/libxls/libxls/issues/124 | null | CWE-787 | libxls/libxls | null | null | https://github.com/libxls/libxls/issues/124 | ==54038==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x602000001070 at pc 0x0000004cf305 bp 0x7fff55151350 sp 0x7fff55151348
READ of size 2 at 0x602000001070 thread T0
#0 0x4cf304 in xls_parseWorkBook /libxls/src/xls.c:1015:37
#1 0x4d7ee5 in xls_open_ole /libxls/src/xls.c:1480:14
#2 0x4c5b4d in... | null | === https://github.com/libxls/libxls/issues/124 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/libxls/libxls/issues/124] | https://nvd.nist.gov/vuln/detail/CVE-2023-38855 |
mruby.cve-2022-0630 | Out-of-bounds Read in Homebrew mruby prior to 3.2. | https://huntr.dev/bounties/f7cdd680-1a7f-4992-b4b8-44b5e4ba3e32 | https://github.com/mruby/mruby/commit/ee06bbb4177a0c65aab9b3006f0f15fe9f3503fd | CWE-125 | mruby/mruby | ecb28f4 | diff --git a/src/vm.c b/src/vm.c
index 6133cbc..52c6405 100644
--- a/src/vm.c
+++ b/src/vm.c
@@ -2776,7 +2776,7 @@ RETRY_TRY_BLOCK:
CASE(OP_HASHCAT, B) {
mrb_value hash = regs[a];
- mrb_assert(mrb_hash_p(hash));
+ mrb_ensure_hash_type(mrb, hash);
mrb_hash_merge(mrb, hash, regs[a+1]);
... | null | null | ASan (inferred) | null | https://nvd.nist.gov/vuln/detail/CVE-2022-0630 |
libredwg.cve-2020-21819 | A heap based buffer overflow vulnerability exists in GNU LibreDWG 0.10.2641via htmlescape ../../programs/escape.c:51. | https://github.com/LibreDWG/libredwg/issues/182#issuecomment-572890901 | https://github.com/LibreDWG/libredwg/issues/182#issuecomment-572890901 | CWE-787 | LibreDWG/libredwg | null | null | https://github.com/LibreDWG/libredwg/issues/182#issuecomment-572890901 | =================================================================
==19607==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x7f433bb56646 bp 0x7ffed1176670 sp 0x7ffed1175de8 T0)
==19607==The signal is caused by a READ memory access.
==19607==Hint: address points to the zero page.
#0 0x7f433bb566... | null | === https://github.com/LibreDWG/libredwg/issues/182#issuecomment-572890901 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/LibreDWG/libredwg/issues/182] | https://nvd.nist.gov/vuln/detail/CVE-2020-21819 |
gpac.cve-2021-32439 | Buffer overflow in the stbl_AppendSize function in MP4Box in GPAC 1.0.1 allows attackers to cause a denial of service or execute arbitrary code via a crafted file. | https://github.com/gpac/gpac/issues/1774 | https://github.com/gpac/gpac/commit/77ed81c069e10b3861d88f72e1c6be1277ee7eae | CWE-120 | gpac/gpac | 77ed81c069e10b3861d88f72e1c6be1277ee7eae~1 | diff --git a/src/isomedia/stbl_write.c b/src/isomedia/stbl_write.c
index 843a30857a..1e4780d657 100644
--- a/src/isomedia/stbl_write.c
+++ b/src/isomedia/stbl_write.c
@@ -37,11 +37,20 @@ gf_realloc low, which greatly impacts performances for large files*/
#ifndef GPAC_DISABLE_ISOM_WRITE
+
+#define CHECK_PACK(_e) \... | https://github.com/gpac/gpac/issues/1774 | 15305==ERROR: AddressSanitizer: SEGV on unknown address 0x616000010000 (pc 0x7ff3a3276461 bp 0x7ffc231be4c0 sp 0x7ffc231be490 T0)
==15305==The signal is caused by a WRITE memory access.
#0 0x7ff3a3276460 in stbl_AppendSize isomedia/stbl_write.c:1650
#1 0x7ff3a3279df4 in MergeTrack isomedia/track.c:703
#2 0x... | null | === https://github.com/gpac/gpac/issues/1774 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/gpac/gpac/issues/1774] | https://nvd.nist.gov/vuln/detail/CVE-2021-32439 |
libredwg.cve-2020-6609 | GNU LibreDWG 0.9.3.2564 has a heap-based buffer over-read in read_pages_map in decode_r2007.c. | https://github.com/LibreDWG/libredwg/issues/179#issue-544834443 | https://github.com/LibreDWG/libredwg/issues/179#issue-544834443 | CWE-125 | LibreDWG/libredwg | null | null | https://github.com/LibreDWG/libredwg/issues/179#issue-544834443 | null | null | === https://github.com/LibreDWG/libredwg/issues/179#issue-544834443 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/LibreDWG/libredwg/issues/179] | https://nvd.nist.gov/vuln/detail/CVE-2020-6609 |
imagemagick.cve-2019-13306 | ImageMagick 7.0.8-50 Q16 has a stack-based buffer overflow at coders/pnm.c in WritePNMImage because of off-by-one errors. | https://github.com/ImageMagick/ImageMagick/issues/1612 | https://github.com/ImageMagick/ImageMagick/commit/e92040ea6ee2a844ebfd2344174076795a4787bd, https://github.com/ImageMagick/ImageMagick/issues/1612, https://github.com/ImageMagick/ImageMagick6/commit/cb5ec7d98195aa74d5ed299b38eff2a68122f3fa | CWE-193, CWE-787 | ImageMagick/ImageMagick | e92040ea6ee2a844ebfd2344174076795a4787bd~1 | diff --git a/coders/pnm.c b/coders/pnm.c
index f6f69bf83c2..a54bc60c33d 100644
--- a/coders/pnm.c
+++ b/coders/pnm.c
@@ -1826,7 +1826,7 @@ static MagickBooleanType WritePNMImage(const ImageInfo *image_info,Image *image,
extent=(size_t) count;
(void) strncpy((char *) q,buffer,extent);
... | https://github.com/ImageMagick/ImageMagick/issues/1612 | ==12131==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7ffc7100b060 at pc 0x0000004477c4 bp 0x7ffc710065b0 sp 0x7ffc71005d60
WRITE of size 10 at 0x7ffc7100b060 thread T0
#0 0x4477c3 in strncpy (install/bin/magick+0x4477c3)
#1 0x7f1cca22b433 in WritePNMImage coders/pnm.c:1902:20
#2 0x7f1cc9ac30... | null | === https://github.com/ImageMagick/ImageMagick/issues/1612 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/ImageMagick/ImageMagick/issues/1612] | https://nvd.nist.gov/vuln/detail/CVE-2019-13306 |
imagemagick.cve-2017-11539 | When ImageMagick 7.0.6-1 processes a crafted file in convert, it can lead to a Memory Leak in the ReadOnePNGImage() function in coders/png.c. | https://github.com/ImageMagick/ImageMagick/issues/582 | https://github.com/ImageMagick/ImageMagick/issues/582 | CWE-772 | ImageMagick/ImageMagick | null | null | https://github.com/ImageMagick/ImageMagick/issues/582 | ==53617==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 152 byte(s) in 1 object(s) allocated from:
#0 0x7f4833557602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602)
#1 0x7f4832a55dba in AcquireMagickMemory MagickCore/memory.c:464
#2 0x7f4832adf331 in AcquireQuantumInfo MagickCore/qua... | null | === https://github.com/ImageMagick/ImageMagick/issues/582 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/ImageMagick/ImageMagick/issues/582] | https://nvd.nist.gov/vuln/detail/CVE-2017-11539 |
libheif.cve-2023-49464 | libheif v1.17.5 was discovered to contain a segmentation violation via the function UncompressedImageCodec::get_luma_bits_per_pixel_from_configuration_unci. | https://github.com/strukturag/libheif/issues/1044 | https://github.com/strukturag/libheif/pull/1048/changes/440c2a505dbfa00faf48da9c71f9b4bc57af9a8d | null | strukturag/libheif | 64ece913266609789f5dc70fe7de9eb759badd7f | diff --git a/libheif/uncompressed_image.cc b/libheif/uncompressed_image.cc
index a0387b6c80..cda5dc3dc2 100644
--- a/libheif/uncompressed_image.cc
+++ b/libheif/uncompressed_image.cc
@@ -531,6 +531,9 @@ int UncompressedImageCodec::get_luma_bits_per_pixel_from_configuration_unci(cons
int alternate_channel_bits = 0;
... | https://github.com/strukturag/libheif/issues/1044 | ==88148==ERROR: AddressSanitizer: heap-use-after-free on address 0x60e000000910 at pc 0x7f7a88d9ab47 bp 0x7ffef17996e0 sp 0x7ffef17996d0
READ of size 2 at 0x60e000000910 thread T0
#0 0x7f7a88d9ab46 in UncompressedImageCodec::get_luma_bits_per_pixel_from_configuration_unci(HeifFile const&, unsigned int) libheif/libh... | null | === https://github.com/strukturag/libheif/issues/1044 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/strukturag/libheif/issues/1044] | https://nvd.nist.gov/vuln/detail/CVE-2023-49464 |
yara.cve-2017-5924 | libyara/grammar.y in YARA 3.5.0 allows remote attackers to cause a denial of service (use-after-free and application crash) via a crafted rule that is mishandled in the yr_compiler_destroy function. | https://github.com/VirusTotal/yara/issues/593 | https://github.com/VirusTotal/yara/commit/c2ed7a46618f93a0dfe011dc608f2b604f365251 | CWE-416 | VirusTotal/yara | 890c3f8 | Done - patched grammar.c, exec.h, exec.c
diff --git a/libyara/exec.c b/libyara/exec.c
index 59072a4..31cb6e8 100644
--- a/libyara/exec.c
+++ b/libyara/exec.c
@@ -205,6 +205,9 @@ int yr_execute_code(
{
switch(*ip)
{
+ case OP_NOP:
+ break;
+
case OP_HALT:
assert(sp == 0); // When... | https://github.com/VirusTotal/yara/issues/593 | ==10220==ERROR: AddressSanitizer: heap-use-after-free on address 0x63100003c862 at pc 0x0000004ef7f5 bp 0x7ffc9082a5d0 sp 0x7ffc9082a5c8
READ of size 8 at 0x63100003c862 thread T0
#0 0x4ef7f4 in yr_compiler_destroy XYZ/yara/libyara/compiler.c:165:35
#1 0x4ede04 in main XYZ/yara/yara.c:1242:5
#2 0x7f05302fa8... | ASan (inferred) | === https://github.com/VirusTotal/yara/issues/593 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/VirusTotal/yara/issues/593] | https://nvd.nist.gov/vuln/detail/CVE-2017-5924 |
mruby.cve-2018-14337 | The CHECK macro in mrbgems/mruby-sprintf/src/sprintf.c in mruby 1.4.1 contains a signed integer overflow, possibly leading to out-of-bounds memory access because the mrb_str_resize function in string.c does not check for a negative length. | https://github.com/mruby/mruby/issues/4062 | null | CWE-190 | mruby/mruby | null | null | https://github.com/mruby/mruby/issues/4062 | $ echo "' %8646911284551352320d'%1" | bin/mruby
/Users/clayton/git/mruby/mrbgems/mruby-sprintf/src/sprintf.c:966:11: runtime error: signed integer overflow: 8646911284551352320 * 2 cannot be represented in type 'long long'
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior /Users/clayton/git/mruby/mrbgems/mruby-sp... | ASan (inferred) | === https://github.com/mruby/mruby/issues/4062 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/mruby/mruby/issues/4062] | https://nvd.nist.gov/vuln/detail/CVE-2018-14337 |
imagemagick.cve-2022-48541 | A memory leak in ImageMagick 7.0.10-45 and 6.9.11-22 allows remote attackers to perform a denial of service via the "identify -help" command. | https://github.com/ImageMagick/ImageMagick/issues/2889 | null | CWE-401 | ImageMagick/ImageMagick | null | null | https://github.com/ImageMagick/ImageMagick/issues/2889 | ==15438==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 13024 byte(s) in 1 object(s) allocated from:
#0 0x494bad in malloc (/usr/local/bin/magick+0x494bad)
#1 0x7f5ee70c0a35 in AcquireMagickMemory MagickCore/memory.c:531:10
#2 0x7f5ee70c0a4b in AcquireCriticalMemory MagickCore/memory.c:607:10
... | null | === https://github.com/ImageMagick/ImageMagick/issues/2889 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/ImageMagick/ImageMagick/issues/2889] | https://nvd.nist.gov/vuln/detail/CVE-2022-48541 |
imagemagick.cve-2019-13300 | ImageMagick 7.0.8-50 Q16 has a heap-based buffer overflow at MagickCore/statistic.c in EvaluateImages because of mishandling columns. | https://github.com/ImageMagick/ImageMagick/issues/1586 | https://github.com/ImageMagick/ImageMagick/commit/a906fe9298bf89e01d5272023db687935068849a, https://github.com/ImageMagick/ImageMagick/issues/1586, https://github.com/ImageMagick/ImageMagick6/commit/5e409ae7a389cdf2ed17469303be3f3f21cec450 | CWE-787 | ImageMagick/ImageMagick | a906fe9298bf89e01d5272023db687935068849a~1 | diff --git a/MagickCore/statistic.c b/MagickCore/statistic.c
index a649880f440..50d56fcf77a 100644
--- a/MagickCore/statistic.c
+++ b/MagickCore/statistic.c
@@ -150,8 +150,11 @@ static PixelChannels **DestroyPixelThreadSet(PixelChannels **pixels)
return(pixels);
}
-static PixelChannels **AcquirePixelThreadSet(con... | https://github.com/ImageMagick/ImageMagick/issues/1586 | ==27479==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x629000018800 at pc 0x0000006205ab bp 0x7ffd7a503310 sp 0x7ffd7a503308
WRITE of size 8 at 0x629000018800 thread T0
#0 0x6205aa in .omp_outlined._debug__.10 MagickCore/statistic.c:654:41
#1 0x621c5e in .omp_outlined..11 MagickCore/statistic.c:618... | null | === https://github.com/ImageMagick/ImageMagick/issues/1586 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/ImageMagick/ImageMagick/issues/1586] | https://nvd.nist.gov/vuln/detail/CVE-2019-13300 |
libredwg.cve-2020-21827 | A heap based buffer overflow vulnerability exists in GNU LibreDWG 0.10 via read_2004_compressed_section ../../src/decode.c:2379. | https://github.com/LibreDWG/libredwg/issues/183 | https://github.com/LibreDWG/libredwg/commit/bcec483e73819af29787d5ed87fc515e1dfd0411 | CWE-787 | LibreDWG/libredwg | bcec483e73819af29787d5ed87fc515e1dfd0411~1 | diff --git a/src/decode.c b/src/decode.c
index 96b48ef4ca..b40bfa7a64 100644
--- a/src/decode.c
+++ b/src/decode.c
@@ -2319,11 +2319,12 @@ read_2004_compressed_section (Bit_Chain *dat, Dwg_Data *restrict dwg,
sec_dat->from_version = dat->from_version;
sec_dat->chain = decomp;
- for (i = 0; i < info->num_sectio... | https://github.com/LibreDWG/libredwg/issues/183 | ==29243==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x6140000005b2 at pc 0x7ffafa9dc77a bp 0x7ffcc19b07e0 sp 0x7ffcc19aff88
WRITE of size 126 at 0x6140000005b2 thread T0
#0 0x7ffafa9dc779 (/usr/lib/x86_64-linux-gnu/libasan.so.4+0x79779)
#1 0x561777b62e9c in memcpy /usr/include/x86_64-linux-gnu/bi... | null | === https://github.com/LibreDWG/libredwg/issues/183 ===
Title: Heap over flow
---
Body:
I found a bug in dwg2dxf.
POC: https://github.com/linhlhq/research/blob/master/PoCs/libreDWG_69b5609/id:000000%2Csig:06%2Csrc:000001%2Cop:flip4%2Cpos:27167
```
==29243==ERROR: AddressSanitizer: heap-buffer-overflow on address 0... | https://nvd.nist.gov/vuln/detail/CVE-2020-21827 |
exiv2.cve-2017-17723 | In Exiv2 0.26, there is a heap-based buffer over-read in the Exiv2::Image::byteSwap4 function in image.cpp. Remote attackers can exploit this vulnerability to disclose memory data or cause a denial of service via a crafted TIFF file. | https://bugzilla.redhat.com/show_bug.cgi?id=1524104 | null | CWE-125 | null | null | null | https://bugzilla.redhat.com/show_bug.cgi?id=1524104 | null | null | null | https://nvd.nist.gov/vuln/detail/CVE-2017-17723 |
imagemagick.cve-2019-13301 | ImageMagick 7.0.8-50 Q16 has memory leaks in AcquireMagickMemory because of an AnnotateImage error. | https://github.com/ImageMagick/ImageMagick/issues/1585, https://github.com/ImageMagick/ImageMagick/issues/1589 | https://github.com/ImageMagick/ImageMagick/commit/7c2c5ba5b8, https://github.com/ImageMagick/ImageMagick/commit/f595a1985233c399a05c0c37cc41de16a90dd025 | CWE-401 | ImageMagick/ImageMagick | 7c2c5ba5b8~1 | diff --git a/MagickCore/annotate.c b/MagickCore/annotate.c
index 494720211e4..3f3ac7fa09d 100644
--- a/MagickCore/annotate.c
+++ b/MagickCore/annotate.c
@@ -277,6 +277,7 @@ MagickExport MagickBooleanType AnnotateImage(Image *image,
{
annotate_info=DestroyDrawInfo(annotate_info);
annotate=DestroyDrawI... | https://github.com/ImageMagick/ImageMagick/issues/1585, https://github.com/ImageMagick/ImageMagick/issues/1589 | null | null | === https://github.com/ImageMagick/ImageMagick/issues/1585 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/ImageMagick/ImageMagick/issues/1585]
=== https://github.com/ImageMagick/ImageMagick/issues/1589 ===
[error fetching issue: 403 Client Error: rate limit excee... | https://nvd.nist.gov/vuln/detail/CVE-2019-13301 |
libarchive.cve-2020-21674 | Heap-based buffer overflow in archive_string_append_from_wcs() (archive_string.c) in libarchive-3.4.1dev allows remote attackers to cause a denial of service (out-of-bounds write in heap memory resulting into a crash) via a crafted archive file. NOTE: this only affects users who downloaded the development code from Git... | null | https://github.com/libarchive/libarchive/commit/4f085eea879e2be745f4d9bf57e8513ae48157f4 | CWE-787 | libarchive/libarchive | 4f085eea879e2be745f4d9bf57e8513ae48157f4~1 | diff --git a/libarchive/archive_string.c b/libarchive/archive_string.c
index bd39c96f10..399299ea63 100644
--- a/libarchive/archive_string.c
+++ b/libarchive/archive_string.c
@@ -75,6 +75,9 @@ __FBSDID("$FreeBSD: head/lib/libarchive/archive_string.c 201095 2009-12-28 02:33
#define wmemmove(a,b,i) (wchar_t *)memmove((... | https://github.com/libarchive/libarchive/issues/1298 | ==2650==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x607000000298 at pc 0x5586b16c5082 bp 0x7ffc3d24a950 sp 0x7ffc3d24a940
WRITE of size 1 at 0x607000000298 thread T0
#0 0x5586b16c5081 in archive_string_append_from_wcs libarchive/archive_string.c:831
#1 0x5586b16c5fd7 in archive_mstring_get_mbs li... | ASan (inferred) | === https://github.com/libarchive/libarchive/issues/1298 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/libarchive/libarchive/issues/1298] | https://nvd.nist.gov/vuln/detail/CVE-2020-21674 |
exiv2.cve-2017-14857 | In Exiv2 0.26, there is an invalid free in the Image class in image.cpp that leads to a Segmentation fault. A crafted input will lead to a denial of service attack. | https://bugzilla.redhat.com/show_bug.cgi?id=1495043 | null | CWE-416 | null | null | null | https://bugzilla.redhat.com/show_bug.cgi?id=1495043 | null | null | null | https://nvd.nist.gov/vuln/detail/CVE-2017-14857 |
yara.cve-2023-40857 | Buffer Overflow vulnerability in VirusTotal yara v.4.3.2 allows a remote attacker to execute arbtirary code via the yr_execute_cod function in the exe.c component. | https://github.com/VirusTotal/yara/issues/1945 | null | CWE-787 | VirusTotal/yara | d1ff3ecc465d7ed882943fd1278dd8981b704f02 | null | https://github.com/VirusTotal/yara/issues/1945 | =================================================================
==1855158==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x604000000248 at pc 0x7f168933dfaf bp 0x7ffd229d5530 sp 0x7ffd229d5520
READ of size 8 at 0x604000000248 thread T0
#0 0x7f168933dfae in yr_execute_code libyara/exec.c:1426
#1 0x7... | null | === https://github.com/VirusTotal/yara/issues/1945 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/VirusTotal/yara/issues/1945] | https://nvd.nist.gov/vuln/detail/CVE-2023-40857 |
matio.cve-2019-9032 | An issue was discovered in libmatio.a in matio (aka MAT File I/O Library) 1.5.13. There is an out-of-bounds write problem causing a SEGV in the function Mat_VarFree() in mat.c. | https://github.com/TeamSeri0us/pocs/tree/master/matio | null | CWE-787 | TeamSeri0us/pocs | null | null | https://github.com/tbeu/matio/issues/103 | =================================================================
==29570==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60200000efd0 at pc 0x7f5b9c14f9fe bp 0x7ffca66d34a0 sp 0x7ffca66d3498
WRITE of size 8 at 0x60200000efd0 thread T0
#0 0x7f5b9c14f9fd in Mat_VarReadNextInfo5 (/home/sebastien/debian/up... | ASan (inferred) | === https://github.com/tbeu/matio/issues/103 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/tbeu/matio/issues/103] | https://nvd.nist.gov/vuln/detail/CVE-2019-9032 |
mruby.cve-2022-1286 | heap-buffer-overflow in mrb_vm_exec in mruby/mruby in GitHub repository mruby/mruby prior to 3.2. Possible arbitrary code execution if being exploited. | https://huntr.dev/bounties/f918376e-b488-4113-963d-ffe8716e4189 | https://github.com/mruby/mruby/commit/b1d0296a937fe278239bdfac840a3fd0e93b3ee9 | CWE-122, CWE-787 | mruby/mruby | b1d0296a937fe278239bdfac840a3fd0e93b3ee9~1 | diff --git a/src/class.c b/src/class.c
index 37fc4e68a4..68a0ff0843 100644
--- a/src/class.c
+++ b/src/class.c
@@ -2361,7 +2361,10 @@ mrb_remove_method(mrb_state *mrb, struct RClass *c, mrb_sym mid)
MRB_CLASS_ORIGIN(c);
h = c->mt;
- if (h && mt_del(mrb, h, mid)) return;
+ if (h && mt_del(mrb, h, mid)) {
+ ... | null | null | ASan (inferred) | null | https://nvd.nist.gov/vuln/detail/CVE-2022-1286 |
yaml-cpp.cve-2018-20574 | The SingleDocParser::HandleFlowMap function in yaml-cpp (aka LibYaml-C++) 0.6.2 allows remote attackers to cause a denial of service (stack consumption and application crash) via a crafted YAML file. | https://github.com/jbeder/yaml-cpp/issues/654 | https://github.com/mongodb-forks/yaml-cpp/commit/9bbdfd07814f3c1ae457643224fdfd1d8aa971b9 | CWE-119 | mongodb-forks/yaml-cpp | 9bbdfd07814f3c1ae457643224fdfd1d8aa971b9~1 | diff --git a/include/yaml-cpp/depthguard.h b/include/yaml-cpp/depthguard.h
new file mode 100644
index 000000000..8ca61ac6c
--- /dev/null
+++ b/include/yaml-cpp/depthguard.h
@@ -0,0 +1,77 @@
+#ifndef DEPTH_GUARD_H_00000000000000000000000000000000000000000000000000000000
+#define DEPTH_GUARD_H_000000000000000000000000000... | https://github.com/jbeder/yaml-cpp/issues/654 | ASAN:DEADLYSIGNAL
=================================================================
==6596==ERROR: AddressSanitizer: stack-overflow on address 0xbf09dee0 (pc 0x0814e423 bp 0xbf09e308 sp 0xbf09ded0 T0)
#0 0x814e422 (/home/user/yaml-cpp/build/util/parse+0x814e422)
#1 0x816fd48 (/home/user/yaml-cpp/build/util/pa... | null | === https://github.com/jbeder/yaml-cpp/issues/654 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/jbeder/yaml-cpp/issues/654] | https://nvd.nist.gov/vuln/detail/CVE-2018-20574 |
libredwg.cve-2021-42586 | A heap buffer overflow was discovered in copy_bytes in decode_r2007.c in dwgread before 0.12.4 via a crafted dwg file. | https://github.com/LibreDWG/libredwg/issues/350 | https://github.com/LibreDWG/libredwg/commit/45d2a290c65ed691be0901ba2b2ef51044e07a16 | CWE-787 | LibreDWG/libredwg | 45d2a290c65ed691be0901ba2b2ef51044e07a16~1 | diff --git a/src/decode_r2007.c b/src/decode_r2007.c
index c1e270fc4b..0fb506a624 100644
--- a/src/decode_r2007.c
+++ b/src/decode_r2007.c
@@ -655,6 +655,8 @@ read_system_page (Bit_Chain *dat, int64_t size_comp, int64_t size_uncomp,
LOG_ERROR ("Invalid r2007 system page: page_size: %" PRId64, page_size);
... | https://github.com/LibreDWG/libredwg/issues/350 | ./dwgread ./tests_64199
=================================================================
==9330==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x62a000005f55 at pc 0x000000ca93c3 bp 0x7ffe5a6134c0 sp 0x7ffe5a6134b8
WRITE of size 1 at 0x62a000005f55 thread T0
#0 0xca93c2 in copy_bytes /root/fuzz/libredwg... | null | === https://github.com/LibreDWG/libredwg/issues/350 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/LibreDWG/libredwg/issues/350] | https://nvd.nist.gov/vuln/detail/CVE-2021-42586 |
openexr.cve-2020-16589 | A head-based buffer overflow exists in Academy Software Foundation OpenEXR 2.3.0 in writeTileData in ImfTiledOutputFile.cpp that can cause a denial of service via a crafted EXR file. | https://github.com/AcademySoftwareFoundation/openexr/commit/6bb36714528a9563dd3b92720c5063a1284b86f8 | https://github.com/AcademySoftwareFoundation/openexr/commit/6bb36714528a9563dd3b92720c5063a1284b86f8 | CWE-787 | AcademySoftwareFoundation/openexr | 6bb36714528a9563dd3b92720c5063a1284b86f8~1 | diff --git a/OpenEXR/IlmImf/ImfTiledInputFile.cpp b/OpenEXR/IlmImf/ImfTiledInputFile.cpp
index 15c51c50af..bda7bad50a 100644
--- a/OpenEXR/IlmImf/ImfTiledInputFile.cpp
+++ b/OpenEXR/IlmImf/ImfTiledInputFile.cpp
@@ -1313,6 +1313,13 @@ TiledInputFile::rawTileData (int &dx, int &dy,
throw IEX_NAMESPACE::A... | https://github.com/AcademySoftwareFoundation/openexr/issues/494 | ==22567==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60400000e178 at pc 0x7f2f375c522a bp 0x7ffe478e5550 sp 0x7ffe478e5540
READ of size 8 at 0x60400000e178 thread T0
#0 0x7f2f375c5229 in Imf_2_3::TileOffsets::operator()(int, int, int, int) (/home/dungnguyen/gueb-testing/openexr/obj-asan/OpenEXR/IlmIm... | null | === https://github.com/AcademySoftwareFoundation/openexr/issues/494 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/AcademySoftwareFoundation/openexr/issues/494] | https://nvd.nist.gov/vuln/detail/CVE-2020-16589 |
openexr.cve-2020-16587 | A heap-based buffer overflow vulnerability exists in Academy Software Foundation OpenEXR 2.3.0 in chunkOffsetReconstruction in ImfMultiPartInputFile.cpp that can cause a denial of service via a crafted EXR file. | https://github.com/AcademySoftwareFoundation/openexr/issues/491 | https://github.com/AcademySoftwareFoundation/openexr/commit/8b5370c688a7362673c3a5256d93695617a4cd9a | CWE-787 | AcademySoftwareFoundation/openexr | 8b5370c688a7362673c3a5256d93695617a4cd9a~1 | diff --git a/OpenEXR/IlmImf/ImfMultiPartInputFile.cpp b/OpenEXR/IlmImf/ImfMultiPartInputFile.cpp
index 6a1fbfdd3b..da061bdbd3 100644
--- a/OpenEXR/IlmImf/ImfMultiPartInputFile.cpp
+++ b/OpenEXR/IlmImf/ImfMultiPartInputFile.cpp
@@ -571,7 +571,7 @@ MultiPartInputFile::Data::chunkOffsetReconstruction(OPENEXR_IMF_INTERNAL_... | https://github.com/AcademySoftwareFoundation/openexr/issues/491 | ==976==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60200000ec98 at pc 0x7f12af53f92f bp 0x7ffc0b8eb5e0 sp 0x7ffc0b8eb5d0
READ of size 8 at 0x60200000ec98 thread T0
#0 0x7f12af53f92e in Imf_2_3::MultiPartInputFile::Data::chunkOffsetReconstruction(Imf_2_3::IStream&, std::vector<Imf_2_3::InputPartData*,... | null | === https://github.com/AcademySoftwareFoundation/openexr/issues/491 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/AcademySoftwareFoundation/openexr/issues/491] | https://nvd.nist.gov/vuln/detail/CVE-2020-16587 |
openexr.cve-2020-16588 | A Null Pointer Deference issue exists in Academy Software Foundation OpenEXR 2.3.0 in generatePreview in makePreview.cpp that can cause a denial of service via a crafted EXR file. | https://github.com/AcademySoftwareFoundation/openexr/issues/493 | https://github.com/AcademySoftwareFoundation/openexr/commit/74504503cff86e986bac441213c403b0ba28d58f | CWE-476 | AcademySoftwareFoundation/openexr | 74504503cff86e986bac441213c403b0ba28d58f~1 | diff --git a/OpenEXR/exrmakepreview/makePreview.cpp b/OpenEXR/exrmakepreview/makePreview.cpp
index ae0e99dfa1..e2d0879847 100644
--- a/OpenEXR/exrmakepreview/makePreview.cpp
+++ b/OpenEXR/exrmakepreview/makePreview.cpp
@@ -120,8 +120,8 @@ generatePreview (const char inFileName[],
previewHeight = max (int (h / (w *... | https://github.com/AcademySoftwareFoundation/openexr/issues/493 | ==5549==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x000000402db3 bp 0x7fbf849cd800 sp 0x7ffe12fc8050 T0)
#0 0x402db2 in generatePreview /home/dungnguyen/gueb-testing/openexr/OpenEXR/exrmakepreview/makePreview.cpp:132
#1 0x402db2 in makePreview(char const*, char const*, int, float, bool... | null | === https://github.com/AcademySoftwareFoundation/openexr/issues/493 ===
[error fetching issue: 403 Client Error: rate limit exceeded for url: https://api.github.com/repos/AcademySoftwareFoundation/openexr/issues/493] | https://nvd.nist.gov/vuln/detail/CVE-2020-16588 |
mruby.cve-2022-0326 | NULL Pointer Dereference in Homebrew mruby prior to 3.2. | https://huntr.dev/bounties/795dcbd9-1695-44bb-8c59-ad327c97c976 | https://github.com/mruby/mruby/commit/b611c43a5de061ec21b343967e1b64c45c373d7e, https://huntr.dev/bounties/795dcbd9-1695-44bb-8c59-ad327c97c976 | CWE-476 | mruby/mruby | b611c43a5de061ec21b343967e1b64c45c373d7e~1 | diff --git a/mrbgems/mruby-compiler/core/codegen.c b/mrbgems/mruby-compiler/core/codegen.c
index c36178c8b0..3996824a2f 100644
--- a/mrbgems/mruby-compiler/core/codegen.c
+++ b/mrbgems/mruby-compiler/core/codegen.c
@@ -1644,14 +1644,13 @@ gen_hash(codegen_scope *s, node *tree, int val, int limit)
}
}
if (upd... | null | null | null | null | https://nvd.nist.gov/vuln/detail/CVE-2022-0326 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.