From: tim.orling@konsulko.com
To: openembedded-core@lists.openembedded.org
Cc: Tim Orling <tim.orling@konsulko.com>
Subject: [PATCH] python3-pyasn1: upgrade 0.6.3 -> 0.6.4
Date: Sat, 18 Jul 2026 10:48:10 -0700 [thread overview]
Message-ID: <20260718174810.1890741-1-tim.orling@konsulko.com> (raw)
From: Tim Orling <tim.orling@konsulko.com>
Upstream release notes:
https://github.com/pyasn1/pyasn1/blob/main/CHANGES.rst#revision-064-released-08-07-2026
Revision 0.6.4, released 08-07-2026
* CVE-2026-59885 (GHSA-8ppf-4f7h-5ppj): Fixed quadratic time complexity
in the OBJECT IDENTIFIER and RELATIVE-OID decoders. A small crafted
substrate encoding many arcs could consume excessive CPU. Arcs are now
accumulated in linear time; decoded values are unchanged (thanks for
reporting, tynus2)
* CVE-2026-59884 (GHSA-m4p7-r5rc-7g4j): Limited BER long-form tag IDs to
20 octets (140 bits), matching the OID arc limit introduced in 0.6.2.
Unbounded tag IDs allowed a crafted substrate to consume excessive CPU
and memory; longer tag IDs are now rejected with PyAsn1Error. Also fixed
Tag and TagSet repr() failing on huge tag (thanks for reporting,
mikeappsec) IDs due to the integer-to-string conversion limit (Python
3.11+)
* CVE-2026-59886 (GHSA-hm4w-wwcw-mr6r): Fixed excessive memory and CPU
consumption in Real.__float__() for values with large base-10 exponents.
Conversion no longer materializes huge intermediate integers; values too
large to represent as a Python float raise OverflowError promptly, and
prettyPrint() renders them as '<overflow>' as before. Also fixed base-10
mantissa normalization to use exact integer arithmetic; mantissas larger
than 2**53 could previously lose precision through float division (thanks
for reporting, gvozdila)
* Pinned PyPI publish GitHub Action to an immutable commit
For full comparison of changes, see:
https://github.com/pyasn1/pyasn1/compare/v0.6.3...v0.6.4
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
---
.../python/{python3-pyasn1_0.6.3.bb => python3-pyasn1_0.6.4.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-pyasn1_0.6.3.bb => python3-pyasn1_0.6.4.bb} (83%)
diff --git a/meta/recipes-devtools/python/python3-pyasn1_0.6.3.bb b/meta/recipes-devtools/python/python3-pyasn1_0.6.4.bb
similarity index 83%
rename from meta/recipes-devtools/python/python3-pyasn1_0.6.3.bb
rename to meta/recipes-devtools/python/python3-pyasn1_0.6.4.bb
index 60b38c57c5..086a21ffe8 100644
--- a/meta/recipes-devtools/python/python3-pyasn1_0.6.3.bb
+++ b/meta/recipes-devtools/python/python3-pyasn1_0.6.4.bb
@@ -3,7 +3,7 @@ HOMEPAGE = "http://pyasn1.sourceforge.net/"
LICENSE = "BSD-2-Clause"
LIC_FILES_CHKSUM = "file://LICENSE.rst;md5=190f79253908c986e6cacf380c3a5f6d"
-SRC_URI[sha256sum] = "697a8ecd6d98891189184ca1fa05d1bb00e2f84b5977c481452050549c8a72cf"
+SRC_URI[sha256sum] = "9c447d8431c947fe4c8febc4ed9e760bc29011a5b01e5c74b67025bd9fb8ce81"
inherit pypi python_setuptools_build_meta ptest-python-pytest
--
2.47.3
reply other threads:[~2026-07-18 17:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260718174810.1890741-1-tim.orling@konsulko.com \
--to=tim.orling@konsulko.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox