Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 26 Feb 2015 14:43:19 -0500 (EST)
Subject: Re: CVE request: Joomla Google Maps Plugin

Hash: SHA1


> Denial of Service / reflection issue (this seems the one akamai is
> most concerned about)

We think the earliest disclosure of this was and it is assigned

> XML injection

We think the earliest disclosure of this was again. We are not sure what set
of impacts would typically have occurred from XML injection within
unpatched versions of this "Google Maps by Reumer" product. The
current version calls libxml_disable_entity_loader. XML injection
could cause a denial of service, in part depending on the version of
libxml2 that is used by the version of PHP. We have assigned
CVE-2013-7429 for this. The ability to place an XSS payload within an
XML document is considered another XSS attack vector (see the next
CVE) disclosed at the same time, and is not within the scope of
CVE-2013-7429. If anyone decides to research older versions of this
product, in order to identify other vulnerabilities associated with
the product's use of the PHP libxml extension, then additional CVE IDs
may be possible.


We think the earliest disclosure of this was again. Use CVE-2013-7430. As
mentioned above, an attack such as <div
xmlns="">[XSS]</div> using a .xml filename
is within the scope of CVE-2013-7430.

> path disclosure

We think the earliest disclosure of this was again. Use CVE-2013-7431.

Two additional vulnerabilities were disclosed on the page, apparently 10 days later in 2013.

Some older versions of the proxy component lack any restrictions on
requests. This issue is not being assigned a CVE ID even though the
researcher lists it as an "Insufficient Anti-automation (IAA)"
vulnerability. In these older versions, the vendor was not trying to
impose restrictions, and imposing restrictions would thus be
considered an opportunity for security hardening, not a vulnerability.
However, the vendor later created a protection mechanism that was
intended to impose these restrictions. The researcher found a way to
bypass this protection mechanism. That is assigned CVE-2013-7432.
Specifically, the way to bypass this protection mechanism is "the
token can be found at page which uses plugin of the site (and it's
setting in URL). This data can be taken from the site automatically."

Also, the researcher provides a new XSS attack vector, a reference to
a .html filename such as url=site/xss.html in the query string. This
is apparently caused by an incomplete fix for the older finding in
which the XSS payload was embedded directly in the query string. Use
CVE-2013-7433 for this later-disclosed XSS variant. (We understand
that url=site/xss.html is conceptually not very different from
url=site/xss.xml - however, we are using separate CVE IDs, in part
because of the different disclosure date.)

Finally, the researcher disclosed one new finding in 2014 in the post. This new finding
is a variant of CVE-2013-7428, but applies specifically to the case
where the attacker controls a subdomain of the victim's domain name.
Use CVE-2014-9686. The researcher gives an apparently realistic
example in which the attacker controls and the
attack target is the web site.

For this issue, one might argue that the attack involving the
plugin_googlemap2_proxy.php filename and the attack involving the
plugin_googlemap3_kmlprxy.php filename have different affected
versions and could have separate CVE IDs. We have decided to use only
one CVE ID because the security problem is caused by the same code in
essentially the same place, even though the file was renamed and
modified somewhat.

- -- 
CVE assignment team, MITRE CVE Numbering Authority
M/S M300
202 Burlington Road, Bedford, MA 01730 USA
[ PGP key available through ]
Version: GnuPG v1.4.14 (SunOS)


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.