dbcve.org
Sling Authentication ServiceApplication · Apache

CVE-2017-15700

HIGH · 8.8 CVSS v3.0 Published 2017-12-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
A flaw in the org.apache.sling.auth.core.AuthUtil#isRedirectValid method in Apache Sling Authentication Service 1.4.0 allows an attacker, through the Sling login form, to trick a victim to send over their credentials.

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 confidence

The org.apache.sling.auth.core.AuthUtil#isRedirectValid method in Apache Sling Authentication Service 1.4.0 contains a flaw that allows attackers to manipulate the redirect URL parameter in the Sling login form. This open redirect vulnerability enables phishing attacks where victims are redirected to malicious sites after authentication, causing their credentials to be exposed to attackers.

MitigationImplement strict validation of redirect URLs in the isRedirectValid method, restricting redirects to trusted domains or paths within the application. Apply allowlist-based URL validation rather than blocklist approaches.

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
Sling Authentication ServiceApplication
Affected:= 1.4.0

CVSS 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
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Sling Authentication Service version
    Locate the org.apache.sling.auth.core bundle or JAR file in your Sling installation (typically in sling/auth/core or lib/ directory) and read its version metadata from MANIFEST.MF or the OSGi bundle information. Alternatively, use the Apache Felix Web Console (system/console/bundles) to view the installed version of the Sling Authentication Service bundle.
    Affected if The installed version is exactly 1.4.0 (or if the bundle version cannot be determined but the file org.apache.sling.auth.core-[version].jar exists with unknown version in the affected range).
  2. Locate the AuthUtil class with isRedirectValid method
    Search for the file AuthUtil.java in the org.apache.sling.auth.core package within your Sling authentication implementation. This is typically found in the source or decompiled JAR under org/apache/sling/auth/core/AuthUtil.java.
    Affected if The AuthUtil.java file exists and contains a method named isRedirectValid that performs URL validation without strict allowlist checking.
  3. Inspect the isRedirectValid method implementation
    Open the AuthUtil.java file and examine the isRedirectValid method. Look for how it validates the redirect parameter - specifically check if it uses blocklist-based validation (checking for disallowed patterns) rather than allowlist-based validation (checking against approved domains/paths).
    Affected if The method allows any URL that passes basic pattern checks without enforcing strict domain/path allowlisting, enabling arbitrary redirect targets.
  4. Check login form configuration for redirect parameter usage
    Examine the Sling login form configuration (typically in org/apache/sling/auth/core/login.jsp or similar form templates) to verify if it accepts and passes a redirect parameter to the authentication handler.
    Affected if The login form accepts and forwards a redirect parameter without server-side validation before passing it to the authentication service.

You are affected if Apache Sling Authentication Service version 1.4.0 is installed AND the login form uses a redirect parameter that is validated by the isRedirectValid method without strict allowlist-based URL validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict validation of redirect URLs in the isRedirectValid method, restricting redirects to trusted domains or paths within the application. Apply allowlist-based URL validation rather than blocklist approaches.

Fix this in Sling Authentication Service Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-15700 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-15700 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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