Is SEP vulnerable to CVE-2023-38545

Products

• Endpoint Protection

Issue/Introduction

CVE-2023-38545: SOCKS5 heap buffer overflow Score: High

https://curl.se/docs/CVE-2023-38545.html
Issue: The options that cause the SOCKS5 proxy with a pass of remote hostname.

This flaw makes curl overflow a heap-based buffer in the SOCKS5 proxy handshake.
When curl is asked to pass along the hostname to the SOCKS5 proxy to allow that to resolve the address instead of it getting done by curl itself,
the maximum length that hostname can be is 255 bytes.If the hostname is detected to be longer than 255 bytes, curl switches to local name
resolving and instead passes on the resolved address only to the proxy. Due to a bug, the local variable that means "let the host resolve the name" could get the wrong value during a slow SOCKS5 handshake, and contrary to the intention, copy the too-long hostname to the target buffer instead of copying just the resolved address there.

Resolution

SEPM and SEP client are not vulnerable to CVE-2023-38545

SEPM
The proxy settings can only be set from the UI, requiring admin rights
even then, socks5h cannot be set as the proxy protocol

SEP Agent
The SEP agent cannot be forced to use a SOCKS proxy via any configuration