Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1640723 - (CVE-2018-18385) CVE-2018-18385 rubygem-asciidoctor: Infinite loop in the #next_block method
CVE-2018-18385 rubygem-asciidoctor: Infinite loop in the #next_block method
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20180926,repor...
: Security
Depends On: 1640727 1640728
Blocks: 1640729
  Show dependency tree / graph
 
Reported: 2018-10-18 11:12 EDT by Andrej Nemec
Modified: 2018-10-22 03:02 EDT (History)
12 users (show)

See Also:
Fixed In Version: rubygem-asciidoctor 1.5.8
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

  None (edit)
Description Andrej Nemec 2018-10-18 11:12:23 EDT 
Asciidoctor allows remote attackers to cause a denial of service (infinite loop), as demonstrated by web applications that deliver untrusted input to this product, because Parser#next_block misuses a "while true" statement.

Upstream issue:

https://github.com/asciidoctor/asciidoctor/issues/2888
Comment 1 Andrej Nemec 2018-10-18 11:13:57 EDT 
Created rubygem-asciidoctor tracking bugs for this issue:

Affects: epel-7 [bug 1640728]
Affects: fedora-all [bug 1640727]
Comment 2 Doran Moppert 2018-10-21 22:25:59 EDT 
Statement:

The version of rubygem-asciidoctor included in Red Hat Virtualization is affected by this flaw, however it is not exposed to user input in such a way that the vulnerability could be exploited by an attacker.
Comment 3 Dan Allen 2018-10-22 03:02:28 EDT 
A fix is now available upstream. The fix is in master at the time of this comment and will be included in the upcoming 1.5.8 release.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.