What it does highlight is the real issue with the use of Open Source tools. BASH is maintained under the auspices of the Free Software Foundation, in practice there is one guy who is responsible for it. His name is Chet Ramey and he works on it on a volunteer basis along side his real job at Case Western Reserve University in the US.
The problem is that because the open source model is meant to ensure that code is peer reviewed by the open source community there is a tendency for people to assume that someone else has done the reviewing and that it must be ok because so many people are using it.
This is essentially what happened with Heartbleed. Only two people actually reviewed the code for Open SSL. And they were the guy who wrote it and the guy who managed the repository for it. Everyone else just went "Ooh, cryptography stuff, thats too complicated for me, I'll just assume someone else has looked at it."
When problems like this arise you have no recourse with a supplier or developer because it's all done on a voluntary basis and you use it at your own risk. Caveat Emptor.
I'm not saying Open Source stuff is bad per se, the Open Source community has produced some of the best software around, but it does mean you need to do your own due diligence on the code you are going to use before you use it, and many large organisations (and small ones ) overlook this and treat it as regular commercial software.