YAML Load Executes Arbitrary Code Compromising 470 Servers?!

YAML RCE APOCALYPSE! yaml.load() executes Python! Attacker uploads malicious config! Backdoor on all servers! 4.7M database exfiltrated! $47M breach! CISO ARRESTED!

#python #pythondisaster #yaml #remotecodeexecution #configloading #productionbug #pythonshorts #pythonwtf #deserialization #careerending #criminalcharges #pyyaml

https://www.youtube.com/watch?v=Lvvwf-SaDeE

YAML Load Executes Arbitrary Code Compromising 470 Servers?! #YAML

YouTube
Just stumbled upon some oddities in #PyYAML and the #YAML 1.1 spec when working on a bug report of #kas. Asked an #LLM and argued with it. TL;DR: Always check the answers against the actual spec.
#oss

Projekt #PyYAML odrzucił wsparcie dla Pythona bez GIL (#freethreading). Skutkiem tego, powstał fork skupiony na dodaniu tego wsparcia. Ze względu na ograniczone potrzeby forka, wspiera on tylko Pythona 3.13+. A że nie da się jeszcze wyrażać zależności warunkowo od wersji freethreading, inne paczki wymagają PyYAML-ft dla wersji Pythona >=3.13 (w tym zwyczajnej, z GIL-em) i zwykłego PyYAML dla <3.13.

Czy świat paczek Pythona nie jest super?

https://github.com/yaml/pyyaml/pull/830#issuecomment-2342475334
https://github.com/Instagram/LibCST/blob/18d4f6aded907bd11b683fa54dad32ca04f84f75/pyproject.toml#L21-L24

#Gentoo #Python

Add free-threading support by FFY00 · Pull Request #830 · yaml/pyyaml

GitHub

#PyYAML rejected #freethreading support. As a result, a new fork has been created with freethreading support. Given the fork's focus on freethreading, it supports only Python 3.13+. Given the lack of environment markers for freethreading (yet), packages end up depending on PyYAML-ft for >=3.13 (including non-freethreading builds), and PyYAML for <3.13.

Isn't #Python #packaging great?

https://github.com/yaml/pyyaml/pull/830#issuecomment-2342475334
https://github.com/Instagram/LibCST/blob/18d4f6aded907bd11b683fa54dad32ca04f84f75/pyproject.toml#L21-L24

#Gentoo

Add free-threading support by FFY00 · Pull Request #830 · yaml/pyyaml

GitHub
#PyYaml -> 🚮 slow, slower, slowest

This library is depended on by a 867 packages ( #pyyaml , requests, hypothesis ), has a bogus CVE and is abandonware.

That's a bit under 1000 releases not counting the iceberg of closed source.

Who files these bogus CVEs, it is like setting $10,000 on fire, but in $100 piles all across the country.

https://pypi.org/project/py/

https://libraries.io/pypi/py

#python

py

library with cross-python path, ini-parsing, io, code, log facilities

PyPI
@orsinium Interesting. I presume you mean this problem with #PyYAML. I hadn't considered #TOML. Will take a look at it. conhttps://stackoverflow.com/questions/76707475/issue-importing-pyyaml-cltk

ℹ️ He actualitzat #PyXavi a la versió v0.3.3, sol.lucionant un problema de dependències amb #PyYaml, que van publicar la 6.0 que al seu torn està trencada i es sol.luciona amb la 6.0.1

La versió ja està publicada a #PyPI
https://pypi.org/project/pyxavi/

Coses de #Python 

pyxavi

Set of utilities to assist on simple Python projects

PyPI

그냥 귀찮아서 잘 알아보지 않고 pyyaml을 설치했다. import yaml 잘 되네.

#yaml #pyyaml #python

Wow I thought I was not affected by the PyYAML uncapped Cython disaster https://github.com/yaml/pyyaml/issues/601 but it turns out I can't install `docker-compose`.

I often refer to @henryiii blog post on the matter https://iscinumpy.dev/post/bound-version-constraints/ but I think in this case it was a big mistake not to cap Cython. In the end, build dependencies are throwaway dependencies, they are used in a temporary, isolated environment and then never used again.

#python #pyyaml #cython

"AttributeError: cython_sources" with Cython 3.0.0a10 · Issue #601 · yaml/pyyaml

When attempting to install PyYAML from sources with Cython 3.0.0a10, e.g. like so: pip install --pre -v git+https://github.com/yaml/pyyaml.git the install fails with: Using pip 21.3.1 from /home/fl...

GitHub