{ "@id": "urn:uuid:f71e6c0a-c604-4118-95bd-369fd2f9dda7", "role": "Document Creator", "author": "https://tuxcare.com", "version": 28, "@context": "https://openvex.dev/ns/v0.2.0", "timestamp": "2026-11-10T15:51:00.040518+00:00", "statements": [ { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.springframework.security/spring-security-config@4.2.12.RELEASE-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-config@4.2.12.RELEASE-tuxcare.1" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2007-1651 does not affect version 4.2.12.RELEASE-tuxcare.1 of org.springframework.security:spring-security-config. already_fixed \u2014 The target repository already contains the fix for CVE-2007-1651. The upstream patch commit f5468087c2 (April 15, 2010) that removes cached DiscoveryInformation from session is present in the target's git history, plus additional security enhancements from commit 89fa771093 (July 13, 2011) that add null checking and ATTRIBUTE_LIST_KEY removal.", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2007-1651" }, "impact_statement": "already_fixed \u2014 The target repository already contains the fix for CVE-2007-1651. The upstream patch commit f5468087c2 (April 15, 2010) that removes cached DiscoveryInformation from session is present in the target's git history, plus additional security enhancements from commit 89fa771093 (July 13, 2011) that add null checking and ATTRIBUTE_LIST_KEY removal." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.springframework.security/spring-security-config@4.2.12.RELEASE-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-config@4.2.12.RELEASE-tuxcare.1" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2007-1652 does not affect version 4.2.12.RELEASE-tuxcare.1 of org.springframework.security:spring-security-config. already_fixed \u2014 The target repository (spring-security 5.7.11.tuxcare) already contains the security fixes for CVE-2007-1652. Both defensive measures from the upstream patches are present: (1) null check rejecting requests with missing DiscoveryInformation at lines 141-144, and (2) immediate session token removal at lines 149-150. These fixes were merged via upstream commits f5468087c2 (April 2010) and 89fa771...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2007-1652" }, "impact_statement": "already_fixed \u2014 The target repository (spring-security 5.7.11.tuxcare) already contains the security fixes for CVE-2007-1652. Both defensive measures from the upstream patches are present: (1) null check rejecting requests with missing DiscoveryInformation at lines 141-144, and (2) immediate session token removal at lines 149-150. These fixes were merged via upstream commits f5468087c2 (April 2010) and 89fa771..." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.springframework.security/spring-security-config@4.2.12.RELEASE-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-config@4.2.12.RELEASE-tuxcare.1" } } ], "timestamp": "2026-10-29T00:29:56.875680+00:00", "status_notes": "Vulnerability CVE-2023-34034 affects version 4.2.12.RELEASE-tuxcare.1 of org.springframework.security:spring-security-config.", "vulnerability": { "name": "CVE-2023-34034" }, "action_statement": "Vulnerability CVE-2023-34034 affects version 4.2.12.RELEASE-tuxcare.1 of org.springframework.security:spring-security-config." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.springframework.security/spring-security-config@4.2.12.RELEASE-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-config@4.2.12.RELEASE-tuxcare.1" } } ], "timestamp": "2026-10-29T07:31:18.734944+00:00", "status_notes": "Vulnerability CVE-2023-34035 affects version 4.2.12.RELEASE-tuxcare.1 of org.springframework.security:spring-security-config.", "vulnerability": { "name": "CVE-2023-34035" }, "action_statement": "Vulnerability CVE-2023-34035 affects version 4.2.12.RELEASE-tuxcare.1 of org.springframework.security:spring-security-config." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.springframework.security/spring-security-config@4.2.12.RELEASE-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-config@4.2.12.RELEASE-tuxcare.1" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2023-34042 does not affect version 4.2.12.RELEASE-tuxcare.1 of org.springframework.security:spring-security-config. not_affected \u2014 Spring Security 4.2.12.RELEASE is NOT affected by CVE-2023-34042. The vulnerability involves a world-writable symlink file (spring-security.xsd) packaged in JARs, but this symlink does not exist in version 4.2.12.RELEASE. The vulnerable symlink was introduced in version 5.7.9 (May 2023), long after the 4.2.x series ended. Version 4.2.12 uses a completely different build architecture (TrangPlugi...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2023-34042" }, "impact_statement": "not_affected \u2014 Spring Security 4.2.12.RELEASE is NOT affected by CVE-2023-34042. The vulnerability involves a world-writable symlink file (spring-security.xsd) packaged in JARs, but this symlink does not exist in version 4.2.12.RELEASE. The vulnerable symlink was introduced in version 5.7.9 (May 2023), long after the 4.2.x series ended. Version 4.2.12 uses a completely different build architecture (TrangPlugi..." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.springframework.security/spring-security-config@4.2.12.RELEASE-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-config@4.2.12.RELEASE-tuxcare.1" } } ], "timestamp": "2026-10-29T02:18:37.843029+00:00", "status_notes": "Vulnerability CVE-2025-22223 does not affect version 4.2.12.RELEASE-tuxcare.1 of org.springframework.security:spring-security-config. not_affected \u2014 Spring Security 4.2.12.RELEASE is NOT affected by CVE-2025-22223. The vulnerability exists only in Spring Security 5.6+ where the new @EnableMethodSecurity API and UniqueSecurityAnnotationScanner class were introduced. This version uses the older @EnableGlobalMethodSecurity API with AnnotationUtils.findAnnotation() which correctly handles generic type resolution through Spring Framework's bridg...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2025-22223" }, "impact_statement": "not_affected \u2014 Spring Security 4.2.12.RELEASE is NOT affected by CVE-2025-22223. The vulnerability exists only in Spring Security 5.6+ where the new @EnableMethodSecurity API and UniqueSecurityAnnotationScanner class were introduced. This version uses the older @EnableGlobalMethodSecurity API with AnnotationUtils.findAnnotation() which correctly handles generic type resolution through Spring Framework's bridg..." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.springframework.security/spring-security-config@4.2.12.RELEASE-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-config@4.2.12.RELEASE-tuxcare.1" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-22753 does not affect version 4.2.12.RELEASE-tuxcare.1 of org.springframework.security:spring-security-config. According to security advisories CVE-2026-22753 does not affect Spring-Security versions earlier than 7.0.0. This is supported by manual code inspection. CVE-2026-22753 is an access-control bypass that occurs when a user-registered PathPatternRequestMatcher.Builder bean (configured with a basePath/servlet path prefix) is silently ignored by the securityMatchers DSL, causing the security filter chain to match a different URL than the user configured. The vulnerability requires two pieces of infrastructure introduced in Spring Security 7.0.0: 1. The PathPatternRequestMatcher.Builder API itself (added in upstream commit aeb2dbc2 on 2025-08-18). 2. The wiring in HttpSecurityConfiguration.createSharedObjects() that registers this Builder as a shared object \u2014 the exact line patched by upstream commit 438c783c (the CVE fix). Neither piece exists in version 4.2.12.RELEASE.", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2026-22753" }, "impact_statement": "According to security advisories CVE-2026-22753 does not affect Spring-Security versions earlier than 7.0.0. This is supported by manual code inspection. CVE-2026-22753 is an access-control bypass that occurs when a user-registered PathPatternRequestMatcher.Builder bean (configured with a basePath/servlet path prefix) is silently ignored by the securityMatchers DSL, causing the security filter chain to match a different URL than the user configured. The vulnerability requires two pieces of infrastructure introduced in Spring Security 7.0.0: 1. The PathPatternRequestMatcher.Builder API itself (added in upstream commit aeb2dbc2 on 2025-08-18). 2. The wiring in HttpSecurityConfiguration.createSharedObjects() that registers this Builder as a shared object \u2014 the exact line patched by upstream commit 438c783c (the CVE fix). Neither piece exists in version 4.2.12.RELEASE." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.springframework.security/spring-security-config@4.2.12.RELEASE-tuxcare.1", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-config@4.2.12.RELEASE-tuxcare.1" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-22754 does not affect version 4.2.12.RELEASE-tuxcare.1 of org.springframework.security:spring-security-config. According to security advisories CVE-2026-22754 does not affect Spring-Security versions earlier than 7.0.0. This is supported by manual code inspection and proof-of-concept tests ported from the upstream fix commit. CVE-2026-22754 is an access-control bypass caused by PathPatternRequestMatcherFactoryBean.afterPropertiesSet() calling this.builder.basePath(this.basePath) and discarding the return value \u2014 PathPatternRequestMatcher.Builder is immutable/copy-on-modify, so the configured basePath was silently dropped and protected URLs (e.g., /spring/path) were left unmatched by the security filter chain. The vulnerability requires two pieces of infrastructure introduced in Spring Security 7.0.0: 1. The PathPatternRequestMatcher.Builder API (added in upstream commit 3e53cc2c4a, \"Use PathPatternRequestMatcher in config\"). 2. The PathPatternRequestMatcherFactoryBean class itself \u2014 the exact file patched by upstream commit 53bcf0d1 (the CVE fix). Neither piece exists in version 4.2.12.RELEASE. The upstream POC tests (RegexMatcher, CiRegexMatcher + AuthorizationManager variants) were ported verbatim and pass.", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2026-22754" }, "impact_statement": "According to security advisories CVE-2026-22754 does not affect Spring-Security versions earlier than 7.0.0. This is supported by manual code inspection and proof-of-concept tests ported from the upstream fix commit. CVE-2026-22754 is an access-control bypass caused by PathPatternRequestMatcherFactoryBean.afterPropertiesSet() calling this.builder.basePath(this.basePath) and discarding the return value \u2014 PathPatternRequestMatcher.Builder is immutable/copy-on-modify, so the configured basePath was silently dropped and protected URLs (e.g., /spring/path) were left unmatched by the security filter chain. The vulnerability requires two pieces of infrastructure introduced in Spring Security 7.0.0: 1. The PathPatternRequestMatcher.Builder API (added in upstream commit 3e53cc2c4a, \"Use PathPatternRequestMatcher in config\"). 2. The PathPatternRequestMatcherFactoryBean class itself \u2014 the exact file patched by upstream commit 53bcf0d1 (the CVE fix). Neither piece exists in version 4.2.12.RELEASE. The upstream POC tests (RegexMatcher, CiRegexMatcher + AuthorizationManager variants) were ported verbatim and pass." } ] }