CVE-2018-11041
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 · uneditedCloud Foundry UAA, versions later than 4.6.0 and prior to 4.19.0 except 4.10.1 and 4.7.5 and uaa-release versions later than v48 and prior to v60 except v55.1 and v52.9, does not validate redirect URL values on a form parameter used for internal UAA redirects on the login page, allowing open redirects. A remote attacker can craft a malicious link that, when clicked, will redirect users to arbitrary websites after a successful login attempt.
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 confidenceCloud Foundry UAA (User Account and Authentication) versions prior to 4.19.0 and uaa-release prior to v60 fail to validate redirect URL parameters on the login page, allowing attackers to craft malicious links that redirect authenticated users to arbitrary external websites after login.
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.0, < 4.7.5> 4.7.5, < 4.10.1> 4.10.1, < 4.19.0> 48, < 52.9> 52.9, < 55.1> 55.1, < 60CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 UAA version via API endpointQuery the UAA server's /info endpoint (e.g., https://your-uaa-host/uaa/info) or use the UAA CLI (uaac target https://your-uaa-host && uaac info) to retrieve the installed UAA version.Affected if The returned version falls within any of these ranges: > 4.6.0 to < 4.7.5, > 4.7.5 to < 4.10.1, or > 4.10.1 to < 4.19.0.
-
Check uaa-release versionIf deployed via BOSH, run 'bosh deployments' and locate the uaa-release, or check the deployment manifest for the release version field.Affected if The uaa-release version is between > 48 and < 52.9, between > 52.9 and < 55.1, or between > 55.1 and < 60.
-
Verify login page accepts redirect parameterInspect the UAA login page form (typically at /uaa/login) and check if it accepts a 'redirect' or 'service' URL parameter. Attempt a test request with an external domain in the redirect parameter (e.g., /uaa/login?redirect=https://example.com).Affected if The server responds with a redirect to the external domain instead of rejecting it or redirecting to an internal path.
-
Check for URL validation in reverse proxyIf a reverse proxy (like HAProxy, NGINX, or Cloud Foundry router) sits in front of UAA, inspect its configuration for any whitelist or validation rules applied to the redirect parameter.Affected if No URL validation whitelist exists and UAA version is within the affected ranges.
You are affected if your UAA version is below 4.19.0 (or uaa-release below v60) and the login page accepts external URLs in the redirect parameter without validation.
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 data4.7.54.10.14.19.0
Upgrade UAA to version 4.19.0 or later, or uaa-release v60 or later. If upgrading is not immediately feasible, implement URL validation on redirect parameters at a reverse proxy or application layer to whitelist only legitimate internal domains.
- 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-2018-11041 — 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-2018-11041 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