V-279358
SV-279358r1179465_rule
CAT II
MongoDB must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values.
From: MongoDB Enterprise Advanced 8.x Security Technical Implementation Guide (V1R1)
Description
<VulnDiscussion>One class of man-in-the-middle or session hijacking attack involves the adversary guessing at valid session identifiers based on patterns in identifiers already known.
The preferred technique for thwarting guesses at Session IDs is the generation of unique session identifiers using a FIPS 140-2/140-3-approved random number generator.
However, it is recognized that available DBMS products do not all implement the preferred technique yet may have other protections against session hijacking. Therefore, other techniques are acceptable, provided they are demonstrated to be effective.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>
Check Procedure
Check the MongoDB configuration file (default location /etc/mongod.conf).
The following option must be present ( "net.tls.mode") and set to "requireTLS":
net:
tls:
mode: requireTLS
If this is not found in the MongoDB configuration file, this is a finding.
Fix Text
Edit the MongoDB configuration file to ensure the "net.tls.mode" option is included and set to the value "requireTLS" as shown below:
net:
tls:
mode: requireTLS
Restart the MongoDB service from the OS.
$ sudo systemctl restart mongod
Further documentation is available at:
https://www.mongodb.com/docs/v8.0/tutorial/configure-ssl/
CCI Reference
CCI-001188- Created
- 2026-04-07 20:08:22
- Last Updated
- 2026-04-07 20:08:22