LiveActive security incident?Get immediate response
CVE Record

CVE-2023-34035: Spring Security versions 5.8 prior to 5.8.5, 6.0 prior to 6.0.5, and 6.1 prior to 6.1.2 could be susceptibl...

Spring Security versions 5.8 prior to 5.8.5, 6.0 prior to 6.0.5, and 6.1 prior to 6.1.2 could be susceptible to authorization rule misconfiguration if the application uses requestMatchers(String) and multiple servlets, one of them being Spring MVC’s DispatcherServlet. (DispatcherServlet is a Spring MVC component that maps HTTP endpoints to methods on @Controller-annotated classes.) Specifically, an application is vulnerable when all of the following are true: * Spring MVC is on the classpath * Spring Security is securing more than one servlet in a single application (one of them being Spring MVC’s DispatcherServlet) * The application uses requestMatchers(String) to refer to endpoints that are not Spring MVC endpoints An application is not vulnerable if any of the following is true: * The application does not have Spring MVC on the classpath * The application secures no servlets other than Spring MVC’s DispatcherServlet * The application uses requestMatchers(String) only for Spring MVC endpoints

HighCVSS 7.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Some Spring Security applications can apply authorization rules incorrectly when they mix Spring MVC with additional servlets and use string-based request matchers for non-MVC endpoints. The issue is configuration-dependent, not a blanket Spring Security exposure.

Executive priority

Prioritize applications that expose internet-facing Java services and use mixed servlet architectures. This is high severity, but remediation can be targeted because the vulnerable conditions are specific and auditable.

Technical view

Affected versions are Spring Security 5.8.0-5.8.4, 6.0.0-6.0.4, and 6.1.0-6.1.1. Vulnerability requires Spring MVC on the classpath, multiple secured servlets including DispatcherServlet, and requestMatchers(String) used for endpoints that are not Spring MVC endpoints.

Likely exposure

Most likely in Java web applications using Spring MVC plus another servlet in the same application, with Spring Security rules covering both. Apps securing only Spring MVC DispatcherServlet, or using string matchers only for MVC endpoints, are described as not vulnerable.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. CVSS 7.3 indicates network reachability, low attack complexity, no privileges, and no user interaction, but exposure depends on the exact application configuration.

Researcher notes

The evidence is limited to the advisory description and CVE metadata. Do not assume all Spring Security users are affected. Focus validation on the three stated conditions and confirm fixed versions against vendor guidance.

Mitigation direction

  • Upgrade to Spring Security 5.8.5, 6.0.5, 6.1.2, or later.
  • Review Spring's advisory before changing matcher behavior.
  • Avoid ambiguous requestMatchers(String) use for non-MVC endpoints in multi-servlet applications.
  • Retest authorization rules for every servlet after dependency changes.

Validation and detection

  • Inventory Spring Security versions across Java applications.
  • Confirm whether Spring MVC is on the application classpath.
  • Identify applications securing multiple servlets, including DispatcherServlet.
  • Review requestMatchers(String) usage for non-MVC endpoint patterns.
  • Run regression tests for protected and public routes.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-34035 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.3CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L3.93.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.3High
CVSS 3.1 vector shape for CVE-2023-34035Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aSpring SecuritySpring Security 5.8.0 to 5.8.4, Spring Security 6.0.0 to 6.0.4, Spring Security 6.1.0 to 6.1.1unaffected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.