Adding to Priyank and BKBK's responses, you haven't said what was the "vulnerable" file that was found by your sec folks. Please let us know.
I'd be surprised it was the bundlesdependency.json file. That just lists what package jars COULD be installed. As bkbk noted, your log line indicates you have update 17 of that awslambda package. Indeed, it's not even clear that that package is your real concern. I sense instead that you just found that referenced in the json file and your raised it as an example. Please confirm.
Again, that file holds the names of ALL packages and their jars, as are available in the bundles folder, and as were placed there by the download of an update.
And while you COULD edit the json file to remove old references, that's not "where" any vuln is going to be, per se (that file). And while the jars in that bundles folder are pointed to by that file, even THOSE are not going to themselves be a vuln, because cf does not "load all files there" at startup, nor are they accessible to cf code. That's important 5o note.
Instead, those files are used by cf to IMPLEMENT whatever package you choose to INSTALL within cf, whether via the CFAdmin page as bkbk noted, or via the cfpm cli tool. In other words, even if some old package is NAMED in that file or EXISTS in that bundles folder, that doesn't itself indicate that any sec vulnerability. What's INSTALLED is what matters.
Sadly, a lot security people or tools "don't care" to consider this: to them if a vulnerable file exists anywhere Ona server, they want it gone. It's a rather hamfisted approach, but they often are responsible for many apps on a server--and indeed often many servers. They may "not have time" to know such facts or even to consider them, though sometimes you might get them to do so.
Assuming you could not, then as BKBK noted, if you WERE to try to remove such references in that json file (or files in that folder), you and your folks need to understand that you'd lose the ability to downgrade to the older updates they relate to. And even if you/rhey KNOW you'd "never want to downgrade", you'd have to be VERY careful in such editing or removal. It's nothing Adobe provides for or documents that I know of.
This brings me back to my original question: what's the actual vulnerability that your scan found? All this may be unrelated to the real solution to that problem. As always, just trying to help. No condescension intended at all.
/Charlie (troubleshooter, carehart.org)
1 Correct answer
6
Replies
AdChoices