{
  "@id": "urn:uuid:62e56d74-73fa-4dae-b74c-3b64ee0c2bb0",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 6,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-02T18:33:00.198409+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.data/spring-data-jpa@2.1.10.RELEASE-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.data/spring-data-jpa@2.1.10.RELEASE-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-02T18:33:00.198409+00:00",
      "status_notes": "Vulnerability CVE-2016-6652 does not affect version 2.1.10.RELEASE-tuxcare.1 of org.springframework.data:spring-data-jpa. not_affected \u2014 The target (spring-data-jpa 2.1.10.RELEASE-tuxcare.1) is not affected by CVE-2016-6652. The SQL injection vulnerability in Sort parameter handling was fixed by upstream Spring developers in September 2016 (commit b8e7feccc), approximately 3 years before version 2.1.10 was released in August 2019. The complete fix\u2014including input validation via checkSortExpression(), the PUNCTATION_PATTERN regex...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2016-6652"
      },
      "impact_statement": "not_affected \u2014 The target (spring-data-jpa 2.1.10.RELEASE-tuxcare.1) is not affected by CVE-2016-6652. The SQL injection vulnerability in Sort parameter handling was fixed by upstream Spring developers in September 2016 (commit b8e7feccc), approximately 3 years before version 2.1.10 was released in August 2019. The complete fix\u2014including input validation via checkSortExpression(), the PUNCTATION_PATTERN regex..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.data/spring-data-jpa@2.1.10.RELEASE-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.data/spring-data-jpa@2.1.10.RELEASE-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-02T03:14:00.140970+00:00",
      "status_notes": "Vulnerability CVE-2019-3797 does not affect version 2.1.10.RELEASE-tuxcare.1 of org.springframework.data:spring-data-jpa. not_affected \u2014 The target Spring Data JPA 2.1.10.RELEASE-tuxcare.1 is NOT affected by CVE-2019-3797. The vulnerability (missing wildcard escaping in LIKE queries) was fixed in the upstream Spring Data JPA 2.1.6.RELEASE (April 2019) via commits DATAJPA-1519, DATAJPA-1522, and DATAJPA-1534. The target version 2.1.10.RELEASE already contains these fixes from the upstream release that TuxCare onboarded. All three...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-3797"
      },
      "impact_statement": "not_affected \u2014 The target Spring Data JPA 2.1.10.RELEASE-tuxcare.1 is NOT affected by CVE-2019-3797. The vulnerability (missing wildcard escaping in LIKE queries) was fixed in the upstream Spring Data JPA 2.1.6.RELEASE (April 2019) via commits DATAJPA-1519, DATAJPA-1522, and DATAJPA-1534. The target version 2.1.10.RELEASE already contains these fixes from the upstream release that TuxCare onboarded. All three..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.data/spring-data-jpa@2.1.10.RELEASE-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.data/spring-data-jpa@2.1.10.RELEASE-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-02T02:39:19.995282+00:00",
      "status_notes": "Vulnerability CVE-2019-3802 does not affect version 2.1.10.RELEASE-tuxcare.1 of org.springframework.data:spring-data-jpa. not_affected \u2014 The target spring-data-jpa version 2.1.10.RELEASE-tuxcare.1 is NOT AFFECTED by CVE-2019-3802. The vulnerability (SQL LIKE wildcard injection in ExampleMatcher with STARTING/ENDING/CONTAINING string matchers) was fixed by the upstream vendor (Spring/Pivotal) in commits DATAJPA-1534 and DATAJPA-1522, which were already present in the upstream 2.1.10.RELEASE that TuxCare onboarded. The fix escapes...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-3802"
      },
      "impact_statement": "not_affected \u2014 The target spring-data-jpa version 2.1.10.RELEASE-tuxcare.1 is NOT AFFECTED by CVE-2019-3802. The vulnerability (SQL LIKE wildcard injection in ExampleMatcher with STARTING/ENDING/CONTAINING string matchers) was fixed by the upstream vendor (Spring/Pivotal) in commits DATAJPA-1534 and DATAJPA-1522, which were already present in the upstream 2.1.10.RELEASE that TuxCare onboarded. The fix escapes..."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.data/spring-data-jpa@2.1.10.RELEASE-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.data/spring-data-jpa@2.1.10.RELEASE-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-28T18:40:55.741562+00:00",
      "status_notes": "Vulnerability CVE-2026-47834 affects version 2.1.10.RELEASE-tuxcare.1 of org.springframework.data:spring-data-jpa.",
      "vulnerability": {
        "name": "CVE-2026-47834"
      },
      "action_statement": "Vulnerability CVE-2026-47834 affects version 2.1.10.RELEASE-tuxcare.1 of org.springframework.data:spring-data-jpa."
    }
  ]
}