FreshPorts - VuXML

This page displays vulnerability information about FreeBSD Ports.

The last vuln.xml file processed by FreshPorts is:

Revision:  519779
Date:      2019-12-10
Time:      21:06:04Z
Committer: mfechner

List all Vulnerabilities, by package

List all Vulnerabilities, by date

These are the vulnerabilities relating to the commit you have selected:

I found 2 entries for ce4b3af8-0b7c-11e1-846b-00235409fd3e. There should be only one.
VuXML IDDescription
0642b064-56c4-11e4-8b87-bcaec565249clibxml2 -- Denial of service

RedHat reports:

A denial of service flaw was found in libxml2, a library providing support to read, modify and write XML and HTML files. A remote attacker could provide a specially crafted XML file that, when processed by an application using libxml2, would lead to excessive CPU consumption (denial of service) based on excessive entity substitutions, even if entity substitution was disabled, which is the parser default behavior.


Discovery 2014-10-16
Entry 2014-10-18
Modified 2015-07-15
libxml2
lt 2.9.2

linux-c6-libxml2
lt 2.7.6_2

linux-f10-libxml2
ge *

CVE-2014-3660
https://rhn.redhat.com/errata/RHSA-2014-1655.html
57f1a624-6197-11e1-b98c-bcaec565249clibxml2 -- heap buffer overflow

Google chrome team reports:

Heap-based buffer overflow in libxml2, allows remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors.


Discovery 2012-01-05
Entry 2012-02-27
libxml2
linux-f10-libxml2
lt 2.7.8_2

CVE-2011-3919
http://googlechromereleases.blogspot.com/2012/01/stable-channel-update.html
76e59f55-4f7a-4887-bcb0-11604004163alibxml2 -- Multiple Issues

libxml2 developers report:

The htmlParseTryOrFinish function in HTMLparser.c in libxml2 2.9.4 allows attackers to cause a denial of service (buffer over-read) or information disclosure.

A buffer overflow was discovered in libxml2 20904-GITv2.9.4-16-g0741801. The function xmlSnprintfElementContent in valid.c is supposed to recursively dump the element content definition into a char buffer 'buf' of size 'size'. The variable len is assigned strlen(buf). If the content->type is XML_ELEMENT_CONTENT_ELEMENT, then (i) the content->prefix is appended to buf (if it actually fits) whereupon (ii) content->name is written to the buffer. However, the check for whether the content->name actually fits also uses 'len' rather than the updated buffer length strlen(buf). This allows us to write about "size" many bytes beyond the allocated memory. This vulnerability causes programs that use libxml2, such as PHP, to crash.

libxml2 20904-GITv2.9.4-16-g0741801 is vulnerable to a stack-based buffer overflow. The function xmlSnprintfElementContent in valid.c is supposed to recursively dump the element content definition into a char buffer 'buf' of size 'size'. At the end of the routine, the function may strcat two more characters without checking whether the current strlen(buf) + 2 < size. This vulnerability causes programs that use libxml2, such as PHP, to crash.

libxml2 20904-GITv2.9.4-16-g0741801 is vulnerable to a heap-based buffer over-read in the xmlDictComputeFastKey function in dict.c. This vulnerability causes programs that use libxml2, such as PHP, to crash. This vulnerability exists because of an incomplete fix for libxml2 Bug 759398.

libxml2 20904-GITv2.9.4-16-g0741801 is vulnerable to a heap-based buffer over-read in the xmlDictAddString function in dict.c. This vulnerability causes programs that use libxml2, such as PHP, to crash. This vulnerability exists because of an incomplete fix for CVE-2016-1839.


Discovery 2017-05-10
Entry 2017-12-13
libxml2
le 2.9.4

https://bugzilla.gnome.org/show_bug.cgi?id=775200
http://www.openwall.com/lists/oss-security/2017/05/15/1
http://www.securityfocus.com/bid/98599
http://www.openwall.com/lists/oss-security/2017/05/15/1
http://www.securityfocus.com/bid/98556
http://www.openwall.com/lists/oss-security/2017/05/15/1
http://www.securityfocus.com/bid/98601
http://www.openwall.com/lists/oss-security/2017/05/15/1
http://www.securityfocus.com/bid/98568
CVE-2017-8872
CVE-2017-9047
CVE-2017-9048
CVE-2017-9049
CVE-2017-9050
7be92050-a450-11e2-9898-001060e06fd4libxml -- Integer overflow

Integer overflow in xpath.c, allows context-dependent attackers to to cause a denial of service (crash) and possibly execute arbitrary code via a crafted XML file that triggers a heap-based buffer overflow when adding a new namespace node, related to handling of XPath expressions.


Discovery 2011-09-02
Entry 2011-11-10
Modified 2011-11-12
libxml
lt 1.8.17_5

libxml2
linux-f10-libxml2
lt 2.7.8

CVE-2011-1944
843a4641-9816-11e2-9c51-080027019be0libxml2 -- cpu consumption Dos

Kurt Seifried reports:

libxml2 is affected by the expansion of internal entities (which can be used to consume resources) and external entities (which can cause a denial of service against other services, be used to port scan, etc.)..


Discovery 2013-02-21
Entry 2013-03-29
libxml2
lt 2.8.0

CVE-2013-0338
CVE-2013-0339
http://seclists.org/oss-sec/2013/q1/391
https://security-tracker.debian.org/tracker/CVE-2013-0338
https://security-tracker.debian.org/tracker/CVE-2013-0339
847ade05-6717-11d8-b321-000a95bc6faelibxml2 stack buffer overflow in URI parsing

Yuuichi Teranishi reported a crash in libxml2's URI handling when a long URL is supplied. The implementation in nanohttp.c and nanoftp.c uses a 4K stack buffer, and longer URLs will overwrite the stack. This could result in denial-of-service or arbitrary code execution in applications using libxml2 to parse documents.


Discovery 2004-02-08
Entry 2004-02-25
libxml2
lt 2.6.6

CVE-2004-0110
http://www.xmlsoft.org/news.html
http://mail.gnome.org/archives/xml/2004-February/msg00070.html
9c7177ff-1fe1-11e5-9a01-bcaec565249clibxml2 -- Enforce the reader to run in constant memory

Daniel Veilland reports:

Enforce the reader to run in constant memory. One of the operation on the reader could resolve entities leading to the classic expansion issue. Make sure the buffer used for xmlreader operation is bounded. Introduce a new allocation type for the buffers for this effect.


Discovery 2015-04-14
Entry 2015-07-01
Modified 2016-01-31
libxml2
lt 2.9.2_3

linux-c6-libxml2
lt 2.7.6_5

linux-f10-libxml2
ge *

CVE-2015-1819
https://git.gnome.org/browse/libxml2/commit/?id=213f1fe0d76d30eaed6e5853057defc43e6df2c9
9ff4c91e-328c-11d9-a9e7-0001020eed82libxml -- remote buffer overflows

infamous41md reports that libxml contains multiple buffer overflows in the URL parsing and DNS name resolving functions. These vulnerabilities could lead to execution of arbitrary code.


Discovery 2004-10-26
Entry 2004-11-09
Modified 2004-11-10
libxml
lt 1.8.17_3

libxml2
lt 2.6.15

CVE-2004-0989
11526
http://marc.theaimsgroup.com/?l=bugtraq&m=109880813013482
http://www.debian.org/security/2004/dsa-582
b8ae4659-a0da-11e1-a294-bcaec565249clibxml2 -- An off-by-one out-of-bounds write by XPointer

Google chrome team reports:

An off-by-one out-of-bounds write flaw was found in the way libxml, a library for providing XML and HTML support, evaluated certain XPointer parts (XPointer is used by libxml to include only the part from the returned XML document, that can be accessed using the XPath expression given with the XPointer). A remote attacker could provide a specially-crafted XML file, which once opened in an application, linked against libxml, would lead to that application crash, or, potentially arbitrary code execution with the privileges of the user running the application.

Note: The flaw to be exploited requires the particular application, linked against libxml, to use the XPointer evaluation functionality.


Discovery 2012-05-15
Entry 2012-05-18
Modified 2014-04-30
libxml2
lt 2.7.8_3

linux-f10-libxml2
lt 2.7.8_3

CVE-2011-3202
http://googlechromereleases.blogspot.com/2012/05/stable-channel-update.html
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2011-3102