{
  "@id": "urn:uuid:93ea62e5-43e0-4db6-a2f6-5c46493db6cf",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 9,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-04T09:03:00.104314+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/ch.qos.logback/logback-classic@1.5.18-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/ch.qos.logback/logback-classic@1.5.18-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-04T09:03:00.104314+00:00",
      "status_notes": "Vulnerability CVE-2017-5929 does not affect version 1.5.18-tuxcare.2 of ch.qos.logback:logback-classic. CVE-2017-5929 is NOT present in logback 1.5.18-tuxcare.2. The vulnerability (unsafe Java deserialization in SocketNode and RemoteAppenderStreamClient) was fixed by upstream vendor (Ceki Gulcu, ceki@qos.ch) in commits leading to logback 1.2.0. The target version 1.5.18 already contains the complete fix: all socket deserialization entry points use HardenedLoggingEventInputStream/HardenedObjectInputStream with whitelist-based class validation. The fix was part of the upstream 1.5.18 release that TuxCare onboarded (commit 2df59eed, 992 commits after the fix). No TuxCare backport was needed for this version.\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 is NOT present in logback 1.5.18-tuxcare.2. The vulnerability (unsafe Java deserialization in SocketNode and RemoteAppenderStreamClient) was fixed by upstream vendor (Ceki Gulcu, ceki@qos.ch) in commits leading to logback 1.2.0. The target version 1.5.18 already contains the complete fix: all socket deserialization entry points use HardenedLoggingEventInputStream/HardenedObjectInputStream with whitelist-based class validation. The fix was part of the upstream 1.5.18 release that TuxCare onboarded (commit 2df59eed, 992 commits after the fix). No TuxCare backport was needed for this version.\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.5.18-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/ch.qos.logback/logback-classic@1.5.18-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T11:58:46.516698+00:00",
      "status_notes": "Vulnerability CVE-2023-6378 does not affect version 1.5.18-tuxcare.2 of ch.qos.logback:logback-classic. CVE-2023-6378 is not present in logback 1.5.18-tuxcare.2. The vulnerability affects the logback receiver component's deserialization of malicious data causing DoS via resource exhaustion. The upstream vendor (Ceki Gulcu) fixed this in commit 9c782b45b by adding two defense layers: (1) ObjectInputFilter with maxdepth=16 and maxarray=10000 in HardenedObjectInputStream, and (2) array length validation (limit 128) in LoggingEventVO.readObject(). This fix shipped in upstream release v_1.5.18, which TuxCare onboarded via commit 2df59eed9. Both defense layers are present and active in HEAD at the receiver's entry point (RemoteAppenderStreamClient uses HardenedLoggingEventInputStream).\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 logback 1.5.18-tuxcare.2. The vulnerability affects the logback receiver component's deserialization of malicious data causing DoS via resource exhaustion. The upstream vendor (Ceki Gulcu) fixed this in commit 9c782b45b by adding two defense layers: (1) ObjectInputFilter with maxdepth=16 and maxarray=10000 in HardenedObjectInputStream, and (2) array length validation (limit 128) in LoggingEventVO.readObject(). This fix shipped in upstream release v_1.5.18, which TuxCare onboarded via commit 2df59eed9. Both defense layers are present and active in HEAD at the receiver's entry point (RemoteAppenderStreamClient uses HardenedLoggingEventInputStream).\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)."
    }
  ]
}
