Yes, server and client were announcing the same version at the time, probably 3.8-dev. As such I can see how it can be considered a corner case - based on Softcoders' reply I think this will probably never affect releases, just development versions of servers. We should be aware, though, that this may also allow for targetted denial of service attacks with the goal to make some server unusable.
I'm not into network protocol design, but basically I would think that servers need to always ensure they will not be affected by any kind of unexpected / false information sent from a client. And that a version string sent by a client should be treated as no more than an indication. Compare this with web server or web application and User Agent string or Referer header. The web application should never rely on those to be correct, and an incorrect value there should not allow the server side to go into a state which prevents it from delivering service, and which it is unable to recover from.
Having said this, I still agree this is less serious and not urgent, since it seems unlikely that someone will want to exploit this anytime soon.
