Skip to content

Security: Despical/PortBridge

Security

SECURITY.md

Security Policy

Security reports are taken seriously. If you find a vulnerability in Port Bridge, please report it privately instead of opening a public issue.

Reporting a Vulnerability

Please send security reports to:

contact@despical.dev

When possible, include the following details:

  • A clear description of the vulnerability.
  • Steps to reproduce the issue.
  • The affected version, commit, branch, or server environment.
  • Any relevant logs, screenshots, configuration examples, or proof of concept details.
  • Whether the issue appears to affect public players, administrators, stored data, tunnel configuration, native executables, or server configuration.

Please do not include destructive payloads, real user data, private credentials, or anything that could damage a running server.

Scope

The following areas are considered security-sensitive:

  • Command permissions, administrator actions, and connection-address disclosure.
  • Bore release downloads, SHA-256 verification, archive extraction, and executable caches.
  • Native process arguments, environment variables, shutdown, and filesystem paths.
  • Relay credentials, log redaction, Minecraft status packets, and network timeouts.
  • Packaged resources, configuration reloads, reconnection, and server startup behavior.

Reports about spam, abuse, or non-security bugs should use the normal GitHub issue tracker instead.

Supported Versions

Only the latest public version of Port Bridge is currently supported. If you are running an older version, please update before reporting unless the same issue also exists on the latest version.

Response

After a valid report is received, the issue will be reviewed as soon as possible. If the report is confirmed, a fix will be prepared privately and released with credit where appropriate.

Please avoid public disclosure until a fix is available.

There aren't any published security advisories