# CVE-2024-38810: Missing Authorization When Using @AuthorizeReturnObject

> Attackers can bypass security annotations in Spring Security, rendering authorization checks ineffective and potentially exposing protected resources.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 20 Aug 2024
- **Updated:** 20 Aug 2024
- **Also known as:** GHSA-hmqf-wpq9-jq83

## What is CVE-2024-38810?

CVE-2024-38810 is a medium-severity missing authorization vulnerability in spring security, published on 20 Aug 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Missing Authorization When Using @AuthorizeReturnObject in Spring Security 6.3.0 and 6.3.1 allows attacker to render security annotations inaffective.

Weakness: CWE-862 (Missing Authorization), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2024-38810?

2 open source packages ship an affected version, including org.springframework.security:spring-security-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.springframework.security:spring-security-core` | Maven | From 6.3.0 | 6.3.2 |
| `org.springframework.security:spring-security-core` | Maven | From 6.3.0 | 6.3.2 |

Products: Vmware Spring Security.

## How do I fix CVE-2024-38810?

Upgrade org.springframework.security:spring-security-core to 6.3.2 or later.

## Is CVE-2024-38810 being exploited?

There is no known exploitation of CVE-2024-38810 in the wild and no public exploit code.

## Other vulnerabilities in spring security

- [CVE-2014-3527](https://insights.sbomify.com/CVE-2014-3527/): Authorization Bypass in Spring Security (critical 9.8)
- [CVE-2026-59354](https://insights.sbomify.com/CVE-2026-59354/): Spring Security OAuth2 Authorization Server: Insufficient validation of Dynamic Client Registration metadata (critical 9.6)
- [CVE-2026-59270](https://insights.sbomify.com/CVE-2026-59270/): Spring Security embedded UnboundID LDAP server exposes well-known administrative bind DN on all network interfaces (critical 9.4)
- [CVE-2026-22732](https://insights.sbomify.com/CVE-2026-22732/): Under Some Conditions Spring Security HTTP Headers Are not Written (critical 9.1)
- [CVE-2023-34034](https://insights.sbomify.com/CVE-2023-34034/): Access Control Bypass in Spring Security (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-38810 and fix it if it is affected.

What it is: CVE-2024-38810 is a medium-severity missing authorization vulnerability in spring security, published on 20 Aug 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-38810 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.springframework.security:spring-security-core (Maven): affected from 6.3.0; fixed in 6.3.2
- org.springframework.security:spring-security-core (Maven): affected from 6.3.0; fixed in 6.3.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-38810/ (Markdown: https://insights.sbomify.com/CVE-2024-38810/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-38810
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-38810
- OSV: https://osv.dev/vulnerability/CVE-2024-38810

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-38810/
Summaries are generated and may contain mistakes; the official description above is the record.