libxml2: Buffer overflow in function xmlSnprintfElementContent
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Text-Only JBCS | |||
| cpe:/a:redhat:jboss_core_services:1 | RHSA-2018:2486 | 2018-08-16T00:00:00Z | |
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-1008-1 | libxml2 security update |
Debian DLA |
DLA-4064-1 | libxml2 security update |
Debian DSA |
DSA-3952-1 | libxml2 security update |
EUVD |
EUVD-2017-17987 | 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. |
Ubuntu USN |
USN-3424-1 | libxml2 vulnerabilities |
Ubuntu USN |
USN-3424-2 | libxml2 vulnerabilities |
No CVSS v4.0
No CVSS v3.1
This CVE is not in the KEV list.
Exploit prediction score: 3.2% (3.185% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
epss
|
epss
|