Splunkbase blocking issues for cloud vetting v4.1.0 #45
Comments
The JS vuln seems to refer to appserver/static/js/build/common.js. This doesn't seem like something to patch manually so I'll wait for a new version of the Splunk add-on builder before looking at this again. |
Do you already have the solution for the I'm assuming that if I took the current release and moved it to a local search head (from web), I'd lose all the KVstore context about prior messages, so I'm eager to get this cloud-vetted. |
Yes |
Does this seem like a jQuery solution? I see a few posts in https://community.splunk.com/t5/Building-for-the-Splunk-Platform/ that mention this technique (both to clean up old junk and to pick up newer jQuery).
|
No that would have been the solution if there were a new add-on builder version that included the updated moment.js or jQuery or whatever. But there isn't yet. In July I rebuilt the add-on from scratch to pass then longstanding cloud vetting issues involving older jQuery versions. It worked then, see below, but AoB hasn't been updated yet. Good news: |
Ah I think I found the origin of the vulnerability. Currently at the top of https://github.com/moment/moment/blob/develop/CHANGELOG.md:
|
Interesting...
That can't be right. |
Fixed! I deleted common.js, the TA keeps working and passes validation. I compared the appserver directory from a fresh TA generated by AoB. And. It didn't contain the common.js file! Apparently I copied the entire appserver directory over when recreating "from scratch" instead of just the appserver/img directory for the icon and screenshot. I'll keep this issue open until the TA is passing the 2nd cloud vetting stage. |
Any update from Splunk vetting? |
Nothing, still pending… |
I'll open a support case to see if that nudges the approval/review process. It's now been more than 30d, which I believe is unusual. |
Ha! It worked! Well done! |
check_for_vulnerable_javascript_library_usage
check_python_sdk_version
The text was updated successfully, but these errors were encountered: