{
  "@id": "urn:uuid:14fe11b6-26f5-4ea4-8313-2b84dd50dc23",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 2,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-03T17:55:03.264677+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.yaml/snakeyaml@2.3-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.yaml/snakeyaml@2.3-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T17:54:50.124770+00:00",
      "status_notes": "Vulnerability CVE-2017-18640 does not affect version 2.3-tuxcare.1 of org.yaml:snakeyaml. SnakeYAML 2.3 is NOT affected by CVE-2017-18640 (billion laughs attack via alias expansion). The vulnerability was fixed in upstream commit da11ddbd by Colm O hEigeartaigh on 2020-02-24, which added maxAliasesForCollections limit (default 50) to prevent exponential alias expansion. This fix was already present in the upstream SnakeYAML 2.3 release that TuxCare onboarded (commit 31031629), 504 commits after the fix. All defense components are present and active by default in the target: LoaderOptions defines the limit, Composer enforces it during parsing, and BaseConstructor prevents recursive keys.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 1.26), NVD (< 1.26), Snyk (< 1.26).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2017-18640"
      },
      "impact_statement": "SnakeYAML 2.3 is NOT affected by CVE-2017-18640 (billion laughs attack via alias expansion). The vulnerability was fixed in upstream commit da11ddbd by Colm O hEigeartaigh on 2020-02-24, which added maxAliasesForCollections limit (default 50) to prevent exponential alias expansion. This fix was already present in the upstream SnakeYAML 2.3 release that TuxCare onboarded (commit 31031629), 504 commits after the fix. All defense components are present and active by default in the target: LoaderOptions defines the limit, Composer enforces it during parsing, and BaseConstructor prevents recursive keys.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 1.26), NVD (< 1.26), Snyk (< 1.26)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.yaml/snakeyaml@2.3-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.yaml/snakeyaml@2.3-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T17:54:50.124770+00:00",
      "status_notes": "Vulnerability CVE-2022-1471 does not affect version 2.3-tuxcare.1 of org.yaml:snakeyaml. CVE-2022-1471 fix already present in upstream version 2.3. The upstream vendor (Andrey Somov) introduced TagInspector defense mechanism on Dec 25-30, 2022, setting UnTrustedTagInspector as the default in LoaderOptions. This blocks all custom global type tags (like !!javax.script.ScriptEngineManager) at parse time, preventing arbitrary class instantiation. TuxCare onboarded the already-fixed upstream version 2.3 on Aug 31, 2024 (commit 31031629). The defense is enforced in Composer.java at lines 238, 265, 309, throwing ComposerException before deserialization occurs. Constructor class now requires LoaderOptions in all constructors, eliminating legacy unsafe APIs.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 2.0), NVD (< 2.0), cve.org (<= 2.0), Snyk (>= 0, < 2.0).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2022-1471"
      },
      "impact_statement": "CVE-2022-1471 fix already present in upstream version 2.3. The upstream vendor (Andrey Somov) introduced TagInspector defense mechanism on Dec 25-30, 2022, setting UnTrustedTagInspector as the default in LoaderOptions. This blocks all custom global type tags (like !!javax.script.ScriptEngineManager) at parse time, preventing arbitrary class instantiation. TuxCare onboarded the already-fixed upstream version 2.3 on Aug 31, 2024 (commit 31031629). The defense is enforced in Composer.java at lines 238, 265, 309, throwing ComposerException before deserialization occurs. Constructor class now requires LoaderOptions in all constructors, eliminating legacy unsafe APIs.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 2.0), NVD (< 2.0), cve.org (<= 2.0), Snyk (>= 0, < 2.0)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.yaml/snakeyaml@2.3-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.yaml/snakeyaml@2.3-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T17:54:50.124770+00:00",
      "status_notes": "Vulnerability CVE-2022-25857 does not affect version 2.3-tuxcare.1 of org.yaml:snakeyaml. Target repository snakeyaml version 2.3 is NOT affected by CVE-2022-25857. The vulnerability (missing nested depth limitation for collections causing DoS) was fixed in upstream SnakeYAML version 1.31 (April 2022) by commit fc300780. Version 2.3 (released 2024) already contains this upstream fix. The defense mechanism is fully present and enabled by default: LoaderOptions.java sets nestingDepthLimit=50 by default, and Composer.java enforces this limit by throwing YAMLException when exceeded. This is an upstream vendor fix, not a TuxCare backport.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 1.31), NVD (< 1.31), cve.org (< 1.31), Snyk (>= 0, < 1.31).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2022-25857"
      },
      "impact_statement": "Target repository snakeyaml version 2.3 is NOT affected by CVE-2022-25857. The vulnerability (missing nested depth limitation for collections causing DoS) was fixed in upstream SnakeYAML version 1.31 (April 2022) by commit fc300780. Version 2.3 (released 2024) already contains this upstream fix. The defense mechanism is fully present and enabled by default: LoaderOptions.java sets nestingDepthLimit=50 by default, and Composer.java enforces this limit by throwing YAMLException when exceeded. This is an upstream vendor fix, not a TuxCare backport.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 1.31), NVD (< 1.31), cve.org (< 1.31), Snyk (>= 0, < 1.31)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.yaml/snakeyaml@2.3-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.yaml/snakeyaml@2.3-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T17:54:50.124770+00:00",
      "status_notes": "Vulnerability CVE-2022-38749 does not affect version 2.3-tuxcare.1 of org.yaml:snakeyaml. not_affected \u2014 The target repository (snakeyaml 2.3) is NOT AFFECTED by CVE-2022-38749. The nesting depth limiting defense that prevents stack overflow from deeply nested YAML collections is already present in the codebase. The fix was introduced by upstream commit fc300780 (authored by Andrey Somov on 2022-04-28) and was included in the upstream snakeyaml 2.3 release that TuxCare onboarded on 2026-09-07. Sin...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2022-38749"
      },
      "impact_statement": "not_affected \u2014 The target repository (snakeyaml 2.3) is NOT AFFECTED by CVE-2022-38749. The nesting depth limiting defense that prevents stack overflow from deeply nested YAML collections is already present in the codebase. The fix was introduced by upstream commit fc300780 (authored by Andrey Somov on 2022-04-28) and was included in the upstream snakeyaml 2.3 release that TuxCare onboarded on 2026-09-07. Sin..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.yaml/snakeyaml@2.3-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.yaml/snakeyaml@2.3-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T17:54:50.124770+00:00",
      "status_notes": "Vulnerability CVE-2022-38750 does not affect version 2.3-tuxcare.1 of org.yaml:snakeyaml. not_affected \u2014 CVE-2022-38750 addresses stack overflow DOS attacks from deeply nested YAML collections. The fix (nesting depth limit with default max of 50) is present in the target repository at version 2.3. The vulnerability pattern is not present because the upstream fix was included in SnakeYAML release 2.3, which TuxCare onboarded. The fix was authored by upstream maintainer Andrey Somov (commit fc300780...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2022-38750"
      },
      "impact_statement": "not_affected \u2014 CVE-2022-38750 addresses stack overflow DOS attacks from deeply nested YAML collections. The fix (nesting depth limit with default max of 50) is present in the target repository at version 2.3. The vulnerability pattern is not present because the upstream fix was included in SnakeYAML release 2.3, which TuxCare onboarded. The fix was authored by upstream maintainer Andrey Somov (commit fc300780..."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.yaml/snakeyaml@2.3-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.yaml/snakeyaml@2.3-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T17:55:03.264677+00:00",
      "status_notes": "Vulnerability CVE-2022-38751 is fixed in version 2.3-tuxcare.1 of org.yaml:snakeyaml.",
      "vulnerability": {
        "name": "CVE-2022-38751"
      }
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.yaml/snakeyaml@2.3-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.yaml/snakeyaml@2.3-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T17:54:50.124770+00:00",
      "status_notes": "Vulnerability CVE-2022-38752 does not affect version 2.3-tuxcare.1 of org.yaml:snakeyaml. not_affected \u2014 Target version 2.3 is not affected by CVE-2022-38752. The upstream fix (commit 5056a448f09c46250346c338e821386caa751182 by Andrey Somov, May 31, 2022) was already present in the upstream release before TuxCare onboarded version 2.3 on September 7, 2026. The fix prevents stack overflow from recursive YAML anchors used as mapping keys by detecting them via isTwoStepsConstruction() and throwing YA...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2022-38752"
      },
      "impact_statement": "not_affected \u2014 Target version 2.3 is not affected by CVE-2022-38752. The upstream fix (commit 5056a448f09c46250346c338e821386caa751182 by Andrey Somov, May 31, 2022) was already present in the upstream release before TuxCare onboarded version 2.3 on September 7, 2026. The fix prevents stack overflow from recursive YAML anchors used as mapping keys by detecting them via isTwoStepsConstruction() and throwing YA..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.yaml/snakeyaml@2.3-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.yaml/snakeyaml@2.3-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T17:54:50.124770+00:00",
      "status_notes": "Vulnerability CVE-2022-41854 does not affect version 2.3-tuxcare.1 of org.yaml:snakeyaml. not_affected \u2014 CVE-2022-41854 is NOT present in SnakeYAML 2.3. The vulnerability (stack overflow DoS from unbounded YAML input) was fixed in upstream version 2.3 before TuxCare onboarded it. Two defenses are present: (1) code point limit (3 MB default) at ScannerImpl.java:315-318 blocking excessive input size, and (2) nesting depth limit (50 levels default) at Composer.java:403-404 preventing stack overflow f...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2022-41854"
      },
      "impact_statement": "not_affected \u2014 CVE-2022-41854 is NOT present in SnakeYAML 2.3. The vulnerability (stack overflow DoS from unbounded YAML input) was fixed in upstream version 2.3 before TuxCare onboarded it. Two defenses are present: (1) code point limit (3 MB default) at ScannerImpl.java:315-318 blocking excessive input size, and (2) nesting depth limit (50 levels default) at Composer.java:403-404 preventing stack overflow f..."
    }
  ]
}
