EUVD-2018-9087

Malware in sbrugna...

libsvg2 Stack Buffer Overflow Vulnerability

libsvg2 is a SVG parser written in C. It can be used for a variety of purposes. A stack buffer overflow vulnerability exists in the 'svgGetNextPathField' function in the svgstring.c file in libsvg2 on 2012-10-19 and earlier. A remote attacker can exploit this vulnerability to cause a denial of...

Design/Logic Flaw

An issue was discovered in libsvg2 through 2012-10-19. The svgGetNextPathField function in svgstring.c returns its input pointer in certain circumstances, which might result in a memory leak caused by wasteful malloc calls...

CVE-2018-17332

An issue was discovered in libsvg2 through 2012-10-19. The svgGetNextPathField function in svgstring.c returns its input pointer in certain circumstances, which might result in a memory leak caused by wasteful malloc calls...

PT-2018-13986

Name of the Vulnerable Software and Affected Versions libsvg2 versions prior to 2012-10-19 Description An issue in the svgGetNextPathField function in svg string.c allows remote attackers to cause a denial of service, potentially leading to an application crash, due to a stack-based buffer overfl...

PT-2018-13984

Name of the Vulnerable Software and Affected Versions libsvg2 versions prior to 2012-10-20 Description An issue was discovered in the svgGetNextPathField function in svg string.c, which returns its input pointer in certain circumstances. This might result in a memory leak caused by wasteful mallo...

CVE-2018-17332: Missing Release of Resource after Effective Lifetime

An issue was discovered in libsvg2 through 2012-10-19. The svgGetNextPathField function in svgstring.c returns its input pointer in certain circumstances, which might result in a memory leak caused by wasteful malloc calls...

CVE-2018-17334: Out-of-bounds Write

An issue was discovered in libsvg2 through 2012-10-19. A stack-based buffer overflow in the svgGetNextPathField function in svgstring.c allows remote attackers to cause a denial of service application crash or possibly have unspecified other impact because a strncpy copy limit is miscalculated...