Users can be created and authenticate with an invalid x509 certificate (see example certificate attached). The provided certificate (client_invalid.pem) is invalid because the "Validity Not Before" is set to a date that has not yet arrived and the "Validity Not After" is a date already passed. The second provided certificate (client_invalid2.pem) has invalid values for public key algorithm, public key modulus, exponent, x509v3 extensions, signature algorithm, as well as negative values for version and serial number. Expected behavior is that mongod should not allow clients to connect who have an invalid x509 certificate.
Users can authenticate with an invalid x509 certificate
- Assignee:
-
Andreas Nilsson (Inactive)
- Reporter:
-
Luke Lovett (Inactive)
- Votes:
-
0 Vote for this issue - Watchers:
-
7 Start watching this issue
- Created:
- Updated:
- Resolved: