[
https://issues.apache.org/jira/browse/TIKA-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18014744#comment-18014744
]
Hudson commented on TIKA-4465:
------------------------------
SUCCESS: Integrated in Jenkins build Tika » tika-branch_3x-jdk11 #2167 (See
[https://ci-builds.apache.org/job/Tika/job/tika-branch_3x-jdk11/2167/])
TIKA-4465 -- fix inputstream type (tallison:
[https://github.com/apache/tika/commit/c20f28529a00b37a5cc5151265a0f92310858be4])
* (edit)
tika-parsers/tika-parsers-standard/tika-parsers-standard-modules/tika-parser-pdf-module/src/main/java/org/apache/tika/parser/pdf/AbstractPDF2XHTML.java
> Extract javascript from name tree in PDFs
> -----------------------------------------
>
> Key: TIKA-4465
> URL: https://issues.apache.org/jira/browse/TIKA-4465
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Minor
> Fix For: 4.0.0, 3.3.0
>
>
> This blog
> [https://labs.senhasegura.blog/unmasking-the-threat-a-deep-dive-into-the-pdf-malicious-2/]
> mentions this malware file (be careful! dangerous!):
> [https://bazaar.abuse.ch/download/4dc9b0c20ea61d91d6a1b5bdce76fb5365de0762efb8f6c2925113c6a8950cae/]
>
>
> We're currently extracting javascript from actions, but not from the name
> tree (document level-javascript).
>
> We should add this extraction if "extractActions" is set to true... or
> better, come up with a better name for that variable in trunk.
>
> Related to this, I'd also like to extract javascript in TikaCLI by default as
> we do for extracting inline images and incremental updates.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
