Subject: bin/21154: Potential misuse of ctype functions [file]
To: None <firstname.lastname@example.org>
From: Christian Biere <email@example.com>
Date: 04/14/2003 13:02:49
>Synopsis: Potential misuse of ctype functions [file]
>Arrival-Date: Mon Apr 14 04:03:01 PDT 2003
>Originator: Christian Biere
>Release: NetBSD 1.6Q
At least the following file(s) seem(s) to be affected:
*** This general description which might only partially apply to this PR ***
The is* (e.g., isdigit() but not isascii()) functions from <ctype.h> as well
as tolower() and toupper() expect an parameter of type int. However, the
behaviour is only defined for values which are EOF or representable as
an unsigned char. Several architectures have char as signed char by default.
This means if you pass a parameter of type char it will be automatically
casted to (signed) int and therefore the value isn't representable as
an unsigned char or EOF for negative values (except -1 which is normally EOF).
The result might be a crash or simply *anything* as the behaviour isn't
defined for these cases.
I have not verified whether there are any preconditions which prevent
an actual problem. The code might work for the suggested platform, it
might not be used, the characters might be prefiltered etc. However,
it's so simple toofix but so often done wrong, that I don't think anyone
should waste his with going into deep here.
KISS: If you work with strings use unsigned char or cast to it. If you use
int make sure that it's from fgetc(), getc() etc. or better check for EOF
and cast it to unsigned char after that.
Furthermore, it's often not considered that these functions respect the
current locale settings.