In theory the RealPlayer AutoUpdate should run and get you up-to-date, according to their privacy page: A background update check may happen automatically and without advanced notification if RealNetworks deems a critical update is required, such as for urgent security patches and bug fixes.
In practice, if you know what realsched.exe is, and you've disabled it, you should go and update RealPlayer yourself, from the application itself or by downloading a fresh copy at at Real.com
It's not trivial for me at least to understand how SecBrowsing can help users identify if they are running a vulnerable version right now. Their versioning system is quite confusing. Here's a snippet of the vulnerability report from RealPlayer for Windows
- RealPlayer SP 1.0.2 - 1.0.5
- RealPlayer SP 1.0.0 and 1.0.1
- RealPlayer 11 (11.0.5 and higher)
- RealPlayer 11 (11.0.1 - 11.0.4)
- RealPlayer 11 (11.0.0)
- RealPlayer 10.5 (188.8.131.525)
- RealPlayer 10.5 (184.108.40.2060-220.127.116.113, 18.104.22.1688, 22.214.171.1241)
- RealPlayer 10
- RealPlayer Enterprise
Which makes Mozilla's effort in building a Plugin Directory with version history a more viable solution to our "latest good version" solution. Mozilla also offers APIs to this service, for other browsers to use even, which is great.
I'm still skeptical on whether we'll be able to identify all these arbitrary versions from the browsers without some help, going forward at least, from the plugin vendors.