cancel
Showing results for 
Search instead for 
Did you mean: 

Head's Up! These forums are read-only. All users and content have migrated. Please join us at community.neo4j.com.

TLS Robot Vulnerability detected on Bolt port 7687

Neo4j version: 4.0.4

Vulnerability: TLS ROBOT Vulnerability Detected

Qualsys ID: 38695

Diagonosis: The TLS vulnerability is also known as Return of Bleichenbacher's Oracle Threat (ROBOT). ROBOT allows an attacker to obtain the RSA key necessary to decrypt TLS traffic under certain conditions. To detect this the vulnerable ciphers should be disabled.

Consequence: An attacker could exploit this vulnerability by sending crafted TLS messages to the device, which would act as an oracle and allow the attacker to carry out a chosen-ciphertext attack.

The above mentioned vulnerability was reported by information security team and they want us to remediate this. On doing some research, I found that Neo4j make implicit use of ciphers that are included as part of the Java platform. I would like to know how can we disable the ciphers at JDK level? Or is there any other way of disabling the ciphers from Neo4j?

1 REPLY 1

The Cipher settings are configurable through

dbms.ssl.policy.bolt.ciphers

A comma-separated list of ciphers suits that will be allowed during cipher negotiation. Valid values depend on the current JRE and SSL provider, see note below for examples.

They need to be configured independently for bolt, https, cluster, backup (and fabric if used).
Those keywords go instead of bolt above.

See: https://neo4j.com/docs/operations-manual/current/security/ssl-framework/#ssl-settings

Nodes 2022
Nodes
NODES 2022, Neo4j Online Education Summit

All the sessions of the conference are now available online