Summary
These are all security issues fixed in the ruby3.4-rubygem-nokogiri-1.18.2-1.1 package on the GA media of openSUSE Tumbleweed.
Fixed packages 1
| Release | Package | Fixed in |
|---|---|---|
| openSUSE · Tumbleweed | rubygem-nokogiri | 1.18.2-1.1 |
Vulnerabilities 44
-
Critical 9.8
Nokogiri does not forbid namespace nodes in XPointer ranges
xpointer.c in libxml2 before 2.9.5 (as used in Apple iOS before 10, OS X before 10.12, tvOS before 10, and watchOS before 3, and other products) does not forbid namespace nodes in XPointer ranges, which allows remote attackers to execute arbitrary code or cau…
-
Critical 9.8
Nokogiri vulnerable to libxslt protection mechanism bypass
libxslt through 1.1.33 allows bypass of a protection mechanism because callers of xsltCheckRead and xsltCheckWrite permit access even upon receiving a -1 error code. xsltCheckRead can return -1 for a crafted URL that is not actually invalid and is subsequentl…
-
Critical 9.8
Nokogiri Command Injection Vulnerability
A command injection vulnerability in Nokogiri v1.10.3 and earlier allows commands to be executed in a subprocess via Ruby's `Kernel.open` method. Processes are vulnerable only if the undocumented method `Nokogiri::CSS::Tokenizer#load_file` is being called wit…
-
High 8.8
Use-after-free vulnerability in libxml2 through 2.9.4, as used in Google Chrome before 52.0.2743.82, allows remote atta…
-
High 8.8
Nokogiri gem, via libxml, is affected by DoS vulnerabilities
Use after free in libxml2 before 2.9.5, as used in Google Chrome prior to 63.0.3239.84 and other products, allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
-
High 8.8
Nokogiri implementation of libxslt lacks integer overflow checks
The xsltAddTextString function in transform.c in libxslt 1.1.29, as used in Blink in Google Chrome prior to 57.0.2987.98 for Mac, Windows, and Linux and 57.0.2987.108 for Android, lacked a check for integer overflow during a size calculation, which allowed a …
-
High 8.8CVE-2021-30560 EPSS 20%
Nokogiri has vulnerable dependencies on libxml2 and libxslt
Use after free in Blink XSLT in Google Chrome prior to 91.0.4472.164 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
-
High 8.8CVE-2021-3518 EPSS 22%
Nokogiri Implements libxml2 version vulnerable to use-after-free
There's a flaw in libxml2 in versions before 2.9.11. An attacker who is able to submit a crafted file to be processed by an application linked with libxml2 could trigger a use-after-free. The greatest impact from this flaw is to confidentiality, integrity, an…
-
High 8.6CVE-2021-3517 EPSS 17%
Nokogiri contains libxml Out-of-bounds Write vulnerability
There is a flaw in the xml entity encoding functionality of libxml2 in versions before 2.9.11. An attacker who is able to supply a crafted file to be processed by an application linked with the affected functionality of libxml2 could trigger an out-of-bounds …
-
High 8.2
Improper Handling of Unexpected Data Type in Nokogiri
Nokogiri is an open source XML and HTML library for Ruby. Nokogiri prior to version 1.13.6 does not type-check all inputs into the XML and HTML4 SAX parsers, allowing specially crafted untrusted inputs to cause illegal memory access errors (segfault) or reads…
-
High 7.5
Nokogiri affected by zlib's Out-of-bounds Write vulnerability
zlib before 1.2.12 allows memory corruption when deflating (i.e., when compressing) if the input has many distant matches.
-
High 7.5
xmlSchemaPreRun in xmlschemas.c in libxml2 2.9.10 allows an xmlSchemaValidateStream memory leak.
-
High 7.5
libxml as used in Nokogiri has an infinite loop in a certain end-of-file situation
xmlStringLenDecodeEntities in parser.c in libxml2 2.9.10 has an infinite loop in a certain end-of-file situation.
-
High 7.5
Improper Restriction of XML External Entity Reference (XXE) in Nokogiri on JRuby
Nokogiri is a Rubygem providing HTML, XML, SAX, and Reader parsers with XPath and CSS selector support. In Nokogiri v1.12.4 and earlier, on JRuby only, the SAX parser resolves external entities by default. Users of Nokogiri on JRuby who parse untrusted docume…
-
High 7.5
valid.c in libxml2 before 2.9.13 has a use-after-free of ID and IDREF attributes.
-
High 7.5
Unchecked return value from xmlTextReaderExpand in Nokogiri
Nokogiri is an open source XML and HTML library for the Ruby programming language. Nokogiri `1.13.8` and `1.13.9` fail to check the return value from `xmlTextReaderExpand` in the method `Nokogiri::XML::Reader#attribute_hash`. This can lead to a null pointer e…
-
High 7.5
Inefficient Regular Expression Complexity in Nokogiri
Nokogiri is an open source XML and HTML library for Ruby. Nokogiri `< v1.13.4` contains an inefficient regular expression that is susceptible to excessive backtracking when attempting to detect encoding in HTML documents. Users are advised to upgrade to Nokog…
-
High 7.5
Uncontrolled Resource Consumption in org.cyberneko.html (nokogiri fork)
org.cyberneko.html is an html parser written in Java. The fork of `org.cyberneko.html` used by Nokogiri (Rubygem) raises a `java.lang.OutOfMemoryError` exception when parsing ill-formed HTML markup. Users are advised to upgrade to `>= 1.9.22.noko2`. Note: The…
-
High 7.5
Apache Xalan Java XSLT library is vulnerable to an integer truncation issue when processing malicious XSLT stylesheets
The Apache Xalan Java XSLT library is vulnerable to an integer truncation issue when processing malicious XSLT stylesheets. This can be used to corrupt Java class files generated by the internal XSLTC compiler and execute arbitrary Java bytecode. Users are re…
-
Medium 6.5
Nokogiri NULL Pointer Dereference
A NULL pointer dereference vulnerability exists in the xpath.c:xmlXPathCompOpEval() function of libxml2 through 2.9.8 when parsing an invalid XPath expression in the XPATH_OP_AND or XPATH_OP_OR case. Applications processing untrusted XSL format inputs with th…
-
Medium 6.5CVE-2022-23437 EPSS 12%
Infinite loop within Apache XercesJ xml parser
There's a vulnerability within the Apache Xerces Java (XercesJ) XML parser when handling specially crafted XML document payloads. This causes, the XercesJ XML parser to wait in an infinite loop, which may sometimes consume system resources for prolonged durat…
-
Medium 6.5
An issue was discovered in libxml2 before 2.10.4. When hashing empty dict strings in a crafted XML document, xmlDictCom…
-
Medium 6.1
Cross-site Scripting in loofah
In the Loofah gem through 2.2.0 for Ruby, non-whitelisted HTML attributes may occur in sanitized output by republishing a crafted HTML fragment.
-
Medium 5.9
Nokogiri Implements libxml2 version vulnerable to null pointer dereferencing
A vulnerability found in libxml2 in versions before 2.9.11 shows that it did not propagate errors while parsing XML mixed content, causing a NULL dereference. If an untrusted XML document was parsed in recovery mode and post-validated, the flaw could be used …
-
Unscored —
parser.c in libxml2 before 2.9.0, as used in Google Chrome before 28.0.1500.71 and other products, allows remote attack…
-
Unscored —
The xmlParserHandlePEReference function in parser.c in libxml2 before 2.9.2, as used in Web Listener in Oracle HTTP Ser…
-
Medium —
Nokogiri vulnerable to libxml XML Entity Expansion
The xmlreader in libxml allows remote attackers to cause a denial of service (memory consumption) via crafted XML data, related to an XML Entity Expansion (XEE) attack.
-
High —
Nokogiri subject to DoS via libxml2 vulnerability
The xmlStringLenDecodeEntities function in parser.c in libxml2 before 2.9.3 does not properly prevent entity expansion, which allows context-dependent attackers to cause a denial of service (CPU consumption) via crafted XML data, a different vulnerability tha…
-
Unscored —
Heap-based buffer overflow in the xmlDictComputeFastQKey function in dict.c in libxml2 before 2.9.3 allows context-depe…
-
Unscored —
Heap-based buffer overflow in the xmlParseXmlDecl function in parser.c in libxml2 before 2.9.3 allows context-dependent…
-
Medium —
Heap-based buffer overflow in nokogiri
Heap-based buffer overflow in the xmlGROW function in parser.c in libxml2 before 2.9.3 allows context-dependent attackers to obtain sensitive process memory information via unspecified vectors.
-
Unscored —
The xmlParseMisc function in parser.c in libxml2 before 2.9.3 allows context-dependent attackers to cause a denial of s…
-
Unscored —
libxml2 2.9.2 does not properly stop parsing invalid input, which allows context-dependent attackers to cause a denial …
-
Unscored —
The xmlParseConditionalSections function in parser.c in libxml2 does not properly skip intermediary entities when it st…
-
Unscored —
The xsltStylePreCompute function in preproc.c in libxslt 1.1.28 does not check if the parent node is an element, which …
-
Unscored —
The xz_decomp function in xzlib.c in libxml2 2.9.1 does not properly detect compression errors, which allows context-de…
-
Unscored —
The xmlNextChar function in libxml2 2.9.2 does not properly check the state, which allows context-dependent attackers t…
-
Unscored —
The xmlSAX2TextNode function in SAX2.c in the push interface in the HTML parser in libxml2 before 2.9.3 allows context-…
-
Unscored —
The xmlParseXMLDecl function in parser.c in libxml2 before 2.9.3 allows context-dependent attackers to obtain sensitive…
-
Unscored —
libxslt in Apple iOS before 10, OS X before 10.12, tvOS before 10, and watchOS before 3 allows remote attackers to exec…
-
Unscored —
GNOME project libxml2 v2.9.10 has a global buffer over-read vulnerability in xmlEncodeEntitiesInternal at libxml2/entit…
-
Unscored —
There's a flaw in libxml2's xmllint in versions before 2.9.11. An attacker who is able to submit a crafted file to be p…
-
Unscored —
A flaw was found in libxml2. Exponential entity expansion attack its possible bypassing all existing protection mechani…
-
Unscored —
In libxml2 before 2.9.14, several buffer handling functions in buf.c (xmlBuf*) and tree.c (xmlBuffer*) don't check for …
References
-
web
https://www.suse.com/security/cve/CVE-2013-2877
-
web
https://www.suse.com/security/cve/CVE-2014-0191
-
web
https://www.suse.com/security/cve/CVE-2015-1819
-
web
https://www.suse.com/security/cve/CVE-2015-5312
-
web
https://www.suse.com/security/cve/CVE-2015-7497
-
web
https://www.suse.com/security/cve/CVE-2015-7498
-
web
https://www.suse.com/security/cve/CVE-2015-7499
-
web
https://www.suse.com/security/cve/CVE-2015-7500
-
web
https://www.suse.com/security/cve/CVE-2015-7941
-
web
https://www.suse.com/security/cve/CVE-2015-7942
-
web
https://www.suse.com/security/cve/CVE-2015-7995
-
web
https://www.suse.com/security/cve/CVE-2015-8035
-
web
https://www.suse.com/security/cve/CVE-2015-8241
-
web
https://www.suse.com/security/cve/CVE-2015-8242
-
web
https://www.suse.com/security/cve/CVE-2015-8317
-
web
https://www.suse.com/security/cve/CVE-2016-4658
-
web
https://www.suse.com/security/cve/CVE-2016-4738
-
web
https://www.suse.com/security/cve/CVE-2016-5131
-
web
https://www.suse.com/security/cve/CVE-2017-15412
-
web
https://www.suse.com/security/cve/CVE-2017-5029
-
web
https://www.suse.com/security/cve/CVE-2018-14404
-
web
https://www.suse.com/security/cve/CVE-2018-25032
-
web
https://www.suse.com/security/cve/CVE-2018-8048
-
web
https://www.suse.com/security/cve/CVE-2019-11068
-
web
https://www.suse.com/security/cve/CVE-2019-20388
-
web
https://www.suse.com/security/cve/CVE-2019-5477
-
web
https://www.suse.com/security/cve/CVE-2020-24977
-
web
https://www.suse.com/security/cve/CVE-2020-7595
-
web
https://www.suse.com/security/cve/CVE-2021-30560
-
web
https://www.suse.com/security/cve/CVE-2021-3516
-
web
https://www.suse.com/security/cve/CVE-2021-3517
-
web
https://www.suse.com/security/cve/CVE-2021-3518
-
web
https://www.suse.com/security/cve/CVE-2021-3537
-
web
https://www.suse.com/security/cve/CVE-2021-3541
-
web
https://www.suse.com/security/cve/CVE-2021-41098
-
web
https://www.suse.com/security/cve/CVE-2022-23308
-
web
https://www.suse.com/security/cve/CVE-2022-23437
-
web
https://www.suse.com/security/cve/CVE-2022-23476
-
web
https://www.suse.com/security/cve/CVE-2022-24836