liveBook · Manning

Vulnerability

As explained in Microservices Patterns, Second Edition

A vulnerability is a weakness in software or its dependencies that can be exploited to compromise security or cause harm.

A vulnerability in a third-party library makes upgrading the dependency a security requirement. Keep the technology stack current, especially library and framework versions, to address vulnerabilities. section 5.3.2 section 5.3.3

Choose the upgrade path based on the change required:

  • When no code changes are needed, the security team can upgrade the library, test the change, and deploy the application in less than a day. section 5.3.3
  • When code changes are required, make large upgrades incrementally, one team at a time. section 5.3.3

How Microservices Patterns, Second Edition covers it

How deep it goes
Connects dependency vulnerabilities to upgrade effort and a rapid fix scenario, but does not detail vulnerability analysis or remediation mechanics.
Examples
Describes upgrading a vulnerable third-party library without code changes, then testing and deploying the application in less than a day.
What you can do after
Apply it by upgrading a vulnerable third-party library, then testing and deploying the application in less than a day when no code changes are needed.
How it connects
Links vulnerability fixes to technology-stack upgrades and the testability and deployability quality attributes.

Also explained in

Compare how 18 books explain vulnerability →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.