Threats affecting pkg:brew/xml2rfc

xml2rfc versions prior to 3.34.0 allow script elements within SVG sources, which can lead to cross-site scripting (XSS) vulnerabilities when rendering HTML output. This issue has been fixed in version 3.34.0. The vulnerability affects websites publishing HTML drafts and RFCs using xml2rfc. Workarounds include removing script elements from SVG files if the SVG source is self-contained within the XML.

xml2rfc versions prior to 3.34.0 have file inclusion irregularities where local file access restrictions are inconsistently enforced. Specifically, XML entity references can include files inside the source directory and below without requiring the --allow-local-file-access flag, and artwork or sourcecode elements with local file src attributes bypass this flag as well. This can lead to unintended disclosure of local files within the source directory when processing untrusted XML input. A fix in version 3.34.0 standardizes file access checks to restrict access appropriately.

xml2rfc versions prior to 3.34.0 contain a vulnerability that allows arbitrary file reads from the filesystem during PDF generation. This occurs when an attacker injects a malicious link element into the prepped RFCXML. The vulnerability has a high severity with a CVSS score of 8.7. A fix is available in version 3.34.0.

xml2rfc versions prior to 3.34.0 contain an arbitrary file read vulnerability. This flaw allows an attacker to read arbitrary files from the filesystem by injecting a malicious link element into the XML when generating PDF files. The vulnerability has a high severity with a CVSS score of 8.7. A fix is available in version 3.34.0. As a workaround, untrusted input with link elements having rel="attachment" should be tested before processing.