{
  "@id": "urn:uuid:3ccb399f-e995-4a97-8ca6-b01ad7623022",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 8,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-04T09:04:11.456857+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.batch/spring-batch-core@4.3.8-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.batch/spring-batch-core@4.3.8-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-03T12:04:03.421384+00:00",
      "status_notes": "Vulnerability CVE-2019-3774 does not affect version 4.3.8-tuxcare.3 of org.springframework.batch:spring-batch-core. CVE-2019-3774 (XXE vulnerability in Spring Batch) is NOT present in this target. The upstream Spring Batch 4.3.8 release already included the XXE fix through Spring Framework's `StaxUtils.createDefensiveInputFactory()` method, which disables DTD processing and external entity resolution. This fix was introduced in commit 264243b73 (Sept 2020) authored by upstream maintainer mbenhassine@vmware.com, well before TuxCare's onboarding of version 4.3.8 in September 2026. The vulnerable pattern (unsafe XMLInputFactory usage allowing external entities) is not present in the target code.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 3.0.10.RELEASE; >= 4.0.0.RELEASE, < 4.0.2.RELEASE; >= 4.1.0.RELEASE, < 4.1.1.RELEASE), NVD (<= 3.0.9; >= 4.0.0, <= 4.0.1; = 4.1.0), cve.org (>= 4.0, < 4.0.1.RELEASE; >= 4.1, < 4.1.0.RELEASE; >= 3.0, < 3.0.9.RELEASE), Snyk (>= 4.1.0.RELEASE, < 4.1.1.RELEASE; >= 4.0.0.RELEASE, < 4.0.2.RELEASE; >= 3.0.9.RELEASE, < 3.0.10.RELEASE).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-3774"
      },
      "impact_statement": "CVE-2019-3774 (XXE vulnerability in Spring Batch) is NOT present in this target. The upstream Spring Batch 4.3.8 release already included the XXE fix through Spring Framework's `StaxUtils.createDefensiveInputFactory()` method, which disables DTD processing and external entity resolution. This fix was introduced in commit 264243b73 (Sept 2020) authored by upstream maintainer mbenhassine@vmware.com, well before TuxCare's onboarding of version 4.3.8 in September 2026. The vulnerable pattern (unsafe XMLInputFactory usage allowing external entities) is not present in the target code.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 3.0.10.RELEASE; >= 4.0.0.RELEASE, < 4.0.2.RELEASE; >= 4.1.0.RELEASE, < 4.1.1.RELEASE), NVD (<= 3.0.9; >= 4.0.0, <= 4.0.1; = 4.1.0), cve.org (>= 4.0, < 4.0.1.RELEASE; >= 4.1, < 4.1.0.RELEASE; >= 3.0, < 3.0.9.RELEASE), Snyk (>= 4.1.0.RELEASE, < 4.1.1.RELEASE; >= 4.0.0.RELEASE, < 4.0.2.RELEASE; >= 3.0.9.RELEASE, < 3.0.10.RELEASE)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.batch/spring-batch-core@4.3.8-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.batch/spring-batch-core@4.3.8-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-04T09:04:11.456857+00:00",
      "status_notes": "Vulnerability CVE-2020-5411 does not affect version 4.3.8-tuxcare.3 of org.springframework.batch:spring-batch-core. The target repository (Spring Batch 4.3.8-tuxcare.4) is not affected by CVE-2020-5411. The vulnerability (unrestricted Jackson deserialization allowing arbitrary code execution) was fixed in the upstream Spring Batch 4.3.8 release by commit 9a79b4572d0aa4bec38fe90957c850920b7f9cea (authored by mbenhassine@vmware.com on 2020-06-10). TuxCare onboarded Spring Batch 4.3.8 on 2026-09-07, which already included the complete fix: a custom TrustedTypeIdResolver that validates deserialized class types against a whitelist and rejects untrusted classes. The vulnerable pattern (enableDefaultTyping() without validation) is not present in the target.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 4.0.0, < 4.2.3), NVD (>= 4.0.0, <= 4.0.4; >= 4.1.0, <= 4.1.4; >= 4.2.0, <= 4.2.2), cve.org (>= 4, < 4.2.3), Snyk (>= 4.0.0.RELEASE, < 4.2.3.RELEASE).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2020-5411"
      },
      "impact_statement": "The target repository (Spring Batch 4.3.8-tuxcare.4) is not affected by CVE-2020-5411. The vulnerability (unrestricted Jackson deserialization allowing arbitrary code execution) was fixed in the upstream Spring Batch 4.3.8 release by commit 9a79b4572d0aa4bec38fe90957c850920b7f9cea (authored by mbenhassine@vmware.com on 2020-06-10). TuxCare onboarded Spring Batch 4.3.8 on 2026-09-07, which already included the complete fix: a custom TrustedTypeIdResolver that validates deserialized class types against a whitelist and rejects untrusted classes. The vulnerable pattern (enableDefaultTyping() without validation) is not present in the target.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 4.0.0, < 4.2.3), NVD (>= 4.0.0, <= 4.0.4; >= 4.1.0, <= 4.1.4; >= 4.2.0, <= 4.2.2), cve.org (>= 4, < 4.2.3), Snyk (>= 4.0.0.RELEASE, < 4.2.3.RELEASE)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.batch/spring-batch-core@4.3.8-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.batch/spring-batch-core@4.3.8-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-10-29T15:30:49.741847+00:00",
      "status_notes": "Vulnerability CVE-2026-47875 does not affect version 4.3.8-tuxcare.3 of org.springframework.batch:spring-batch-core. not_affected \u2014 Spring Batch 4.3.8 is NOT AFFECTED by CVE-2026-47875. The vulnerability affects JobParameterDeserializer's use of Class.forName() to support arbitrary/custom types, a feature introduced in Spring Batch 5.0.0-M7 (Sept 2022, commit 2660f2bb). Version 4.3.8 only supports 4 built-in JobParameter types (String, Long, Date, Double) via a switch statement and never calls Class.forName() for job parame...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-47875"
      },
      "impact_statement": "not_affected \u2014 Spring Batch 4.3.8 is NOT AFFECTED by CVE-2026-47875. The vulnerability affects JobParameterDeserializer's use of Class.forName() to support arbitrary/custom types, a feature introduced in Spring Batch 5.0.0-M7 (Sept 2022, commit 2660f2bb). Version 4.3.8 only supports 4 built-in JobParameter types (String, Long, Date, Double) via a switch statement and never calls Class.forName() for job parame..."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.batch/spring-batch-core@4.3.8-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.batch/spring-batch-core@4.3.8-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-10-21T15:35:29.868749+00:00",
      "status_notes": "Vulnerability CVE-2026-47878 is fixed in version 4.3.8-tuxcare.3 of org.springframework.batch:spring-batch-core.",
      "vulnerability": {
        "name": "CVE-2026-47878"
      }
    }
  ]
}