Security Alert Fixes

Place to record and track OpenEMR security alerts and their fixes (in chronological order from earlier to later):

• Arbitrary Database Creation/Database Enumeration

• Fixed in most recent 4.0.0 patch and dev version

• Local File Inclusion

• Fixed in most recent 4.0.0 patch and dev version

• Reflected Cross-site Scripting

• This link is dead. Bradymiller 20:04, 30 November 2012 (UTC)

• Multiple cross-site scripting

• There are 4 items here:

• The first two items likely still exist. A user needs to be authenticated(logged in) into OpenEMR to be able to do this; note a codebase refactoring is currently underway to fix these types of vulnerabilities.
• The last 2 items will be fixed in next 4.1.1 patch and dev version.

• sql-injection

• This item is fixed in most recent 4.1.0 patch and dev version.

• sql-injection

• Fixed in most recent 4.1.0 patch and dev version

• sql-injection

• Fixed in most recent 4.1.0 patch and dev version

• Multiple Local File Inclusion and arbitrary command execution vulnerabilities

• Fixed in most recent 4.1.0 patch and dev version

• arbitrary file upload vulnerability

• Fixed in most recent 4.1.1 patch and dev version

• Multiple Vulnerabilities

• There are 7 items here:

• The first item is same as the arbitrary file upload vulnerability item reported above and has been fixed in most recent 4.1.1 patch and dev version.
• The second item likely still exists. A user needs to be authenticated(logged in) into OpenEMR to be able to do this; note a codebase refactoring is currently underway to fix these types of vulnerabilities.
• The third item is fixed in most recent 4.1.1 patch and dev version.
• The fourth item likely still exists. A user needs to be authenticated(logged in) into OpenEMR to be able to do this; note a codebase refactoring is currently underway to fix these types of vulnerabilities.
• The fifth item will be fixed in next 4.1.1 patch and dev version.
• The sixth item will be fixed in next 4.1.1 patch and dev version.
• The seventh item is fixed in most recent 4.1.1 patch and dev version.

TODO:

• Systematically go through the http://osvdb.org/ site to ensure all vulnerabilities have been addressed. (2/20/2013)