GHSA-6H2X-4GJF-JC5W

Vulnerability from github – Published: 2022-09-21 21:42 – Updated: 2022-09-21 21:42
VLAI
Summary
autogluon.multimodal vulnerable to unsafe YAML deserialization
Details

Impact

A potential unsafe deserialization issue exists within the autogluon.multimodal module, where YAML files are loaded via yaml.load() instead of yaml.safe_load(). The deserialization of untrusted data may allow an unprivileged third party to cause remote code execution, denial of service, and impact to both confidentiality and integrity.

Impacted versions: >=0.4.0;<0.4.3, >=0.5.0;<0.5.2.

Patches

The patches are included in autogluon.multimodal==0.4.3, autogluon.multimodal==0.5.2 and Deep Learning Containers 0.4.3 and 0.5.2.

Workarounds

Do not load data which originated from an untrusted source, or that could have been tampered with. Only load data you trust.

References

  • https://cwe.mitre.org/data/definitions/502.html
  • https://www.cvedetails.com/cve/CVE-2017-18342/
Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "autogluon.multimodal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.4.0"
            },
            {
              "fixed": "0.4.3"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "autogluon.multimodal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.5.0"
            },
            {
              "fixed": "0.5.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [],
  "database_specific": {
    "cwe_ids": [
      "CWE-502"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2022-09-21T21:42:05Z",
    "nvd_published_at": null,
    "severity": "HIGH"
  },
  "details": "### Impact\n\nA potential unsafe deserialization issue exists within the `autogluon.multimodal` module, where YAML files are loaded via `yaml.load()` instead of `yaml.safe_load()`. The deserialization of untrusted data may allow an unprivileged third party to cause remote code execution, denial of service, and impact to both confidentiality and integrity.\n\nImpacted versions: `\u003e=0.4.0;\u003c0.4.3`, `\u003e=0.5.0;\u003c0.5.2`.\n\n### Patches\nThe patches are included in `autogluon.multimodal==0.4.3`, `autogluon.multimodal==0.5.2` and Deep Learning Containers `0.4.3` and `0.5.2`.\n\n### Workarounds\nDo not load data which originated from an untrusted source, or that could have been tampered with. **Only load data you trust.**\n\n### References\n* https://cwe.mitre.org/data/definitions/502.html\n* https://www.cvedetails.com/cve/CVE-2017-18342/\n",
  "id": "GHSA-6h2x-4gjf-jc5w",
  "modified": "2022-09-21T21:42:05Z",
  "published": "2022-09-21T21:42:05Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/awslabs/autogluon/security/advisories/GHSA-6h2x-4gjf-jc5w"
    },
    {
      "type": "WEB",
      "url": "https://github.com/awslabs/autogluon/pull/1987"
    },
    {
      "type": "WEB",
      "url": "https://github.com/awslabs/autogluon/commit/23a37e74e58d03055c84a1b89c5af6c3db296b5e"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/awslabs/autogluon"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [],
  "summary": "autogluon.multimodal vulnerable to unsafe YAML deserialization"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…