asciidoctor-include-ext

Version	Released
`0.4.0` minor	Mar 29, 2022
`0.3.1` patch 1 CVE	Apr 14, 2019
`0.3.0` minor 1 CVE	May 09, 2018
`0.2.0` minor 1 CVE	May 03, 2018
`0.1.1` patch 1 CVE	Dec 13, 2017
`0.1.0` initial 1 CVE	Dec 12, 2017

0.4.0 minor

Mar 29, 2022

0.3.1 patch

1 CVE

CVE-2022-24803 GHSA-v222-6mr4-qj29 Mar 31, 2022

Command Injection vulnerability in asciidoctor-include-ext

10.0 / 10

Critical

Network Low None None Changed High High High

Impact

Applications using Asciidoctor (Ruby) with asciidoctor-include-ext (prior to version 0.4.0), which render user-supplied input in AsciiDoc markup, may allow an attacker to execute arbitrary system commands on the host operating system. ~~This attack is possible even when allow-uri-read is disabled!~~ (EDIT: it’s not)

Patches

The vulnerability has been fixed in commit c7ea001 (and further improved in cbaccf3), which is included in version 0.4.0.

Workarounds

require 'asciidoctor/include_ext'

class Asciidoctor::IncludeExt::IncludeProcessor
  # Overrides superclass private method to mitigate Command Injection
  # vulnerability in asciidoctor-include-ext <0.4.0.
  def target_uri?(target)
    target.downcase.start_with?('http://', 'https://') \
      && URI.parse(target).is_a?(URI::HTTP)
  rescue URI::InvalidURIError
    false
  end
end

References

https://sakurity.com/blog/2015/02/28/openuri.html

Credits

This vulnerability was discovered by Joern Schneeweisz from the GitLab Security Research Team.

For more information

See commit message c7ea001.

If you have any questions or comments about this advisory open an issue in jirutka/asciidoctor-include-ext.

Affected versions


          0.1.0


          0.1.1


          0.2.0


          0.3.0


          0.3.1

Fixed in


          0.4.0

References

Updated Nov 08, 2023 · Source: OSV.dev

Apr 14, 2019

0.3.0 minor

1 CVE

CVE-2022-24803 GHSA-v222-6mr4-qj29 Mar 31, 2022

Command Injection vulnerability in asciidoctor-include-ext

10.0 / 10

Critical

Network Low None None Changed High High High

Impact

Applications using Asciidoctor (Ruby) with asciidoctor-include-ext (prior to version 0.4.0), which render user-supplied input in AsciiDoc markup, may allow an attacker to execute arbitrary system commands on the host operating system. ~~This attack is possible even when allow-uri-read is disabled!~~ (EDIT: it’s not)

Patches

The vulnerability has been fixed in commit c7ea001 (and further improved in cbaccf3), which is included in version 0.4.0.

Workarounds

require 'asciidoctor/include_ext'

class Asciidoctor::IncludeExt::IncludeProcessor
  # Overrides superclass private method to mitigate Command Injection
  # vulnerability in asciidoctor-include-ext <0.4.0.
  def target_uri?(target)
    target.downcase.start_with?('http://', 'https://') \
      && URI.parse(target).is_a?(URI::HTTP)
  rescue URI::InvalidURIError
    false
  end
end

References

https://sakurity.com/blog/2015/02/28/openuri.html

Credits

This vulnerability was discovered by Joern Schneeweisz from the GitLab Security Research Team.

For more information

See commit message c7ea001.

If you have any questions or comments about this advisory open an issue in jirutka/asciidoctor-include-ext.

Affected versions


          0.1.0


          0.1.1


          0.2.0


          0.3.0


          0.3.1

Fixed in


          0.4.0

References

Updated Nov 08, 2023 · Source: OSV.dev

May 09, 2018

0.2.0 minor

1 CVE

CVE-2022-24803 GHSA-v222-6mr4-qj29 Mar 31, 2022

Command Injection vulnerability in asciidoctor-include-ext

10.0 / 10

Critical

Network Low None None Changed High High High

Impact

Applications using Asciidoctor (Ruby) with asciidoctor-include-ext (prior to version 0.4.0), which render user-supplied input in AsciiDoc markup, may allow an attacker to execute arbitrary system commands on the host operating system. ~~This attack is possible even when allow-uri-read is disabled!~~ (EDIT: it’s not)

Patches

The vulnerability has been fixed in commit c7ea001 (and further improved in cbaccf3), which is included in version 0.4.0.

Workarounds

require 'asciidoctor/include_ext'

class Asciidoctor::IncludeExt::IncludeProcessor
  # Overrides superclass private method to mitigate Command Injection
  # vulnerability in asciidoctor-include-ext <0.4.0.
  def target_uri?(target)
    target.downcase.start_with?('http://', 'https://') \
      && URI.parse(target).is_a?(URI::HTTP)
  rescue URI::InvalidURIError
    false
  end
end

References

https://sakurity.com/blog/2015/02/28/openuri.html

Credits

This vulnerability was discovered by Joern Schneeweisz from the GitLab Security Research Team.

For more information

See commit message c7ea001.

If you have any questions or comments about this advisory open an issue in jirutka/asciidoctor-include-ext.

Affected versions


          0.1.0


          0.1.1


          0.2.0


          0.3.0


          0.3.1

Fixed in


          0.4.0

References

Updated Nov 08, 2023 · Source: OSV.dev

May 03, 2018

0.1.1 patch

1 CVE

CVE-2022-24803 GHSA-v222-6mr4-qj29 Mar 31, 2022

Command Injection vulnerability in asciidoctor-include-ext

10.0 / 10

Critical

Network Low None None Changed High High High

Impact

Applications using Asciidoctor (Ruby) with asciidoctor-include-ext (prior to version 0.4.0), which render user-supplied input in AsciiDoc markup, may allow an attacker to execute arbitrary system commands on the host operating system. ~~This attack is possible even when allow-uri-read is disabled!~~ (EDIT: it’s not)

Patches

The vulnerability has been fixed in commit c7ea001 (and further improved in cbaccf3), which is included in version 0.4.0.

Workarounds

require 'asciidoctor/include_ext'

class Asciidoctor::IncludeExt::IncludeProcessor
  # Overrides superclass private method to mitigate Command Injection
  # vulnerability in asciidoctor-include-ext <0.4.0.
  def target_uri?(target)
    target.downcase.start_with?('http://', 'https://') \
      && URI.parse(target).is_a?(URI::HTTP)
  rescue URI::InvalidURIError
    false
  end
end

References

https://sakurity.com/blog/2015/02/28/openuri.html

Credits

This vulnerability was discovered by Joern Schneeweisz from the GitLab Security Research Team.

For more information

See commit message c7ea001.

If you have any questions or comments about this advisory open an issue in jirutka/asciidoctor-include-ext.

Affected versions


          0.1.0


          0.1.1


          0.2.0


          0.3.0


          0.3.1

Fixed in


          0.4.0

References

Updated Nov 08, 2023 · Source: OSV.dev

Dec 13, 2017

0.1.0 initial

1 CVE

CVE-2022-24803 GHSA-v222-6mr4-qj29 Mar 31, 2022

Command Injection vulnerability in asciidoctor-include-ext

10.0 / 10

Critical

Network Low None None Changed High High High

Impact

Applications using Asciidoctor (Ruby) with asciidoctor-include-ext (prior to version 0.4.0), which render user-supplied input in AsciiDoc markup, may allow an attacker to execute arbitrary system commands on the host operating system. ~~This attack is possible even when allow-uri-read is disabled!~~ (EDIT: it’s not)

Patches

The vulnerability has been fixed in commit c7ea001 (and further improved in cbaccf3), which is included in version 0.4.0.

Workarounds

require 'asciidoctor/include_ext'

class Asciidoctor::IncludeExt::IncludeProcessor
  # Overrides superclass private method to mitigate Command Injection
  # vulnerability in asciidoctor-include-ext <0.4.0.
  def target_uri?(target)
    target.downcase.start_with?('http://', 'https://') \
      && URI.parse(target).is_a?(URI::HTTP)
  rescue URI::InvalidURIError
    false
  end
end

References

https://sakurity.com/blog/2015/02/28/openuri.html

Credits

This vulnerability was discovered by Joern Schneeweisz from the GitLab Security Research Team.

For more information

See commit message c7ea001.

If you have any questions or comments about this advisory open an issue in jirutka/asciidoctor-include-ext.

Affected versions


          0.1.0


          0.1.1


          0.2.0


          0.3.0


          0.3.1

Fixed in


          0.4.0

References

Updated Nov 08, 2023 · Source: OSV.dev

Dec 12, 2017

Activity

Details

Impact

Patches

Workarounds

References

Credits

For more information

Impact

Patches

Workarounds

References

Credits

For more information

Impact

Patches

Workarounds

References

Credits

For more information

Impact

Patches

Workarounds

References

Credits

For more information

Impact

Patches

Workarounds

References

Credits

For more information

Impact

Patches

Workarounds

References

Credits

For more information