Actually, you didn't explain they were false positives
I didn't use this term, true. Still, quoting my previous response:
crypto-util is a library by the Jenkins project. The CVE points to Erlang Open Telecom Platform and is pretty obviously unrelated
"SpringSource Spring Framework 2.5.x before 2.5.6.SEC02…" (and you can stop reading right there)
the class was introduced in Spring 3.0.
You deflected and said it wasn't your problem. … It's clearly out of date. Rather than attacking the requestor, could you address the request?
The outdated component is clearly a problem. It is however not a problem in the way you brought up – having these security vulnerabilities. I'm not attacking you, I point out that what you wrote specifically doesn't look like a problem.
As far as I'm concerned (and since you keep bringing up my employer in an unrelated issue tracker, I'm not speaking on behalf of CloudBees), it's simply a matter of effort to benefit. It's almost certain that many plugins will break and require adaptation. And "not getting false positive security scanner findings" isn't the kind of benefit I would want to see for months of effort. In fact, if the issue description is correct and we'd have to update Groovy, it would almost certainly introduce new security vulnerabilities (via Script Security).