Using Components With Known Vulnerabilities
Usage of third-party software components in the development process may lead to this type of attack. Known components like third-party application frameworks, libraries, technologies that may have exposure to major vulnerabilities.
These kinds of threats are often difficult to exploit and cause serious data breaches.
How Can One Be Exposed To These Threats?
- Not knowing the version of components used directly as well as in nested dependencies, includes both client-side and server-side
- Not scanning for vulnerabilities regularly instead of using security bulletins.
- Failing to upgrade the underlying platform, frameworks, and dependencies in a risk-based fashion
- If the components configuration are unsecured one may be open to these type of threats
- Failing to check the compatibility of updated library patches
Mitigation Against These Threats
- Avoid the usage of unnecessary features, components, files, documentation.
- Revisit the libraries that are previously unmaintained and avoid creating security patches for older versions.
- Prefer secured packages and choose components from official packages over secured links
- Always deploy the security patch, in case of unavailability try using a virtual patch to monitor, detect or protect against the discovered issue
- Organizations must make sure there is an action plan for triaging, monitoring, and applying configurations dynamically.
- Usage of WAF may help to mitigate these types of vulnerabilities.
Try Modshield SB WAF
Modshield SB works based on a set of rulesets, the most common type of ruleset used across any WAF is OWASP Top 10 ModSecurity rulesets. StrrongBox IT’s Modshield SB works on the core ModSecurity rulesets, which can avert threats Using Components With Known Vulnerabilities during the time of the attack.