ShiroApplication · Apache
CVE-2020-17510
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 · uneditedApache Shiro before 1.7.0, when using Apache Shiro with Spring, a specially crafted HTTP request may cause an authentication bypass.
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 confidenceApache Shiro before version 1.7.0 contains an authentication bypass vulnerability when integrated with the Spring framework. Attackers can craft specific HTTP requests to bypass authentication checks and gain unauthorized access to protected resources.
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
ShiroApplication
< 1.7.0
Debian LinuxOperating system
= 9.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Apache Shiro installationLocate Shiro JAR files in your application's lib directory, check pom.xml for shiro-core dependency, or look for Shiro in your build.gradle dependencies. Note the exact version number displayed.Affected if The installed version is any version before 1.7.0 (e.g., 1.6.0, 1.5.3, 1.4.x)
-
Verify Spring framework integrationExamine your application configuration files (such as web.xml, applicationContext.xml, shiro.ini, or Spring Boot configuration classes) for the presence of both Apache Shiro and Spring framework beans or filter configurations working together.Affected if Shiro is configured alongside Spring framework in the same application
-
Check for exposed authentication endpointsReview your application's web.xml, Spring Security configuration, or controller mappings to identify URLs protected by Shiro's authentication filter that are accessible over the network.Affected if Shiro-protected endpoints are publicly accessible or accessible to untrusted users
-
Confirm version is vulnerableCompare the identified Shiro version against the affected range: any version strictly lower than 1.7.0 is considered vulnerable.Affected if Installed Shiro version is less than 1.7.0 and the application uses Spring integration
You are affected if Apache Shiro version is below 1.7.0 and Shiro is integrated with the Spring framework in your application.
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.
dbcve · scoped1.7.0
Upgrade Apache Shiro to version 1.7.0 or later. If immediate upgrading is not possible, review and restrict access to affected endpoints while planning the upgrade.
Apache Shiro 1.7.0 or later
- Upgrade Apache Shiro to version 1.7.0 or later by updating the dependency in your project's build configuration (e.g., Maven pom.xml or Gradle build.gradle)
- After upgrading, rebuild and redeploy the application
- Verify that the authentication bypass vulnerability is resolved by testing with the specially crafted HTTP request patterns
- Ensure all existing authentication and authorization functionality continues to work correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Shiro
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-17510 — 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-2020-17510 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