CVE-2024-22236VulnerabilityPublished 31 Jan 2024Updated 3 Jun 2025

CVE-2024-22236: Spring Cloud Contract · Vulnerability

Affects Spring Cloud ContractSource CVE Database V5

Not known to be exploited · CVSS 3.3 Low.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

3.3Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 31 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Mavenorg.springframework.cloud/spring-cloud-contract-shade`pkg:maven/org.springframework.cloud/spring-cloud-contract-shade`Other threats	Affected =3.1.0 =4.0.0 =4.1.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-22236, European organizations should: 1) Upgrade Spring Cloud Contract to the fixed versions 4.1.1, 4.0.5, or 3.1.10 or later, where the issue with temporary directory permissions has been addressed. 2) Review and harden permissions on temporary directories used during test execution to ensure they are not accessible by unauthorized users. This includes configuring the underlying operating system and build environments to enforce strict access controls. 3) Isolate development and testing environments from production and restrict local user access to these environments, especially in shared or CI/CD systems. 4) Audit and monitor file system permissions and access logs for unusual access patterns to temporary directories used by Spring Cloud Contract. 5) Educate development and DevOps teams about secure handling of test artifacts and the importance of patching dependencies promptly. 6) Consider containerizing test environments with minimal privileges and ephemeral storage to reduce the risk of local information disclosure. These steps go beyond generic patching advice by emphasizing environment hardening, access control, and operational security best practices tailored to the vulnerability context.

Description

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.

Impact

For European organizations, the impact of CVE-2024-22236 is generally limited but still noteworthy in contexts where Spring Cloud Contract is used extensively in development and testing pipelines. Organizations relying on microservices architectures and contract testing with Spring Cloud Contract may inadvertently expose sensitive test data or configuration details if temporary directories are accessible to unauthorized local users. This could lead to leakage of proprietary API contract information or test credentials, potentially aiding further attacks. While the vulnerability does not directly affect production systems or cause service disruption, the exposure of internal test data could undermine trust and compliance, especially under stringent data protection regulations such as GDPR. Additionally, organizations with shared development environments or CI/CD infrastructures could face increased risk if proper isolation and access controls are not enforced. The low CVSS score reflects the limited scope and local nature of the vulnerability, but the risk is amplified in multi-tenant or poorly secured development setups.

CWE-377Insecure Temporary File (opens in a new tab)
Class weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
Creating and using insecure temporary files can leave application and system data vulnerable to attack.
OWASP Cheat Sheets
Authorization (opens in a new tab)
Attack patterns
Explore for Predictable Temporary File Names (opens in a new tab)
Screen Temporary Files for Sensitive Information (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

spring.io/security/cve-2024-22236 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Jul 2025, 13:25 UTC

WeaknessesCWE-377

Technical details

References

Community reviews

Related threats