citrus_euc module accept wrong byte sequence.
Issue #12
closed
citrus_euc module doesn't check second byte range, so illegal byte sequence (ex: "\xA4\x0") may wrongly converted to wchar_t(by mbrtowc) and other encoding(by iconv). this bug derived from 4.4BSD rune, it's 20 years old!
Comments (3)
-
reporter -
reporter - changed status to resolved
BUGFIX: Issue
#12-- citrus_euc module accept wrong byte sequence.→ <<cset 19be40a6c09e>>
-
reporter - changed status to closed
- Log in to comment
minimal test case: