In July 2020, we introduced a novel attack class called Shadow Attacks. In our recent research, we discovered a new variant of the attack which relies only on an Incremental Update containing a malicioustrailer. A proof-of-concept exploit working on Foxit (Version: 22.214.171.124938) can be downloaded here.
The story so far ...
Shadow attacks are attacks bypassing the integrity protection of digitally signed PDF documents. The attacks abuse two legitimate features in PDF documents which we briefly explain.
In PDFs, there are multiple techniques to hide content that is not displayed when the document is opened. We, as attackers, usually hide malicious objects without referencing them in the xref section.
New content can be appended to a signed PDF document. This is quite dangerous though. The digital signature in PDFs protects a specific range of bytes. Any appended content does not break the signature verification since it is outside this range. As a result, any new Incremental Update does not violate the cryptographic verification of the digital signature.
But, Incremental Updates are quite dangerous since they may completely change the displayed content of the document. In 2019, we showed different techniques based on Incremental Updates – the Incremental Saving Attacks. As a countermeasure, most vendors warn if additional content is added after signing the document. BUT … not always!!!
There are meaningful use cases where Incremental Updates in digitally signed documents are allowed. For instance, contracts should be signed by multiple parties and each new signature is applied via additional Incremental Update. Also, PAdES defines Incremental Updates as part of the long-term validation of digitally signed PDFs. In summary, Incremental Updates are painful from a security perspective. Currently, vendors are trying to estimate whether an Incremental Update is malicious or not by analyzing its content.
Shadow attacks, in general, deceive the PDF applications that an Incremental Update is not malicious. This can be done by providing an Incremental Update with minimal content. In 2020, we estimated that appending an xref section and a trailer is sufficient to bypass the detection mechanisms of popular applications such as Adobe Reader and Foxit Reader.
Trailer-based Shadow Attack
Three months ago, we tried to reduce the content of the malicious Incremental Update. Our idea was to use only a malicioustrailer and still change the content of the entire document when it is opened. Let’s see how this can be done.
The Signer's view on the document
If a signer gets the document depicted on the left side, he or she sees the content “Sign the document to get a reward”. The document contains a hidden content depicted as red text – the 4 0 obj containing the text “You are fired. Get out immediately” and an xref section pointing to that object. However, the trailer references another xref section, see (1) and (2). Thus, the red text is never shown. From the signer's perspective, there is no possibility to detect the hidden content by opening and reviewing the document. As a result, the signer, for example the company director, signs the document.
The Victim's view on the document
We assume that the attacker receives the signed document and manipulates it. The attacker appends only a trailer that points to the hiddenmaliciousxref section (the red one). When the victim opens the document, the content “You are fired. Get out immediately” is shown. However, the digital signature validation does not throw any warning since … well … what could go wrong if only a trailer is appended.
Honest vs. Malicious Trailer
There are small differences between the honest and the malicioustrailer– the byte position of the xref section. Now, the trailer points to the hidden xref section.
Impact and Exploit
We successfully applied the new attack on Foxit Reader (Version: 126.96.36.199938). We promptly reported the vulnerability and provided a Proof-of-Concept (PoC) exploit, known as CVE-2021-40326. Foxit acknowledged the attack and published a security fix with the new version Foxit Reader 11.1.
We are not aware of any further implementations vulnerable to this attack. If you think that your application might be vulnerable to the attack, then just download the exploit and test on your own.