Bug 787915 - xml: xmltex hash table collisions CPU usage DoS
Summary: xml: xmltex hash table collisions CPU usage DoS
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: hashdos, oCERT-2011-003 782164 787916
TreeView+ depends on / blocked
 
Reported: 2012-02-07 02:53 UTC by Kurt Seifried
Modified: 2019-09-29 12:50 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-25 20:15:08 UTC
Embargoed:


Attachments (Terms of Use)

Description Kurt Seifried 2012-02-07 02:53:17 UTC
Juraj Somorovsky reported that certain XML parsers/servers are affected by the
same, or similar, flaw as the hash table collisions CPU usage denial of
service.  Sending a specially crafted message to an XML service can result in
longer processing time, which could lead to a denial of service.  It is
reported that this attack on XML can be applied on different XML nodes (such as
entities, element attributes, namespaces, various elements in the XML security,
etc.).

xmltex is written in TeX. xmltex appears to use the "group" array(ish) type to
store XML elements however it is unclear if this is vulnerable, it needs 
investigation.

Comment 1 Kurt Seifried 2012-02-07 02:54:31 UTC
passivetex-1.25-11 uses xmltex

Comment 2 Ondrej Vasik 2012-02-07 06:41:33 UTC
As a side note here, both - passivetex and xmltex packages are almost dead packages. No upstream, no future releases expected and now many upstream applications previously dependent on them started to use different things. Even the docbook stylesheets upstream plans to remove extra hacks for passivetex, so it is likely these packages will fade away soon.

Comment 6 Tomas Hoger 2013-07-25 20:15:08 UTC
I'm wontfixing this.  This issue never really got confirmed, and even if it is confirmed, it's impact does not justify fixing.


Note You need to log in before you can comment on or make changes to this bug.