Auditing Open-Source Components
Preface
Contents
Chapter 1: The Realpolitik of Open-Source Component Security
- The arena: why open-source components specifically
- Axis one: fixes are parameter-level
- Axis two: what vendors choose not to fix is a signal
- Axis three: severity grades an instance, magnitude grades a fleet
- Axis four: attack-surface weight is the distance to the bug
- The six-stage pipeline
- The realpolitik, stated once
Chapter 2: Case Study — The Injection the Maintainers Missed Twice
- Stage 1: The release note as a map of omissions
- Stage 2: Pinning the root cause at two tags
- Stage 3: Closing the chain
- Stage 4: A graded proof
- Stage 5: Drawing the boundary
- Fifteen minutes of verification
- Stage 6: What a real fix looks like
- Twice, and why it matters
Chapter 3: Target Selection — The Scale-and-Surface Framework
- Two axes, one map
- Counting the fleet
- Weighing the surface before reading a line
- Reading the vendor before the code
- Two public profiles, one comparison
- The selection run
- An hour of reconnaissance you can repeat
Chapter 4: Case Study — When the Fix Isn’t a Fix
- Four gates between a fix and a fleet
- Ghostcat: the fix that asked for configuration
- Heartbleed: the fix that could not find its fleet
- The radius rule, stated and used
- Fifteen minutes of verification
Chapter 5: Static Chain Closure — From Entry to Sink
- The direction of the walk
- Enumerating the entries
- Following the data
- The four sink families
- The toolchain, honestly
- Reading a public chain end to end
- Fifteen minutes of verification
Chapter 6: Proof Without a Lab — String-Level Simulation
- Why pure static reports starve
- The three grades
- Building the harness
- The DataEase replay, as method
- Limits, stated plainly
- Fifteen minutes of verification
Chapter 7: Scaling the Harness — Burp Extender Automation
- The automation boundary
- The host and its hooks
- Pattern one: batch fingerprinting
- Pattern two: tag-diff surveillance
- Pattern three: regression re-fire
- The BApp Store: when a tool outlives its finding
- Limits, stated plainly
- Fifteen minutes of verification
Chapter 8: The Disclosure Pipeline — From Finding to Payout
- The channel map
- Matching the finding to the channel
- The six elements of a report that closes
- Windows and tempo
- Getting paid
- Limits, stated plainly
- Fifteen minutes of verification
Chapter 9: The Operating Cadence — Running This as a Practice
- The week as the unit of work
- The four days, one by one
- The workbench
- Energy, honestly
- From the first hole to the tenth
- Limits, stated plainly
- Fifteen minutes of verification