The parser_yyerror function in the UTF-8 parser in Ruby 2.4.1 allows attackers to cause a denial of service (invalid write or read) or possibly have unspecified other impact via a crafted Ruby script, related to the parser_tokadd_utf8 function in parse.y. NOTE: this might have security relevance as a bypass of a $SAFE protection mechanism. Upstream bug: https://bugs.ruby-lang.org/issues/13742
Created ruby tracking bugs for this issue: Affects: fedora-all [bug 1473721]
This is not vulnerability according to upstream [1]: ~~~ Note that this is not a vulnerability. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11465 is invalid. ~~~ [1] https://bugs.ruby-lang.org/issues/13742#note-3
Patch: https://github.com/ruby/ruby/commit/80d502b88116e95e4b17b4e7278d0d47106253db Possibly also relevant: https://github.com/ruby/ruby/commit/f29e5013adcd9c8753587471727e3280aaf89686#diff-6d840db07406437770b610102b284273
Lowering impact because this is disputed upstream. Unfortunately, I've not been able to reproduce this issue myself yet, so I can't say if the dispute is correct.
Statement: Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Additionally, the security impact of this flaw is disputed by the upstream Ruby project.