Skip to content

Security: DangerMouseUK/oss-server

SECURITY.md

Security policy

oss-server is a zone server. It listens on a UDP port, and everything that arrives there comes from somebody who has not logged in yet. That is the shape of the risk here: an unauthenticated stranger on the internet is the ordinary case, not the exceptional one.

Reporting a vulnerability

Use GitHub's private reporting, not a public issue.

Security → Report a vulnerability, or go straight to https://github.com/DangerMouseUK/oss-server/security/advisories/new

That opens a private thread with the maintainer. Nothing in it is visible to anyone else unless and until an advisory is published.

If you are not sure whether what you found is a security problem, report it privately anyway. Deciding that is our job. A private report that turns out to be an ordinary bug costs nothing; a public issue that turns out to be a real vulnerability cannot be taken back.

Which version

There are no releases and no tags yet, so there is no version table here and it would be dishonest to invent one. main is the only version there is. When you report something, say which commit you were on — git rev-parse HEAD.

In scope

Anything a connected player, or someone who has not connected at all, can do to a server that is running this code:

  • Crashing or hanging it. Untrusted input is never supposed to panic the server, so a panic reachable from the wire is a broken invariant and a remote denial of service at the same time.
  • Making it consume memory or CPU out of proportion to what was sent — unbounded allocation from a length field, work that grows faster than its input, a loop a peer can keep alive.
  • Crossing a boundary the server is supposed to enforce: reading or acting in an arena you are not in, obtaining a capability belonging to another player, or reaching an operator command without the authority for it.
  • The admin and metrics HTTP API.
  • The configuration reader. .conf files with #include are parsed from disk, and a zone directory is routinely something an operator downloaded from somebody else.
  • File transfer and map download, in both directions.
  • The billing interface, including what a billing server can do to a zone that trusts it.

Out of scope

  • Zones that other people run. This project publishes a server; it does not operate anybody's zone. If something is wrong with a zone you played on, that belongs to whoever runs it, not here.
  • Cheating, and getting past the anti-cheat. A client that lies to a server is the problem this whole genre has always had, and the plausibility checks are a mitigation rather than a boundary. Findings about them are genuinely welcome — as ordinary issues, because treating every anti-cheat bypass as a security vulnerability would bury the reports that are one. The exception is if a crafted position or weapon packet can crash, hang or corrupt the server for other players: that is squarely in scope, and please report it privately.
  • Reports generated by a scanner with no analysis attached. Tell us what an attacker would actually be able to do.

What to expect

This is a volunteer project with one maintainer, and replies will not be instant.

  • Acknowledgement within seven days. If you have heard nothing after that, the message went astray rather than being ignored — please ping the thread.
  • We will tell you whether we think it is a real vulnerability, and why.
  • If it is, we will fix it on main and publish an advisory. You will be credited by whatever name you ask for, or not at all if you prefer.
  • We will not ask you to sit on something indefinitely. If we go quiet or cannot fix it, publishing is your call.

There is no bug bounty, and there is no funding to start one.

One thing this policy is not for

This file is about vulnerabilities in this code. It is not a channel for questions about what the project does or does not implement, or why. Those belong in an ordinary issue.

Much of what this server parses is implemented in the shared crates. If the bug is in packet decoding, the transport layer or a map file, it may belong in oss-core — report it wherever you found it and we will move it if needed. Do not let uncertainty about which repository it belongs in stop you reporting it.

There aren't any published security advisories