能否使用Nessus攻击脚本语言（NASL）调用运行C++程序？

Great question—let’s dive into whether this is feasible and how to pull it off.

Core Answer: Yes, but with key constraints #

NASL (Nessus Attack Scripting Language) does support executing external programs/scripts via its built-in exec() function. This means triggering your C++ Zigbee-to-MQTT bridge is technically possible, though you’ll need to account for Nessus’s security model and runtime permissions.

How to Implement It #

Here’s a quick example of how you’d call your C++ program from a NASL script:

# Define the absolute path to your compiled C++ binary
zigbee_mqtt_bridge = "/opt/zigbee-mqtt-bridge/bridge";

# Execute the program and capture its output (optional)
bridge_output = exec(cmd: zigbee_mqtt_bridge, output: TRUE);

# Verify execution status
if (typeof(bridge_output) == "string") {
  display("Bridge started successfully. Output: " + bridge_output);
} else {
  display("Failed to launch the Zigbee-to-MQTT bridge. Check permissions/path.");
}

If you need to pass command-line arguments to your C++ program, just append them to the cmd string:

bridge_output = exec(cmd: zigbee_mqtt_bridge + " --config /etc/bridge-config.json", output: TRUE);

Critical Feasibility & Security Notes #

For this to work reliably, you’ll need to address these points:

• File Permissions: The user account running Nessus (typically nessus or root depending on your setup) must have execute permissions for your C++ binary, plus any read/write access it needs to its config files or hardware interfaces.
• Nessus Configuration: By default, Nessus restricts external program execution for untrusted scripts. Ensure your custom NASL script is placed in Nessus’s designated custom scripts directory (usually /opt/nessus/lib/nessus/plugins/custom/ or similar) and that Nessus’s security settings allow external execution for trusted scripts.
• Security Risks: Calling external programs introduces attack surface—never use user-controlled input to build your exec() command (this opens you to command injection). Also, run Nessus with the least privilege necessary; avoid running it as root unless your bridge absolutely requires it.

Final Verdict #

Your proposed approach is fully feasible as long as you handle permissions, pathing, and security constraints correctly. The exec() function is the standard way to trigger external tools from NASL, so it should work smoothly for your Zigbee-to-MQTT bridge.

内容的提问来源于stack exchange，提问作者LostJosh