dbcve.org
Spring Cloud ContractFramework / library · VMware

CVE-2024-22236

MEDIUM · 5.5 CVSS v3.1 Published 2024-01-31
Fix available
A fix is available. Upgrade to 3.1.10 / 4.0.5 or later.
See remediation →
57/100
Remediation priority · Elevated
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 Contract, versions 4.1.x prior to 4.1.1, versions 4.0.x prior to 4.0.5, and versions 3.1.x prior to 3.1.10, test execution is vulnerable to local information disclosure via temporary directory created with unsafe permissions through the shaded com.google.guava:guava dependency in the org.springframework.cloud:spring-cloud-contract-shade dependency.

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

The Spring Cloud Contract shaded dependency includes a vulnerable version of com.google.guava:guava that creates temporary directories with unsafe permissions (likely world-readable). During test execution, sensitive files placed in these temp directories can be read by other local users, enabling local information disclosure.

MitigationUpgrade Spring Cloud Contract to version 4.1.1, 4.0.5, or 3.1.10 or later, which bundle a patched guava dependency that creates temp directories with secure permissions.

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 ContractFramework / library
Affected:>= 3.1.0, < 3.1.10>= 4.0.0, < 4.0.5= 4.1.0

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

CVSS:3.1/AV:L/AC:L/PR:L/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. Locate Spring Cloud Contract dependency
    Search your project build files (pom.xml, build.gradle) or JAR manifests for 'spring-cloud-contract' or check the classpath for org.springframework.cloud.contract jar files.
    Affected if Spring Cloud Contract is found in the project dependencies
  2. Determine Spring Cloud Contract version
    Check the version specified in pom.xml or build.gradle for the spring-cloud-contract dependency, or run 'mvn dependency:tree' or 'gradle dependencies' to see the resolved version.
    Affected if Version is 3.1.0 through 3.1.9, 4.0.0 through 4.0.4, or exactly 4.1.0
  3. Identify guava transitive dependency
    Run 'mvn dependency:tree | grep guava' or 'gradle dependencies | grep guava' to see if com.google.guava:guava is pulled in as a transitive dependency of Spring Cloud Contract.
    Affected if guava is present as a transitive dependency
  4. Check guava version
    In the dependency tree output, note the guava version number (e.g., 31.1-jre, 32.0.0-jre). Compare this to known vulnerable guava versions that have unsafe temp directory permissions.
    Affected if guava version is before the patched version (guava 32.1.2-jre or later typically contains the fix)

Your environment is affected if Spring Cloud Contract version falls within 3.1.0-3.1.9, 4.0.0-4.0.4, or 4.1.0 AND the bundled guava dependency contains the unsafe temp directory creation behavior.

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 3.1.10 / 4.0.5 or later
Fixed in 3.1.104.0.5
Interim mitigation

Upgrade Spring Cloud Contract to version 4.1.1, 4.0.5, or 3.1.10 or later, which bundle a patched guava dependency that creates temp directories with secure permissions.

Recommended fix High confidence

3.1.10 for 3.1.x line, 4.0.5 for 4.0.x line, or 4.1.1 for 4.1.x line

  1. Update the Spring Cloud Contract dependency version in your project's pom.xml or build.gradle to one of the fixed versions: 3.1.10, 4.0.5, or 4.1.1
  2. For Maven: Change the version in the org.springframework.cloud:spring-cloud-contract dependency to the appropriate fixed version
  3. For Gradle: Update the version in the dependencies block to the appropriate fixed version
  4. Run your build to verify the upgrade resolves the issue and does not break existing functionality
  5. Ensure your test suite passes to confirm the unsafe temporary directory permissions issue is resolved

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

Fix this in Spring Cloud Contract Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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