liveBook · Manning

Side-channel attack

As explained in Secure APIs

A side-channel attack infers information about a system from inadvertently exposed characteristics of its operation rather than from its intended outputs.

A side-channel attack infers internal information from characteristics a system exposes unintentionally, rather than from its intended outputs. section 4.3

For APIs, an attacker can compare request-response latencies for existing and nonexistent resources. Consistent timing differences may reveal resource identifiers and enable enumeration. section 4.3

Timing reveals resource existence

An endpoint may return the same apparent result for two resource requests, yet respond faster for a nonexistent record. Repeated measurements let an attacker distinguish which identifiers exist. section 4.3

Reduce timing-based leakage by:

  • Checking whether the API responds with different latencies for existing and nonexistent resources. section 4.3
  • Putting measures in place to deliver consistent response times across requests when timing differences appear. section 4.3

How Secure APIs covers it

How deep it goes
Defines side channels and explains timing-based resource enumeration, but does not develop attack automation.
Examples
Uses differing API latencies for existing and nonexistent resources as the concrete example.
What you can do after
Diagnose/debug with it by comparing endpoint latencies and applying consistent-response-time measures.
How it connects
Connects side-channel attacks with APIs, timing attacks, request-response latency, and resource enumeration.

Also explained in

Compare how 3 books explain side-channel attack →

Related concepts

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