Skip to content
Fencer Intel
high —

GHSA-6h2x-4gjf-jc5w json

autogluon.multimodal vulnerable to unsafe YAML deserialization

published 4y ago modified last yr.

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### 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/

Patch / fix

  • pypi autogluon-multimodal 0.4.3, 0.5.2

Is GHSA-6h2x-4gjf-jc5w in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
pypi autogluon-multimodal
>=0.4.0, <0.4.3
>=0.5.0, <0.5.2
0.4.3
0.5.2

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.