CVE-2017-4994
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 · uneditedAn issue was discovered in Cloud Foundry Foundation cf-release versions prior to v263; UAA release 2.x versions prior to v2.7.4.18, 3.6.x versions prior to v3.6.12, 3.9.x versions prior to v3.9.14, and other versions prior to v4.3.0; and UAA bosh release (uaa-release) 13.x versions prior to v13.16, 24.x versions prior to v24.11, 30.x versions prior to 30.4, and other versions prior to v40. There was an issue with forwarded http headers in UAA that could result in account corruption.
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 confidenceThe UAA (User Account and Authentication) server in Cloud Foundry has a vulnerability related to improper handling of forwarded HTTP headers. This header injection flaw could allow attackers to manipulate authentication sessions or poison headers, potentially leading to account corruption where user accounts become compromised or improperly merged.
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<= 39= 13.1= 13.2= 13.3= 13.4= 13.5= 13.6= 13.7= 13.8= 13.9= 13.10= 13.11<= 262<= 4.2.0= 2.2.5.4= 2.7.1= 2.7.2= 2.7.3= 2.7.4= 2.7.4.1= 2.7.4.2= 2.7.4.3= 2.7.4.4= 2.7.4.5= 2.7.4.6CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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.
-
Identify the installed UAA versionRun 'uaac target' and then 'uaac version' or check the BOSH deployment manifest for the UAA release version. For Cloud Foundry CF, check 'cf version' output.Affected if The version matches any of: UAA Bosh <=39 or 13.1-13.11; CF <=262; UAA <=4.2.0 or 2.2.5.4 or 2.7.1-2.7.4.6
-
Determine if UAA is behind a reverse proxyInspect network configuration or load balancer settings in front of the UAA service. Check if requests pass through a proxy, load balancer, or API gateway before reaching UAA.Affected if A reverse proxy or load balancer forwards client request headers to UAA without sanitization
-
Verify forwarded HTTP header handlingExamine the UAA configuration file (typically in /uaa or under the BOSH deployment) for settings related to 'X-Forwarded-*' headers, 'proxyHeaders' or 'trustedProxy' configuration.Affected if UAA is configured to trust and process forwarded headers from untrusted upstream proxies
-
Test header injection possibilitySend a request to UAA with manipulated X-Forwarded-Host, X-Forwarded-Proto, or similar headers and observe if the values are reflected in responses or session data.Affected if Injected header values appear in responses or affect authentication state
You are affected if your UAA version is one of the vulnerable releases listed AND the service is behind a reverse proxy that forwards HTTP headers without sanitization.
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 dataUpgrade UAA to patched versions (v2.7.4.18+, v3.6.12+, v3.9.14+, v4.3.0+, v13.16+, v24.11+, v30.4+, or v40+ depending on release track) and validate that reverse proxy headers are being properly sanitized before reaching the UAA service.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-4994 — 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-2017-4994 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