{
  "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json",
  "bomFormat": "CycloneDX",
  "specVersion": "1.6",
  "serialNumber": "urn:uuid:2bfb79d6-8235-56d5-a917-07e5b41ab5a6",
  "version": 1,
  "metadata": {
    "supplier": {
      "name": "TuxCare",
      "url": [
        "https://tuxcare.com"
      ]
    }
  },
  "components": [
    {
      "name": "spring-security-core",
      "purl": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1",
      "type": "library",
      "group": "org.springframework.security",
      "bom-ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1",
      "version": "5.4.8-tuxcare.1",
      "pedigree": {
        "ancestors": [
          {
            "name": "spring-security-core",
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.4.8",
            "type": "library",
            "group": "org.springframework.security",
            "version": "5.4.8"
          }
        ]
      },
      "supplier": {
        "url": [
          "https://tuxcare.com"
        ],
        "name": "TuxCare"
      }
    }
  ],
  "vulnerabilities": [
    {
      "id": "CVE-2010-3700",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:98316a46-7364-5ecc-b12f-f02a966fda8b",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2010-3700 does not affect version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 CVE-2010-3700 (path parameter security bypass) is NOT present in Spring Security 5.4.8. The fix was added by upstream Spring Security in October 2010 (commit 7d97adc687, SEC-1584) and was already included in the 5.4.8 release that TuxCare onboarded. The defense (HttpFirewall with RequestWrapper) strips path parameters from URLs before security pattern matching, preventing attacks like /admin.ht...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2011-2731",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:d8b6780e-7454-55fb-8249-ebbff6af6663",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2011-2731 does not affect version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 CVE-2011-2731 is NOT present in Spring Security 5.4.8. The vulnerability (race condition allowing privilege escalation via shared SecurityContext in RunAsManager) was fixed by upstream Spring Security in commits SEC-1750 and SEC-1967, which are both present in the target. These fixes were already included in the upstream Spring Security 5.4.8 release that TuxCare onboarded. The fixes create thr...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2011-2732",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:4d9ff910-216b-52df-a0a3-4285dc8e589c",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2011-2732 does not affect version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 Spring Security 5.4.8 is NOT affected by CVE-2011-2732. The CRLF injection vulnerability in logout functionality was fixed by upstream Spring Security in 2011 (commit 824464516 by Luke Taylor). Both defense mechanisms from the vendor patches are present in the target: (1) FirewalledResponse validates redirect locations and rejects CR/LF characters (line 46 explicitly references SEC-1790), and (...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2011-2894",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:71830cf5-6e00-5c72-b925-c9b093e7584c",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2011-2894 does not affect version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 CVE-2011-2894 describes a deserialization vulnerability where Spring Security's ContextPropagatingRemoteInvocation serialized entire SecurityContext objects from untrusted sources, enabling remote code execution via malicious deserialized objects. The vendor patch (ba719dc0e1, May 2011) replaced SecurityContext object serialization with String-only transmission of principal and credentials. The...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2012-5055",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:c1b2d8da-8e38-5c17-8793-2117c46dcea1",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2012-5055 does not affect version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 CVE-2012-5055 is NOT present in the target. The fix for the timing attack vulnerability was authored by upstream Spring Security maintainer Rob Winch (rwinch@vmware.com) in commit c076f0f2e1 on 2012-10-07 and shipped in the upstream Spring Security 5.4.8 release that TuxCare onboarded. The target contains the complete mitigation: dummy password validation in the UsernameNotFoundException handle...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2014-0097",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:66622506-2f02-5a7a-b48a-534c17433092",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2014-0097 affects version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core."
      }
    },
    {
      "id": "CVE-2014-3527",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:bbc6a30c-c119-5d0c-95b7-3d16bf969db9",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2014-3527 does not affect version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core. CVE-2014-3527 is NOT present in Spring Security 5.4.8. The vulnerability (using untrusted HTTP Host header values for CAS proxy ticket service URL construction) was fixed by upstream commit 934937d9c1 authored by Rob Winch (rwinch@gopivotal.com) and shipped in the Spring Security 5.4.8 release before TuxCare onboarded it. The fix replaces HttpServletRequest header-based host/port extraction with protocol/host/port parsed from the trusted configured ServiceProperties service URL, preventing attackers from manipulating service identity via Host header injection.",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2016-5007",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:a4be202d-729f-5afa-8464-c2323c2ec504",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2016-5007 does not affect version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core. CVE-2016-5007 addresses URL pattern matching inconsistencies between Spring Security authorization rules and Spring MVC routing that could allow attackers to bypass security protections. The target repository (Spring Security 5.4.8) is NOT AFFECTED because both upstream fixes for this vulnerability were already present in the Spring Security 5.4.8 release that TuxCare onboarded. The fixes include: (1) MvcRequestMatcher class that aligns security pattern matching with Spring MVC's matching logic, and (2) DefaultHttpFirewall enhancement that rejects requests containing URL-encoded slashes (%2f/%2F) which was a primary bypass technique. Both fixes were authored by upstream Spring Security maintainer Rob Winch and shipped before the first TuxCare commit (d97501a77 \"Onboard version 5.4.8\"). The DefaultHttpFirewall protection is active by default, preventing the exploitation path described in the CVE.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 4.1.1), NVD (= 3.2.0; = 3.2.1; = 3.2.2; = 3.2.3; = 3.2.4; = 3.2.5; = 3.2.6; = 3.2.7; = 3.2.8; = 3.2.9; = 3.2.10; = 4.0.0; = 4.0.1; = 4.0.2; = 4.0.3; = 4.0.4; = 4.1.0), cve.org (>= 3.2, < 3.3; >= 4.0, < 4.1; = 4.1.0), Snyk (>= 3.2.0.RELEASE, < 4.1.1.RELEASE; >= 3.2.0.RELEASE, < 4.1.1.RELEASE).",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2016-9879",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:6b740376-2ed1-54b7-91fc-2bbcdcc91ae4",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2016-9879 does not affect version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core. Target repository Spring Security 5.4.8 is NOT AFFECTED by CVE-2016-9879. The vulnerability pattern (missing URL-encoded slash validation allowing security constraint bypass) is not present because the upstream vendor fix was already included in Spring Security 5.4.8 when TuxCare onboarded it. The fix detects and rejects URLs containing %2f or %2F in the requestURI before security constraint matching occurs, preventing attackers from bypassing security rules via path parameter confusion.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 3.2.10.RELEASE; >= 4.0.0.RELEASE, < 4.1.4.RELEASE; >= 4.2.0.RELEASE, < 4.2.1.RELEASE), NVD (= 3.2.0; = 3.2.1; = 3.2.2; = 3.2.3; = 3.2.4; = 3.2.5; = 3.2.6; = 3.2.7; = 3.2.8; = 3.2.9; = 4.1.0; = 4.1.1; = 4.1.2; = 4.1.3; = 4.2.0), Snyk (>= 3.2.0.RELEASE, < 3.2.10.RELEASE; >= 4.0.0.RELEASE, < 4.1.4.RELEASE; >= 4.2.0.RELEASE, < 4.2.1.RELEASE; <= 0).",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2017-4995",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:562fb907-a7f1-5c01-9bd4-8841d1817253",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2017-4995 does not affect version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core. Spring Security 5.4.8 is not affected by CVE-2017-4995. The upstream fix for this Jackson deserialization vulnerability was already present in version 5.4.8 when TuxCare onboarded it. The target code implements whitelist-based type resolution (AllowlistTypeIdResolver) that validates classes during deserialization, preventing arbitrary code execution via deserialization gadgets. The fix was authored by Rob Winch (upstream Spring Security maintainer) in commit 5dee8534cd1 on 2017-05-31, predating the TuxCare onboarding commit d97501a77a by amoniatovskiy@cloudlinux.com.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 4.2.0.RELEASE, < 4.2.3.RELEASE; >= 5.0.0.M1, < 5.0.0.M2), NVD (= 4.2.0-release; = 4.2.1-release; = 4.2.2-release; = 5.0.0-m1), cve.org (= 4.2.0.RELEASE; = 4.2.2.RELEASE; = 5.0.0.M1), Snyk (>= 4.2.0.RELEASE, < 4.2.3.RELEASE).",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2018-1199",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:74fec598-37e2-5ae6-9feb-a9101220f939",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2018-1199 does not affect version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 CVE-2018-1199 is not present in Spring Security 5.4.8. The vulnerability involved bypassing security constraints using URL path parameters with semicolons (e.g., /secured/admin.html;x=user.html). The upstream vendor fix (commit 0eef5b4b425ab42b9fa0fde1a3f36a37b92558f2 by Rob Winch) introduced StrictHttpFirewall, which rejects requests containing semicolons (literal ';', '%3b', '%3B') in URLs by...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2018-15801",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:bee64953-a27d-52ea-84d9-d2cee42bc00f",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2018-15801 does not affect version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core. CVE-2018-15801 is NOT present in Spring Security 5.6.5-tuxcare.1. The vulnerability exploited Java's URL.equals() method which performs DNS resolution, allowing different issuer URLs to be treated as equivalent. The upstream fix (commit 19649db9ce by Josh Cummings) was already present in Spring Security 5.4.8 that TuxCare onboarded. The target uses string comparison for issuer validation (issuer::equals where issuer is String), not URL.equals(), eliminating the vulnerability. The issuer claim is converted to String by MappedJwtClaimSetConverter.convertIssuer() before validation.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.1.0, < 5.1.2; >= 5.1.0, < 5.1.2), cve.org (>= 5.1.x, < 5.1.2), Snyk (>= 5.1.0, < 5.1.2.RELEASE).",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2019-11272",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:264bd5e3-e96c-5fb1-8ba2-6fd42745c58a",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2019-11272 does not affect version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core. Spring Security 5.4.8 is not affected by CVE-2019-11272. The vulnerable class PlaintextPasswordEncoder was removed from Spring Security in version 5.0.0 (October 2017), before the CVE was published. The CVE explicitly affects \"versions 4.2.x up to 4.2.12, and older unsupported versions.\" Version 5.4.8 does not contain PlaintextPasswordEncoder and therefore cannot exhibit the null-to-string conversion vulnerability. The current plaintext password encoder (NoOpPasswordEncoder) uses String.equals() which correctly handles null encoded passwords by returning false.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 4.2.13; < 4.2.13.RELEASE), NVD (< 4.2.13), cve.org (>= 4.2, < 4.2.13.RELEASE), Snyk (>= 4.2.0.RELEASE, < 4.2.13.RELEASE).",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2019-3795",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:81a08df0-c45c-5e69-9172-d9cde791fe3e",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2019-3795 does not affect version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 The target Spring Security 5.4.8 is not affected by CVE-2019-3795. The vulnerability (insecure randomness when using SecureRandomFactoryBean#setSeed) has been fixed in the upstream code. The fix ensures nextBytes() is called before setSeed() to prevent the custom seed from replacing the entire internal state, making the RNG output predictable. This fix was authored by Josh Cummings (upstream ma...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2020-5407",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:47cdb35f-b090-5cba-950b-6a08a44c4d01",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2020-5407 does not affect version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core. Version 5.4.8 is on a newer release line than any version the advisories list as affected. Advisories: GitHub GHSA-48rw-j489-928m (affected below 5.3.2), NVD (affected below 5.3.2), CVE record (affected below 5.3.2).",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2020-5408",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:da7ecc85-f545-5e0a-b155-cc10cad314cb",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2020-5408 does not affect version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 CVE-2020-5408 affects Spring Security's queryable text encryptor which uses a fixed null IV with CBC mode, enabling dictionary attacks. The target version 5.4.8 contains the upstream vendor's fix: the queryableText() method is deprecated with explicit security warnings directing users away from this insecure API. The deprecation was added by upstream commit db155b30 (2020-04-30) and shipped in ...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2021-22119",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:0c16f923-08a4-548d-8533-38dcb352b542",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2021-22119 does not affect version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core. The target Spring Security 5.4.8 is NOT affected by CVE-2021-22119. The fix for this DoS vulnerability was already included in the upstream Spring Security 5.4.8 release, which was then onboarded by TuxCare. The vulnerable pattern (unbounded accumulation of OAuth2 authorization requests in session storage) is not present in the target code because the fix commit e447a35cf2 authored by Craig Andrews shipped in the upstream release before TuxCare's onboarding commit d97501a77a.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.5.0, < 5.5.1; >= 5.4.0, < 5.4.7; >= 5.3.0, < 5.3.10; >= 5.2.0, < 5.2.11; >= 5.5.0, < 5.5.1; >= 5.4.0, < 5.4.7; >= 5.3.0, < 5.3.10; >= 5.2.0, < 5.2.11), NVD (>= 5.2.0, < 5.2.11; >= 5.3.0, < 5.3.10; >= 5.4.0, < 5.4.7; >= 5.5.0, < 5.5.1), cve.org (>= 5.5, < 5.5.1; >= 5.4, < 5.4.7; >= 5.3, < 5.3.10; < 5.2.x; < 5.2.11), Snyk (>= 5.5.0, < 5.5.1; >= 5.4.0, < 5.4.7; >= 5.3.0.RELEASE, < 5.3.10.RELEASE; >= 5.2.0.RELEASE, < 5.2.11.RELEASE).",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2022-22976",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:52c3a21c-81cb-5db8-aa21-2986bb0938ea",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2022-22976 affects version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core."
      }
    },
    {
      "id": "CVE-2022-22978",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:3f83ff1f-139e-581e-8b76-7ee443bca93f",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2022-22978 is fixed in version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core."
      }
    },
    {
      "id": "CVE-2022-31692",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:c9e7d418-9c9c-5c96-822d-23d80e492561",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2022-31692 does not affect version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core. Prechecker: No vulnerable code from the fix was found; this version has none of the entry points of the fix's regression test and no class named after a file the fix changes. Version 5.4.8 is on an older release line than any version the advisories list as affected. Advisories: GitHub GHSA-mmmh-wcxm-2wr4 (newer lines only), NVD (newer lines only).",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2023-20862",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:c2900f10-b45b-5f51-90e4-387780ea59f6",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2023-20862 does not affect version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 Spring Security 5.4.8 is NOT AFFECTED by CVE-2023-20862. The vulnerability requires both invalidateHttpSession(false) AND the requireExplicitSave(true) feature introduced in Spring Security 5.8+. Version 5.4.8 does not have requireExplicitSave \u2014 it always uses SecurityContextPersistenceFilter's automatic save mechanism, which properly removes the session-stored authenticated context after logou...",
        "justification": "protected_at_runtime"
      }
    },
    {
      "id": "CVE-2024-22234",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:7f02f755-0df7-5501-9a0e-cbafd1d57463",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2024-22234 affects version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core."
      }
    },
    {
      "id": "CVE-2024-22257",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:e8d516b2-a951-5a89-82da-702b06a78a84",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2024-22257 is fixed in version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core."
      }
    },
    {
      "id": "CVE-2024-38810",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:923532ab-0272-52d8-8ce7-0f49b63fe9fd",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2024-38810 does not affect version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 Spring Security 5.4.8 is not affected by CVE-2024-38810. The vulnerability concerns the @AuthorizeReturnObject annotation, which was introduced in Spring Security 6.2.5/6.3.0 and does not exist in version 5.4.8. The CVE specifically affects versions 6.3.0 and 6.3.1, which are much newer than the target version. Exhaustive searches confirmed no presence of this annotation or its implementation i...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2024-38827",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:9d34f93e-4117-5cd0-a71e-a9cc5b82f426",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2024-38827 is fixed in version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core."
      }
    },
    {
      "id": "CVE-2025-22223",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:58a747f4-1c8b-5e8c-a0a5-3246aa440b82",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2025-22223 does not affect version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 Spring Security 5.4.8 is not affected by CVE-2025-22223. The vulnerability specifically targets the @EnableMethodSecurity annotation scanning system introduced in Spring Security 5.5+. Version 5.4.8 does not have this feature - it uses the older @EnableGlobalMethodSecurity system with a different architecture (PrePostAnnotationSecurityMetadataSource). The vulnerable component UniqueSecurityAnno...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2025-22234",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:31a5f2d1-7722-5895-8e72-c1a099e68c3c",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2025-22234 does not affect version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 Spring Security 5.4.8 is not affected by CVE-2025-22234. This CVE describes a timing attack vulnerability introduced by the CVE-2025-22228 fix, which added a `for_check` parameter to BCrypt's password hashing to differentiate between encoding new passwords (rejects >72 bytes) and matching existing passwords (allows >72 bytes for backwards compatibility). The target repository does not contain t...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2025-41232",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:99697fc6-8fe1-5169-a65e-1794d81abf53",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2025-41232 does not affect version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core. CVE-2025-41232 is in UniqueSecurityAnnotationScanner, which Spring Security 6.4 added for method security in AspectJ mode. Spring Security 5.4.8 does not contain that scanner, so it is not affected.",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2025-41248",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:0c8a7982-e60c-5243-8ca4-d20629b0339a",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2025-41248 does not affect version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core. CVE-2025-41248 affects the annotation lookup used by @EnableMethodSecurity. Spring Security 5.4.8 predates @EnableMethodSecurity, which was added in 5.6, and has no such lookup, so it is not affected.",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2026-22746",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:a45efd9a-9b94-5f7f-91e7-c4a76e3e4c3d",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-22746 is fixed in version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core."
      }
    },
    {
      "id": "CVE-2026-22751",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:72bd06c1-409f-5b73-a69c-9b36a3cc6b96",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-22751 does not affect version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 Spring Security 5.4.8 is not affected by CVE-2026-22751. The vulnerable component (JdbcOneTimeTokenService and the entire OneTimeToken authentication feature) does not exist in this version. The OneTimeToken feature was introduced in Spring Security 6.4.0 (October 2024), years after version 5.4.8 was released (circa 2021). TuxCare correctly backported the fix to affected versions 6.4.3 and 6.4....",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2026-59276",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:82c6ba1e-9f64-52da-9ccc-4be5637870f0",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-59276 is fixed in version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core."
      }
    },
    {
      "id": "CVE-2026-59277",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:e7d02102-f45b-5d79-89d1-d7dd8c58ee37",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-59277 does not affect version 5.4.8-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 Spring Security 5.4.8 does not contain the InetAddressMatchers utility class or its matchInternal()/matchExternal() methods that are vulnerable in CVE-2026-59277. This feature was introduced in later versions of Spring Security (likely 6.x). The target version only has the older IpAddressMatcher class for CIDR/subnet matching, which does not perform internal/external network classification and ...",
        "justification": "code_not_present"
      }
    }
  ],
  "dependencies": [
    {
      "ref": "pkg:maven/org.springframework.security/spring-security-core@5.4.8-tuxcare.1"
    }
  ]
}