{
  "@id": "urn:uuid:42a9c698-c0ea-4f2f-9b26-303ad698ddea",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 34,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-04T09:12:34.459172+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-oauth2-client@5.8.16-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-oauth2-client@5.8.16-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-10-20T10:05:00.136501+00:00",
      "status_notes": "Vulnerability CVE-2007-1651 is a false positive for org.springframework.security:spring-security-oauth2-client 5.8.16-tuxcare.6. direct vulnerability is in OpenID project",
      "vulnerability": {
        "name": "CVE-2007-1651"
      },
      "impact_statement": "direct vulnerability is in OpenID project"
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-oauth2-client@5.8.16-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-oauth2-client@5.8.16-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2007-1652 is a false positive for org.springframework.security:spring-security-oauth2-client 5.8.16-tuxcare.6. CVE-2007-1652 is a vulnerability in JanRain's myOpenID service, on the OpenID Provider side. The CVE record carries vendor and product \\\"n/a\\\" and a single version-unbounded CPE, cpe:2.3:a:openid:openid:*, and every reference points to JanRain's myOpenID security announcement of March 2007 and the openid.net security mailing list threads of the same month. The reported mechanism - a crafted web page that forcibly logs a user into an OpenID-enabled site, releases the user's personal information to it, and silently adds it to the user's trusted-sites list by way of a cached authentication token - consists entirely of decisions taken by an OpenID Provider. A relying party has no trusted-sites list and no auto-approval step at which the flaw could occur. The openid module of this library implements only the relying-party (consumer) role: OpenIDAuthenticationFilter drives the two-leg consumer flow and OpenID4JavaConsumer wraps openid4java's ConsumerManager. The tree contains no OpenID Provider implementation - no use of openid4java's server package or ServerManager - and no trusted-sites or auto-approval handling anywhere. Nor could this library have been affected when the issue was disclosed: the CVE was published on 24 March 2007, while the earliest OpenID code in the project dates from 20 April 2007 and only reached the shipped openid module in January 2008. The vulnerability therefore does not apply to this library in any version.",
      "vulnerability": {
        "name": "CVE-2007-1652"
      },
      "impact_statement": "CVE-2007-1652 is a vulnerability in JanRain's myOpenID service, on the OpenID Provider side. The CVE record carries vendor and product \\\"n/a\\\" and a single version-unbounded CPE, cpe:2.3:a:openid:openid:*, and every reference points to JanRain's myOpenID security announcement of March 2007 and the openid.net security mailing list threads of the same month. The reported mechanism - a crafted web page that forcibly logs a user into an OpenID-enabled site, releases the user's personal information to it, and silently adds it to the user's trusted-sites list by way of a cached authentication token - consists entirely of decisions taken by an OpenID Provider. A relying party has no trusted-sites list and no auto-approval step at which the flaw could occur. The openid module of this library implements only the relying-party (consumer) role: OpenIDAuthenticationFilter drives the two-leg consumer flow and OpenID4JavaConsumer wraps openid4java's ConsumerManager. The tree contains no OpenID Provider implementation - no use of openid4java's server package or ServerManager - and no trusted-sites or auto-approval handling anywhere. Nor could this library have been affected when the issue was disclosed: the CVE was published on 24 March 2007, while the earliest OpenID code in the project dates from 20 April 2007 and only reached the shipped openid module in January 2008. The vulnerability therefore does not apply to this library in any version."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-oauth2-client@5.8.16-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-oauth2-client@5.8.16-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T09:12:34.459172+00:00",
      "status_notes": "Vulnerability CVE-2021-22119 does not affect version 5.8.16-tuxcare.6 of org.springframework.security:spring-security-oauth2-client. CVE-2021-22119 describes a DoS vulnerability in Spring Security OAuth2 Client where multiple authorization requests could exhaust session storage. The fix limits session storage to one authorization request by default. The target version (5.8.16-tuxcare.16) includes the upstream Spring Security 5.8.16 release which already contains the fix in both Web (commit 35f5ebdbcf) and WebFlux (commit 700bda68b7) implementations. Both fixes were authored by upstream Spring Security developers and were already present in the upstream release before TuxCare onboarding. The vulnerable pattern (unbounded session storage via Map) is not present in the target; the defense (single request storage) is active by default.\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": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2021-22119"
      },
      "impact_statement": "CVE-2021-22119 describes a DoS vulnerability in Spring Security OAuth2 Client where multiple authorization requests could exhaust session storage. The fix limits session storage to one authorization request by default. The target version (5.8.16-tuxcare.16) includes the upstream Spring Security 5.8.16 release which already contains the fix in both Web (commit 35f5ebdbcf) and WebFlux (commit 700bda68b7) implementations. Both fixes were authored by upstream Spring Security developers and were already present in the upstream release before TuxCare onboarding. The vulnerable pattern (unbounded session storage via Map) is not present in the target; the defense (single request storage) is active by default.\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)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-oauth2-client@5.8.16-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-oauth2-client@5.8.16-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T09:04:11.456857+00:00",
      "status_notes": "Vulnerability CVE-2022-31690 does not affect version 5.8.16-tuxcare.6 of org.springframework.security:spring-security-oauth2-client. Target Spring Security 5.8.16 is not affected by CVE-2022-31690. The vulnerable scope-defaulting pattern was removed by upstream Spring Security fixes (commits 75004587a4 and fde26e003a) that shipped in the upstream 5.8.x series before TuxCare onboarded this version. All OAuth2 token response clients now preserve the Authorization Server's explicit scope response instead of defaulting empty scopes to requested scopes, eliminating the privilege escalation vulnerability.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.7.0, < 5.7.5; < 5.6.9), NVD (>= 5.6.0, < 5.6.9; >= 5.7.0, < 5.7.5), cve.org (>= 5.7, <= 5.7.4; >= 5.6, <= 5.6.8), Snyk (< 5.4.11; >= 5.6.0, < 5.6.9; >= 5.7.0, < 5.7.5).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2022-31690"
      },
      "impact_statement": "Target Spring Security 5.8.16 is not affected by CVE-2022-31690. The vulnerable scope-defaulting pattern was removed by upstream Spring Security fixes (commits 75004587a4 and fde26e003a) that shipped in the upstream 5.8.x series before TuxCare onboarded this version. All OAuth2 token response clients now preserve the Authorization Server's explicit scope response instead of defaulting empty scopes to requested scopes, eliminating the privilege escalation vulnerability.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.7.0, < 5.7.5; < 5.6.9), NVD (>= 5.6.0, < 5.6.9; >= 5.7.0, < 5.7.5), cve.org (>= 5.7, <= 5.7.4; >= 5.6, <= 5.6.8), Snyk (< 5.4.11; >= 5.6.0, < 5.6.9; >= 5.7.0, < 5.7.5)."
    }
  ]
}