Microsoft Word 2007 SP3, Office 2010 SP2, Word 2010 SP2, Office Compatibility Pack SP3, Word Viewer, Word Automation Services on SharePoint Server 2010 SP2, Word Automation Services on SharePoint Server 2013 SP1, Office Web Apps 2010 SP2, and Office Web Apps Server 2013 SP1 allow remote attackers to obtain sensitive information from process memory via a crafted Office document, aka Microsoft Office Information Disclosure Vulnerability.
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Office | Microsoft | 2010-sp2 (including) | 2010-sp2 (including) |
| Office_compatibility_pack | Microsoft | * | * |
| Office_web_apps | Microsoft | 2010-sp2 (including) | 2010-sp2 (including) |
| Office_web_apps | Microsoft | 2013-sp1 (including) | 2013-sp1 (including) |
| Sharepoint_server | Microsoft | 2010-sp2 (including) | 2010-sp2 (including) |
| Sharepoint_server | Microsoft | 2013-sp1 (including) | 2013-sp1 (including) |
| Word | Microsoft | 2007-sp3 (including) | 2007-sp3 (including) |
| Word | Microsoft | 2010-sp2 (including) | 2010-sp2 (including) |
| Word_viewer | Microsoft | * | * |
There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:
Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:
Information exposures can occur in different ways:
It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.