Skip to content

fix(express): honor configured trust proxy hop count (#3933)#3936

Merged
PierreBrisorgueil merged 1 commit into
masterfrom
fix/trust-proxy-honor-hopcount
Jul 2, 2026
Merged

fix(express): honor configured trust proxy hop count (#3933)#3936
PierreBrisorgueil merged 1 commit into
masterfrom
fix/trust-proxy-honor-hopcount

Conversation

@PierreBrisorgueil

Copy link
Copy Markdown
Contributor

Problem

initMiddleware treated config.trust.proxy as a boolean gate then always set Express trust proxy to fully-permissive true, discarding the configured hop count. production.config.js sets trust.proxy: 1, but that 1 was thrown away → req.ip derived from the client-controlled leftmost X-Forwarded-For → the IP-keyed auth rate limiter (login/forgot/signup) is bypassable by rotating a spoofed header (ERR_ERL_PERMISSIVE_TRUST_PROXY).

Fix

Forward the configured value: app.set('trust proxy', config.trust.proxy). A boolean true still fully-trusts the chain; a numeric hop count like 1 is now honored so req.ip resolves to the real socket IP. Falsy values still leave Express at its safe default.

Test

Added express trust-proxy unit tests: hop count survives (not collapsed to true), the compiled fn trusts the immediate proxy but not a further client-controlled hop, booleans still work, falsy leaves the default.

Closes #3933

https://claude.ai/code/session_01V1mhCDsSUnn3WGtevd3YFX

initMiddleware treated config.trust.proxy as a boolean gate then always set
Express `trust proxy` to the fully-permissive `true`, discarding the configured
value. A configured bounded hop count (e.g. 1) was thrown away, so req.ip
resolved from the client-controlled leftmost X-Forwarded-For and the IP-keyed
rate limiter (lib/middlewares/rateLimiter.js) could be bypassed by rotating a
spoofed header (express-rate-limit ERR_ERL_PERMISSIVE_TRUST_PROXY).

Forward the configured value verbatim: booleans still work, and a numeric hop
count / subnet is now honored. Adds unit tests asserting the setting resolves
to the configured hop count and that the compiled trust fn trusts only the
immediate proxy, not a further spoofed hop.

Closes #3933

Claude-Session: https://claude.ai/code/session_01V1mhCDsSUnn3WGtevd3YFX
@coderabbitai

coderabbitai Bot commented Jul 2, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@PierreBrisorgueil, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: ac7f5c94-fb0f-4c89-a8b3-66115816a6ed

📥 Commits

Reviewing files that changed from the base of the PR and between 7916876 and 23f0488.

📒 Files selected for processing (2)
  • lib/services/express.js
  • lib/services/tests/express.trustProxy.unit.tests.js
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/trust-proxy-honor-hopcount

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@codecov

codecov Bot commented Jul 2, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.67%. Comparing base (7916876) to head (23f0488).

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #3936   +/-   ##
=======================================
  Coverage   92.67%   92.67%           
=======================================
  Files         169      169           
  Lines        5546     5546           
  Branches     1782     1783    +1     
=======================================
  Hits         5140     5140           
  Misses        326      326           
  Partials       80       80           
Flag Coverage Δ
integration 61.07% <100.00%> (ø)
unit 74.28% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.


Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7916876...23f0488. Read the comment docs.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@PierreBrisorgueil PierreBrisorgueil merged commit 2344d4c into master Jul 2, 2026
8 checks passed
@PierreBrisorgueil PierreBrisorgueil deleted the fix/trust-proxy-honor-hopcount branch July 2, 2026 12:18
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.

🔒 trust proxy hardcoded to true discards configured hop count — auth rate limiter bypassable

1 participant