Skip to content

Commit ef22247

Browse files
committed
BE-5248 New AS Release 2.7.18.12
1 parent 8cc4686 commit ef22247

2 files changed

Lines changed: 10 additions & 1 deletion

File tree

Include/patchlevel.h

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@
2727
#define PY_RELEASE_SERIAL 0
2828

2929
/* Version as a string */
30-
#define PY_VERSION "2.7.18.11"
30+
#define PY_VERSION "2.7.18.12"
3131
/*--end constants--*/
3232

3333
/* Subversion Revision number of this file (not of the repository). Empty

Misc/NEWS.d/2.7.18.12.rst

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
.. bpo: ?
2+
.. date: 2025-01-22
3+
.. nonce:
4+
.. release date: 2025-01-22
5+
.. section: Core and Builtins
6+
7+
CVE-2023-27043
8+
9+
The legacy email.utils.parseaddr function in Python through 3.11.4 allows attackers to trigger "RecursionError: maximum recursion depth exceeded while calling a Python object" via a crafted argument. This argument is plausibly an untrusted value from an application's input data that was supposed to contain a name and an e-mail address. NOTE: email.utils.parseaddr is categorized as a Legacy API in the documentation of the Python email package. Applications should instead use the email.parser.BytesParser or email.parser.Parser class. NOTE: the vendor's perspective is that this is neither a vulnerability nor a bug. The email package is intended to have size limits and to throw an exception when limits are exceeded; they were exceeded by the example demonstration code.

0 commit comments

Comments
 (0)