DEV Community

OnaEiuspkz
OnaEiuspkz

Posted on

TypeDB's small HTTP footprint and the default-password review

TypeDB's small HTTP footprint and the default-password review

TypeDB exposes a gRPC service on port 1729 by default and an HTTP endpoint on port 8000. The HTTP endpoint accepts credentials at a sign-in route, returns a temporary token, and uses that token for subsequent requests. A count-only ZoomEye measurement on November 17, 2026 used sub_type=all, page 1, and a page size of 1. app="TypeDB" returned 0. title="TypeDB" returned 15.

The small title count makes a targeted review practical. TypeDB's documentation says all client connections require authentication. Community Edition and on-premise Enterprise deployments start with an administrative user named admin. The default Community Edition password is password. The documentation explicitly recommends changing default passwords before production deployment. The HTTP endpoint uses token authentication, with a default token lifetime of 30 minutes.

What the counts can support

A public title match does not reveal whether the instance uses the default password. It also does not reveal whether TLS is enabled. TypeDB documentation warns that Community Edition or on-premise Enterprise may run with encryption disabled, in which case a username and password travel over the network in plain text. A page or service can be reachable while still requiring correct credentials. The review should establish configuration, not assume a successful login.

Start with owned assets. Locate TypeDB servers, developer instances, test clusters, and applications that embed TypeDB drivers. Record the server version, gRPC and HTTP listeners, TLS configuration, default administrator state, token lifetime, credential storage, and owner. Check container images and Kubernetes manifests for environment variables that set or preserve an initial password. A secret that exists in a deployment template can survive longer than the engineer who created it expects.

For the HTTP endpoint, verify that access is restricted to intended users and networks. The sign-in endpoint exchanges credentials for a token. If the endpoint is public, it should use TLS and a credential policy appropriate for the deployment. Token expiry reduces the lifetime of a stolen credential, but it does not replace revocation or user lifecycle management. Review how TypeDB users are created, disabled, and removed.

For the gRPC endpoint, confirm whether it is exposed beyond the application network. Many deployments need drivers to reach it, but browsers and public clients usually do not. A network policy can limit the source set. TypeDB's documentation recommends firewalls and TLS for production. The database service should not depend on obscurity or a difficult protocol as its authentication control.

Verification and next steps

The title count of 15 is small enough that false positives matter. Some matches may be documentation pages, community posts, or hosted examples. Use certificate subject names and approved domain lists to separate likely deployments. Do not enumerate usernames or try admin with guessed passwords. If the organisation owns a match, use configuration access to verify the account state.

Monitoring should include sign-in failures, token issuance, expired-token use, user creation, and password changes. A sudden burst of sign-in attempts against an internet-facing TypeDB HTTP endpoint can indicate credential probing. A successful sign-in from an unexpected network should be correlated with driver connections and query activity. Logs from proxies and the TypeDB service should share a clock and a request identifier where possible.

The 0 app result is not proof that TypeDB has no network presence. It means the selected product fingerprint query returned no matches in this observation. TypeDB's title may appear in pages that the fingerprint does not classify. The title count is also not a vulnerability count. It is a small set of candidates for a configuration review.

The practical value here is the direct link between documentation and action: change the default password, enable TLS, limit both ports, and verify token and user lifecycle. With only 15 title matches, an organisation can afford to ask a precise question of each candidate instead of relying on a broad claim about exposed databases.

References

Top comments (0)