# CVE-2023-34042: Spring Security's spring-security.xsd file is world writable > A world-writable configuration file in Spring Security allows local attackers to modify it, potentially leading to future exploits. - **Severity:** Medium 4.1 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 5 Feb 2024 - **Updated:** 3 Jun 2025 - **Also known as:** GHSA-9gp8-6cg8-7h34 ## What is CVE-2023-34042? CVE-2023-34042 is a medium-severity vulnerability in Spring Security, published on 5 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim. ### Official 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. Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource) ## Which versions are affected by CVE-2023-34042? 8 open source packages ship an affected version, including org.springframework.security:spring-security-config. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.springframework.security:spring-security-config` | Maven | From 5.7.9 | 5.7.11 | | `org.springframework.security:spring-security-config` | Maven | From 5.7.9 | 5.7.11 | | `org.springframework.security:spring-security-config` | Maven | From 5.8.4 | 5.8.7 | | `org.springframework.security:spring-security-config` | Maven | From 5.8.4 | 5.8.7 | | `org.springframework.security:spring-security-config` | Maven | From 6.0.4 | 6.0.7 | | `org.springframework.security:spring-security-config` | Maven | From 6.0.4 | 6.0.7 | | `org.springframework.security:spring-security-config` | Maven | From 6.1.1 | 6.1.4 | | `org.springframework.security:spring-security-config` | Maven | From 6.1.1 | 6.1.4 | Products: Vmware Spring Security. ## How do I fix CVE-2023-34042? Upgrade org.springframework.security:spring-security-config to a fixed version for your release line: 5.7.11, 5.8.7, 6.0.7 or 6.1.4. ## Is CVE-2023-34042 being exploited? There is no known exploitation of CVE-2023-34042 in the wild and no public exploit code. ## Other vulnerabilities in Spring Security - [CVE-2014-3527](https://insights.sbomify.com/CVE-2014-3527/): Authorization Bypass in Spring Security (critical 9.8) - [CVE-2026-59354](https://insights.sbomify.com/CVE-2026-59354/): Spring Security OAuth2 Authorization Server: Insufficient validation of Dynamic Client Registration metadata (critical 9.6) - [CVE-2026-59270](https://insights.sbomify.com/CVE-2026-59270/): Spring Security embedded UnboundID LDAP server exposes well-known administrative bind DN on all network interfaces (critical 9.4) - [CVE-2026-22732](https://insights.sbomify.com/CVE-2026-22732/): Under Some Conditions Spring Security HTTP Headers Are not Written (critical 9.1) - [CVE-2023-34034](https://insights.sbomify.com/CVE-2023-34034/): Access Control Bypass in Spring Security (critical 9.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-34042 and fix it if it is affected. What it is: CVE-2023-34042 is a medium-severity vulnerability in Spring Security, published on 5 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-34042 in the wild and no public exploit code. Affected packages and fixed versions: - org.springframework.security:spring-security-config (Maven): affected from 5.7.9; fixed in 5.7.11 - org.springframework.security:spring-security-config (Maven): affected from 5.7.9; fixed in 5.7.11 - org.springframework.security:spring-security-config (Maven): affected from 5.8.4; fixed in 5.8.7 - org.springframework.security:spring-security-config (Maven): affected from 5.8.4; fixed in 5.8.7 - org.springframework.security:spring-security-config (Maven): affected from 6.0.4; fixed in 6.0.7 - org.springframework.security:spring-security-config (Maven): affected from 6.0.4; fixed in 6.0.7 - org.springframework.security:spring-security-config (Maven): affected from 6.1.1; fixed in 6.1.4 - org.springframework.security:spring-security-config (Maven): affected from 6.1.1; fixed in 6.1.4 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-34042/ (Markdown: https://insights.sbomify.com/CVE-2023-34042/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-34042 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-34042 - OSV: https://osv.dev/vulnerability/CVE-2023-34042 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-34042/ Summaries are generated and may contain mistakes; the official description above is the record.