Skip to content
Fencer Intel
low 3.3

CVE-2024-22236 json

Spring Cloud Contract vulnerable to local information disclosure

published 2y ago modified 4mo ago also GHSA-p6rp-mx85-m459 , EUVD-2024-0392

cvss
3.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 13%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.springframework.cloud:spring-cloud-contract-shade 3.1.10, 4.0.5, 4.1.1
  • Spring Spring Cloud Contract 3.1.10, 4.0.6, 4.1.1

Is CVE-2024-22236 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2y ago

Exploit prediction

0.22% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 3.3 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
GitHub 3.1 3.3 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.springframework.cloud:spring-cloud-contract-shade
>=4.1.0, <4.1.1
>=4.0.0, <4.0.5
>=3.1.0, <3.1.10
4.1.1
4.0.5
3.1.10

Affected products

  • Spring Spring Cloud Contract

Classification

Weakness
  • CWE-377 DEPRECATED: Insecure Temporary File
  • CWE-732 Incorrect Permission Assignment for Critical Resource
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.