CaddyWeb server / proxy · Caddyserver
CVE-2023-50463
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe caddy-geo-ip (aka GeoIP) middleware through 0.6.0 for Caddy 2, when trust_header X-Forwarded-For is used, allows attackers to spoof their source IP address via an X-Forwarded-For header, which may bypass a protection mechanism (trusted_proxy directive in reverse_proxy or IP address range restrictions).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe caddy-geo-ip middleware through version 0.6.0 for Caddy 2 trusts the X-Forwarded-For HTTP header without validation when the trust_header X-Forwarded-For option is configured. Attackers can send a crafted X-Forwarded-For header to spoof their source IP address, thereby bypassing IP-based protection mechanisms such as the trusted_proxy directive in reverse_proxy or IP address range restrictions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
CaddyWeb server / proxy
<= 0.6.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if caddy-geo-ip middleware is loadedRun 'caddy list-modules' or inspect your Caddyfile/global config to see if the geoip module is listedAffected if The caddy-geo-ip module appears in the loaded modules list
-
Identify the installed caddy-geo-ip versionRun 'caddy list-modules -v' to see version info, or check the Caddy module JSON config for the geoip handler versionAffected if Version is 0.6.0 or lower
-
Check for trust_header X-Forwarded-For configurationInspect your Caddyfile for 'trust_header X-Forwarded-For' or check the JSON config under the geoip handler configurationAffected if The trust_header option is set to X-Forwarded-For or a variant enabling this behavior
-
Verify the geoip middleware is actively usedReview your site configuration to confirm the geoip handler is actually applied to a route or siteAffected if The geoip middleware is actively processing requests in a production route
You are affected if caddy-geo-ip version 0.6.0 or lower is installed and the trust_header X-Forwarded-For option is explicitly configured in your Caddy configuration.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataAvoid trusting the X-Forwarded-For header directly; instead, use Caddy's built-in trusted_proxy functionality with proper IP range configuration, or implement server-side validation of the X-Forwarded-For header to ensure it cannot be controlled by clients.
Fix this in Caddy
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-50463 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-50463 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data