[prev in list] [next in list] [prev in thread] [next in thread] 

List:       oss-security
Subject:    [oss-security] Re: CVE-request: Dewplayer issues
From:       cve-assign () mitre ! org
Date:       2013-12-30 16:16:25
Message-ID: 201312301616.rBUGGPZ0009399 () linus ! mitre ! org
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> PoC: /wp-content/plugins/advanced-dewplayer/admin-panel/download-file.php?dew_file=../../../../wp-config.php
> 

Use CVE-2013-7240 for this dew_file directory traversal issue.

> Assigning one CVE for vulnerability in different software components e.g.
> libraries used in WordPress plugins makes it very difficult to coordinate
> updates with end-users. Examples:
> http://osvdb.org/83413
> http://osvdb.org/90374

When a vulnerability originally came into existence through a single
action of a single developer, we currently don't like to assign
multiple CVE IDs on the basis of the vulnerable code later being
shipped in many separately maintained products. We can enter an
internal issue report about the effect on CVE usability because of this
"difficult to coordinate" observation.

> PoC: http://example.com/wp-content/plugins/flash-player-widget/dewplayer.swf?mp3=http://example.mp3
>                 
> PoC: http://example.com/wp-content/plugins/advanced-dewplayer/dewplayer.swf?mp3=http://example.mp3
> 

Just to clarify: the dewplayer.swf file is thought to be essentially
the same in these two cases, and you're asking for two different CVE
IDs to be assigned? It seems very unlikely at this point that we can
provide more than one CVE ID for those, but we just wanted to confirm
that we're answering the right question.

> Q: Does content spoofing issues normally get CVE as the risk is probably
> minimal?

If we think the vendor's security policy is that dewplayer.swf should
not be able to reference off-site media files in this way, then the
issue is currently eligible for a CVE assignment. We're not sure that
a spoofing impact would be the primary motivation for changing this.
Perhaps a stronger motivation is that the vendor doesn't want
dewplayer.swf to trigger arbitrary outbound TCP traffic from the web
host, possibly including traffic to intranet servers in some
environments.

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

iQEcBAEBAgAGBQJSwZu2AAoJEKllVAevmvmsuWoIAI3mI5Yc4YxnJH2Fds04k9LJ
bwSMONh+1rxxnjImg864NJAPTCEWKoCdczV+5kMK8TL5puu8vM352hBixtJ/Tq9q
vsxGWxwV1v/yIPkSAorxYJ1yhCmLj3KXunwujmc4qQUcMr0OCPb4ITdKps58mt9d
aR+rNy31nrtwc1uJIa5OXg//Fp6jE877hWBFBKTzcLwMdVNqSzDzhW6KdqKWJEG8
JMxQ1o6qHz4h6mm34m+vQn45Qbt6KroiVgkNgXfP5FaJNWRONsvj2WYbrRyhE0/i
u3JKfuquPCKtjDocBdeihdHjwiNE93M1x6swaZ1jpcrF0pjT7NAFKDQk8S/emVA=
=ykRj
-----END PGP SIGNATURE-----


[prev in list] [next in list] [prev in thread] [next in thread]