Skip to content

CVE-2023-27043 Unicode follow-up: add parseaddr regression test (Python 3.7) #82

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
icanhasmath wants to merge 1 commit into
base: 3.7.17.x
Choose a base branch
from
Open

CVE-2023-27043 Unicode follow-up: add parseaddr regression test (Python 3.7) #82

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions Lib/test/test_email/test_email.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3319,6 +3319,23 @@ def test_parsing_errors(self):
# Test email.utils.supports_strict_parsing attribute
self.assertEqual(email.utils.supports_strict_parsing, True)

def test_parseaddr_unicode(self):
# CVE-2023-27043 Unicode regression guard. The 2.7 refactor had to
# accept both str and unicode at the parseaddr() boundary; in Python 3
# str is already Unicode, so this test just pins that strict-mode
# parsing still accepts valid non-ASCII input and agrees with the
# non-strict path.
for addr in (
'user@example.com',
'Test User <user@example.com>',
'"Test User" <user@example.com>',
'"Sürname, Firstname" <to@example.com>',
):
with self.subTest(addr=addr):
strict = utils.parseaddr(addr, strict=True)
self.assertNotEqual(strict, ('', ''))
self.assertEqual(strict, utils.parseaddr(addr, strict=False))

def test_getaddresses_nasty(self):
for addresses, expected in (
(['"Sürname, Firstname" <to@example.com>'],
Expand Down