01Description
The application loads client-side JavaScript libraries, such as jQuery, Bootstrap or AngularJS, at versions with publicly known vulnerabilities.
02Impact
Known vulnerabilities in client-side libraries, typically cross-site scripting or prototype pollution, may be exploitable depending on how the application uses them. Unsupported libraries such as AngularJS will not receive fixes.
03Severity
Typically
Low
Typically Low. Usually Low, as many library vulnerabilities are not reachable. Raise it if the vulnerable function is used in a way that can be exploited.
04How to verify
- 1Identify libraries and versions from loaded scripts, for example with Retire.js.
- 2Match versions against published advisories.
- 3Assess whether the vulnerable functionality is used by the application.
Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.
05Remediation
- 1Update libraries to current supported versions.
- 2Remove unused libraries.
- 3Add software composition analysis to the build pipeline to catch vulnerable dependencies.
Draft findings like this from your own evidence
Book a demo