# CVE-2024-22263: Arbitrary File Write Vulnerability in Spring Cloud Data Flow

> Attackers with API access can write arbitrary files to the server via crafted upload requests, potentially compromising the system.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jun 2024
- **Updated:** 1 Aug 2024

## What is CVE-2024-22263?

CVE-2024-22263 is a high-severity vulnerability in Spring Cloud Skipper, published on 19 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Spring Cloud Data Flow is a microservices-based Streaming and Batch data processing in Cloud Foundry and Kubernetes. The Skipper server has the ability to receive upload package requests. However, due to improper sanitization for upload path, a malicious user who has access to skipper server api can use a crafted upload request to write arbitrary file to any location on file system, may even compromises the server.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

No fix has been published for CVE-2024-22263 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-22263 being exploited?

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

Public exploit code:

- (CVE-2024-22263) Spring Cloud Dataflow Arbitrary File Writing Scanner (github_poc): https://github.com/securelayer7/CVE-2024-22263_Scanner

## Fix prompt for AI coding agents

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

What it is: CVE-2024-22263 is a high-severity vulnerability in Spring Cloud Skipper, published on 19 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-22263 in the wild and no public exploit code.

Affected product: Spring Cloud Skipper. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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