Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Thu, 22 Oct 2009 15:35:58 +0200
From: Jan Lieskovsky <>
To: "Steven M. Christey" <>
CC: oss-security <>,
        Marc Schoenefeld <>, Joe Orton <>,
        Ondrej Vasik <>, Roman Rakus <>,
        CERT-FI Vulnerability Co-ordination <>
Subject: Regarding expat bug 1990430

Hello Steve, vendors,

   this is due:




    When looking at the patches, while the source code bases (patches)
    are different, the XML reproducer is the same - so is different
    source code sufficient to distinguish the CVE ids, or should
    they be merged?


    The testcases here were provided by CERT-FI and are the
    same as for:

    But different CVE identifiers needed to be used, due the
    fact, CVE-2009-1885 issue was disclosed earlier, than
    other vendors were prepared to release libxml2 updates.

    They also affect different code bases: CVE-2009-1885
    Apache Xerces C++, while CVE-2009-2414, CVE-2009-2416 libxml / libxml2.

    CVE originally assigned to Apache Xerces2 Java (does it embed
    its own copy of expat), but also reported as expat issue here:

    Expat patch:

    The expat library is embedded also in:
      a, w3c-libwww
      b, PyXML

    And probably also in other packages (still need to get the complete list). In this case,
    the reproducer, code base and patch are the same, just the expat library is embedded
    in multiple other products. Two questions remain to be answered here:

    a, Does Apache Xerces2 Java contain embedded copy ot the expat library (i.e. it's
       completely the same issue as in expat, w3c-libwww, PyXML and others) - Marc
       could you help to reply this question?

    b, Can we use CVE-2009-2625 to reference expat, w3c-libwww(expat), PyXML (expat)
       issues too or another one need to be assigned for these? (But the decision
       depends on the answer to previous question).

Hoping this will bring at least a little bit more light into above [1] doubts

Thanks && Regards, Jan.
Jan iankko Lieskovsky / Red Hat Security Response Team

Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.