CVE-2017-16931
UnknownEPSS 4.45%
Last modified
CVE-2017-16931 is a vulnerability of currently unknown severity. parser.c in libxml2 before 2.9.5 mishandles parameter-entity references because the NEXTL macro calls the xmlParserHandlePEReference function in the case of a '%' character in a DTD name.. EPSS estimates a 4.45% chance of exploitation in the next 30 days.
Description
parser.c in libxml2 before 2.9.5 mishandles parameter-entity references because the NEXTL macro calls the xmlParserHandlePEReference function in the case of a '%' character in a DTD name.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Xmlsoft | Libxml2 | <= 2.9.4 |
References
- http://xmlsoft.org/news.htmlRelease Notes, Vendor Advisory
- https://bugzilla.gnome.org/show_bug.cgi?id=766956Permissions Required
- https://github.com/GNOME/libxml2/commit/e26630548e7d138d2c560844c43820b6767251e3Patch, Third Party Advisory
- http://xmlsoft.org/news.htmlRelease Notes, Vendor Advisory
- https://bugzilla.gnome.org/show_bug.cgi?id=766956Permissions Required
- https://github.com/GNOME/libxml2/commit/e26630548e7d138d2c560844c43820b6767251e3Patch, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-16931?
parser.c in libxml2 before 2.9.5 mishandles parameter-entity references because the NEXTL macro calls the xmlParserHandlePEReference function in the case of a '%' character in a DTD name.
How severe is CVE-2017-16931?
Severity scoring for CVE-2017-16931 is pending analysis. The EPSS model estimates a 4.45% probability of exploitation in the next 30 days.
How do I fix CVE-2017-16931?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
Are you affected by CVE-2017-16931?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST