Dgraph is an open source distributed GraphQL database. Prior to 25.3.3, a vulnerability has been found in Dgraph that gives an unauthenticated attacker full read access to every piece of data in the database. This affects Dgraph's default configuration where ACL is not enabled. The attack requires two HTTP POSTs to port 8080. The first sets up a schema predicate with @unique @index(exact) @lang via /alter (also unauthenticated in default config). The second sends a crafted JSON mutation to /mutate?commitNow=true where a JSON key contains the predicate name followed by @ and a DQL injection payload in the language tag position. The injection exploits the addQueryIfUnique function in edgraph/server.go, which constructs DQL queries using fmt.Sprintf with unsanitized predicateName that includes the raw pred.Lang value. The Lang field is extracted from JSON mutation keys by x.PredicateLang(), which splits on @, and is never validated by any function in the codebase. The attacker injects a closing parenthesis to escape the eq() function, adds an arbitrary named query block, and uses a # comment to neutralize trailing template syntax. The injected query executes server-side and its results are returned in the HTTP response. This vulnerability is fixed in 25.3.3.
The attack requires sending two HTTP POST requests to port 8080. The first request, directed to the /alter endpoint, creates a schema predicate with attributes @unique @index(exact) @lang — which is possible without authentication in the default configuration. The second request sends a crafted JSON mutation to /mutate?commitNow=true, where the JSON key contains the predicate name, the @ character, and an injection payload inserted in the 'language tag' field. The vulnerable addQueryIfUnique function in edgraph/server.go constructs DQL queries using fmt.Sprintf without sanitizing the predicateName value, which contains the raw value of pred.Lang. The Lang field comes from the JSON mutation keys and is extracted by x.PredicateLang() by splitting on the @ character, never undergoing any validation. The attacker injects a closing parenthesis to escape the eq() function, adds any query block, and using the # comment character neutralizes the rest of the template syntax — the injected query is executed on the server side, and its results are returned in the HTTP response.
An unauthenticated attacker can read all data stored in the Dgraph database. The data confidentiality breach is complete, with no impact on integrity and availability.
Update Dgraph to version 25.3.3 or later, where the vulnerability has been fixed. As an interim security measure, consider enabling the ACL mechanism and restricting network access to port 8080 to trusted hosts only.
Dgraph in versions earlier than 25.3.3, running in the default configuration with ACL mechanism disabled.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NDgraph
APPDgraph< 25.3.3
Related vulnerabilities
Dgraph — wstrzyknięcie zapytania DQL umożliwia nieautoryzowany odczyt danych
Dgraph: ujawnienie tokenu admina przez endpoint /debug/vars bez uwierzytelnienia
Dgraph: ujawnienie tokenu admina przez niezabezpieczony endpoint /debug/pprof/cmdline
Dgraph: nieuwierzytelniony dostęp do mutacji restoreTenant (SSRF, RCE danych)
Dgraph jest otwartym rozproszoną bazą danych GraphQL. Istniejące logi audytu Dgraph są podatne na ataki brute ...