Tóm tắt nhanh
- CVE-2022-39353 là lỗ hổng mức NGHIÊM TRỌNG (CVSS 9.8) ảnh hưởng xmldom (xmldom project), @xmldom/xmldom, xmldom.
- Xác suất bị khai thác trong 30 ngày tới (EPSS): 1.6%, cao hơn 75.3% các lỗ hổng khác.
- Cách xử lý: cập nhật lên 0.7.7, 0.8.4, 0.6.0, 0.9.0-beta.4 hoặc mới hơn.
| Gói / sản phẩm | Phiên bản bị ảnh hưởng | Phiên bản đã vá |
|---|
| xmldom | = 0.9.0≥ 0.7.0, < 0.7.7≥ 0.8.0, < 0.8.4< 0.6.0
| 0.7.70.8.40.6.0
|
| @xmldom/xmldom npm | ≥ 0.8.0, < 0.8.4≥ 0.9.0-beta.1, < 0.9.0-beta.4< 0.7.7
| 0.8.40.9.0-beta.40.7.7
|
| xmldom npm | ≤ 0.6.0
| Chưa có bản vá |
Mô tả
Impact
xmldom parses XML that is not well-formed because it contains multiple top level elements, and adds all root nodes to the childNodes collection of the Document, without reporting any error or throwing.
This breaks the assumption that there is only a single root node in the tree, which led to https://nvd.nist.gov/vuln/detail/CVE-2022-39299 and is a potential issue for dependents.
Patches
Update to @xmldom/xmldom@~0.7.7, @xmldom/xmldom@~0.8.4 (dist-tag latest) or @xmldom/xmldom@>=0.9.0-beta.4 (dist-tag next).
Workarounds
One of the following approaches might help, depending on your use case:
- Instead of searching for elements in the whole DOM, only search in the
documentElement.
- Reject a document with a document that has more then 1
childNode.
References
For more information
If you have any questions or comments about this advisory:
Mô tả của NVD
xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) `DOMParser` and `XMLSerializer` module. xmldom parses XML that is not well-formed because it contains multiple top level elements, and adds all root nodes to the `childNodes` collection of the `Document`, without reporting any error or throwing. This breaks the assumption that there is only a single root node in the tree, which led to issuance of CVE-2022-39299 as it is a potential issue for dependents. Update to @xmldom/xmldom@~0.7.7, @xmldom/xmldom@~0.8.4 (dist-tag latest) or @xmldom/xmldom@>=0.9.0-beta.4 (dist-tag next). As a workaround, please one of the following approaches depending on your use case: instead of searching for elements in the whole DOM, only search in the `documentElement`or reject a document with a document that has more then 1 `childNode`.
Bạn đang dùng một trong các sản phẩm này? Quét site để biết có đang lộ phiên bản có lỗ hổng không.
Quét site miễn phí