bpo-38708: email: Fix a potential IndexError when parsing Message-ID (GH-17504)

Fix a potential IndexError when passing an empty value to the message-id
parser. Instead, HeaderParseError should be raised.
(cherry picked from commit 3ae4ea1931)

Co-authored-by: Abhilash Raj <maxking@users.noreply.github.com>
This commit is contained in:
Miss Islington (bot) 2019-12-08 18:12:50 -08:00 committed by GitHub
parent f66f4a09d0
commit 2abd3a8f58
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 8 additions and 1 deletions

View File

@ -2047,7 +2047,7 @@ def get_msg_id(value):
no-fold-literal = "[" *dtext "]"
"""
msg_id = MsgID()
if value[0] in CFWS_LEADER:
if value and value[0] in CFWS_LEADER:
token, value = get_cfws(value)
msg_id.append(token)
if not value or value[0] != '<':

View File

@ -2583,6 +2583,11 @@ class TestParser(TestParserMixin, TestEmailBase):
# get_msg_id
def test_get_msg_id_empty(self):
# bpo-38708: Test that HeaderParseError is raised and not IndexError.
with self.assertRaises(errors.HeaderParseError):
parser.get_msg_id('')
def test_get_msg_id_valid(self):
msg_id = self._test_get_x(
parser.get_msg_id,
@ -2694,6 +2699,7 @@ class TestParser(TestParserMixin, TestEmailBase):
self.assertEqual(msg_id.token_type, 'msg-id')
@parameterize
class Test_parse_mime_parameters(TestParserMixin, TestEmailBase):

View File

@ -0,0 +1 @@
Fix a potential IndexError in email parser when parsing an empty msg-id.