You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
3. Configure the rest of the settings accordingly (BODY, LHOST, LPORT, etc)
32
30
4.```exploit```
@@ -62,3 +60,38 @@ While editing, you should avoid modifying the following unless you are an advanc
62
60
in front of the payload string. The blank space is for making the payload less obvious
63
61
at first sight if the user views the file properties.
64
62
* The VB code in the macro.
63
+
64
+
## Trusted Document
65
+
66
+
By default, Microsoft Office does not execute macros automatically unless it is considered as a
67
+
trusted document. This means that if a macro is present, the user will most likely need to manually
68
+
click on the "Enable Content" button in order to run the macro.
69
+
70
+
Many in-the-wild attacks face this type of challenge, and most rely on social-engineering to trick
71
+
the user into allowing the macro to run. For example, making the document look like something
72
+
written from a legit source, such as [this attack](https://motherboard.vice.com/en_us/article/these-hackers-cleverly-disguised-their-malware-as-a-document-about-trumps-victory).
73
+
74
+
To truly make the macro document to run without any warnings, you must somehow figure out a way to
75
+
sign the macro by a trusted publisher, or using a certificate that the targeted machine trusts.
76
+
77
+
For testing purposes, another way to have a certificate is to create a self-signed one using
78
+
Microsoft Office's SELFCERT.exe utility. This tool can be found in the following path on
0 commit comments