| title | Security Policy |
|---|---|
| description | Vulnerability reporting process for the ma2-onPC-mcp MCP server |
| version | 1.1.0 |
| created | 2026-04-04 00:00:00 UTC |
| last_updated | 2026-04-07 19:09:40 UTC |
| Version | Supported |
|---|---|
| 3.35.x | Yes |
| < 3.35 | No |
The following components are in scope for security reports:
- MCP server (
src/server.py,src/server_orchestration_tools.py) — tool dispatch, input validation, safety gate - Telnet client (
src/telnet_client.py) — command injection, authentication, session handling - Auth & credentials (
src/auth.py,src/credentials.py) — OAuth scope enforcement, credential resolution - Session manager (
src/session_manager.py) — session pool, keepalive, reconnect - License enforcement (
src/license.py,src/license_tiers.py) — tier gating bypass - Agent harness (
src/agent/) — plan-level governance, policy bypass, privilege escalation
- grandMA2 onPC application itself (report to MA Lighting)
- MA Lighting network infrastructure
- Third-party dependencies (report upstream)
Do not open a public GitHub issue for security vulnerabilities.
- Email the maintainer privately at: thisis.romar+security@gmail.com
- Include:
- Affected component and version
- Steps to reproduce
- Impact assessment (what an attacker could do)
- Suggested fix (if any)
- You will receive an acknowledgment within 48 hours.
- A fix or mitigation will be provided within 14 days of confirmation.
If the vulnerability is critical (e.g., remote command execution on a live console), we will coordinate disclosure timing with you.
- 14-day grace period from confirmed report to public disclosure.
- Credit will be given to the reporter in the release notes unless anonymity is requested.
- We follow coordinated disclosure — please do not publish details before the grace period expires.