12243 matches found
CVE-2018-16413
ImageMagick 7.0.8-11 Q16 has a heap-based buffer over-read in the MagickCore/quantum-private.h PushShortPixel function when called from the coders/psd.c ParseImageResourceBlocks function...
CVE-2018-16382
Netwide Assembler NASM 2.14rc15 has a buffer over-read in x86/regflags.c...
CVE-2018-16382
Netwide Assembler NASM 2.14rc15 has a buffer over-read in x86/regflags.c...
CVE-2018-16382
Netwide Assembler NASM 2.14rc15 has a buffer over-read in x86/regflags.c...
CVE-2018-16382
CVE-2018-16382 affects Netwide Assembler (NASM) 2.14rc15, with a buffer over-read in x86/regflags.c. The connected Nessus/Red Hat advisories confirm this vulnerability and list CVE-2018-16382 among unpatched/exposed NASM issues, but do not specify a concrete fixed version or patch candidate in th...
CVE-2018-16382
Netwide Assembler NASM 2.14rc15 has a buffer over-read in x86/regflags.c...
CVE-2018-16382
Netwide Assembler NASM 2.14rc15 has a buffer over-read in x86/regflags.c...
CVE-2018-16413
ImageMagick 7.0.8-11 Q16 has a heap-based buffer over-read in the MagickCore/quantum-private.h PushShortPixel function when called from the coders/psd.c ParseImageResourceBlocks function...
CVE-2018-16412
ImageMagick 7.0.8-11 Q16 has a heap-based buffer over-read in the coders/psd.c ParseImageResourceBlocks function...
CVE-2018-16368
SplashXPath::strokeAdjust in splash/SplashXPath.cc in Xpdf 4.00 allows remote attackers to cause a denial of service heap-based buffer over-read via a crafted pdf file, as demonstrated by pdftoppm...
CVE-2018-16368
CVE-2018-16368 affects Xpdf (SplashXPath.c) in versions around 4.00 and 4.01.01, where SplashXPath::strokeAdjust() can be triggered by a crafted PDF sent to pdftoppm, enabling a remote attacker to cause a denial of service via a heap-based buffer over-read. Related entries note potential informat...
CVE-2018-16368
SplashXPath::strokeAdjust in splash/SplashXPath.cc in Xpdf 4.00 allows remote attackers to cause a denial of service heap-based buffer over-read via a crafted pdf file, as demonstrated by pdftoppm...
Heap overflow
Exiv2::Internal::PngChunk::parseTXTChunk in Exiv2 v0.26 allows remote attackers to cause a denial of service heap-based buffer over-read via a crafted image file, a different vulnerability than CVE-2018-10999...
PYSEC-2018-135
Exiv2::Internal::PngChunk::parseTXTChunk in Exiv2 v0.26 allows remote attackers to cause a denial of service heap-based buffer over-read via a crafted image file, a different vulnerability than CVE-2018-10999...
CVE-2018-16336
Exiv2::Internal::PngChunk::parseTXTChunk in Exiv2 v0.26 allows remote attackers to cause a denial of service heap-based buffer over-read via a crafted image file, a different vulnerability than CVE-2018-10999...
CVE-2018-16336
CVE-2018-16336 affects Exiv2 (v0.26) via Exiv2::Internal::PngChunk::parseTXTChunk. The vulnerability is a heap-based buffer over-read caused by processing crafted TXT chunks in PNG files, enabling a remote denial of service. Connected sources corroborate this issue within Exiv2’s PNG/text parsing...
CVE-2018-15158
The libesedbpagereadvalues function in libesedbpage.c in libesedb through 2018-04-01 allows remote attackers to cause a heap-based buffer over-read via a crafted esedb file. NOTE: the vendor has disputed this as described in the GitHub issue comments...
CVE-2018-15157
The libfsclfsblockread function in libfsclfsblock.c in libfsclfs before 2018-07-25 allows remote attackers to cause a heap-based buffer over-read via a crafted clfs file. NOTE: the vendor has disputed this as described in the GitHub issue comments...
CVE-2018-15160
The libesedbcatalogdefinitionread function in libesedbcatalogdefinition.c in libesedb through 2018-04-01 allows remote attackers to cause a heap-based buffer over-read via a crafted esedb file. NOTE: the vendor has disputed this as described in the GitHub issue comments...
CVE-2018-15159
The libesedbpagereadtags function in libesedbpage.c in libesedb through 2018-04-01 allows remote attackers to cause a heap-based buffer over-read via a crafted esedb file. NOTE: the vendor has disputed this as described in the GitHub issue comments...