Hi,
And on the flip side, using an XSLT-based process to extract meaningful
information from a docx source is a nice way to read and understand its
contents (to some definition of "contents") without risk of executing embedded
macros ... a Word document is a program and XSLT offers a way to get the data
out of it -- maybe mapping it into another program such as an HTML page with
embedded Javascript.
Caveat executor, indeed.
Cheers, Wendell
-----Original Message-----
From: Michael Kay mike(_at_)saxonica(_dot_)com
<xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com>
Sent: Sunday, April 10, 2022 6:14 AM
To: xsl-list <xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com>
Subject: Re: [xsl] XSLT programs that blur the distinction between program and
data?
In general, any interpreter treats its data as "the program" ...
Needless to say using <xsl:evaluate> in unrestricted ways could be a
significant security risk,
Indeed. And I've certainly seen (and written) real applications in which
xsl:evaluate (or equivalent) was used to evaluate XPath expressions read from
cells in Excel spreadsheets. The operating system has no idea this is going on,
so the distinction between read permission and execute permission is
meaningless.
Michael Kay
Saxonica
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--