Microsoft Graphics Component Memory Corruption
CVE-2013-3906 is a high-severity improper control of generation of code vulnerability in Excel Viewer from Microsoft, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. CISA added it to the Known Exploited Vulnerabilities catalogue on February 15, 2022, which means attacks have been observed in the wild.
Attackers are already exploiting this vulnerability, according to CISA.
What to do
- Check which version of Excel Viewer you run against the affected versions below, and install the vendor's latest release.
- CISA's required action: Apply updates per vendor instructions.
- Read the advisory on technet.microsoft.com for workarounds and exact fixed builds.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Microsoft | Excel Viewer | Not specified in the record | Not stated |
| Microsoft | Lync | 2010; 2013 | Not stated |
| Microsoft | Office | 2003; 2007; 2010 | Not stated |
| Microsoft | Office Compatibility Pack | Not specified in the record | Not stated |
| Microsoft | Powerpoint Viewer | 2010 | Not stated |
| Microsoft | Word Viewer | Not specified in the record | Not stated |
| Microsoft | Windows Server 2008 | Not specified in the record | Not stated |
| Microsoft | Windows Vista | Not specified in the record | Not stated |
Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.8 | High | NVD |
| CVSS 3.1 | 7.8 | High | CISA (ADP) |
| CVSS 2.0 | 9.3 | High | NVD |
Official description
GDI+ in Microsoft Windows Vista SP2 and Server 2008 SP2; Office 2003 SP3, 2007 SP3, and 2010 SP1 and SP2; Office Compatibility Pack SP3; and Lync 2010, 2010 Attendee, 2013, and Basic 2013 allows remote attackers to execute arbitrary code via a crafted TIFF image, as demonstrated by an image in a Word document, and exploited in the wild in October and November 2013.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Control of Generation of Code
The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
How developers prevent this class of flaw
- Refactor your program so that you do not have to dynamically generate code.
- Run your code in a jail or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which code can be executed by your product. Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection. This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise. Be careful to avoid CWE-243 and other weaknesses related to jails.
- Use dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.
More Improper Control of Generation of Code vulnerabilities (CWE-94)
Timeline
- CVE record published.
- Added to CISA's Known Exploited Vulnerabilities catalogue.
- Deadline for US federal agencies to remediate, set by CISA.
- CISA published its SSVC assessment (exploitation: active, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Third-party and government advisories
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2013-3906US Government Resource
Technical write-ups (may include proof of concept)
- exploit-db.com/exploits/30011Exploit, Third Party Advisory, VDB Entry
Other vulnerabilities in Excel Viewer
- 8.8 High severity
Microsoft MSHTML Remote Code Execution Exploited
- 7.8 High severity
Microsoft Office Security Feature Bypass Exploited
- 9.3 High severity
Microsoft PowerPoint Memory Corruption Exploited
- 7.8 High severity
- 9.3 High severity
Microsoft Office Remote Code Execution Exploited
- 9.3 High severity
Recent Improper Control of Generation of Code vulnerabilities
- 9.8 Critical severity
- 8.8 High severity
- 9.8 Critical severity
- 7.8 High severity
- 9.3 High severity
- 9.8 Critical severity
phpMyAdmin Remote Code Execution Exploited
Spotted an error? Tell us.