Fedora has issued an advisory today (May 27): https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/thread/6HIYEYZRQEP6QTHT3EHH3RGFYJIHIMAO/ The issue is fixed upstream in 2.4.0: https://github.com/jpadilla/pyjwt/security/advisories/GHSA-ffqj-6fqr-9h24 Mageia 8 is also affected.
Assignee: bugsquad => pythonStatus comment: (none) => Fixed upstream in 2.4.0Whiteboard: (none) => MGA8TOO
New release is now built: python3-pyjwt-2.4.0-1.mga8.noarch.rpm Sources: python-pyjwt-2.4.0-1.mga8.src.rpm
Assignee: python => qa-bugsCC: (none) => yves.brungard_mageiaStatus comment: Fixed upstream in 2.4.0 => (none)
This module is used by: ceph-mgr buildbot-master python3-pygithub
Whiteboard: MGA8TOO => (none)Version: Cauldron => 8
MGA8-64 Plasma on Acer Aspire 5253 No installation issues Had a quick look at the packages using this, but this is all stuff deep into python development. Way over my head. And there isn't a previous update to refer to. Is it acceptable to OK this on clean install???
CC: (none) => herman.viaene
That sounds reasonable.
Whiteboard: (none) => MGA8-64-OK
Yes, validate on clean update over the prior version.
CC: (none) => davidwhodgins
Validating.
Keywords: (none) => validated_updateCC: (none) => andrewsfarm, sysadmin-bugs
Keywords: (none) => advisory
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGASA-2022-0244.html
Resolution: (none) => FIXEDStatus: NEW => RESOLVED