CVE-2023-22602 | Apache Shiro before 1.11.0, when used with Spring Boot 2.6+, may allow authentication bypass through a specially crafted HTTP request

When using Apache Shiro before 1.11.0 together with Spring Boot 2.6+, a specially crafted HTTP request may cause an authentication bypass. The authentication bypass occurs when Shiro and Spring Boot are using different pattern-matching techniques. Both Shiro and Spring Boot < 2.6 default to Ant style pattern matching. Mitigation: Update to Apache Shiro 1.11.0, or set the following Spring Boot configuration value: `spring.mvc.pathmatch.matching-strategy = ant_path_matcher`

Published: 2023-01-14 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-22602 is rated Moderate Risk (41.8/100): CVSS High severity, with low exploitation likelihood (EPSS 0.15%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2023-22602

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-21 1.03% 0.15% -0.88%
2 2025-11-18 0.15% 1.03% +0.88%
3 2025-11-10 — 0.15% —

Full EPSS history (10 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-22602

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2023-22602

GitHub Security Advisory for CVE-2023-22602

GHSA-7cxr-h8wm-fg4c · Severity: high · Ecosystem: maven — Apache Shiro Interpretation Conflict vulnerability

OS Trackers for CVE-2023-22602

vendor priority summary link
debian not yet assigned CVE-2023-22602 not yet assigned priority: Debian including 1 source packages (shiro), 4 status rows across 4 suites (bookworm, bullseye, sid, trixie): open 4. https://security-tracker.debian.org/tracker/CVE-2023-22602
redhat medium — https://access.redhat.com/security/cve/CVE-2023-22602
ubuntu medium CVE-2023-22602 medium priority: Ubuntu including 1 source packages (shiro), 11 status rows across 11 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, trusty, upstream, xenial): not-affected 6, ignored 4, released 1. https://ubuntu.com/security/CVE-2023-22602

Affected software / configurations for CVE-2023-22602

Vendor Product Version Raw CPE
apache shiro < 1.11.0 cpe:2.3:a:apache:shiro:*:*:*:*:*:*:*:*
vmware spring_boot 2.6.0 cpe:2.3:a:vmware:spring_boot:2.6.0:\+:*:*:*:*:*:*

References for CVE-2023-22602

cvelogic Threat Intelligence