{
  "@id": "urn:uuid:17457002-a75a-439e-9acd-35603e3e0871",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 8,
  "@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.4.14-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/ch.qos.logback/logback-classic@1.4.14-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-04T09:03:00.104314+00:00",
      "status_notes": "Vulnerability CVE-2017-5929 does not affect version 1.4.14-tuxcare.1 of ch.qos.logback:logback-classic. CVE-2017-5929 is NOT affecting this target. The vulnerability involves unsafe Java deserialization via ObjectInputStream in SocketNode and related classes, allowing arbitrary code execution. The upstream fix (commit f46044b80 by ceki@qos.ch) was already present in Logback 1.4.14 when TuxCare onboarded it. The fix replaces plain ObjectInputStream with HardenedObjectInputStream, which implements class whitelisting via resolveClass() override and blocks proxy-based bypasses. All network deserialization entry points (SocketNode in logback-classic and logback-access, RemoteAppenderStreamClient) use the hardened streams. The vulnerable pattern (unfiltered deserialization) is not present in the target.\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 affecting this target. The vulnerability involves unsafe Java deserialization via ObjectInputStream in SocketNode and related classes, allowing arbitrary code execution. The upstream fix (commit f46044b80 by ceki@qos.ch) was already present in Logback 1.4.14 when TuxCare onboarded it. The fix replaces plain ObjectInputStream with HardenedObjectInputStream, which implements class whitelisting via resolveClass() override and blocks proxy-based bypasses. All network deserialization entry points (SocketNode in logback-classic and logback-access, RemoteAppenderStreamClient) use the hardened streams. The vulnerable pattern (unfiltered deserialization) is not present in the target.\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.4.14-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/ch.qos.logback/logback-classic@1.4.14-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T11:59:19.723998+00:00",
      "status_notes": "Vulnerability CVE-2023-6378 does not affect version 1.4.14-tuxcare.1 of ch.qos.logback:logback-classic. The target repository logback version 1.4.14-tuxcare.2 is NOT AFFECTED by CVE-2023-6378. The serialization DoS vulnerability was fixed by upstream commit 9c782b45be4abdafb7e17481e24e7354c2acd1eb authored by Ceki Gulcu (ceki@qos.ch), which was already included in the upstream 1.4.14 release before TuxCare onboarded it. Both LoggingEventVO.java and HardenedObjectInputStream.java contain the complete mitigations at HEAD.\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": "The target repository logback version 1.4.14-tuxcare.2 is NOT AFFECTED by CVE-2023-6378. The serialization DoS vulnerability was fixed by upstream commit 9c782b45be4abdafb7e17481e24e7354c2acd1eb authored by Ceki Gulcu (ceki@qos.ch), which was already included in the upstream 1.4.14 release before TuxCare onboarded it. Both LoggingEventVO.java and HardenedObjectInputStream.java contain the complete mitigations at HEAD.\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)."
    }
  ]
}
