dbcve.org
Spring SecurityFramework / library · VMware

CVE-2024-38810

HIGH · 7.5 CVSS v3.1 Published 2024-08-20
Fix available
A fix is available. Upgrade to 6.3.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Missing Authorization When Using @AuthorizeReturnObject in Spring Security 6.3.0 and 6.3.1 allows attacker to render security annotations inaffective.

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

In Spring Security 6.3.0 and 6.3.1, the @AuthorizeReturnObject annotation fails to properly enforce authorization on returned objects, allowing attackers to bypass security checks and access data they shouldn't have permission to view.

MitigationUpgrade to Spring Security 6.3.2 or later where the vulnerability is patched, and audit all usages of @AuthorizeReturnObject to verify authorization is correctly enforced.

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
Spring SecurityFramework / library
Affected:>= 6.3.0, < 6.3.2

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Check Spring Security version
    Inspect your build configuration file (pom.xml, build.gradle, or equivalent) or the Spring Security library JAR manifest to identify the exact version of spring-security-core (or spring-security-web) in use. Look for entries like spring-security-core:6.3.0 or spring-security-web:6.3.1.
    Affected if The installed version is 6.3.0 or 6.3.1 (versions >= 6.3.0 and < 6.3.2 are affected)
  2. Search for @AuthorizeReturnObject usage
    Search your Java/Kotlin source code for any usage of the annotation @AuthorizeReturnObject, including fully qualified references such as org.springframework.security.authorization.method.AuthorizeReturnObject. Search across all source files in your project.
    Affected if The annotation is present and being used on methods that return objects requiring authorization checks
  3. Verify method return type
    For each method annotated with @AuthorizeReturnObject, identify the return type of that method and determine whether the returned objects contain sensitive data that should be protected by authorization checks.
    Affected if Methods with @AuthorizeReturnObject return sensitive data that should require authorization but the annotation is not enforcing it properly in versions 6.3.0-6.3.1
  4. Test authorization enforcement
    If possible, invoke methods annotated with @AuthorizeReturnObject using an account that should NOT have permission to access the returned data, and verify whether the authorization check is properly blocking unauthorized access.
    Affected if The method executes successfully and returns data without throwing an AccessDeniedException or authentication error when called by an unauthorized user

You are affected if your environment uses Spring Security version 6.3.0 or 6.3.1 AND employs @AuthorizeReturnObject on methods returning sensitive data that should be protected but may be accessible without proper authorization.

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 6.3.2 or later
Fixed in 6.3.2
Interim mitigation

Upgrade to Spring Security 6.3.2 or later where the vulnerability is patched, and audit all usages of @AuthorizeReturnObject to verify authorization is correctly enforced.

Recommended fix High confidence

Spring Security 6.3.2

  1. Update the Spring Security dependency version in your project's pom.xml or build.gradle file to 6.3.2 or later
  2. For Maven: Change <spring-security.version> to 6.3.2 or update the spring-security-dependencies bom
  3. For Gradle: Change implementation 'org.springframework.security:spring-security-core:6.3.0' to implementation 'org.springframework.security:spring-security-core:6.3.2'
  4. Rebuild and test the application to ensure the authorization annotations work correctly
  5. Verify that @AuthorizeReturnObject properly enforces authorization on returned objects

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

Fix this in Spring Security Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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