{
  "@id": "urn:uuid:b995c3a0-90fb-4ee7-ab76-9b62b29b6bd3",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 30,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-10T15:50:03.446715+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-config@4.2.20.RELEASE-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-config@4.2.20.RELEASE-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2007-1651 does not affect version 4.2.20.RELEASE-tuxcare.7 of org.springframework.security:spring-security-config. Version 4.2.20.RELEASE is not vulnerable. Summary: The target repository is NOT VULNERABLE to CVE-2007-1651. The security fix has already been applied.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2007-1651"
      },
      "impact_statement": "Version 4.2.20.RELEASE is not vulnerable. Summary: The target repository is NOT VULNERABLE to CVE-2007-1651. The security fix has already been applied."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-config@4.2.20.RELEASE-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-config@4.2.20.RELEASE-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2007-1652 does not affect version 4.2.20.RELEASE-tuxcare.7 of org.springframework.security:spring-security-config. Version 4.2.20.RELEASE is not vulnerable. Summary: The target repository is NOT VULNERABLE to CVE-2007-1652. The security fix has already been applied. The code contains the necessary null check for DiscoveryInformation that prevents replay attacks and session-based exploitation.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2007-1652"
      },
      "impact_statement": "Version 4.2.20.RELEASE is not vulnerable. Summary: The target repository is NOT VULNERABLE to CVE-2007-1652. The security fix has already been applied. The code contains the necessary null check for DiscoveryInformation that prevents replay attacks and session-based exploitation."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-config@4.2.20.RELEASE-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-config@4.2.20.RELEASE-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-10-29T00:29:56.875680+00:00",
      "status_notes": "Vulnerability CVE-2023-34034 affects version 4.2.20.RELEASE-tuxcare.7 of org.springframework.security:spring-security-config.",
      "vulnerability": {
        "name": "CVE-2023-34034"
      },
      "action_statement": "Vulnerability CVE-2023-34034 affects version 4.2.20.RELEASE-tuxcare.7 of org.springframework.security:spring-security-config."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-config@4.2.20.RELEASE-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-config@4.2.20.RELEASE-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-10-29T07:31:18.734944+00:00",
      "status_notes": "Vulnerability CVE-2023-34035 affects version 4.2.20.RELEASE-tuxcare.7 of org.springframework.security:spring-security-config.",
      "vulnerability": {
        "name": "CVE-2023-34035"
      },
      "action_statement": "Vulnerability CVE-2023-34035 affects version 4.2.20.RELEASE-tuxcare.7 of org.springframework.security:spring-security-config."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-config@4.2.20.RELEASE-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-config@4.2.20.RELEASE-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2023-34042 does not affect version 4.2.20.RELEASE-tuxcare.7 of org.springframework.security:spring-security-config. 4.2.20.RELEASE is not vulnerable because CVE-2023-34042 only affects Spring Security 5.7.9\u20135.7.10, 5.8.4\u20135.8.6, 6.0.4\u20136.0.6, and 6.1.1\u20136.1.3. Version 4.2.20.RELEASE is in the 4.2.x line, which is outside those ranges. The advisory and NVD do not list any 4.x versions as affected, so 4.2.20.RELEASE is not in scope.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2023-34042"
      },
      "impact_statement": "4.2.20.RELEASE is not vulnerable because CVE-2023-34042 only affects Spring Security 5.7.9\u20135.7.10, 5.8.4\u20135.8.6, 6.0.4\u20136.0.6, and 6.1.1\u20136.1.3. Version 4.2.20.RELEASE is in the 4.2.x line, which is outside those ranges. The advisory and NVD do not list any 4.x versions as affected, so 4.2.20.RELEASE is not in scope."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-config@4.2.20.RELEASE-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-config@4.2.20.RELEASE-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-10-29T02:15:57.456054+00:00",
      "status_notes": "Vulnerability CVE-2025-22223 does not affect version 4.2.20.RELEASE-tuxcare.7 of org.springframework.security:spring-security-config. not_affected \u2014 Spring Security 4.2.20.RELEASE is not affected by CVE-2025-22223. The vulnerability is specific to the @EnableMethodSecurity annotation and UniqueSecurityAnnotationScanner class, both introduced in Spring Security 5.6+. Version 4.2.x uses the older @EnableGlobalMethodSecurity architecture with a completely different annotation scanning mechanism (PrePostAnnotationSecurityMetadataSource using Sp...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2025-22223"
      },
      "impact_statement": "not_affected \u2014 Spring Security 4.2.20.RELEASE is not affected by CVE-2025-22223. The vulnerability is specific to the @EnableMethodSecurity annotation and UniqueSecurityAnnotationScanner class, both introduced in Spring Security 5.6+. Version 4.2.x uses the older @EnableGlobalMethodSecurity architecture with a completely different annotation scanning mechanism (PrePostAnnotationSecurityMetadataSource using Sp..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-config@4.2.20.RELEASE-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-config@4.2.20.RELEASE-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-22753 does not affect version 4.2.20.RELEASE-tuxcare.7 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.20.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.20.RELEASE."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-config@4.2.20.RELEASE-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-config@4.2.20.RELEASE-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-22754 does not affect version 4.2.20.RELEASE-tuxcare.7 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.20.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.20.RELEASE. The upstream POC tests (RegexMatcher, CiRegexMatcher + AuthorizationManager variants) were ported verbatim and pass."
    }
  ]
}
