Facebook Google Plus Twitter LinkedIn YouTube RSS Menu Search Resource - BlogResource - WebinarResource - ReportResource - Eventicons_066 icons_067icons_068icons_069icons_070

[R2] Oracle Outside In Content Access vspdf.dll Multiple Remote DoS



Oracle Outside In Content Access vspdf.dll Catalog Dictionary /Pages Key Handling Infinite Loop DoS (CVE-2017-3294 / S0788726)

While exploring the details of MS16-108 to develop a detection plugin for Nessus, Tenable found an infinite loop vulnerability in the vspdf.dll library used by Microsoft Exchange Server, which is actually part of the Oracle Outside In libraries used by Exchange. Inside the DLL, there is a segment of code to recursively retrieve the indirect object from a "reference" object. If the indirect object refers to itself, an infinite loop is formed. That segment of code is found in many places in the DLL. To cause an infinite loop, an attacker would need to craft a PDF file with specific content to trigger it.

When vspdf.dll processes the /Pages key in the Catalog dictionary, it references object 8, which references itself, causing an infinite loop. A complete attack PDF (obj_ref_loop.pdf) has been created as a proof of concept for the vendor. This was tested against 64-bit vspdf.dll, (used in Microsoft Exchange Server) and 64-bit vspdf.dll, (used in Oracle Outside In).

Other notes: A up-to-date Microsoft Exchange Server uses vspdf.dll in scanningprocess.exe. The infinite loop can be triggered by sending an email with a specially crafted PDF file to the Exchange Server. It appears that multiple instances of scanningprocess.exe (three in Exchange Server 2013 SP1) are spawned to scan email attachments, and scanningprocess.exe is being monitored (likely by another watch-dog process). If scanningprocess.exe is not responsive (i.e., attached to a debugger, one of the threads is in infinite loop state) within a certain amount of time (approximately a couple of minutes), the process gets terminated and a new scanningprocess.exe is spawned.

Oracle Outside In Content Access vspdf.dll /CalRGB /Matrix Entry Handling Invalid Read DoS (CVE-2017-3295 / S0788761)

A second new vulnerability we discovered is a read access violation (DoS) in the code that processes the /Matrix entry within a /CalRGB entry. The code assumes there are nine elements in the value of the /Matrix key. An attacker can supply less than 9 elements, causing a read access violation. This was tested in 64-bit vspdf.dll, (used in Microsoft Exchange Server) and 64-bit vspdf.dll, (used in Oracle Outside In).


Oracle has released patches to address this vulnerability, as part of the January 17, 2017 CPU.

Disclosure Timeline

2016-10-03 - Issue discovered
2016-10-17 - Issue reported to Oracle via [email protected] a day before Oct CPU fixes 247 vulns
2016-10-18 - Oracle acks the report
2016-10-19 - Oracle assigns S0788726 to "OIT Content Access vspdf.dll Reference Object Handling Infinite Loop DoS" and S0788761 to "OIT Read Access Violation (DoS) Processing CalRGB"
2016-10-25 - Oracle automated status, "Issue fixed in main codeline, scheduled for a future CPU"
2016-11-22 - Oracle automated status, "Issue fixed in main codeline, scheduled for a future CPU"
2016-12-21 - Oracle automated status, "Issue fixed in main codeline, scheduled for a future CPU"
2017-01-13 - Oracle automated status, "fixed in the upcoming Critical Patch Update, January 17, 2017"
2017-01-16 - Tenable asks for the CVE assignments for these issues
2017-01-17 - Oracle releases Jan 2017 CPU
2017-01-17 - Oracle replies with our assignments
2017-01-18 - Tenable asks about Oracle CVSS scores for the two issues, considerably different than ours
2017-01-23 - Oracle replies with CVSS "justification" and fixes creditee
2017-01-23 - Tenable gives more CVSS scoring feedback
2017-01-24 - Oracle says they are reviewing the CVSS scores
2017-01-25 - Oracle agrees with our CVSS scores, will update advisory
2017-01-30 - Oracle updates advisory with new CVSS scores

All information within TRA advisories is provided “as is”, without warranty of any kind, including the implied warranties of merchantability and fitness for a particular purpose, and with no guarantee of completeness, accuracy, or timeliness. Individuals and organizations are responsible for assessing the impact of any actual or potential security vulnerability.

Tenable takes product security very seriously. If you believe you have found a vulnerability in one of our products, we ask that you please work with us to quickly resolve it in order to protect customers. Tenable believes in responding quickly to such reports, maintaining communication with researchers, and providing a solution in short order.

For more details on submitting vulnerability information, please see our Vulnerability Reporting Guidelines page.

If you have questions or corrections about this advisory, please email [email protected]