{
  "@id": "urn:uuid:eb78ce27-5262-48d7-8348-fe68569f385f",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 6,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-02T18:32:00.321693+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.data/spring-data-jpa@3.5.12-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.data/spring-data-jpa@3.5.12-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-02T18:32:00.321693+00:00",
      "status_notes": "Vulnerability CVE-2016-6652 does not affect version 3.5.12-tuxcare.1 of org.springframework.data:spring-data-jpa. not_affected \u2014 CVE-2016-6652 (SQL injection via Sort function calls) is NOT present in Spring Data JPA 3.5.12-tuxcare.1. The fix (DATAJPA-965) was implemented by upstream Spring developers in September 2016 and is already present in the target. The defense mechanism validates Sort expressions via QueryUtils.checkSortExpression(), rejecting properties containing punctuation (functions/expressions) unless expli...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2016-6652"
      },
      "impact_statement": "not_affected \u2014 CVE-2016-6652 (SQL injection via Sort function calls) is NOT present in Spring Data JPA 3.5.12-tuxcare.1. The fix (DATAJPA-965) was implemented by upstream Spring developers in September 2016 and is already present in the target. The defense mechanism validates Sort expressions via QueryUtils.checkSortExpression(), rejecting properties containing punctuation (functions/expressions) unless expli..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.data/spring-data-jpa@3.5.12-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.data/spring-data-jpa@3.5.12-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-02T03:15:00.599057+00:00",
      "status_notes": "Vulnerability CVE-2019-3797 does not affect version 3.5.12-tuxcare.1 of org.springframework.data:spring-data-jpa. not_affected \u2014 CVE-2019-3797 affects Spring Data JPA versions up to 2.1.5, 2.0.13, and 1.11.19 where derived queries using startingWith/endingWith/containing predicates could return more results than intended due to unescaped SQL LIKE wildcards. The target version 3.5.12 is NOT AFFECTED because the upstream vendor (Pivotal/VMware) fixed this vulnerability in 2019 via commits DATAJPA-1519, DATAJPA-1522, and DA...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-3797"
      },
      "impact_statement": "not_affected \u2014 CVE-2019-3797 affects Spring Data JPA versions up to 2.1.5, 2.0.13, and 1.11.19 where derived queries using startingWith/endingWith/containing predicates could return more results than intended due to unescaped SQL LIKE wildcards. The target version 3.5.12 is NOT AFFECTED because the upstream vendor (Pivotal/VMware) fixed this vulnerability in 2019 via commits DATAJPA-1519, DATAJPA-1522, and DA..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.data/spring-data-jpa@3.5.12-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.data/spring-data-jpa@3.5.12-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-02T02:42:44.518665+00:00",
      "status_notes": "Vulnerability CVE-2019-3802 does not affect version 3.5.12-tuxcare.1 of org.springframework.data:spring-data-jpa. not_affected \u2014 CVE-2019-3802 is not present in Spring Data JPA 3.5.12. The vulnerability involved SQL wildcard injection in ExampleMatcher queries (STARTING/ENDING/CONTAINING string matchers) where user input was directly concatenated into LIKE patterns without escaping. The upstream vendor (Spring Data JPA team) fixed this in commit 075b4bad6 (DATAJPA-1534) by adding proper escaping of SQL wildcards (_, %, \\...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-3802"
      },
      "impact_statement": "not_affected \u2014 CVE-2019-3802 is not present in Spring Data JPA 3.5.12. The vulnerability involved SQL wildcard injection in ExampleMatcher queries (STARTING/ENDING/CONTAINING string matchers) where user input was directly concatenated into LIKE patterns without escaping. The upstream vendor (Spring Data JPA team) fixed this in commit 075b4bad6 (DATAJPA-1534) by adding proper escaping of SQL wildcards (_, %, \\..."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.data/spring-data-jpa@3.5.12-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.data/spring-data-jpa@3.5.12-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-28T17:36:45.476697+00:00",
      "status_notes": "Vulnerability CVE-2026-47834 affects version 3.5.12-tuxcare.1 of org.springframework.data:spring-data-jpa.",
      "vulnerability": {
        "name": "CVE-2026-47834"
      },
      "action_statement": "Vulnerability CVE-2026-47834 affects version 3.5.12-tuxcare.1 of org.springframework.data:spring-data-jpa."
    }
  ]
}