On this page
CVEs That Do Not Affect TOS or Will Not Be Fixed
CVEs that do not Affect TOS
The following CVEs do not affect TOS:
-
TOS does not allow user control over Kubernetes Ingress resources. The ingress-nginx component in TOS is internal-only, not internet-facing, and not user-configurable.
-
TOS customers do not have RBAC or API access to ingress objects and therefore cannot modify ingress rules.
-
TOS ingress configuration is static and vendor-controlled, and is isolated within the cluster. The vulnerability relies on ingress annotation manipulation, which is not possible in TOS.
-
TOS does not use an OpenSSH client ProxyCommand with %r and an untrusted remote username in the default TOS or TufinOS deployment model.
-
TOS does not use the admission controller component of Ingress-NGINX and therefore is not affected.
-
TOS uses the default configuration where the readonly parameter is set to true and write access to the default servlet is disabled.
-
TOS is not affected.
-
TOS does not use the OIDCStripCookies setting in its configuration.
-
TOS products do not use OpenSSL version 3.x.
-
TOS does not use Spring Data MongoDB and therefore is not affected.
-
According to the Spring Framework vendor, this CVE affects applications running on JDK 9 and above. TOS runs on JDK 8 and is therefore not affected.
-
TOS does not use Spring Cloud functions and therefore is not affected.
-
TOS does not use Spring Cloud Gateway and therefore is not affected.
-
TOS products do not use the JDBCAppender in the Log4j configuration.
-
TOS products do not use the Chainsaw UI.
-
TOS products do not use the JMSSink in the Log4j configuration.
-
TOS products do not use the JMSAppender in the Log4j configuration.
-
The Apache Tomcat AJP port is disabled.
-
The Keycloak Undertow AJP port is bound to localhost.
CVEs that will not be Fixed
The following CVEs will not be fixed by Tufin:
-
Username enumeration in Tufin SecureTrack.
Tufin has categorized the vulnerability as low severity and has decided not to fix it.
This attack requires access to the internal network. If an attacker is part of the internal network, they do not require access to TOS to know the usernames.
Was this helpful?
Thank you!
We’d love your feedback
We really appreciate your feedback
Send this page to a colleague