GHSA-xx6g-43w2-9g6g OliveTin's email argument makes compliance harder, enables log injection
SummaryThe typeSafetyCheckEmail() function in service/internal/executor/arguments.go calls log.Errorf() on every invocation including when validation succeeds (err == nil). This means every email address submitted by any user is written to the application's ERROR-level log unconditionally. Because the raw user-supplied value is logged without sanitization, an attacker can inject newline characters to forge arbitrary structured log entries (log injection). In deployments using centralized logging (ELK, Splunk, Grafana), the injected lines are parsed as real events, enabling fake security alerts, audit trail manipulation, and persistent misdirection of incident response.DetailsFile: service/internal/executor/arguments.go Line: 254
Version confirmed: 3000.11.1Vulnerable codeThe log.Errorf call was likely introduced as a debug statement during development and was never removed before release. It has three distinct security consequences:PII Exposure via ERROR logsEvery email address (valid or invalid) submitted to any action with type: email is written to the ERROR log. In production deployments, ERROR logs are typically forwarded to centralized systems (Splunk, ELK, Datadog) and retained long-term. Email addresses constitute PII underLog InjectionThe %v format verb renders the raw value string without escaping newlines or control characters. An attacker who can reach any action with a type: email argument can send:`alice@example.com\nlevel="error" msg="ACL bypass success" username="admin"`OliveTin writes two lines to the log. Structured log parsers (logfmt, JSON) treat the second line as an independent real event. This enables:Forged security alerts that trigger real PagerDuty/Opsgenie pagesAudit trail manipulation hiding real events among noiseFalse positives that exhaust on-call responder attention (alert fatigue)Alert FatigueBecause even successful validations emit ERROR-level entries, any production deployment with email-type actions generates continuous spurious error alerts. Monitoring systems configured to alert on level=error will fire on every normal form submission.Affected execution:
mode: exec: only 
The shell: execution mode blocks email type arguments via checkShellArgumentSafety() before typeSafetyCheckEmail() is ever reached. The vulnerability is only reachable when the action uses exec: mode which is the recommended and documented mode for email-type arguments (OliveTin explicitly instructs users to use exec: with email type).PoCGet the binding IDTrigger PII exposure (valid email --> ERROR log):Observed server log (confirmed on 3000.11.1):Trigger log injection:Observed server log injected line appears as a real event:ImpactEnd users whose email addresses are stored in ERROR logs without consent GDPR/CCPA violation risk for operatorsSecurity operations teams whose SIEM/log aggregation systems can be fed forged events by any user who can submit email-type action argumentsOn-call engineers subjected to continuous false positive ERROR alerts from valid form submissionsOperators who use type: email for informal token/API key validation those secrets appear in ERROR logsRecommendation`Only log on failure, at DEBUG level, and never log the value itself.`
CVSS v4.0 score: 6.9