Bug 1212000 - VUL-0: CVE-2023-34411: alacritty: xml-rs: denial of service via an invalid <! token (such as <!DOCTYPEs/%<!A nesting) in an XML document.
Summary: VUL-0: CVE-2023-34411: alacritty: xml-rs: denial of service via an invalid <!...
Status: RESOLVED FIXED
Alias: None
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents (show other bugs)
Version: unspecified
Hardware: Other Other
: P3 - Medium : Major
Target Milestone: ---
Assignee: Avindra Goolcharan
QA Contact: Security Team bot
URL: https://smash.suse.de/issue/368371/
Whiteboard:
Keywords:
Depends on:
Blocks: CVE-2023-34411
  Show dependency tree / graph
 
Reported: 2023-06-05 09:24 UTC by Thomas Leroy
Modified: 2024-07-02 14:11 UTC (History)
2 users (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

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

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Leroy 2023-06-05 09:24:26 UTC 
+++ This bug was initially created as a clone of Bug #1211996 +++

CVE-2023-34411

The xml-rs crate before 0.8.14 for Rust and Crab allows a denial of service
(panic) via an invalid <! token (such as <!DOCTYPEs/%<!A nesting) in an XML
document.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-34411
https://www.cve.org/CVERecord?id=CVE-2023-34411
https://github.com/00xc/xml-rs/commit/0f084d45aa53e4a27476961785f59f2bd7d59a9f
https://github.com/netvl/xml-rs/commit/c09549a187e62d39d40467f129e64abf32efc35c
https://github.com/netvl/xml-rs/compare/0.8.13...0.8.14
https://github.com/netvl/xml-rs/pull/226
Comment 1 Thomas Leroy 2023-06-05 09:25:06 UTC 
openSUSE:Factory/alacritty embeds a vulnerable version of xml-rs crate.
Comment 2 Camila Camargo de Matos 2024-07-02 14:11:33 UTC 
I will be closing this bug as RESOLVED as it seems like openSUSE:Factory/alacritty has been updated such that now it embeds xml-rs at version 0.8.20, which is already fixed for the issue.