Difference between revisions of "Security Alert Fixes"

From OpenEMR Project Wiki
Line 32: Line 32:


:'''TODO''':
:'''TODO''':
:*Systematically go through the http://osvdb.org/ site to ensure all vulnerabilities have been addressed. (2/20/2013)
:*Systematically go through the http://osvdb.org/ site to ensure all vulnerabilities have been addressed.
<br>
<br>
<br>
<br>
[[Category:Security]][[Category:Developer Guide]]
[[Category:Security]][[Category:Developer Guide]]

Revision as of 22:22, 20 February 2013

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

  • Fixed in most recent 4.0.0 patch and dev version
  • Fixed in most recent 4.0.0 patch and dev version
  • This link is dead.
  • 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 are fixed in most recent 4.1.1 patch and dev version.
  • This item is fixed in most recent 4.1.0 patch and dev version.
  • Fixed in most recent 4.1.0 patch and dev version
  • Fixed in most recent 4.1.0 patch and dev version
  • Fixed in most recent 4.1.0 patch and dev version
  • Fixed in most recent 4.1.1 patch and dev version
  • 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 is fixed in most recent 4.1.1 patch and dev version.
  • The sixth item is fixed in most recent 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.