Skip to content

Spring Security's spring-security.xsd file is world writable

Moderate severity GitHub Reviewed Published Feb 6, 2024 to the GitHub Advisory Database • Updated Nov 29, 2024

Package

maven org.springframework.security:spring-security-config (Maven)

Affected versions

>= 6.1.1, <= 6.1.3
>= 6.0.4, <= 6.0.6
>= 5.8.4, <= 5.8.6
>= 5.7.9, <= 5.7.10

Patched versions

6.1.4
6.0.7
5.8.7
5.7.11

Description

The spring-security.xsd file inside the spring-security-config jar is world writable which means that if it were extracted it could be written by anyone with access to the file system.

While there are no known exploits, this is an example of “CWE-732: Incorrect Permission Assignment for Critical Resource” and could result in an exploit. Users should update to the latest version of Spring Security to mitigate any future exploits found around this issue.

References

Published by the National Vulnerability Database Feb 5, 2024
Published to the GitHub Advisory Database Feb 6, 2024
Reviewed Feb 6, 2024
Last updated Nov 29, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

EPSS score

0.042%
(5th percentile)

Weaknesses

CVE ID

CVE-2023-34042

GHSA ID

GHSA-9gp8-6cg8-7h34

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.