Skip to content

Code injection via unsafe YAML loading

High severity GitHub Reviewed Published Dec 8, 2021 in awslabs/sockeye • Updated Oct 25, 2024

Package

pip sockeye (pip)

Affected versions

< 2.3.24

Patched versions

2.3.24

Description

Impact

Sockeye uses YAML to store model and data configurations on disk. Versions below 2.3.24 use unsafe YAML loading, which can be made to execute arbitrary code embedded in config files.

An attacker can add malicious code to the config file of a trained model and attempt to convince users to download and run it. If users run the model, the embedded code will run locally.

Patches

The issue is fixed in version 2.3.24 and above by #964.

For more information

If you have any questions or comments about this advisory:

Attribution

This vulnerability was reported by Masatoshi Yoshizawa of yamory Security Team.

References

@mjdenkowski mjdenkowski published to awslabs/sockeye Dec 8, 2021
Reviewed Dec 8, 2021
Published by the National Vulnerability Database Dec 8, 2021
Published to the GitHub Advisory Database Dec 9, 2021
Last updated Oct 25, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS score

0.186%
(57th percentile)

Weaknesses

CVE ID

CVE-2021-43811

GHSA ID

GHSA-ggmr-44cv-24pm

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.