Requested by: @U3P2L4XNE
Slack thread: https://slack.com/archives/C0ALHS9H3S5/p1782282700481099
-
Branch/Environment:
- Environment: Visor SandboxJS
-
Describe the bug:
The Visor SandboxJS environment silently aborts execution when an await expression is placed inside a try-catch block. The script stops executing and returns undefined without throwing any visible errors.
-
Reproduction steps:
- Create a Visor script with a
try-catch block.
- Inside the
try block, add an await expression (e.g., await bash(...)).
- Run the script.
-
Actual behavior:
The script execution silently aborts at the await expression and returns undefined.
-
Expected behavior:
The await expression should execute normally inside the try-catch block, or if there's an error, it should be caught by the catch block.
-
Business Impact:
- Blocking implementation? Yes, it causes scripts like the CVE processor to fail silently and report incorrect results (e.g., Processed: 0).
Requested by: @U3P2L4XNE
Slack thread: https://slack.com/archives/C0ALHS9H3S5/p1782282700481099
Branch/Environment:
Describe the bug:
The Visor SandboxJS environment silently aborts execution when an
awaitexpression is placed inside atry-catchblock. The script stops executing and returnsundefinedwithout throwing any visible errors.Reproduction steps:
try-catchblock.tryblock, add anawaitexpression (e.g.,await bash(...)).Actual behavior:
The script execution silently aborts at the
awaitexpression and returnsundefined.Expected behavior:
The
awaitexpression should execute normally inside thetry-catchblock, or if there's an error, it should be caught by thecatchblock.Business Impact: