RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1689271 - Wrong alert sent when client uses PKCS#1 signatures in TLS 1.3 [rhel-8]
Summary: Wrong alert sent when client uses PKCS#1 signatures in TLS 1.3 [rhel-8]
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: nss
Version: 8.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: 8.1
Assignee: nss-nspr-maint
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On: 1684604
Blocks: 1728259
TreeView+ depends on / blocked
 
Reported: 2019-03-15 14:52 UTC by Alicja Kario
Modified: 2019-08-09 17:57 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1728259 (view as bug list)
Environment:
Last Closed: 2019-08-09 17:57:51 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Mozilla Foundation 1535630 0 P5 NEW Wrong alert sent when client uses PKCS#1 signatures in TLS 1.3 2020-06-11 11:15:04 UTC

Description Alicja Kario 2019-03-15 14:52:53 UTC 
Description of problem:
Server rejects the CertificateVerify message signed with PKCS#1 algorithm and sha256, sha384 and sha512 hash using incorrect alert - decode_error instead of illegal_parameter

Version-Release number of selected component (if applicable):
nss-3.41.0-5.el8.x86_64

How reproducible:
always

Steps to Reproduce:
1. tlsfuzzer test-tls13-certificate-verify.py

Actual results:
check rsa_pkcs1_sha256 signature is refused ...
Error encountered while processing node <tlsfuzzer.expect.ExpectAlert object at 0x7f0457fafd90> (child: <tlsfuzzer.expect.ExpectClose object at 0x7f0457fafdd0>) with last message being: <tlslite.messages.Message object at 0x7f0456f394d0>
Error while processing
Traceback (most recent call last):
  File "scripts/test-tls13-certificate-verify.py", line 583, in main
    runner.run()
  File "/home/hkario/dev/tlsfuzzer/tlsfuzzer/runner.py", line 227, in run
    node.process(self.state, msg)
  File "/home/hkario/dev/tlsfuzzer/tlsfuzzer/expect.py", line 1412, in process
    raise AssertionError(problem_desc)
AssertionError: Expected alert description "illegal_parameter" does not match received "decrypt_error"

Expected results:
check rsa_pkcs1_sha256 signature is refused ...
ok

Additional info:
server does send correct alerts for SHA224, SHA1 and md5 signatures
Comment 2 Simo Sorce 2019-05-29 19:10:37 UTC 
Is this going to be fixed in the rebase?
If so set appropriate flags please
Note You need to log in before you can comment on or make changes to this bug.