This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Sign in with your Check Point UserCenter/PartnerMap account to access more great content and get a chance to win some Apple AirPods! If you don't have an account, create one now for free!
I'm having quite a strange issue lately. Hopefully you all can help me out.
I have a R82JHF118 gateway running the following blades: fw vpn cvpn urlf av appi ips identityServer SSL_INSPECT anti_bot ThreatEmulation content_awareness Scrub zero_phishing.
HTTPS inspection is enabled on one inbound connection from the internet towards an web application with Websocket capabilities. For some reason, the inbound HTTPS inspection connection broke. I checked the logs on the gateway but there were no issues and errors seen. Traffic was coming in correctly and, according to the logs, the flow was inspected without issues.
I ran a TCPdump and found out that the connection was able to establish on the front and back-end of the gateway, but when the first application data was sent, the gateway immediately reset the connection towards the server and the client at the same time. Eventually I found out that HTTPS inspection was not passing the traffic correctly because configuring a bypass rule for this flow, solved the issue. I ran some WSTLSD debugs but nothing extraordinary in the logs. When I did a fw ctl zdebug + drop, I found the following error message:
Apparently, there is a hardcoded kernel limit were the firewall does not allow more than 4 parsers attached to a flow. While the TLS_PARSER_LAST was the fifth, the connection was dropped before it was sent out of the interface. I tried a lot of stuff and configuration combinations but was not able to fix this issue. Hereby my list: - Used inline layer and normal fw rule. - Changed services object to custom object with and without handler. - Disabled features like app cntrl, urlf, content awareness on the inline layer. - Disabled IPS. - Changed IPS settings from autonomous Policy to custom. - Created a global exception for IPS/Threat Prevention. - Created a exception for app cntrl and urlf. - Changed https inspection in fail-open/fail-closed mode.
The only workaround that worked was settings a kernel parameter: fw ctl set int tls_parser_enable0
But this workaround prevents some deep inspection features, so it's not the best solution.
Do you guys have any idea what happened and how to solve this issue?
I recall back during Covid 19 time another kernel parameter breaking ssl inspection user check page. Maybe unrelated, but will check when i get up. Its only 3.23 am lol
Best, Andy "Have a great day and if its not, change it"