McAfee spots Adobe Reader PDF-tracking flaw

McAfee said it has found a vulnerability in Adobe Systems’ Reader program that reveals when and where a PDF document is opened.

The issue is not a serious problem and does not allow for remote code execution, wrote McAfee’s Haifei Li in a blog post. But McAfee does consider it a security problem and has notified Adobe. It affects every version of Adobe Reader, including the latest version, 11.0.2, Li wrote.

McAfee recently detected some “unusual” PDF samples, Li wrote. McAfee withheld some key details of the vulnerability, but did generally describe it.

The issue occurs when someone launches a link to another file path, which calls on a JavaScript API (application programming interface). Reader warns a user when they are going to call on a resource from another place, such as a link on the Internet.

If the external resource does not exist, the warning dialog does not appear, but the API returns some TCP traffic, Li wrote. By manipulating a second parameter with a special value, the API’s behavior changes to reveal information. That could include information such as the location of a document on a system “by calling the JavaScript ‘this.path’ value,” Li wrote.

“Malicious senders could exploit this vulnerability to collect sensitive information such as IP address, Internet service provider or even the victim’s computing routine,” Li wrote. “In addition, our analysis suggests that more information could be collected by calling various PDF JavaScript APIs.”

Li suggests the problem could be used for reconnaissance by attackers.

“Some people might leverage this issue just out of curiosity to know who has opened their PDF documents, but others won’t stop there,” Li wrote. “An APT [advanced persistent threat] attack usually consists of several sophisticated steps. The first step is often collecting information from the victim; this issue opens the door.”

McAfee suggests that Adobe Reader users disable JavaScript until a patch is released. Adobe officials could not be immediately reached for comment.

Send news tips and comments to jeremy_kirk@idg.com. Follow me on Twitter: @jeremy_kirk