# CVE-2022-27772: Temporary Directory Hijacking to Local Privilege Escalation Vulnerability in org.springframework.boot:spring-boot

> Attackers can hijack temporary directories in Spring Boot to escalate privileges or read sensitive data.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-cm59-pr5q-cw85

## What is CVE-2022-27772?

CVE-2022-27772 is a high-severity path traversal vulnerability in n/a, published on 30 Mar 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

spring-boot versions prior to version v2.2.11.RELEASE was vulnerable to temporary directory hijacking. This vulnerability impacted the org.springframework.boot.web.server.AbstractConfigurableWebServerFactory.createTempDir method. NOTE: This vulnerability only affects products and/or versions that are no longer supported by the maintainer

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

## Which versions are affected by CVE-2022-27772?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.springframework.boot:spring-boot` | Maven | All versions | 2.2.11.RELEASE |
| `org.springframework.boot:spring-boot` | Maven | All versions | 2.2.11.RELEASE |

Products: Vmware Spring Boot.

## How do I fix CVE-2022-27772?

Upgrade org.springframework.boot:spring-boot to 2.2.11.RELEASE or later.

## Is CVE-2022-27772 being exploited?

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

Public exploit code:

- https://github.com/puneetbehl/grails3-cve-2022-27772 (github_poc): https://github.com/puneetbehl/grails3-cve-2022-27772

## Other vulnerabilities in n/a

- [CVE-2023-20873](https://insights.sbomify.com/CVE-2023-20873/): Spring Boot Security Bypass with Wildcard Pattern Matching on Cloud Foundry (critical 9.8)
- [CVE-2026-40976](https://insights.sbomify.com/CVE-2026-40976/): Spring Boot's default security filter chain has no authorization rule with Actuator but without Health (critical 9.1)
- [CVE-2026-22731](https://insights.sbomify.com/CVE-2026-22731/): Authentication Bypass under Actuator Health groups paths (high 8.2)
- [CVE-2026-22733](https://insights.sbomify.com/CVE-2026-22733/): Authentication Bypass under Actuator CloudFoundry endpoints (high 8.2)
- [CVE-2026-40972](https://insights.sbomify.com/CVE-2026-40972/): Spring Boot DevTools remote secret comparison is vulnerable to timing attacks (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-27772 and fix it if it is affected.

What it is: CVE-2022-27772 is a high-severity path traversal vulnerability in n/a, published on 30 Mar 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-27772 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.springframework.boot:spring-boot (Maven): affected all versions; fixed in 2.2.11.RELEASE
- org.springframework.boot:spring-boot (Maven): affected all versions; fixed in 2.2.11.RELEASE

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-2022-27772/ (Markdown: https://insights.sbomify.com/CVE-2022-27772/index.md)
```

## Sources

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

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