[Date Prev][Date Next]
(ITS#5803) Incorrect filters (e.g. substrings) may trigger "disconnect"
Full_Name: Pierangelo Masarati
Submission from: (NULL) (18.104.22.168)
Submitted by: ando
When a malformed filter is encountered, ber decoding may stop before the
specific element has been parsed. This results in a decoding error later, that
triggers a "disconnect" response. To reproduce: search with
"(objectClass=foo*bar)". The correct behavior would consist in parsing the
whole filter anyway and identify it as COMPUTED UNDEFINED.