I read that the theoretical weakness in SSL has been proven real. Is there a workaround that we can apply as users or admins to protect our users/selves?
The hole only allows for data to be injected, if that injection can cause a data leak of some kind, then you'll need to re-work the server side program to ensure that injected data cannot cause the leaking of sensitive information.
That is, the user's session remains secure on the outbound side (that is, server to client), those communications remain secret, the communications from the inbound side (client to server), the data from the client still remains secret as well, however, that data can have information appended or prepended to it by a man-in-the-middle attack.
So, there is no need for a workaround unless your server/service is made to be vulnerable by this type of attack, and if it is, then the workaround would be specific to your web application.
The attack suggests an ability to present data under the trusted credentials of the client which depending on your environment and the uses of the end servers in question could lead to privilege escalation and the like.
The risk is proportional to the data your protecting and the lengths someone would go to to steal it.
Practically the documents suggest little defence. As the problem is an attack from beneath the protocol i.e. below the transport layer then using IPSEC could be an option. This would work best in a closed population of users whereby you have control of the end machines. IPSEC would be less suitable fro an general uncontrolled Internet environment.