FLOSSHack is back! The next workshop will be held on January 13th, 2013 from 2pm to 6pm at Free Geek. The workshop's target is OpenMRS, an open source medical records system and platform. An overview of the FLOSSHack workflow can be found on the "FLOSSHack for Participants" page.
The OpenMRS developers recommend that we use version 1.9.2 "Standalone", which is available here. The source code for the 1.9.x branch can get checked out using git with the command:
git clone -b 1.9.x https://github.com/openmrs/openmrs-core.git
For now, the only remote access to the event will be via IRC:
Network: freenode Channel: #flosshack
You are welcome to start looking for vulnerabilities right now. If you do find any vulnerabilities in the application prior to the workshop, please email them to
tim . morgan |at|
owasp . org. That way you get credit for them if you're the first to find a given flaw. At the end of the workshop, there will be prizes for both finding the "best" vulnerability and for finding the most vulnerabilities. Also, be sure to keep any flaws you find under wraps so that way OpenMRS maintainers have some time to correct everything before they are made public.
OpenMRS is an application which enables design of a customized medical records system with no programming knowledge (although medical and systems analysis knowledge is required). It is a common framework upon which medical informatics efforts in developing countries can be built. OpenMRS is implemented in Java and generally is used under Tomcat. It uses Hibernate to interact with a MySQL database for record storage. For more information, see the FAQ.
Ideas for Attacks
Based on observations and conversations with the OpenMRS team, the following vulnerability classes and attack scenarios seem relevant:
- Cross-site Scripting (XSS)
- SQL Injection: While they use Hibernate, HQL injection is worth keeping an eye out for
- Authorization: The app supports a very flexible role/privilege system that is configurable per deployment.
- Platform deployment issues: the standalone installer supports Linux, Mac OS X, and Windows, so some platform-specific weaknesses could crop up.
- REST web services API: this is a new interface that hasn't been tested as well
- SSL-related problems