lintai docs

Appearance

Rule Reference

SEC345lintai-ai-securitystablejsonwarn

Plugin hook: TLS verification disabled

Plugin hook command disables TLS verification in a network-capable execution path

Provider
lintai-ai-security
Surface
json
Scope
per_file
Tier
stable
Severity
warn
Confidence
high
Detection
structural
Remediation
message_only

Activation Model

Preset Membership

This rule is part of the builtin activation graph through these preset memberships.

basemembership
mcpmembership

Lifecycle

Stable Lifecycle Contract

State

stable_gated

Graduation rationale

Checks committed plugin hook command values for explicit TLS-bypass tokens in a network-capable execution context.

Deterministic signal basis

JsonSignals command-string analysis over ArtifactKind::CursorPluginHooks objects gated by network markers plus TLS-bypass tokens.

Malicious corpus
plugin-hook-command-tls-bypass
Benign corpus
plugin-hook-command-safe
structured evidence required remediation reviewed
Canonical note

Structural stable rule intended as a high-precision check with deterministic evidence.

Nearby Signals

Related Rules

SEC301MCP config: shell trampolineMCP configuration shells out through sh -c or bash -cjsonstable
SEC302Config: insecure HTTP endpointConfiguration contains an insecure http:// endpointjsonstable
SEC303MCP config: credential env passthroughMCP configuration passes through credential environment variablesjsonstable
SEC304Config: TLS verification disabledConfiguration disables TLS or certificate verificationjsonstable
SEC305Config: hardcoded auth materialConfiguration embeds static authentication material in a connection or auth valuejsonstable
SEC309Config: literal secrets in configConfiguration commits literal secret material in env, auth, or header valuesjsonstable

Why It Matters ​

A committed plugin hook that disables certificate verification weakens the trust boundary for every machine that runs the hook. In this context the unsafe setting is part of shipped executable behavior.

What Triggers ​

SEC345 applies to committed plugin hook command values and triggers when a network-capable hook command contains explicit TLS-bypass markers such as --insecure.

Example that triggers:

json
{"hooks":{"stop":[{"command":"curl --insecure https://internal.test/bootstrap.sh"}]}}

Example that stays clean:

json
{"hooks":{"stop":[{"command":"node ./hooks/cleanup.js --mode safe"}]}}

False Positives ​

The rule is structural and gated by both network context and explicit TLS-bypass markers.

Remediation ​

Remove the TLS-bypass flag or NODE_TLS_REJECT_UNAUTHORIZED=0 style override from the network-capable plugin hook command.