dbcve.org
Spring Cloud Data FlowFramework / library · VMware

CVE-2024-37084

HIGH · 8.8 CVSS v3.1 Published 2024-07-25
Fix available
A fix is available. Upgrade to 2.11.4 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
In Spring Cloud Data Flow versions prior to 2.11.4,  a malicious user who has access to the Skipper server api can use a crafted upload request to write an arbitrary file to any location on the file system which could lead to compromising the server

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

This is a path traversal/file write vulnerability in Spring Cloud Data Flow's Skipper server component. An authenticated user with access to the Skipper server API can craft malicious upload requests to write arbitrary files to any location on the server's filesystem, potentially achieving remote code execution and full server compromise.

MitigationUpgrade Spring Cloud Data Flow to version 2.11.4 or later which contains the fix for this vulnerability. If immediate upgrade is not possible, restrict and monitor Skipper server API access to trusted users only.

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 Cloud Data FlowFramework / library
Affected:>= 2.11.0, < 2.11.4

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

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

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. Identify if Spring Cloud Data Flow is installed
    Check for Spring Cloud Data Flow installation by looking for typical installation directories (e.g., /opt/spring-cloud-dataflow, /opt/scdf), or check running processes for 'spring-cloud-dataflow' or 'skipper' components using 'ps aux | grep -i spring' or 'ps aux | grep -i skipper'. Check systemd services if deployed as services.
    Affected if Spring Cloud Data Flow or Skipper processes are found running on the system
  2. Determine the installed Spring Cloud Data Flow version
    If installed from a package, check the installed version using the package manager (e.g., 'rpm -q spring-cloud-dataflow-server' or 'dpkg -l | grep spring-cloud-dataflow'). If running from a JAR, check the JAR file name or inspect the manifest. If running in Kubernetes, check the container image tag or Helm release version.
    Affected if The installed version falls within the range >= 2.11.0 and < 2.11.4
  3. Verify if the Skipper server component is enabled and running
    Check if the Skipper server is active by querying the process list ('ps aux | grep skipper') or by checking if port 7577 (default Skipper REST API port) is listening using 'netstat -tlnp | grep 7577' or 'ss -tlnp | grep 7577'.
    Affected if Skipper server is running and its API port is accessible on the network
  4. Check Skipper server API accessibility
    Determine if the Skipper REST API (typically on port 7577) is exposed to untrusted networks. Review firewall rules, Kubernetes network policies, or reverse proxy configurations to identify if the API is accessible from outside the trusted management network.
    Affected if The Skipper API is accessible from untrusted networks or the internet without proper network segmentation

The environment is affected if Spring Cloud Data Flow version 2.11.0 through 2.11.4 is installed with the Skipper server component running and its API is network-accessible to potential attackers.

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

Upgrade Spring Cloud Data Flow to version 2.11.4 or later which contains the fix for this vulnerability. If immediate upgrade is not possible, restrict and monitor Skipper server API access to trusted users only.

Recommended fix High confidence

2.11.4

  1. 1. Review the Spring Cloud Data Flow upgrade documentation for your deployment type
  2. 2. Ensure you have a backup of your current configuration and data
  3. 3. Stop the Spring Cloud Data Flow server
  4. 4. Update the Spring Cloud Data Flow version to 2.11.4 in your deployment configuration (pom.xml, docker-compose.yml, or Kubernetes manifests)
  5. 5. Verify the Skipper server is also updated to a compatible version
  6. 6. Restart the Spring Cloud Data Flow server
  7. 7. Verify the application starts successfully and the vulnerability is resolved
Caveat Review release notes for any configuration or API changes between your version and 2.11.4

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

Fix this in Spring Cloud Data Flow Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,080
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,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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