CVE-2018-15798
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 · uneditedPivotal Concourse Release, versions 4.x prior to 4.2.2, login flow allows redirects to untrusted websites. A remote unauthenticated attacker could convince a user to click on a link using the oAuth redirect link with an untrusted website and gain access to that user's access token in Concourse.
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 confidenceOpen redirect vulnerability in Pivotal Concourse's OAuth login flow allows remote attackers to specify arbitrary redirect URLs. Attackers can craft malicious links that redirect users to attacker-controlled websites with their OAuth access token as a parameter, enabling token theft and unauthorized access to Concourse.
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.0.0, < 4.2.2CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/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.
-
Verify Concourse is deployedIdentify Concourse processes or containers running in your environment. Check for 'concourse' binary, 'concourse-web' process, or 'concourse/concourse' Docker container.Affected if Concourse software is present in the environment
-
Determine installed Concourse versionRun 'concourse --version' for the binary, or check the container image tag (e.g., 'docker images' for 'concourse/concourse'), or access the web UI and check the version footer.Affected if Version is 4.0.0 or higher but lower than 4.2.2
-
Confirm OAuth login is enabledInspect Concourse configuration files (typically 'web' section in deployment manifests or environment variables). Look for 'CONCOURSE_OAUTH' variables, 'auth' configuration block, or OAuth provider settings (GitHub, GitLab, generic OIDC).Affected if OAuth-based authentication is configured and active for the Concourse web node
-
Check redirect URI configurationReview OAuth client configuration for 'redirect_uri' or 'redirect_url' settings. Examine whether the configuration restricts redirects to only internal/approved domains or allows arbitrary external URLs.Affected if Redirect URIs are not validated against an allowlist of trusted domains
You are affected if running Concourse version 4.0.0 through 4.2.1 with OAuth login enabled, particularly if the redirect URI allows external domains.
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.2.2
Upgrade to Pivotal Concourse Release version 4.2.2 or later which includes proper validation of OAuth redirect URIs to prevent redirects to untrusted external domains.
- Consultation2.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15798 — 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-15798 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