CVE-2017-18262
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 · uneditedBlackboard Learn (Since at least 17th of October 2017) has allowed Unvalidated Redirects on any signed-in user through its endpoints for handling Shibboleth logins, as demonstrated by a webapps/bb-auth-provider-shibboleth-BBLEARN/execute/shibbolethLogin?returnUrl= URI.
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 confidenceThis is an Open Redirect vulnerability in Blackboard Learn's Shibboleth authentication module. The `returnUrl` parameter in the `/execute/shibbolethLogin` endpoint accepts arbitrary URLs without server-side validation, allowing authenticated users to be redirected to attacker-controlled sites after authentication.
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<= 9.1= 9.1CVSS 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.
-
Identify installed Blackboard Learn versionAccess the Blackboard administration panel or check system information files. Look for version details in the system's 'About' page, installation logs, or version metadata files.Affected if Installed version is 9.1 or any version lower than 9.1 (e.g., 9.0, 8.x, 7.x)
-
Verify Shibboleth authentication module is enabledAccess Blackboard's Building Blocks or Authentication settings in the admin panel. Check if the Shibboleth authentication provider is installed and configured as an active authentication method.Affected if Shibboleth authentication module is enabled and listed as an active authentication provider
-
Confirm vulnerable endpoint existsAttempt to access or probe the /execute/shibbolethLogin endpoint on the server. This may require authenticated access. Check the application's URL routing or endpoint documentation.Affected if The /execute/shibbolethLogin endpoint responds or is accessible within the application
-
Inspect returnUrl parameter handlingReview application configuration files, web.xml, or Shibboleth configuration for the login handler. Look for any server-side validation or allowlist logic applied to the returnUrl parameter.Affected if No server-side allowlist validation exists for the returnUrl parameter, or the endpoint accepts external URLs without filtering
-
Review server logs for suspicious redirect patternsExamine authentication logs, access logs, and Shibboleth logs for entries containing the shibbolethLogin endpoint with unusual or external URLs in the returnUrl parameter.Affected if Logs contain redirect attempts to external/untrusted domains via the returnUrl parameter
You are affected if your Blackboard Learn version is 9.1 or lower AND the Shibboleth authentication module is enabled, with the /execute/shibbolethLogin endpoint accepting unvalidated returnUrl parameters.
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 dataImplement strict allowlist validation on the `returnUrl` parameter to ensure only trusted, internal URLs are permitted for redirection. Reject or sanitize any URLs pointing to external domains.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18262 — 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-18262 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