upgrading jQuery due to CVE exposure #1499
-
I was trying to upgrade jQuery library which is a dependency of the linked target is a html page that contain JS scripts which is leading to the jQuery bundling. As the page does not belong to us, we have no way telling them to upgrade! I tried linking page to JDK 17's api doc just to debug, but it didn't help. any pointers? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
jquery is not a dependency but part of the javadoc included in the bundle.
jquery is provided by the javadoc tool, so if we upgrade the JDK (that includes a fix) it will get a newer jquery version. Beside that, before taking further actions it would be useful to link the CVE and analyze it if it actually apply to our use-case. |
Beta Was this translation helpful? Give feedback.
Is likely irrelevant for javadoc unless we assume you can add custom code to javadoc pages (in wich case an attacker can literally do anything)
We do not use "Drupal, Backdrop CMS, and other products" so also not relevant for javadoc.
If one ist still concerned, it might work to simply replace the jquery version in the product, or even delete it (what might degrade some functions like search).