[SERVER-49081] Disallow IP addresses in split horizon configurations Created: 24/Jun/20  Updated: 29/Oct/23  Resolved: 07/Aug/20

Status: Closed
Project: Core Server
Component/s: Replication, Security
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Task Priority: Major - P3
Reporter: Spencer Jackson Assignee: Gabriel Marks
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
causes SERVER-50827 Nodes with IP addresses in split hori... Closed
Backwards Compatibility: Fully Compatible
Sprint: Security 2020-08-10
Participants:
Linked BF Score: 37

 Description   

Split Horizons rely on SNI to identify which horizon clients are a member of, and should observe topology information from. SNI is defined in RFC6066, which states:

Currently, the only server names supported are DNS hostnames;
...
Literal IPv4 and IPv6 addresses are not permitted in "HostName".

Because it is not permissible, by the standard, to advertise IP addresses in the SNI extension, some TLS client implementations have inconsistent behaviour when asked to connect to servers with IP addresses in horizon definitions. The mongo shell, as of SERVER-42287, will refuse to advertise such extensions.

We should prevent invocations of replSetInitiate or replSetReconfig from accepting split horizon definitions which contain IP addresses in horizon definitions.



 Comments   
Comment by Githook User [ 07/Aug/20 ]

Author:

{'name': 'Gabriel Marks', 'email': 'gabriel.marks@mongodb.com', 'username': 'marksg07'}

Message: SERVER-49081 Add check for IP addresses in split horizon configurations
Branch: master
https://github.com/mongodb/mongo/commit/adb23953e19f055aed6a19ead71d36d64ff2f069

Generated at Thu Feb 08 05:18:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.