An issue was discovered in the libp2p-deflate crate before 0.27.1 for Rust. An uninitialized buffer is passed to AsyncRead::pollread(), which is a user-provided trait function.
Off-by-one error in the pngformattedwarning function in pngerror.c in libpng 1.5.4 through 1.5.7 might allow remote attackers to cause a denial of service (application crash) and possibly execute arbitrary code via unspecified vectors, which trigger a stack-based buffer overflow.
An issue was discovered in the libp2p-core crate before 0.8.1 for Rust. Attackers can spoof ed25519 signatures.
libpng 1.0.6 through 1.0.32, 1.2.0 through 1.2.26, and 1.4.0beta01 through 1.4.0beta19 allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a PNG file with zero length "unknown" chunks, which trigger an access of uninitialized memory.
pngrtran.c in libpng 1.5.x before 1.5.1 allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted palette-based PNG image that triggers a buffer overflow, related to the pngdoexpandpalette function, the pngdorgbtogray function, and an integer underflow. NOTE: some of these details are obtained from third party information.
A flaw was found in libpng 1.6.38. A crafted PNG image can lead to a segmentation fault and denial of service in pngsetuppaethrow() function.
Memory leak in pngwutil.c in libpng 1.2.13beta1, and other versions before 1.2.15beta3, allows context-dependent attackers to cause a denial of service (memory leak or segmentation fault) via a JPEG image containing an iCCP chunk with a negative embedded profile length.
Multiple off-by-one errors in libpng before 1.2.32beta01, and 1.4 before 1.4.0beta34, allow context-dependent attackers to cause a denial of service (crash) or have unspecified other impact via a PNG image with crafted zTXt chunks, related to (1) the pngpushreadzTXt function in pngread.c, and possibly related to (2) pngtest.c.
A vulnerability was reported in Libpng where the input buffer might not have the same length as the pre-defined value hardcoded in the pngimage so that the index is out of bound in the later loop.
References: https://github.com/glennrp/libpng/issues/302
An out-of-bounds read in pngconverttorfc1123 in png.c was found.
Upstream bug:
http://sourceforge.net/p/libpng/bugs/241/
Upstream patch:
http://sourceforge.net/p/libpng/code/ci/fbf0f024346ca0a4ffc64b082a95c6b6bb6d29c4/
CVE assignment:
http://seclists.org/oss-sec/2015/q4/161
libpng through version 1.6.34 is vulnerable to an integer overflow and resultant divide-by-zero in the pngrutil.c:pngcheckchunklength() function. An attacker could exploit this to cause a denial of service via crafted PNG file.
Upstream Bug:
https://sourceforge.net/p/libpng/bugs/278/
Upstream Patch:
https://github.com/glennrp/libpng/commit/8a05766cb74af05c04c53e6c9d60c13fc4d59bf2
It was found that specially crafted SVG file can trigger crash in pngwriterow when converting the given SVG using librsvg2 and cairo. Crash happens inside libpng when trying to access invalid pointer.
Acknowledgements:
Name: Gustavo Grieco
A vulnerability was found in libpng 1.6.36. The function pngimagefree in png.c has a use-after-free because pngimagefreefunction is called under pngsafeexecute.
References: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12803 https://github.com/glennrp/libpng/issues/275
The libpng package contains a library of functions for creating andmanipulating PNG (Portable Network Graphics) image format files. Steve Grubb discovered a out of bounds memory access flaw in libpng. Anattacker could carefully craft a PNG file in such a way that it would causean application linked to libpng to crash when opened by a victim. Thisissue may not be used to execute arbitrary code. Users are advised to upgrade to these updated packages that contain abackported security fix not vulnerable to this issue.