liveBook · Manning

Vulnerability

As explained in "Looks Good to Me"

A weakness or problem in software that can be exploited to compromise confidentiality, integrity, availability, or control.

A vulnerability is a security weakness in code that can expose personal or sensitive data or compromise a system. During review, look for glaring vulnerabilities that automated checks may miss. section 3.3.2 section 3.3.3

Use vulnerability findings to guide review decisions:

  • Check whether applicable security standards are followed. section 3.3.2
  • Treat vulnerabilities that expose sensitive data or compromise the system as blocking issues. section 3.3.3
  • Reserve blocking decisions for critical security problems; handle minor concerns through constructive feedback or a separate pull request. section 3.3.3

A review decision

A reviewer notices a security weakness that could expose sensitive data. Because it affects system security, the reviewer blocks approval rather than treating it as a minor refactoring suggestion. section 3.3.3

How "Looks Good to Me" covers it

How deep it goes
Identifies glaring vulnerabilities and approval consequences but does not detail exploit analysis or remediation techniques.
Examples
Uses vulnerabilities missed by automation and weaknesses exposing personal or sensitive data as review examples.
What it assumes
Assumes a team-defined review focus and applicable security standards.
What you can do after
Evaluate review findings and block changes that introduce vulnerabilities affecting data or system security.
How it connects
Connects vulnerabilities with security standards, automated checks, sensitive data, and pull-request approval.

Also explained in

Compare how 16 books explain vulnerability →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of "Looks Good to Me". The section links point to the parts of the book it draws on.