New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
heap-buffer-overflow in S__byte_dump_string (utf8.c:709) #15659
Comments
From @geeknikTriggered with AFL+ASAN in Perl v5.25.6 (v5.25.5-104-gaff2be5). Note: If Passing malformed UTF-8 to "_Perl_IDStart" is deprecated at test273 line 3.==5806==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60400000a1b3 is located 0 bytes to the right of 35-byte region SUMMARY: AddressSanitizer: heap-buffer-overflow /root/perl/utf8.c:709 Valgrind + non-ASAN Perl: Passing malformed UTF-8 to "_Perl_IDStart" is deprecated at test273 line 3. gdb + non-ASAN Perl + libdislocator.so: Program received signal SIGSEGV, Segmentation fault. |
From @geeknik |
From @khwilliamsonOn 10/15/2016 03:40 PM, Brian Carpenter (via RT) wrote:
This is fundamentally the result of poor initial design in the utf8 This particular ticket isn't a security issue, since the problem has not
|
The RT System itself - Status changed from 'new' to 'open' |
From @tonycozOn Wed, 19 Oct 2016 20:46:15 -0700, public@khwilliamson.com wrote:
Would you have a list of UTF-8 functions/macros that don't take a length limit and their replacements (if any)? This would give others a checklist we can use to: - add replacements where they don't exist - deprecate them where they aren't already deprecated - replace the use of the deprecated functions in core - possibly add the replacements to Devel::PPPort Tony |
From @khwilliamsonOn 01/16/2017 05:24 PM, Tony Cook via RT wrote:
I forgot about this ticket. These have all been fixed in core, are all It took a bunch of commits to accomplish this, but are the ones that added them, with surrounding commits involved in I'm reluctant to put them in PPPort, as the unsafe ones weren't in it, So this ticket can be closed. Should it be moved to the public queue? |
From @tonycozOn Mon, Jan 16, 2017 at 09:29:43PM -0700, Karl Williamson wrote:
Thanks.
If the unsafe ones aren't there, we can leave the safe ones out for now.
This is a public project, ideally we keep security tickets private Tony |
From @khwilliamsonMoved to public queue and closed |
@khwilliamson - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#129887 (status was 'resolved')
Searchable as RT129887$
The text was updated successfully, but these errors were encountered: