{
  "@id": "urn:uuid:f57ad99d-0655-419e-9de1-a14a4f4df143",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 9,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-04T09:02:00.202619+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/ch.qos.logback/logback-classic@1.2.13.tuxcare",
          "identifiers": {
            "purl": "pkg:maven/ch.qos.logback/logback-classic@1.2.13.tuxcare"
          }
        }
      ],
      "timestamp": "2026-11-04T09:02:00.202619+00:00",
      "status_notes": "Vulnerability CVE-2017-5929 does not affect version 1.2.13.tuxcare of ch.qos.logback:logback-classic. CVE-2017-5929 deserialization vulnerability is NOT present in logback 1.2.13. The fix (HardenedObjectInputStream with class whitelisting) was introduced in upstream release 1.2.0 by ceki@qos.ch and is present in the target. All vulnerable deserialization entry points (SocketNode in logback-classic and logback-access, RemoteAppenderStreamClient) use hardened streams instead of plain ObjectInputStream. No plain ObjectInputStream usage remains in production code.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 1.2.0; < 1.2.0), NVD (< 1.2.0), Snyk (>= 0.3, < 1.2.0; >= 0.6, < 1.2.0; < 1.1.11).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2017-5929"
      },
      "impact_statement": "CVE-2017-5929 deserialization vulnerability is NOT present in logback 1.2.13. The fix (HardenedObjectInputStream with class whitelisting) was introduced in upstream release 1.2.0 by ceki@qos.ch and is present in the target. All vulnerable deserialization entry points (SocketNode in logback-classic and logback-access, RemoteAppenderStreamClient) use hardened streams instead of plain ObjectInputStream. No plain ObjectInputStream usage remains in production code.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 1.2.0; < 1.2.0), NVD (< 1.2.0), Snyk (>= 0.3, < 1.2.0; >= 0.6, < 1.2.0; < 1.1.11)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/ch.qos.logback/logback-classic@1.2.13.tuxcare",
          "identifiers": {
            "purl": "pkg:maven/ch.qos.logback/logback-classic@1.2.13.tuxcare"
          }
        }
      ],
      "timestamp": "2026-11-03T11:58:00.062525+00:00",
      "status_notes": "Vulnerability CVE-2023-6378 does not affect version 1.2.13.tuxcare of ch.qos.logback:logback-classic. CVE-2023-6378 is not present in target version 1.2.13. The upstream fix commit bb095154be011267b64e37a1d401546e7cc2b7c3 (authored by ceki@qos.ch) was already included in the upstream release before TuxCare onboarding. Both defense mechanisms are present: (1) LoggingEventVO.readObject() validates array lengths before allocation, rejecting negative or oversized values, and (2) HardenedObjectInputStream installs JVM-level deserialization filters limiting array size (10000) and object graph depth (16). The vulnerable pattern (unbounded array allocation during deserialization) has been removed.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 1.3.0, < 1.3.12; >= 1.4.0, < 1.4.12; >= 1.3.0, < 1.3.12; >= 1.4.0, < 1.4.12; < 1.2.13; < 1.2.13), NVD (>= 1.2.0, < 1.2.13; >= 1.3.0, < 1.3.12; >= 1.4.0, < 1.4.12), Snyk (< 1.2.13; >= 1.3.0-alpha0, < 1.3.12; >= 1.4.0, < 1.4.12; < 1.2.13; >= 1.3.0-alpha0, < 1.3.12; >= 1.4.0, < 1.4.12).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2023-6378"
      },
      "impact_statement": "CVE-2023-6378 is not present in target version 1.2.13. The upstream fix commit bb095154be011267b64e37a1d401546e7cc2b7c3 (authored by ceki@qos.ch) was already included in the upstream release before TuxCare onboarding. Both defense mechanisms are present: (1) LoggingEventVO.readObject() validates array lengths before allocation, rejecting negative or oversized values, and (2) HardenedObjectInputStream installs JVM-level deserialization filters limiting array size (10000) and object graph depth (16). The vulnerable pattern (unbounded array allocation during deserialization) has been removed.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 1.3.0, < 1.3.12; >= 1.4.0, < 1.4.12; >= 1.3.0, < 1.3.12; >= 1.4.0, < 1.4.12; < 1.2.13; < 1.2.13), NVD (>= 1.2.0, < 1.2.13; >= 1.3.0, < 1.3.12; >= 1.4.0, < 1.4.12), Snyk (< 1.2.13; >= 1.3.0-alpha0, < 1.3.12; >= 1.4.0, < 1.4.12; < 1.2.13; >= 1.3.0-alpha0, < 1.3.12; >= 1.4.0, < 1.4.12)."
    }
  ]
}