Malicious RTF — malware analysis report

Static analysis result for SHA-256 8c04c33ea4357f69…

MALICIOUS

RTF

48.6 KB Created: 2011-11-15 09:21:00 Authoring application: TX_RTF32 10.1.323.501 First seen: 2017-12-24
MD5: 5fe6704f1436b4179ca68577b0af79c0 SHA-1: 575352dc1caf8826850334ad33e5f5ec9b9d4d49 SHA-256: 8c04c33ea4357f69326ce38b9f84a2c5610f4b3dfe22dcd92b73f9de31033487
282 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF file contains critical heuristics indicating exploitation of CVE-2017-0199 via a composite moniker. This vulnerability allows the document to fetch and execute an embedded OLE object from a remote URL. The presence of ClamAV's Rtf.Exploit.CVE_2017_0199-6335035-0 detection further confirms this exploit.

Heuristics 7

  • Composite Moniker — CVE-2017-8570 (drops SCT script) critical CVE related CVE_2017_8570
    RTF \objdata decodes to OLE data containing the Composite Moniker — CVE-2017-8570 (drops SCT script) CLSID — the vulnerable control/moniker is embedded directly in the document's object stream, the delivery shape of this exploit. RTF objects auto-render when Word opens the file.
  • CVE-2017-0199 (OLE2Link / remote URL Moniker) critical CVE likely CVE_2017_0199
    RTF contains a URL Moniker OLE link whose decoded target is remote. Office can fetch and process the response through the CVE-2017-0199 OLE2Link attack path, but the server-side content type is not proven statically.
  • Composite Moniker in RTF OLE object high CVE related RTF_COMPOSITE_MONIKER_RELATED
    RTF contains Composite Moniker CLSID in OLE object context, but no nearby scriptlet/SCT payload was confirmed. Treat as related moniker attack-surface evidence rather than proof of CVE-2017-8570 exploitation.
  • ClamAV: Rtf.Exploit.CVE_2017_0199-6335035-0 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Rtf.Exploit.CVE_2017_0199-6335035-0
  • Automatically linked OLE object high RTF_OBJAUTLINK
    RTF contains \objautlink — an automatically linked OLE object surface that can be updated or activated when Word opens the document.
  • OLE object data medium RTF_OBJDATA
    RTF contains 2 \objdata section(s) — embedded OLE objects
  • Embedded URL info EMBEDDED_URL
    One or more URLs were extracted from the document. The URL itself is not a detection — see the per-URL labels for which channel (macro, JS, link annotation, document body, ...) reached each URL.
    URL http://schemas.microsoft.com/office/word/2003/wordml In RTF body
    • https://methodm.cerner.com/client/7237/UBMC_UT_Community_Works_Implementation/ProjectDeliverables/CommWx_System%20Review_Data%20Collection%20-%20Core.xlsIn RTF body

Extracted artifacts 2

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off000017c4.bin rtf-objdata-decoded RTF \objdata at offset 0x17C4 3625 bytes
SHA-256: 59b648007ca86a9ff69052f8c4282aafaad31c59c2ab910c417da8aa9b37865b
objdata_01_off000037e0.bin rtf-objdata-decoded RTF \objdata at offset 0x37E0 3625 bytes
SHA-256: 6a01f84c1a8c2f2308411818ea29ae9b51225be9e2b28400fc7e190c092d996a

Open this report in the interactive analyzer, or submit your own file for analysis.