T06 · System Persistence
- Location
SKILL.md:39- Finding
Persistent TDengine Service Enabled Without Explicit Opt-In
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 39–43
Vulnerability Type: System service persistence
Risk Level: Highbash ### 3. 启动服务 安装完成后,通过 systemd 管理服务: ```bash systemctl start taosd systemctl enable taosdTechnical Analysis
The instruction
systemctl enable taosdregisters the TDengine daemon with the system service manager so that it starts automatically during subsequent boots. This creates cross-session persistence and changes system-wide startup configuration, normally requiring elevated privileges.Persistent startup is related to operating a database server, but it is not required to complete installation or perform the documented one-time database validation. Enabling the service by default therefore exceeds the minimum privileges and system modifications necessary for basic setup. The persistence also increases the consequences of a compromised or untrusted TDengine installation because any substituted daemon would execute automatically after reboot.
Attack Path
- The user follows the documented installation procedure, potentially with administrative privileges.
- The external TDengine installer installs the
taosdexecutable and its systemd service definition. - The user runs
systemctl start taosd, launching the database daemon. - The user runs
systemctl enable taosd, registering the daemon for automatic execution at system startup. - The daemon continues to execute after reboots. If the downloaded distribution or installed service has been compromised, attacker-controlled code receives persistent execution through the enabled service.
Impact Assessment
The change affects the host's system-wide service configuration and survives both the Skill run and system reboots. It requires administrative authorization in a typical Linux environment.
The persistent daemon expands the machine's network attack surface, particularly if TDengine listens on the ...[truncated 357 chars]
- Remediation
View remediation
Remediation Suggestions
- Do not enable the service automatically as part of the default installation flow.
- Start the service only for immediate validation with
systemctl start taosd. - Present boot-time enablement as a separate, optional step that requires explicit user consent.
- Explain that
systemctl enablechanges persistent, system-wide configuration and generally requires administrative privileges. - Run
taosdunder a dedicated, unprivileged service account with restrictive systemd hardening options. - Bind the service only to required trusted interfaces and restrict ports 6030–6041 with host and network firewalls.
- Provide rollback commands such as
systemctl disable --now taosdand documented uninstall procedures. - Verify the installed executable and service definition before enabling automatic startup.
