|
Dreamweaver Database Connection Script Security Issue
|
|
Secunia Advisory:
|
SA11284
|
|
|
Release Date:
|
2004-04-05
|
|
Last Update:
|
2004-04-06
|
|
Popularity:
|
8,853 views
|
|
|
Critical:
|
Not critical
|
|
Impact:
|
Security Bypass
|
|
Where:
|
From remote
|
|
Solution Status:
|
Vendor Workaround
|
|
| Software: | Macromedia Dreamweaver MX
Macromedia Dreamweaver MX 2004
Macromedia Dreamweaver UltraDev 4
|
|
|
Subscribe:
|
Instant alerts on relevant vulnerabilities 
|
|
Description:
Macromedia has issued an advisory regarding a security issue in Dreamweaver, potentially allowing malicious people to manipulate databases.
The problem is that "Using Driver On Testing Server" and "Using DSN on Testing Server" causes Dreamweaver to upload a script, which can be exploited to query valid DSNs and issue SQL queries.
This is not considered a vulnerability, as it is clearly stated that the functionality is intended for test systems.
The issue affects:
* Dreamweaver MX 2004
* Dreamweaver MX
* Dreamweaver UltraDev 4
Solution:
Remove the script from production systems.
Macromedia has published a technote with further details:
http://www.macromedia.com/support/dreamweaver/ts/documents/rem_db_security.htm
Provided and/or discovered by:
The vendor credits David Litchfield, NGSSoftware.
Changelog:
2004-04-06: Added link to NGSSoftware advisory.
Original Advisory:
Macromedia:
http://www.macromedia.com/devnet/security/security_zone/mpsb04-05.html
NGSSoftware:
http://www.nextgenss.com/advisories/dreamweaver.txt
|
|
|
Track this Secunia Advisory
|
Customers of the Secunia Vulnerability Intelligence solutions will automatically receive updates when new information regarding this advisory is released.
Read more about our Vulnerability Intelligence solutions and what they can do for you and your company.
|
|
|
About this Secunia Advisory
|
Please note: The information that this Secunia Advisory is based on comes from a third party unless stated otherwise.
Secunia collects, validates, and verifies all vulnerability reports issued by security research groups, vendors, and others.
|
