CVE-2008-5705: The cTrigger::DoIt function in src/ctrigger.cpp in the trigger mechanism in the daemon in Verlihub 0.9.8d-RC2 and earlier, when user triggers are enabled…

PriorityP258critical9.3CVSS 2.0

AVNACMAuNCCICAC

EXPLOIT

EPSS

5.42%

91.7th percentile

The cTrigger::DoIt function in src/ctrigger.cpp in the trigger mechanism in the daemon in Verlihub 0.9.8d-RC2 and earlier, when user triggers are enabled, allows remote attackers to execute arbitrary commands via shell metacharacters in an argument.

Affected

1 ranges

Vendor	Product	Version range	Fixed in
verlihub-project	verlihub	—	—

Detection & IOCsextracted from sources · hover to see the quote

path/tmp/trigger.tmp↗

→Look for shell metacharacters (backticks, semicolons, dollar signs, pipes, redirects, etc.) in trigger arguments sent to a Verlihub daemon — these are the injection vector in cTrigger::DoIt() ↗
→Monitor for unexpected child processes spawned by the Verlihub daemon process (verlihub), especially shells or commands like cat, id, whoami, which would indicate successful trigger-based RCE ↗
→Alert on creation or modification of /tmp/trigger.tmp by the Verlihub daemon, as this file is used as the output sink for injected shell commands ↗
→The vulnerable code path is specifically in src/ctrigger.cpp : cTrigger::DoIt() — target this function in source-level audits or binary analysis of Verlihub 0.9.8d-RC2 and earlier ↗

·Exploitation requires user triggers to be enabled in the Verlihub daemon configuration — deployments with triggers disabled are not vulnerable ↗
·If the Verlihub daemon is configured to run as root, successful exploitation yields full root-level command execution on the host ↗

CVEs like this are exactly what “Exploited This Week” covers.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.