Get the real story via our monthly newsletter

Search

    2
    0

rss

Send to a colleague

Home > Commentary > Trends Archive > FatWire XSS vulnerability, and the perils of Web 2.0

Browse TrendWatch Blog

Recent Blog Entries

The Complete Archive

Trends by Vendor


TrendWatch by Channel

Web Content Management Trends

Enterprise Portals Trends

ECM Trends

Web Analytics Trends

Enterprise Search Trends

SharePoint Trends

Digital & Media Asset Management Trends

XML & Component Content Management Trends


Report Excerpt

The Web CMS Report 2008 looks at... Content Server's Web Services API

"Java APIs are also exposed as Web Services, with SOAP bindings and WSDL files automatically configured. Like other vendors, however, results in the field using these new APIs have been mixed at best. For one thing, the WSDL files point to JSP pages (so that FatWire can access its tag library) and not actual Java APIs. This limits substantially what you can do and brooks performance problems as well..."

(p. 273)

More about The Web CMS Report 2008

 

TrendWatch Blog

FatWire XSS vulnerability, and the perils of Web 2.0

20-Nov-2007

Andrew Davies of Portcullis Computer Security Ltd reports that an older version of FatWire's Web CMS product, Content Server 6.3.0, exposes cross-site scripting (XSS) vulnerabilities "in multiple locations" in the Web UI, "mainly with the search and advanced search functions." FatWire told Davies that it had already fixed the vulnerability in a patch release.

The vulnerability is of a type where a specially-crafted URL (containing JavaScript) can cause mischief if an unsuspecting user clicks a link containing that URL. Also, just typing something like <script>alert('Hacked!')</script> in a search box will cause a script to execute, reportedly.

Just for kicks, I tried searching for word of the vulnerability on http://developernet.fatwire.com. But the Search box was disabled. Probably wise.

My goal here is not to ding FatWire specifically (and remember, 6.3 is not the latest version of Content Server), but to remind you that, in your quest for customer-facing interactivity, to the extent you turn over dynamic interaction to your Web CMS, you are inheriting their security profile. I think we'll see more of these alerts. Forewarned is forearmed.

Update (29 November): FatWire says that the XSS vulnerability described by Portcullis affects only the administrative search interface, not any UI that can seen by non-admins. A patch is available directly from FatWire.

- Submitted by: Kas Thomas, Analyst

All CMS Channel Trends

Join the conversation

Digg This! Search Technorati Tag it on Del.icio.us



Get a Free Sample

Wondering about CMS Watch research? Sign up to receive free samples of any of our products.




What we do

CMS Watch™ evaluates content-oriented technologies, publishing head-to-head comparative reviews of leading solutions. What makes us special?

  • Our critical analysis exposes product weaknesses as well as strengths
  • We deliver unrivaled technical depth and comprehensive project advice
  • Our research is led by international topic experts
  • We only work for buyers -- never for vendors

Contact us

CMS Watch

info@cmswatch.com

18113 Town Center Drive, Ste 217

Olney, MD USA 20832

1 800 325 6190 (N. America only)

+1 617 763 5336 (customer service)

+1 301 585 7004 (editorial)

Fax: +1 214 242 3048