dbcve.org
ShiroApplication · Apache

CVE-2023-46749

MEDIUM · 6.5 CVSS v3.1 Published 2024-01-15
Fix available
A fix is available. Upgrade to 1.13.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
Apache Shiro before 1.13.0 or 2.0.0-alpha-4, may be susceptible to a path traversal attack that results in an authentication bypass when used together with path rewriting Mitigation: Update to Apache Shiro 1.13.0+ or 2.0.0-alpha-4+, or ensure `blockSemicolon` is enabled (this is the default).

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 confidence

Apache Shiro before 1.13.0 or 2.0.0-alpha-4 contains a path traversal vulnerability that can be exploited when used in conjunction with path rewriting mechanisms. The attack involves manipulating path segments, specifically using semicolon characters, to bypass authentication checks. The `blockSemicolon` setting (enabled by default) mitigates this issue.

MitigationUpdate Apache Shiro to version 1.13.0 or later (or 2.0.0-alpha-4 or later), or verify that the `blockSemicolon` configuration option remains enabled (it is enabled by default).

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
Affected:< 1.13.0= 2.0.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checks

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

  1. Identify Apache Shiro version
    Locate the Shiro JAR file in your application classpath or build dependencies (e.g., shiro-core.jar) and note the version number. Check your pom.xml, build.gradle, or the MANIFEST.MF file inside the Shiro JAR.
    Affected if Version is below 1.13.0 or equals 2.0.0 (including 2.0.0 without -alpha-4 suffix)
  2. Locate Shiro configuration file
    Find the Shiro configuration file in your deployment, typically named shiro.ini, or look for a ShiroFilterConfiguration bean in your Java configuration classes or XML context files.
    Affected if Configuration file exists in your environment
  3. Verify blockSemicolon setting
    Search the Shiro configuration file for the line 'blockSemicolon = false' or look for any explicit setting that disables this security option. Also check if blockSemicolon is set to true explicitly.
    Affected if blockSemicolon is explicitly set to false, OR if using a vulnerable Shiro version and blockSemicolon setting cannot be verified (default is true but may have been changed)

You are affected if your Apache Shiro version is below 1.13.0 or equals 2.0.0 AND the blockSemicolon setting has been explicitly disabled in your configuration.

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.

dbcve · scoped
Upgrade available Upgrade to 1.13.0 or later
Fixed in 1.13.0
Interim mitigation

Update Apache Shiro to version 1.13.0 or later (or 2.0.0-alpha-4 or later), or verify that the `blockSemicolon` configuration option remains enabled (it is enabled by default).

Recommended fix High confidence

Apache Shiro 1.13.0+ or 2.0.0-alpha-4+

  1. Identify the current Apache Shiro version in use by checking project dependencies (e.g., pom.xml, build.gradle, or lock files)
  2. For Maven projects: Update the Shiro dependency version to 1.13.0 or later. Example: Change <artifactId>shiro-core</artifactId><version>1.12.0</version> to <version>1.13.0</version>
  3. For Gradle projects: Update the version string. Example: implementation 'org.apache.shiro:shiro-core:1.13.0'
  4. If using 2.0.0-alpha series: Update to version 2.0.0-alpha-4 or later
  5. After updating, rebuild and test the application to verify functionality remains intact
  6. Verify that blockSemicolon remains enabled (it is enabled by default in affected versions after the fix)
Caveat Minor: Upgrading between minor versions may introduce behavioral changes; review the Shiro release notes for 1.13.0 and 2.0.0-alpha-4 for any breaking changes relevant to your application

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Shiro Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-46749 — 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-2023-46749 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