To prevent cross-site scripting, it's important to encode data before outputting it.

Up until now, it has been quite hard to ensure you're encoding everywhere throughout your app.

It's great to see the new syntax in ASP.NET 4 to automatically encode:

First Name: <%: Model.FirstName %> Last
Name: <%: Model.FirstName %><formmethod="post"><%: Html.TextBox("FirstName") %><%: Html.TextBox("LastName") %></form>

(From Phil Haack's blog)

This means that for all new web applications, you can build using <%: %> instead of <%= %>, which is great for ASP.NET MVC applications where that syntax is common.

For older applications you will be able to opt in to the new encoding syntax, but your old code will keep working exactly as it already does (perhaps insecurely, if you're not encoding!)

Here's hoping that we'll be able to replace the standard HtmlEncode with the AntiXSS goodness I described here:

• What is encoding? Cross site scripting and the AntiXSS encoding methods

Kirk

Daniel presented this talk at the Wellington Silverlight user group last Wednesday.

I enjoyed this talk. Daniel went back to basics and showed how to get up and running with Silverlight and WPF development, covered the various layouts you can use in XAML, and went through some of the fundamentals of how XAML and code interact.

I think the part I most appreciated was the content that Daniel left out of his talk. He was very well prepared, and had intentionally kept things simple, which is hard to do when you have deep technical knowledge and enjoy sharing it - I struggle with keeping my talks focussed without diverting on a tangent.

Well done Daniel, I'm looking forward to your next talk!

Kirk

I attended Richard's Domain Driven Design introduction at the Wellington .NET user group back on the September 23.

Richard introduced Domain Driven Design and the motivations behind using it, covered the 'building blocks' and then gave some examples of how to put it in practice.

Richard has blogged the details of his talk here: Slides from my Domain Driven Design 101 Talk

I enjoyed Richard's slide deck, and his presentation style - simple slides so that my focus was on what he was saying. The parts of his talk that I took the most out of were the encapsulation of business logic into Specifications (different from the testing concept), and the explicit anti-corruption layer when interfacing with any external system.

Thanks Richard!

Kirk

We got some great feedback from attendees at this year's Code Camp in Auckland. I thought I'd share some stats from the survey sent to attendees.

We counted 300 people there at one time, so we estimate somewhere between 300 and 350 people came along for sessions during the day. Note that approximately half of the attendees responded to the survey that these figures were drawn from.

We had three streams: Development, SQL and Security.

Attendance was roughly:

• Development: 68%
• SQL: 19%
• Security 13%

Although, people could switch between streams as they wished.

Did you also go to TechEd?

• Yes: 30%
• No: 70%

How did you find out about Code Camp?

• dot.net.nz mailing list: 23%
• Co-worker: 35%
• MSDN Flash Email: 22%
• via a blog: 5%

Session feedback:

• 94% of session feedback was in the range 'satisfied' to 'very satisfied'
• 40% of feedback was 'very satisfied'

Regions:

• 85% from Auckland
• 4% each from Wellington and Bay of Plenty
• 3% each from Waikato and Canterbury

User groups:

• 51% of people attend one or more of their local user groups
• To the remainder: come along and join us!

The presenter with the most feedback on his sessions was the AWESOME Ivan Towlson.

We got lots of great general comments, here are a few:

Great work guys! Thoroughly enjoyed.

Really enjoyed the day - thanks guys!

Thanks for the opportunity for those of us who could not attend TechEd

I am a sole operator / consultant with very limited budget, so "free" events are really appreciated.  I am very happy to dedicate my time to attendance at events that are run as well as this was.  Thanks again.

We appreciate international visitors giving up their mornings to our benefit

I really enjoyed every session and thought that each one had a valuable piece of information to take away - well done!

Thanks everyone for your feedback (good and bad constructive), we'll use it all to help make the next community Code Camp even better!

To find out about future Code Camps, and user group events in your area, please visit the dot.net.nz website and sign up to a mailing list.

Kirk

I'm happy to be presenting two sessions at TechEd this year. It would be great to see you there!

DEV304 Visual Studio Team System 2010: Odyssey Two

Presenter: Kirk Jackson

Tue 9/15 | 17:10-18:25 | Ballroom 1

Visual Studio 2008 is the best and most productive development environment ever! Microsoft have been busy the past couple of years putting even more great features into your favourite tool, and in Visual Studio 2010 we'll be seeing: new programming languages; diagramming tools and visualisers; new project types; and enhancements to the IDE. Come along and hear about these great features, and learn some new tips to help you make the most of Visual Studio 2010!

SEC313 Hack-Ed: Teaching the Good Guys Bad Tricks

Presenters: Kirk Jackson, Andy Prow

Wed 9/16 | 12:10-13:25 | New Zealand Room 2

You can't fight a war that you don't know you're waging. You can't defend your website against attack unless you know the tricks that the bad guys will use.

Join the "Flight of the Pwnchords*" and learn the tricks that Andy "the hacker" will use and watch as Kirk "the developer" tries to defend his ASP.NET website against them. By the end of this session you will have an understanding of some of the common attacks, such as Cross-Site Scripting (XSS), Cross-Domain Request Forgery (CDRF), and will have an appreciation of how layering your defenses (defense-in-depth) can help protect you from exploit chaining.

The session will also give you some practical tips that you can apply straight away in Visual Studio 2008 to help you build secure websites.

(* AKA "New Zealand's fourth most popular comedy hacking duo")

Cheers,

Kirk

Visual Studio 2010 will have better support for a multi-monitor setup, but it's possible to get part of the way in 2008 already.

Toolbars and property windows (e.g. Solution Explorer, Class View) can be dragged into separate windows (2010 will add the ability to drag documents into separate windows too):

Window positioning gets a bit weird when you switch from one monitor to another, or change resolutions - a common occurrence when you're a laptop user docking and un-docking.

You can create two settings files, one for your single monitor layout, and one for your multi-monitor layout, and use them when starting Visual Studio 2008:

1. Arrange your windows the way you like them
2. Go to Tools > Import and Export Settings > Export selected environment settings
3. You get a great tree-view of every possible setting category in Visual Studio. Click the top node to deselect everything, and scroll down and select only General Settings > Window Layouts:
   
4. Save your settings file somewhere handy (e.g. d:\multimon.vssettings)
5. Repeat for each layout you like

Now you have two or more settings files, you just need to create a shortcut icon for each one somewhere in your start menu.

Edit the target, and add the parameter /resetsettings D:\multimon.vssettings to the end (replace the path with each settings file path).

Now when you launch your new shortcut, it will start Visual Studio 2008 with the correct window layout. Because you only exported and imported the Window Layouts, all the other settings stay the same.

You may also want to make these changes to your shortcut:

• Add the /nosplash parameter to your Target, to avoid the "Visual Studio" splash screen and make it slightly faster to start (perception is everything!)
• Check the Run as administrator option, which is useful if you often need to restart Visual Studio to connect to the ASP.NET worker process when developing under IIS.

Cheers,

Kirk

Previous VS2008 Tips:

• Visual Studio Tips n Tricks (DEV313)
• Visual Studio - Copy references
• Turn off outlining / regions in Visual Studio
• Visual Studio 2008 tip of the day - relive the series
• Explore files from Visual Studio
• Snippet Designer released
• Ctrl + . -- Bring up that annoying smart tag menu
• Temporary Projects - You don't have to save them
• Christchurch - Visual Studio Tips'n'Tricks
• Visual Studio - Regedit your tab ordering and add a column guide

Code Camp is less than two weeks away!

If you want to catch some free sessions on the state-of-the-art in .NET development, SQL Server and developer security then sign up for Code Camp Auckland 2009 now.

Code Camps are non-profit, and organised by members of the local developer community. This year the Auckland Code Camp is the day before TechEd (Sunday 13 September), so we've managed to nab a few great speakers on their day off to present to us.

It's the biggest Code Camp ever - over 14 hours of sessions across 3 streams from 10am till 5pm:

Development...

• What's Happening in .NET Languages and Why Should You Care?
• .NET on the iPhone and Beyond
• Behaviour Driven Development
• Domain Specific Languages
• C# 4.0 new features
• Silverlight with Prism
• Becoming Certified
• Lightning Talks
• and more!

The latest and greatest in development topics, by the people that know!

SQL Server?

• SQL Server Virtualisation Best Practices and Recommendations
• SQL Server Analysis Services and Gemini
• Query Optimization and Query Tuning
• Understanding SQL Server Indexing
• SQL Server Maintenance

Training and guidance from the best SQL trainers in the industry!

Security!

• Secure Development Lifecycle and Threat Modelling workshop
• Secure Coding Practices

We are lucky to have Michael Howard, author of Writing Secure Code and 24 Deadly Sins of Software Security giving a free workshop for developers, architects and team leads on Threat Modelling and the Secure Development Lifecycle. This will be followed by a session on how to write secure .NET code.

Auckland has never seen such an awesome free event!

Presenters that are offering their time include Greg Low, Nicholas Dritsas and Auckland's Alex Henderson of Architecture Chat fame.

To cover the costs of the event, we have the help of our generous sponsors: Microsoft, Datacom, Intergen, INETA and Xero.

All that's left for you to do is to visit the website for more details, and sign up now!

See you there on Sunday 13 September,

Kirk

Today at the Wellington .NET User Group, Kevin presented a talk on "Windows Mobile 6.5 Widgets".

Kevin has kindly provided his slides and samples for download:

I found this interesting. I haven't developed any applications for Windows Mobile, though I have played around a bit with the emulator and deploying code from within Visual Studio.

Widgets seem like a lot simpler application development model than native or compact framework applications. The application development model is similar to Vista sidebar gadgets, as there is a packaged zip file containing the application inside - and the application is 'simply' Javascript and HTML. Widgets can use XHR or DOM manipulation, and have access to a small amount of local storage to store preference information.

Windows Mobile 6.5 treats widgets as first-class application citizens within the OS - they have icons on the revamped start screen, and appear in the uninstall screen. As far as the user knows, they are the same as a native application.

Where the process is currently let down is in deployment and debugging. Currently a widget can only be deployed through the Windows Mobile marketplace, after the developer has signed up and the application has been reviewed (I think!). Debugging from Visual Studio seems non-existent, meaning that development is through trial and error.

I could see an enterprising person (like Kevin) building a Javascript library that simulated the API provided by the widget infrastructure, so that widgets could be developed and tested on a desktop before being deployed on a device. Kevin, am I right that all that is needed is the Widget object and some fake ActiveX controls?

All up, an interesting session.

Cheers!

Kirk

Today I went to Nelson for lunch, and presented on Caching to the Nelson .NET User Group.

The talk was a repeat of my Wellington and Auckland talk from a few months ago, and covered various places you typically cache data in a .NET app, motivating the discussion of memcached and Velocity.

It was nice to get down to Nelson to briefly soak up the sun and meet a few new people.

View my previous post on Caching for further info.

Thanks for having me Daniel!

Kirk

So this was a few weeks ago, but I thought I would post some notes here anyway.

Bevan gave a talk at the Wellington .NET User Group titled "Towards Supportability" (view his slides and notes).

Apart from marvelling at his good looking slides, the main thing I took away from his talk was the points he made on documentation. Bevan gave an approach for document systems for the person fighting the fire when all hell breaks loose. When a system is broken, and people are all over the poor systems administrator to fix it, they don't need thick architecture documents, they need something quick and actionable.

The 'Supportability' document structure:

• Architecture - a summary of physical deployment
• Symptoms - a list of failure modes that users might encounter
• Actions - possible remedies
• Procedures - step by step instructions for common procedures
• Reference - additional reference material

The most important parts are the symptoms and actions - how to diagnose what's wrong and how to recover from it.

Cheers Bevan!

Kirk

There's a lot of technology groups in Wellington. I decided to get together a list of all of them so that we could see if we clash on our regular meeting days. Please let me know if your group is missing, or the details need updating.

Most of these groups run free events with the support of their sponsors!

Form more info about geek events in Wellington, head over to wellington.geek.nz or dot.net.nz.

Microsoft technology focussed:

• Wellington .NET User Group: First and Third Wednesday of the month
• Wellington SQL: Third Thursday of the month
• Wellington Sharepoint: Last Wednesday of the month
• Wellington Dynamics: No fixed day, normally near the end of the month
• Wellington Infrastructure: Monday night, once every 2 months
• Wellington Silverlight: Monthly
• Wellington Team System: Bi-monthly
  

Other technologies:

• OLPC Friends in Testing: Saturday mornings
• Wellington Python User Group: Second Thursday of the month
• Erlang Users Group: first Thursday of the month
• Wellington Perl Mongers: second Tuesday of the month
• Wellington Creative Suite User Group: First Tuesday of the month
• Flex User Group: Second Wednesday of the month
  
• Wellington Java user group: third Wednesday of the month
• WellRailed
• Wellington PHP Group
• WellyLUG Linux User Group: Third Wednesday of the month
• Wellington Macintosh Society: Mondays
• Wellington Agile Professionals Network: Mondays
• Wellington Novell Users International: Monthly
  

Technology 'agnostic':

• Wellington Geeks Lunch: Tuesday lunchtime
• Unlimited Potential: various days of the month
• NZ ICT - voice of industry
• Wellington Solution Architects Forum: lunchtime
• Wellington's Web Design & Dev Meetup
• Thursday Night Curry: Thursday evenings
• Information Security Interest Group (ISIG): Last Thursday of the month
• Technical Communicators Association: Last Monday of the month
• Test Professionals Network
• NZ Computer Society

Happy Geeking!

Kirk

Craig, Owen and I (all from Xero) went along to the Wellington Summer of Code session last night to demo Visual Studio, the .NET runtime and ASP.NET MVC to 30-ish eager and willing University Students.

It was an interesting time. Allfields hosted us in a couple of their training rooms, which was pretty cool as the students got to follow along using their own copies of Visual Web Developer. The Allfields facility is pretty good - each room had about 20 PCs for students to use, and the guys there set up a video link between the two rooms.

Students: If you're got .NET questions, be sure to sign up to the dot.net.nz mailing lists.

I'm looking forward to meeting with the students again as the programme continues, and hopefully work with one of them at Xero!

Kirk

If you store, transmit or process credit card data, PCI applies.

How can OWASP help you with PCI compliance?

Credit card data:

• Primary Account Number (PAN): Can store it, but protection required.
• Can never store the CVD 3 digit number or mag stripe

Card data attacks have been increasing in sophistication.

PCI-DSS affects anyone who transmits, processes or stores payment card data. E.g. merchants, service providers (e.g. Paymark, DPS).

Look at 12 requirements of PCI-DSS (firewalls, storage etc)

Protecting stored data:

You must not store sensitive authentication data. Principle: if you don't need it, don't store it. Consider outsourcing, truncation, tokenisation.

Tokenisation: Replace PAN with a unique identifier "token"

Truncation: don't store all the data (e.g. first 4, last 4 digits)

Encryption: Encrypt at point of capture, only decrypt when required, use industry standard encryption, protect your keys.

Developing secure applications / Test app was built securely / Use secure coding guidelines:

Standard OWASP guidelines

Annual risk assessment:

Every year, new threats will affect your site. Go and re-assess against the new threats.

Fixing legacy systems: make sure no old data is lying around.

Real life example: it's very easy to mess up (example of reverting to old code)

Parting thoughts: achieve, maintain and validate compliance. Secure development is a key activity. OWASP is a good source. Reduce storage of PAN data.

Bug chaining - an idea that hasn't really propagated yet.

How do we rate how severe a bug is? Consider how easy it is to exploit, where it is accessible from (client-side, server-side, internet, local, mass exploitable, targeted exploit, etc).

Audience attempted to rate the severity of a couple of bugs:

• SQL injection on authenticated site -> medium/high
• File upload php files on authenticated site -> high/critical
• Local file disclosure -> medium/high
• XSS - reflective, authenticated -> low/medium

Is attacker considered 'authenticated' once there is an XSS attack? Any subsequent attacks can be treated as authenticated.

When you join together the XSS bug with the file upload bug, then it's critical!

Bug chaining: taking multiple bugs and chaining them together to create exploitable vulnerabilities. Instead of looking at each individual bug, look at how they can be combined together.

There are now frameworks to help chain together exploits - and this is how a lot of worms now work.

Recent examples of chaining exploits: PHPMyAdmin <= 3.1.3; SugarCRM <= 5.2.0e - compromise server through 3 bugs together.

How to deal with this? CVSSv2:

• Common Vulnerability Scoring System v2.0
• Scoring system for assessing bugs
• Considers exploit complexity, application location, authentication, target likelihood etc
• Can be very complex, time consuming, difficult to follow

"You can explain this stuff all day, but when network admins actually see you do it, that's when they understand" Brett Moore

VtigerCRM - large open-source CRM system which fixed problems with a security patch, but don't link to the fix (and haven't installed it themselves!).

He wrote a BeEf module for VtigerCRM that can run as an auto-run module (took less than 2 hours to write):

• Chains file upload and XSS bug to upload a malicious PHP script to start a command shell
• Connection is from server to the attackers machine, so user doesn't need to stay connected

Summary:

Don't look at severity of individual bugs - need to look at how bugs can be joined together.

Understand the bugs.

Follow the OWASP coding and testing guidelines.

Tools:

• BeEf - command console for an attacker to run script on the client computer. Modular list of exploits, and control multiple victims. Autorun modules to automatically execute modules within 1.5-2 seconds.

Firefox extensions: They're just software, like ActiveX. Extend, modify and control the browser.

Firefox extension points:

• XUL: XML user interface language
• XBL: XML Binding Language - logical behaviour of widgets
• XPCOM: Reusable components, interface to file system etc.
• XPConnect: Allows Javascript to connect to XPCOM
• Chrome: Special browser zone that is fully trusted by firefox - code is fully trusted, has access to filesystem, user passwords etc.

Mozilla security extension model is non-existent. All extensions are fully trusted by Firefox - no boundaries between extensions, they can modify each other without the user knowing. Can be coded in C++ and subject to memory corruption etc.

Extensions are very popular (billion downloads) and can be found everywhere - social networks, search engines, software packages (skype, anti-virus), anti-phishing toolbars.

Biggest problem is the human side of things - Addins.mozilla.org recommend extensions and add a 'recommended' icon next to them. Extension source code isn't read by third parties ("It's not the linux kernel").

There's no protection from an extension with a security problem, it will bypass any other phishing / malware protection extensions.

Extensions aren't signed (even the Mozilla ones), so we can't rely on people checking signatures.

If an extension is originally trusted, then subsequent updates won't go through the same review process.

No current guidelines for testing a Firefox extension, so security-assessement.com havce come up with their own methodology (whitepaper to be released this year, early next year):

• Isolated testing: Only test one extension at a time, on different OSes with different Firefox versions.
• Information gathering: How does the extension work, how is it installed? Look inside the extension package (a zip file) and look for malicious files (e.g. .exe, .msi etc)
• Look for XPInstall API functions that are dangerous (e.g. executing code on install)
• Look for suspicious files in the extension folder (e.g. softlinks to other directories)
• Look inside install.rdf - some tags can hide extensions so they don't appear in the addon manager
• Extensions can have the same description as other installed extensions, so two appear in addon manager
• Does the extension try to trick the user into thinking it's verified?
• Look for pointers outside the extension, or flags that expose the extension object or content to untrusted code (e.g. contentaccessible=yes or xpcnativewrappers=no)
• Extensions can be merged into the firefox UI - e.g. top toolbar, bottom status bar. They can also modify existing buttons e.g. Reload, Back, Forward or Home button.
• Use the extension. Check the DOM of a test page with the extension loaded (they used mozreply to do this)
• Debugging: can set breakpoints using Javascript debugger.
• Sandbox: can be sidestepped by replacing code inside the sandbox or evaluating it from outside
• XPCOM components: .dll or .so - compiled code that the extension may ship with, or may use existing components on the machine. May need to review source code or decompile. A bunch of components to watch out for.
• wrappedJSObject: removes the protection of the XPComComponent, so they are avoiding the firefox protection.
• Watch out for callback functions, which may be replaced / modified
• window.OpenDialog: Opens any URI with elevated chrome privileges
• Auth: Some expose credentials in plain text, e.g. GET or basic auth
• Auth: Some expose functionality via javascript that can side-step normal process
• Skype extension - a javascript call that any web page can use to start dialing your skype to any
• XSS: Watch out for XSS issues - can execute in the chrome zone from DOM events, embedded XSS, recursive iframes
• XSS: Extensions loading external scripts

They have applied their methodology to different extensions, and some responses have been slow or non-existent!

Here are some extensions that were demoed and had problems. They are all common or Mozilla recommended (all these have been fixed):

• FireFTP: Could include malicious code in the welcome method of an FTP server, and the browser would execute it. Showed a proof of concept sending the contents of win.ini to a different server, and using BeEf to control client.
• CoolPreviews: Susceptible to XSS if a data:// URI is used. Showed a remote code execution when right-clicking on a link and previewing it with CoolPreviews.
• WizzRSS: HTML and Javascript in the <description> tag of RSS feeds is executed in the chrome zone. Showed a reverse shell onto the Windows machine from a malicious users machine.

Extension developers and vendors haven't got a security disclosure process yet - they don't know how to deal with the issues yet. Some extensions don't even publish an email address for the author.

Tools:

• Firebug
• MozRepl
• BeEf - command console for an attacker to run script on the client computer.