Skip to content

fix(proxy): remove internal ID headers from proxy responses#4

Merged
dviejokfs merged 1 commit intomainfrom
feat/remove-internal-id-response-headers
Feb 16, 2026
Merged

fix(proxy): remove internal ID headers from proxy responses#4
dviejokfs merged 1 commit intomainfrom
feat/remove-internal-id-response-headers

Conversation

@dviejokfs
Copy link
Copy Markdown
Contributor

Summary

  • Remove X-Project-ID, X-Environment-ID, and X-Deployment-ID headers from proxy responses — these leaked sequential internal integer IDs to end users, enabling enumeration and exposing potential IDOR attack surface
  • Preserve X-Request-ID for request tracing — operators can correlate with server-side logs for full routing context
  • Update README to add transactional email + DKIM and MCP server features to the feature matrix

Security

The removed headers exposed internal database IDs (sequential integers) on every proxied response. This allowed external observers to:

  • Enumerate how many projects/environments/deployments exist
  • Track growth rate over time
  • Potentially use IDs for IDOR attacks against any endpoint that accepts these IDs

Remove X-Project-ID, X-Environment-ID, and X-Deployment-ID headers from
proxy responses. These headers leaked sequential internal integer IDs to
end users, enabling enumeration of projects/environments/deployments and
exposing potential IDOR attack surface.

X-Request-ID is preserved for request tracing. Operators can correlate
request IDs with server-side logs for full routing context.

Also update README to add transactional email and MCP server features.
@dviejokfs dviejokfs merged commit 22811fa into main Feb 16, 2026
4 of 5 checks passed
@dviejokfs dviejokfs deleted the feat/remove-internal-id-response-headers branch February 16, 2026 22:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant