Red Hat Bugzilla – Bug 985449
p11-kit: upgrade to most recent UTF-8 specification
Last modified: 2017-08-01 12:52:09 EDT
common/utf8.c:utf8_to_uchar() does not reject surrogate characters in the input, which are invalid in UTF-8. UTF-8 was redefined in RFC 3629 so that code points in astral planes (unreachable with UTF-16) are no longer valid UTF-8.
The other conversion routines in that file do not seem to handle surrogate characters properly, either.
I'm not sure how relevant this is in practice, and if you can use platform conversion routines like iconv instead of rolling your own thing.
Agree with this. But punting to future release. The UTF-8 support is only used to generate OpenSSL symlinks when extracting. So not totally critical. Need to make sure that what we do here is compatible with how OpenSSL does this stuff.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.