3 ms·

Yeah you're right, I originally said no action was taken because I was going off of my recollection of the original issue 2 years ago. When Rust released this b

Yeah you're right, I originally said no action was taken because I was going off of my recollection of the original issue 2 years ago. When Rust released this blog post (Jan 20th 2022) the same issue had been fixed already in Python. When I asked around about C++, people pasted the reference link and said it didn't need to be fixed because it was defined as UB. I stand corrected, they did fix it. And good on them for fixing it and not closing it as "spec says its fine". It's still bad they didn't file a CVE for it, knowing that other languages did so. It reduces trust in their ecosystem.

adev_ 3y ago
> It's still bad they didn't file a CVE for it, knowing that other languages did so. It reduces trust in their ecosystem. Curiosity question: Do you know if python has also a CVE for this exact same problem ? I am not able to find it back through their git history.
- lifthrasiir 3y ago
  In my understanding, no. I believe it was bpo-4489 [1], and I couldn't find a matching advisory from the PSF's database [2] which should contain most historical advisories as well (it does seem to miss earliest advisories like PSF-2005-001 and PSF-2006-001 though). [1] https://github.com/python/cpython/issues/48739 https://github.com/python/cpython/issues/48739 [2] https://github.com/psf/advisory-database/ https://github.com/psf/advisory-database/