DEV Community

andreagomez
andreagomez

Posted on

Fission's 252 title matches and zero app fingerprints need router and control-plane evidence

Fission's 252 title matches and zero app fingerprints need router and control-plane evidence

Fission deploys functions on Kubernetes and routes HTTP triggers through a router. Its name also appears in physics, nuclear engineering, and general technical writing. That ambiguity is why a title count needs a second signal before it becomes a deployment inventory.

ZoomEye returned 252 matches for title="Fission" and zero for app="Fission" on 2026-11-22 at 00:45 UTC. The query used sub_type=all, page 1, and pagesize=1. These are index matches, not proof of an exposed function platform.

Open the title query in ZoomEye. The title field catches every page that uses the word. The application field did not return a recognized product fingerprint in this probe. A zero app count can mean no deployments, a missing fingerprint, or a different fingerprint value.

Function routing and control are different planes

Fission's architecture uses Kubernetes custom resources and an API server with authentication, authorization, and validation. Its function calls can be routed through a router. Documentation for Fission authentication says function authentication is optional and is enabled with authentication.enabled=true.

When enabled, the router registers an authentication endpoint and creates a secret containing a username, a generated password, and a JWT signing key. Clients exchange the username and password for a token, then send the token in the Authorization header. The default token lifetime is 120 seconds.

The control plane and the function routes should not be treated as one host count. A public function route may be intended. The Kubernetes API and Fission control plane should be reachable only through an administrative path. The router's auth state determines whether a caller can invoke a function directly.

Filter the title noise before testing

Review candidate pages for product-specific markers such as Fission routes, documentation links, CLI references, function names, or a login page that matches the operator's deployment. Do not send probes to every page that contains the word Fission.

For an authorized candidate, check whether the router authentication feature is enabled. Test the /auth/login path if it is part of the deployment, then test a function route without a token and with a malformed token. A valid 401 or rejected request is evidence that the boundary works; a successful invocation without a token requires immediate review.

Inspect the Kubernetes service and ingress that expose the router. Confirm that the control-plane service account, function runtime images, and function secrets are not exposed by the same ingress. The operator should be able to explain which routes are public and which require authentication.

Measure the same scope over time

Keep the exact title query and the application query in the inventory. A title-only baseline can detect pages that use the name, while the app query can show whether ZoomEye recognizes a product signature. Neither result establishes ownership.

If a known Fission deployment disappears from the title results, do not assume it was removed. The page may be private, the title may have changed, or the crawler may have missed it. If a new title match appears, validate the product and owner before treating it as a finding.

The article's most useful value is the distinction between a public function route and the platform that manages secrets and deployments. Fission's authentication documentation gives defenders a concrete configuration to check, while the ZoomEye result gives a limited discovery lead.

References

Top comments (0)