-
Type: Bug
-
Resolution: Done
-
Priority: Critical - P2
-
None
-
Component/s: None
-
None
The BSON spec defines two string types:
- The "string" type is a sequence of bytes encoded with a length. This sequence can include null bytes since the length of the sequence is encoded.
- The "cstring" type is a null terminated sequence of bytes. It is not encoded with a length. The sequence ends with a null byte so it can not include null bytes.
This ticket is to validate that drivers do not allow sequences including null bytes wherever a cstring is required (e.g. document keys, database and collection name, regular expressions, ...)
- depends on
-
CXX-519 Ensure null bytes are not allowed within cstrings (keys, db/coll name, regex)
- Closed
- is duplicated by
-
SERVER-7005 Documents containing keys with embedded null characters can be created
- Closed
- is related to
-
JAVA-891 Document fields accept NULL characters
- Closed
-
PHPC-891 BSON encoding should throw if PHP keys contain null bytes
- Closed
-
RUBY-646 Ensure we check for null characters in strings and symbols used as keys
- Closed
-
PHPC-721 Javascript constructor should throw if code contains null bytes
- Closed
-
PHPC-724 Regex constructor should throw if pattern or flags contain null bytes
- Closed
- related to
-
CSHARP-788 Strengthen checks for nulls in CStrings
- Closed