CVE-2025-6504
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 · uneditedIn HDP Server versions below 4.6.2.2978 on Linux, unauthorized access could occur via IP spoofing using the X-Forwarded-For header. Since XFF is a client-controlled header, it could be spoofed, allowing unauthorized access if the spoofed IP matched a whitelisted range. This vulnerability could be exploited to bypass IP restrictions, though valid user credentials would still be required for resource access.
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 · moderate confidenceHDP Server versions below 4.6.2.2978 on Linux incorrectly trust the X-Forwarded-For (XFF) HTTP header for IP-based access control. Since XFF is a client-controlled header that can be set arbitrarily, attackers can spoof this header to bypass IP whitelist restrictions, though valid credentials remain required for resource access.
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< 4.6.2.2978CVSS 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
- High
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H
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.
-
Identify installed HDP Server versionLocate the Hybrid Data Pipeline installation directory and check the version file or use the product's built-in version command. Common locations include /opt/hdp or the installation path configured during setup.Affected if The installed version is below 4.6.2.2978
-
Determine if IP-based access control is configuredReview the HDP Server access control configuration files or web interface for any IP whitelist, IP allowlist, or IP-based access rule configurations.Affected if IP-based access restrictions are defined and active in the HDP configuration
-
Check X-Forwarded-For header handlingInspect the HDP Server proxy or web server configuration to verify whether X-Forwarded-For headers are being used as the source of client IP for access control decisions.Affected if XFF headers are used for IP-based access control instead of the actual client connection IP
-
Verify reverse proxy configurationExamine any reverse proxy, load balancer, or web server in front of HDP to determine if XFF headers are being passed through without being overwritten with the actual client IP.Affected if Reverse proxies are not configured to overwrite XFF headers with the real client IP, allowing client-controlled values to reach HDP
You are affected if your HDP Server version is below 4.6.2.2978 and IP-based access control is enforced using X-Forwarded-For headers that can be controlled by clients.
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.
dbcve · scoped4.6.2.2978
Upgrade HDP Server to version 4.6.2.2978 or later. Alternatively, ensure reverse proxies or load balancers overwrite XFF headers with the actual client IP and disable direct access to backend servers.
Hybrid Data Pipeline version 4.6.2.2978 or later
- Upgrade Hybrid Data Pipeline to version 4.6.2.2978 or later on Linux systems
- After upgrade, verify IP whitelisting functionality works correctly
- Ensure valid user credentials are still required for resource access (as noted in the vulnerability description)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6504 — 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-2025-6504 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