No, it really does not. It prohibits an exploit hosted on an unknown site from running.
That is quite different from protecting against JS browser vulnerabilities.
Now, if NoScript added JS sandboxing of some advanced variety employing heuristics such that it detected attempts to exploit vulnerabilities and blocked that code (whilst avoiding solving the halting problem!), then I'd consider a weaker form of the statement, such as "NoScript protects against many JS browser vulnerabilities", as true. But AFAIK, it doesn't do anything like that.
It doesn't even employ signature based techniques that could also protect against some vulnerabilities.
That is quite different from protecting against JS browser vulnerabilities.
Now, if NoScript added JS sandboxing of some advanced variety employing heuristics such that it detected attempts to exploit vulnerabilities and blocked that code (whilst avoiding solving the halting problem!), then I'd consider a weaker form of the statement, such as "NoScript protects against many JS browser vulnerabilities", as true. But AFAIK, it doesn't do anything like that.
It doesn't even employ signature based techniques that could also protect against some vulnerabilities.