[
https://issues.apache.org/jira/browse/PDFBOX-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18108339#comment-18108339
]
Michael Klink commented on PDFBOX-6244:
---------------------------------------
{quote}Yes (rather a security report). And it was somebody who made a previous
security report (about something else) that did result in a CVE,{quote}
Ah, maybe the person who in a recently updated issue asked whether they "can
get a CVE for this?" 😉
Nonetheless, I still doubt JavaDocs are the appropriate place for such
clarifications, I still think a dedicated top-level documentation chapter
"Security Considerations" discussing intended PDFBox behavior in respect to
security features would be best.
Just talking about signatures may be not enough, though. I already see people
arguing that PDFBox should respect Purview Sensitivity Labels...
{quote}so I expected more security people to come up with this.{quote}
or more AIs? <sigh>
> Clarify that parsing doesn't check signatures
> ---------------------------------------------
>
> Key: PDFBOX-6244
> URL: https://issues.apache.org/jira/browse/PDFBOX-6244
> Project: PDFBox
> Issue Type: Improvement
> Components: Documentation
> Reporter: Tilman Hausherr
> Assignee: Tilman Hausherr
> Priority: Minor
> Fix For: 2.0.38, 3.0.9 PDFBox, 4.0.0
>
>
> Clarify that parsing doesn't check whether any signatures are verified /
> valid, and that loading a manipulated / "updated" PDF will not fail parsing.
> This applies to certification constraints as well. This behavior is not a
> security flaw, it's a missing feature. The ShowSignature example offers a
> limited signature check. The gold standard is Adobe Reader.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
