-
Notifications
You must be signed in to change notification settings - Fork 456
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.
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
Crash during OCSP response parsing for ephtsecure.cdc.gov #254
Comments
@konklone do you have a short code snippet to attempt to reproduce this? |
Sure, this will reproduce the issue: import sslyze
from sslyze.synchronous_scanner import SynchronousScanner
from sslyze.plugins.certificate_info_plugin import CertificateInfoScanCommand
hostname = "ephtsecure.cdc.gov"
server_info = sslyze.server_connectivity.ServerConnectivityInfo(hostname=hostname, port=443)
server_info.test_connectivity_to_server()
scanner = SynchronousScanner()
certs = scanner.run_scan_command(server_info, CertificateInfoScanCommand()) When running that in an
|
I couldn't reproduce this issue specifically, but nassl definitely was not ready to handle non-successful OCSP responses; your test servers returns a "Try again later" response. |
@nabla-c0d3 I'm facing a similar issue when scanning python -m sslyze --regular e-saksham.nic.in
Python v3.8.2 |
When running the certificate info scanner on
ephtsecure.cdc.gov
, using the Python API and running aCertificateInfoScanCommand()
, I get a crash in a text parsing function insidenassl
that looks related to OCSP response parsing:This is using a SynchronousScanner on Ubuntu 16.04. On another system, also Ubuntu 16.04, I got a segfault.
The text was updated successfully, but these errors were encountered: