{
  "@id": "urn:uuid:f68de2f5-6b60-4ed7-a4db-2a72b4490292",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 6,
  "@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/ch.qos.logback/logback-classic@1.4.11-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/ch.qos.logback/logback-classic@1.4.11-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-04T09:04:11.456857+00:00",
      "status_notes": "Vulnerability CVE-2017-5929 does not affect version 1.4.11-tuxcare.2 of ch.qos.logback:logback-classic. The target repository (Logback 1.4.11) is not vulnerable to CVE-2017-5929. The unsafe Java deserialization vulnerability was fixed in upstream Logback 1.2.0 (February 2017) by introducing HardenedObjectInputStream with whitelist-based class validation. This fix was already present in upstream version 1.4.11 when TuxCare onboarded it. Both SocketNode classes (logback-classic and logback-access) use the hardened stream implementations that validate incoming serialized objects against explicit whitelists, preventing arbitrary code execution via malicious deserialization. The fix commit f46044b805bca91efe5fd6afe52257cd02f775f8 was authored by upstream maintainer ceki@qos.ch, not TuxCare.\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": "The target repository (Logback 1.4.11) is not vulnerable to CVE-2017-5929. The unsafe Java deserialization vulnerability was fixed in upstream Logback 1.2.0 (February 2017) by introducing HardenedObjectInputStream with whitelist-based class validation. This fix was already present in upstream version 1.4.11 when TuxCare onboarded it. Both SocketNode classes (logback-classic and logback-access) use the hardened stream implementations that validate incoming serialized objects against explicit whitelists, preventing arbitrary code execution via malicious deserialization. The fix commit f46044b805bca91efe5fd6afe52257cd02f775f8 was authored by upstream maintainer ceki@qos.ch, not TuxCare.\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": "affected",
      "products": [
        {
          "@id": "pkg:maven/ch.qos.logback/logback-classic@1.4.11-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/ch.qos.logback/logback-classic@1.4.11-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-22T17:59:25.481992+00:00",
      "status_notes": "Vulnerability CVE-2023-6378 affects version 1.4.11-tuxcare.2 of ch.qos.logback:logback-classic.",
      "vulnerability": {
        "name": "CVE-2023-6378"
      },
      "action_statement": "Vulnerability CVE-2023-6378 affects version 1.4.11-tuxcare.2 of ch.qos.logback:logback-classic."
    }
  ]
}
