Skip to content

Security: coilyco-flight-deck/umbra

SECURITY.md

Security Policy

Hello and thank you for your interest! πŸŽ‰ πŸ”’

Supported versions

This package is at v0. Only the latest commit on main is supported for security fixes - there are no published releases yet to backport to.

Version Supported
main (latest) βœ…
any pinned commit ❌ (upgrade)

Reporting a vulnerability

Please disclose any vulnerabilities by emailing coilysiren@gmail.com. Expect a first response within 48 hours; follow-up cadence by email after that. This project is run on volunteer time, so please have patience πŸ™‡

What counts as a vulnerability

umbra is a security-boundary framework. Issues here can have outsized impact on every downstream consumer. Specifically interested in reports of:

  • argv passing through policy.ValidateArgSlice that should have been rejected (shell metacharacter escapes, encoding tricks, locale-dependent bypasses)
  • audit log entries that are unparseable, truncatable, or omittable by the wrapped action
  • scope-token bypasses (a read token executing a write action, etc)
  • gittree.CheckClean returning OK on a tree that does not reconstruct from git history
  • CONNECT-proxy allowlist bypasses in the egress package

Out of scope (file as regular issues, not vulnerabilities):

  • bare urfave/cli framework bugs - report those upstream at urfave/cli
  • consumer misuse of the public API (e.g. forgetting to wire verb.Wrap) - that is a documentation issue
  • crashes on intentionally malformed yaml in repocfg - failing loudly is the intended behavior

There aren't any published security advisories