{
  "@id": "urn:uuid:3d6a680a-9e9d-4595-9056-e778eb3f46c7",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 8,
  "@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@3.4.13-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.data/spring-data-jpa@3.4.13-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-02T18:33:00.198409+00:00",
      "status_notes": "Vulnerability CVE-2016-6652 does not affect version 3.4.13-tuxcare.4 of org.springframework.data:spring-data-jpa. not_affected \u2014 The target repository (spring-data-jpa 3.4.13-tuxcare.6) is NOT affected by CVE-2016-6652. The vulnerability fix was already present in the upstream Spring Data JPA 3.4.13 release that TuxCare onboarded. The fix commit (b8e7fecccc7dc8edcabb4704656a7abe6352c08f) was authored by Christoph Strobl (cstrobl@pivotal.io) on 2016-09-06, nearly 10 years before TuxCare onboarded this version on 2026-07-1...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2016-6652"
      },
      "impact_statement": "not_affected \u2014 The target repository (spring-data-jpa 3.4.13-tuxcare.6) is NOT affected by CVE-2016-6652. The vulnerability fix was already present in the upstream Spring Data JPA 3.4.13 release that TuxCare onboarded. The fix commit (b8e7fecccc7dc8edcabb4704656a7abe6352c08f) was authored by Christoph Strobl (cstrobl@pivotal.io) on 2016-09-06, nearly 10 years before TuxCare onboarded this version on 2026-07-1..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.data/spring-data-jpa@3.4.13-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.data/spring-data-jpa@3.4.13-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-02T03:15:00.599057+00:00",
      "status_notes": "Vulnerability CVE-2019-3797 does not affect version 3.4.13-tuxcare.4 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 due to missing SQL LIKE wildcard escaping in derived queries. The target version 3.4.13-tuxcare.6 is not affected because the upstream fix (DATAJPA-1519 and DATAJPA-1522) was already present in the upstream Spring Data JPA 3.4.13 release that TuxCare onboarded. The EscapeCharacter class with complete wildcard escapi...",
      "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 due to missing SQL LIKE wildcard escaping in derived queries. The target version 3.4.13-tuxcare.6 is not affected because the upstream fix (DATAJPA-1519 and DATAJPA-1522) was already present in the upstream Spring Data JPA 3.4.13 release that TuxCare onboarded. The EscapeCharacter class with complete wildcard escapi..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.data/spring-data-jpa@3.4.13-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.data/spring-data-jpa@3.4.13-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-02T02:37:37.853216+00:00",
      "status_notes": "Vulnerability CVE-2019-3802 does not affect version 3.4.13-tuxcare.4 of org.springframework.data:spring-data-jpa. not_affected \u2014 CVE-2019-3802 is NOT present in spring-data-jpa 3.4.13-tuxcare.6. The vulnerability involved missing wildcard escaping in ExampleMatcher LIKE queries (STARTING, ENDING, CONTAINING), allowing malicious input containing SQL wildcards (%, _) to match more database records than intended. The upstream fix (commits 075b4bad6, d15f5efc5, and related) added escaping via EscapeCharacter.escape() and was...",
      "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.4.13-tuxcare.6. The vulnerability involved missing wildcard escaping in ExampleMatcher LIKE queries (STARTING, ENDING, CONTAINING), allowing malicious input containing SQL wildcards (%, _) to match more database records than intended. The upstream fix (commits 075b4bad6, d15f5efc5, and related) added escaping via EscapeCharacter.escape() and was..."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.data/spring-data-jpa@3.4.13-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.data/spring-data-jpa@3.4.13-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-10-15T10:58:32.977310+00:00",
      "status_notes": "Vulnerability CVE-2026-47834 is fixed in version 3.4.13-tuxcare.4 of org.springframework.data:spring-data-jpa.",
      "vulnerability": {
        "name": "CVE-2026-47834"
      }
    }
  ]
}