Skip to content

fix: validate inputs to prevent GITHUB_ENV injection#2

Merged
stack72 merged 1 commit intomainfrom
security/input-validation
Apr 3, 2026
Merged

fix: validate inputs to prevent GITHUB_ENV injection#2
stack72 merged 1 commit intomainfrom
security/input-validation

Conversation

@stack72
Copy link
Copy Markdown
Contributor

@stack72 stack72 commented Apr 3, 2026

Summary

  • Add newline validation on api-key and swamp-club-url inputs to prevent GITHUB_ENV injection — a multiline value could inject arbitrary environment variables into subsequent workflow steps
  • Enforce https:// scheme on swamp-club-url to prevent credentials from being sent over plaintext HTTP or to non-HTTP destinations

Test plan

  • Existing CI tests pass (no change to happy-path behavior)
  • Manually verify that passing a URL without https:// prefix fails with a clear error
  • Manually verify that passing a value with embedded newlines fails with a clear error

🤖 Generated with Claude Code

Add newline checks on api-key and swamp-club-url inputs to prevent
environment variable injection via GITHUB_ENV. Also enforce https://
scheme on swamp-club-url to prevent credentials being sent over
plaintext or to non-HTTP destinations.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@stack72 stack72 merged commit f2f0ff9 into main Apr 3, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant