ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
SSL v3/4 vulnerabilities in APM
Article ID: 127063
Updated On:
Products
CA Application Performance Management Agent (APM / Wily / Introscope)
INTROSCOPE
Issue/Introduction
Getting below vulnerability in APM servers(MOM , EM and TIM).
**************************************************************************
The remote service accepts connections encrypted using SSL 2.0 and/or
SSL 3.0. These versions of SSL are affected by several cryptographic
flaws, including:
- An insecure padding scheme with CBC ciphers.
- Insecure session renegotiation and resumption schemes.
An attacker can exploit these flaws to conduct man-in-the-middle
attacks or to decrypt communications between the affected service and
clients.
Although SSL/TLS has a secure means for choosing the highest supported
version of the protocol (so that these versions will be used only if
the client or server support nothing better), many web browsers
implement this in an unsafe way that allows an attacker to downgrade
a connection (such as in POODLE). Therefore, it is recommended that
these protocols be disabled entirely.
NIST has determined that SSL 3.0 is no longer acceptable for secure
communications. As of the date of enforcement found in PCI DSS v3.1,
any version of SSL will not meet the PCI SSC's definition of 'strong
cryptography'.
**************************************************************************
The remote service accepts connections encrypted using SSL 2.0 and/or
SSL 3.0. These versions of SSL are affected by several cryptographic
flaws, including:
- An insecure padding scheme with CBC ciphers.
- Insecure session renegotiation and resumption schemes.
An attacker can exploit these flaws to conduct man-in-the-middle
attacks or to decrypt communications between the affected service and
clients.
Although SSL/TLS has a secure means for choosing the highest supported
version of the protocol (so that these versions will be used only if
the client or server support nothing better), many web browsers
implement this in an unsafe way that allows an attacker to downgrade
a connection (such as in POODLE). Therefore, it is recommended that
these protocols be disabled entirely.
NIST has determined that SSL 3.0 is no longer acceptable for secure
communications. As of the date of enforcement found in PCI DSS v3.1,
any version of SSL will not meet the PCI SSC's definition of 'strong
cryptography'.
Environment
APM 10.x
Resolution
We can disable SSL3.0 protocol using configuration. Please change configuration in em-jetty-config.xml and webview-jetty-config.xml file.
Please add below configuration under org.eclipse.jetty.server.SslConnectionFactory. This configuration will disable the SSL3 protocol
(Set name="ExcludeProtocols")
(Array type="java.lang.String")
(Item)SSLv3(/Item)
(/Array)
(/Set)
For Tim, You should change the configuration in httpd.conf/httpd-ssl.conf file of the machine.
And also,
Check below property is enabled in the file <EM_HOME>\jre\lib\security\java.security
jdk.tls.disabledAlgorithms=SSLv3, RC4, MD5withRSA, DH keySize < 768
Please add below configuration under org.eclipse.jetty.server.SslConnectionFactory. This configuration will disable the SSL3 protocol
(Set name="ExcludeProtocols")
(Array type="java.lang.String")
(Item)SSLv3(/Item)
(/Array)
(/Set)
For Tim, You should change the configuration in httpd.conf/httpd-ssl.conf file of the machine.
And also,
Check below property is enabled in the file <EM_HOME>\jre\lib\security\java.security
jdk.tls.disabledAlgorithms=SSLv3, RC4, MD5withRSA, DH keySize < 768
Feedback
Yes
No
Powered by
